Actually, this is a wellknown bug in the Axis framework: https://issues.apache.org/jira/browse/AXIS2-4900
The question that comes to mind is this: Is it ok that JBoss has chosen another URL-format than the standard java-way (vfszip: instead of jar:file:)?
Shouldn't the virtual file system be transparent to the rest of the world?
Apart from waiting for a fix from Axis, what would your suggestion be as to how I can deploy Axis2 modules in JBoss 5?
Hello. I'm completely newbie to jboss. I deploy axis2.war in jboss.5.1.0 and jboss.6.0.0.Final. Everything looks fine because i can see http://localhost:8080/axis2 . Now. To obtain an axis2.war working (when I say working I simply mean that I can reach http://localhost:8080/axis2) i follow these steps (thanks to http://technoracle.blogspot.com/2009/11/how-to-deploy-axis2war-to-jboss-5.html):
- unpack the .war,
- remove lib/xercesImpl-2.8.1.jar (this is enought to get an axis2.war working on jboss.5.1.0),
- remove lib/jaxb-xjc-2.1.7.jar (I did it to get axis2.war working on jboss.6.0.0.Final),
-rebuild the .war (jar -cvf axis2.war *).
Here come the question: why is this working? Why, now that I removed those files, axis2 is running? Thanks in advance.
|Retrieving data ...|