Have you started the server first. I found that there are differences
between the servers. There is defintely a difference between TomCat and
JRun. (TomCat needs a restart and JRUN not). I see you want to deploy a WAR.
So its a web application. Do you use the TOMCAT or "JBOSS" web container. If
its the TOMCAT version, there is a specific setting.
Leo
> Have you started the server first. I found that there are differences
> between the servers. There is defintely a difference between TomCat and
> JRun. (TomCat needs a restart and JRUN not). I see you want to deploy a WAR.
> So its a web application. Do you use the TOMCAT or "JBOSS" web container. If
> its the TOMCAT version, there is a specific setting.
I am using JBoss. I think by default it uses
an embeded Tomcat as its Servlet Engine.
The web archive "jmx-console.war" is not mine.
It is just the main tool for administering JBoss.
I only tried to start the server within Lomboz.
Nothing more! Perhaps the problem has to do
with the JBoss version. I am using JBoss 3.2.2,
but Lomboz' config file was for 3.2.1. Trying
everything, now I added some libs to the
"Classpath" for JBoss in Lomboz config "Server
Definitions":
.../lib/jdom.jar
.../lib/xercesImpl.jar
.../lib/gnu.regexp.jar
.../lib/xmp-apis.jar
The result: Now I can start JBoss within Lomboz :)
But calling my web results in an
"Error running javac.exe compiler"
Adding the variable "JAVA_HOME" did not help :(
thanx!
Marcus
Marcus Beyer - 11 Nov 2003 13:25 GMT
> The result: Now I can start JBoss within Lomboz :)
> But calling my web results in an
> "Error running javac.exe compiler"
> Adding the variable "JAVA_HOME" did not help :(
Now I found out, that it works, when I put the bin dir
of javac.exe to the Windows system PATH before running
Eclipse. I don't like that. Isn't there another way?
Marcus
Ville Oikarinen - 12 Nov 2003 08:51 GMT
I must admit that I didn't read the problem description very carefully.
Anyway, ClassDefNotFoundException's are sometimes caused by classloader
problems. Note that JBoss uses a different classloader for its own classes and
for each application so that they are protected from each other.
So if you deploy some jars in a wrong directory, some classes cannot see each
other when they should - and vice versa.
Ville Oikarinen