Hi Peter,
I suppose one could say that web-module classes should not be (and indeed,
are not) visible from EJB's because that violates the layered structure of
the application (the logic/storage oriented EJB's shouldn't need to know
about the presentation layer).
If you have a class that needs to be visible from the EJB's you could put
it in the EJB module. The web module will still be able to see it.
Nick
At 08:42 PM 8/14/01 +0200, you wrote:
>Hello Orion-List-Readers!
>
>I'm working on a web application consisting of an EJB and a web module.
>
>In our application there are certain model beans which are referenced
>from both the EJBs and the (Struts) action-beans which belong to the web
>module.
>
>Without any further measures classes in one module can't use or inherit
>from classes in the other module.
>During development we set a library path in server.xml so that the
>classes could be referenced from both modules.
>Now for deployment I'm looking for a "cleaner" solution.
>Is there a way to place classes or a jar-file in an .ear-archive that
>the classes can be referenced from EJB and web-module without setting a
>path in server.xml??
>
>regards,
>Peter
