• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Can a EJB module reference a WEB module?

 
Luciano Queiroz
Ranch Hand
Posts: 172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi folks!

Is it possible for a EJB module to reference a WEB module?
In the same EAR there is a EJB module (.jar) and a web module (.war).
The classes in the EJB module use classes in the WEB module.
But everytime I deploy the EAR and test the EJBs, 9iAS throws a ClassNotFoundException from the EJB.

I already tried to use a MANIFEST file in EJB.jar but I don't know which value I have to insert in the Class-Path attribute to reference classes in the web module.

Any help would be appreciated.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34860
369
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Luciano,
This seems to me to be more of a design question (about ejb modules referencing web modules), so I'm moving it to:
J2EE

Why does your ejb module need to refer to a web module? Does the web module also refer to the ejb module? You want to avoid circular dependencies.

Without knowing more about your situation, it looks like a refactoring is in order. The classes that are used by both the ejb module and web module can be moved to a separate "common" project/jar file. That way the structure is clearer and you don't have the awkward dependency structure.
 
Navin Keswani
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The problem has a very simple solution just make an entry into your manifest file of your jar file using the following syntax

Class-Path: some.jar somexyz.war

the jars or wars have to seperated by spaces.

I hope this solves your problem.

Regards,
Navin Keswani
 
Luciano Queiroz
Ranch Hand
Posts: 172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Very simple, but it didn't solve my problem.
 
Karthik Guru
Ranch Hand
Posts: 1209
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Luciano Queiroz:
Very simple, but it didn't solve my problem.


Did you try Jeanne suggestion of creating a common.jar of all the shared classes and putting it in the lib folder of the ear?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic