Hi all !
I am building a "proof of concept" for an application we will convert here
to EJBs. Anyways, in the proof of concept, I have a servlet which calls a
session bean which in turn calls an Entity bean to update the database.
The problem I have seems to be with the classpath. The beans are deployed
properly, and they are working with my test client (stand alone app). When I
wish to access the session bean from the servlet, it won't work unless my
client jar (containing the beans) is specifically inserted in the classpath
of the AppServer. Something like ias -classpath c:\myjars\myclientjar.jar
OK, fair enough. Now, what I was wondering is if there was another way to
insert this bean in the classpath in another way, or if I could use a wild
card for my client jars.
I find it quite annoying to specify all my jar files in the classpath
instead of just putting them all in the same directory and using something
like ias -classpath c:\myjars\*.jar .
I admit that I've never seen this anywhere but in AppServer, they do use it
for their internal jars...
Any hint on this quite unclear question ? :)
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
