The jboss-deployment-structure.xml (as well as anything around disabling
subsystems, standalone/domain mode, etc. mentioned in another reply to
this thread) is a JBoss AS 7 concept and does not apply to JBoss 5.x series.
You should really consider moving to a recent JBoss version, as your
scenario (basically, downgrading a full JavaEE server to a simple
servlet container) was not supported in 5.
Something you might want to try (but it's really a workaround) is to
manually install the JBossWS-Native stack on top of JBoss AS 5.x, to
avoid clashes on Apache CXF classes.
Cheers
Alessio
On 08/10/13 15:51, diepie wrote:
Hi!
I'am trying to deploy my CXF web application to JBoss 5.1 GA. All features
work fine in Tomcat, but the internal JBoss-WS jars are causing some
unexpected behavior (the same as written here
<http://stackoverflow.com/questions/14454420/stackoverflowerror-coming-when-cxf-security-authentication-webservice-deployed-i>
), therefore I want to turn the Jboss webservice subsystem down as it is
written here.
<http://cxf.apache.org/docs/application-server-specific-configuration-guide.html>
. The problem is that placing jboss-deployment-structure.xml in the WEB-INF
does not have any effect even after restarting the server, so I assume it is
not supported in version 5.1. Removing jbossws.deployer from /deployers and
jbossws.sar from /deploy (as written here
<https://community.jboss.org/wiki/JBoss5xTuningSlimming> ) is not a valid
option because there are many applications which may be affected by it.
So my question is how to disable the internal JBoss WS module?
Many thanks,
Peter
--
View this message in context:
http://cxf.547215.n5.nabble.com/Turn-off-JBoss-WS-in-JBoss-5-1-tp5734813.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Alessio Soldano
Web Service Lead, JBoss
