Hi --
This is a deployment problem -- I'm using Weblogic 4.51 w/ IBM VAJava.
I'm trying to avoid distributing the Bean class within a .jar file
to the clients: it's a general good practice, all they need is the
interfaces, they certainly shouldn't be instantiating the Bean, and the
bytecode for the bean may contain private data which could be misused.
It seems that if I remove the bean class from the ejb-jar and stick it
into the server classpath directly it still fails to deploy. Reading
through the EJB spec this does seem to be proper behavior.
Is the only way to do this to massage the ejb-jar, pull out the
interface .class files and distribute only those to the clients? It's
doable, and certainly even scriptable, but it's still kind of hokey.
Curious what others are doing.
Ranjan
===========================================================================
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".
