Hi Dipti,
yes, JBoss AS 6 comes with JBossWS-CXF which is the Apache CXF based
version of the JBoss webservices integration. So iow you're not supposed
to embed your cxf libraries in your ws deployment archive. Thinks might
probably change a bit here in JBoss 7 to offer some more freedom from
this point of view.
If you still want to provide your own CXF libs and not use the proper
JBoss integration (which I'd frankly suggest you to do), you can
download and install the JBossWS-Native ws stack on top of AS 6 (that is
not based on Apache CXF).
Cheers
Alessio
On 04/12/2011 03:51 AM, Dipti Vaidya wrote:
Update: I know what the issue is though I don't know how to fix it.
I noticed that Jboss 6 comes with cxf libraries in the /commons/lib/
directory and when I spin up my server, it is picking up the extensions.xml
from those libraries.
I tried to do the jboss-classloading.xml file as suggested online but I
still get the same issue:
Here's what my jboss-classloading.xml looks like:
<?xml version="1.0" encoding="UTF-8"?>
Can someone please tell me how to ignore / isolate the cxf libraries that
come with jboss 6 and only use the ones that are in my app?
Thanks,
Dipti
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-problem-on-JBoss-AS-6-tp4296130p4297227.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Alessio Soldano
Web Service Lead, JBoss
