Hello!
> * 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. :-)
Sorry, but deploy.jar and stop.jar don't run (anymore?), because they're
missing org.jboss.logging.Logger, which is not in any listed jar-file.
Also if I add jboss.jar to classpath (which of course contains
Logger-class) the same error is thrown (jdk1.3 and jdk1.2.2/os: linux,
CVS from today, 24. august)
Any hints ?
Regards, nils
--
NILS HARTMANN
CURRY. SMILE @ WORK.
Curry Communication GmbH
Behringstr. 28a
22765 Hamburg
TEL +49.40.398 344 08
FAX +49.40.398 344 09
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
