I think starting your client from a script where you set exactly the
classpath you need (ignoring the gloabal classpath) is a good idea, rather
than relying on the global classpath. Maybe theres a better way...?
david jencks
On 2001.07.27 02:33:30 -0400 Alice Ad wrote:
> thanks for the reply. y
thanks for the reply. yea, i was putting a lot of
things in my classpath and when i cleaned it up jboss
ran fine. but now (im running client on the same host)
i have to add classpaths for the client to pickup
initial context etc. so this time i again added all
jboss/client/*.jar on my classpath. i
jboss as downloaded should start with empty classpath if you use
run.sh/run.bat., or just run.jar if you want to start it some other way.
Usually putting things in the classpath breaks something else later. The
jmx framework adds everything in jboss's lib/ext to the internal classpath.
Are you do
From my experience, apart from the normal values in the classpath
variable. You need to point the JBoss classpath to the packages where the
JBoss server can find the remote and home interfaces for all classes, as
this is require by your JSP, JavaBeans.
Devraj
At 15:21 26/07/01 -0700, you wro
Hi,
Can anyone please tell me what classpaths to set for
JBoss to start? Every time I do something new and try
to start the server, some class files are not found
and I have to spend quite a time to figure out what
classpath to add.
thanks a lot!
