Hey
Since it is a pain to figure out which classes are required for jBoss
clients, I have changed the build so that it now creates a /client
directory which contains libraries intended for client side use. It also
contains a few server commands that can be used to access the server
remotely.
Here are the files:
* jndi.jar - required for JNDI usage unless you're on JDK1.3 (which has
jndi.jar bundled)
* jnp-client.jar - this is the client side of the jBoss JNDI
implementation. This is always required! (Powerusers may use dynamic
classloading to load this as well however. Use the Reference mechanism.
Figure it out)
* jboss-client.jar - this is required for clients that do not want to
use RMI's dynamic classloading. It is used to talk to the EJB container
implementation. If it is not in the clients classpath, then dynamic
classloading will be attempted. Normal rules for DCL applies.
* deploy.jar - server command to deploy beans. Takes one parameter: the
URL to the beans to deploy (may be directory or jar). If it's a file
URL, then it needs to be relative to the servers file system
* stop.jar - used to stop the server nicely. This will cause the method
"stop()" of all MBeans in the server to be called. So, if you add your
own MBean and it has a stop() method, then it will be included in this
stop procedure.
That's all for now. To recap: put jndi.jar, jnp-client.jar and
jboss-client.jar in your classpath to be sure that it works. Powerusers
will not need anything in classpath, but may instead rely on dynamic
classloading for every class (including JNDI implementation through the
Reference mechanism).
Hope this makes things a tad easier. :-)
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
