Hi,
wrt support issues, etc. you should really get in touch with Red Hat
support to clarify what you can do and what you can't. The JAX-RS impl
of Apache CXF is not "supported" anyway in JBoss EAP afaik, as a matter
of fact those jars not even included in it.
From a technical point of view, I confirm what I suspected on yesterday
but could not verify as I didn't have EAP 6.0.1 locally: the module
structure is slightly different among JBoss AS 7.1.1.Final and JBoss EAP
6.0.1, in particular the 'org.apache.cxf' module has been split into
'org.apache.cxf' (containing the cxf-api jar only) and
'org.apache.cxf.impl' (with the rest of the libs, *except* for jaxrs
ones). So you need to fix your jboss-deployment-structure.xml accordingly.
Alessio
On 19/12/13 19:11, mayankeagle wrote:
Sure, that's fine. I can wait till tomorrow. I don't have an account on JBoss
forums but will create and post it there tomorrow as well if its not
resolved there.
I need to use the default version of CXF which ships with JBoss EAP because
we are having an organizational direction to go ahead with JBoss EAP so that
we can buy support (as opposed to GA, which is community edition and we
can't buy support for it). As per JBoss support, we need to use the default
modules which ship with it to be able to claim support. If we change the JAR
files (e.g., if I change CXF to 2.7.5 instead of the default 2.6.8), then
they won't be able to support it.
I have checked this version of JBoss has the CXF impl module as well. As per
Sergey, it should have the schema in the JAR. The Spring module I have
created is version 3.2.3.
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-2-6-8-issue-with-JBoss-6-0-1-EAP-tp5737992p5738088.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Alessio Soldano
Web Service Lead, JBoss
