Uhh ... isn't this unnecessarily vendor-specific? I've had utility classes
used by both web and ejb layers and I just stick them with the EJB JAR file
and things seem to work out fine.
At 06:20 PM 11/15/2000 +0100, you wrote:
><snip/>
>
>
>>At any rate..my main question here is, the EJB class in the jar file is
>>referencing the core class. I don't have the core package in the jar file. I
>>thought if I deployed the jar file into the same web-app as the other
>>classes were in, it would have access to these classes. I compile classes to
>>WEB-INF/classes. Is this not the case? Is there some trickery to getting EJB
>>classes to see the WEB-INF/classes?
>
>no, it's impossible and not meant to be that way.
>
>two possible cases:
>
>- your class is not application specific but a general utility in which
>case you could put it in a library that is specified in the library path
>of global-application and therefore visible for all web an ejb modules in
>all application or you have to explicitly put it where the ejb code gets it
>- it is application specific and used by both web an ejb then you have to
>put it in a separate jar which you reference in orion-application.xml (or
>the dir it's located in, look at the library element) and it will be
>visible to both ejb and web modules.
>
>HTH
>
>robert
>
>>Thanks for any help.
>
>(-) Robert Krüger
>(-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH
>(-) Brüder-Knauß-Str. 79 - 64285 Darmstadt,
>(-) Tel: 06151 665401, Fax: 06151 665373
>(-) [EMAIL PROTECTED], www.signal7.de
