Hello,
We used both 3.2.1 and 3.2.2RC4 and we got the same problem. We have an ear
containing EJBs, WAR, and a WSR defining our web service.
Attached the web-service.xml we use
If we deploy the ear, eveything went fine, jboss-net found the web service
and deploys it. We can access it throug our
Hi,
this seems to be a similar problem. But we don't get any exception (On RC4), the
ws is just not present after redeploy. I use version numbers in JNDI-Paths, so I
can have two versions of the same ear and ejbs on one JBoss - this is useful if
a clustered frontend uses JBoss. And both
Regarding your problem, put axis package in debug mode, it might help
Regards,
Stephane
-Original Message-
From: Bernd Koecke [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 9:27 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JBossNET hot deployment problem
We used to have the same problem with standard deployments running
on java 1.4
The problem boiled down to caching of proxy classes
somewhere in the RMIClassLoader or Class.forName()
that breaks hot deployment.
This was usually seen when people included a jndi.properties in their
deployments,
-
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 11:29 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JBossNET hot deployment
problem(ClassCastException)
We used to have the same problem with standard deployments running
on java 1.4
The problem boiled down
-
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 11:29 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JBossNET hot deployment
problem(ClassCastException)
We used to have the same problem with standard deployments running
on java 1.4
The problem
