0

I am trying to create a simple WSDL based webservice to be deployed on Wildfly using Apache CXF. I tried the standard web.xml, cxf-servlet.xml configurations with the wsdl file but the server gave me the following error

Apache CXF library (cxf-api-2.7.3.jar) detected in ws endpoint deployment; either provide a proper deployment replacing embedded libraries with container module dependencies or disable the webservices subsystem for the current deployment adding a proper jboss-deployment-structure.xml

I am using Maven for my build and deploy process. On reading further I realize that Wildfly uses the JBossWS stack and Spring based CXF configuration is discouraged. Also should I be using wsdl2java or wsprovide/wsconsume ? Could anyone please point guide me on how to setup a simple project to create a WSDL first webservice and deploy on Wildfly or point me to a working example.

Appreciate the help, thanks.

Aleksandr M
  • 24,264
  • 12
  • 69
  • 143
Nova Guy
  • 505
  • 2
  • 9
  • 16
  • wildfly uses cxf for webservices. Dont bundle it with your deployment. Since you are using maven, set scope to provided – maress Oct 02 '14 at 14:23
  • I tried that and it now gives the following error: java.lang.ClassNotFoundException: org.apache.cxf.transport.servlet.CXFServlet from [Module "deployment.SimpleJaxWSExample.war:main" from Service Module Loader] – Nova Guy Oct 02 '14 at 15:18
  • What IDE are you using? I am doing this on wildfly with Netbeans quite easily. – Namphibian Oct 02 '14 at 22:40

3 Answers3

1

The reason for the message above is exactly that the webservices subsystem of WildFly spotted Apache CXF libraries in the deployment. That's not how a JavaEE application making use of webservices is expected to be provided and deployed on a JavaEE container like WildFly, basically because the container is responsible for supplying the WS engine functionalities. In particular, when it comes to WildFly, Apache CXF is internally used hence by adding some cxf libs in his deployment, the user can possibly end up into complex classloading issues that he might not be able to easily solve. Anyway, the message says what has to be done: (JBoss) modules dependencies has to be defined in the deployment. That can be easily done in the deployment MANIFEST.MF; some doc on this at https://docs.jboss.org/author/display/JBWS/JBoss+Modules (but you can google for JBoss Modules and find many info).

Generally speaking, I really suggest to read the doc at https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheCXFintegration-BuildingWSapplicationstheJBossway which explains the JBossWS integration with Apache CXF a bit more in details and gives direction on proper packaging apps.

Alessio Soldano
  • 671
  • 3
  • 3
1

Add all the dependancies with provided scope, as wildfly has its own cxf jars. wildfly does not required cxf jars to execute the ws. only you required cxf jars for IDE to compile the project.

<dependency>
    <groupId>org.apache.cxf</groupId>
    <artifactId>cxf-rt-frontend-jaxws</artifactId>
    <version>${cxf.version}</version>
    <scope>provided</scope>
</dependency>
<dependency>
    <groupId>org.apache.cxf</groupId>
    <artifactId>cxf-rt-transports-http</artifactId>
    <version>${cxf.version}</version>
    <scope>provided</scope>
</dependency>
    <!-- Jetty is needed if you're are not using the CXFServlet -->
<dependency>
    <groupId>org.apache.cxf</groupId>
    <artifactId>cxf-rt-transports-http-jetty</artifactId>
    <version>${cxf.version}</version>
    <scope>provided</scope>
</dependency>

you can find the answer here

Community
  • 1
  • 1
Nirmal Dhara
  • 2,121
  • 18
  • 27
0

Additional suggestion: read http://jbossws.blogspot.it/2014/09/how-to-kick-start-ws-project-in-few.html and try the described maven archetype to build a properly setup & working WS client in few seconds.

Should you be interested, I've also written a book which covers this topic too, see http://jbossws.blogspot.it/2014/09/a-book-on-jax-ws-in-wildfly-and-more.html

Alessio Soldano
  • 671
  • 3
  • 3