How to pick CXF over Metro on Glassfish

Question

I'm having the following problem (reported there by someone else) when running my enterprise application under Glassfish. Under Jetty it works fine.

javax/xml/ws/spi/Provider mentions creating a META-INF/services/javax.xml.ws.spi.Provider resource, but this is already supplied with CXF and creating an additional resource file does not solve this problem under Glassfish.

Does anyone know how to ensure that CXF is picked up under GlassFish?
(I'm using a Maven Multi-modules project with CXF dependency 2.2.5)

Thanks!
Tim

EDIT #1

Skipping the problem for now and just working with Metro, but I'd really like to know how to use CXF instead if anyone has any pointers.. If nothing works I might have to switch web application container (or look into Metro to fill my requirements)

EDIT #2

Some of the solutions detail the fix for war's by adding <class-loader delegate="false"/> to the sun-web.xml file. However, this does not work for non-war ee apps.

I'm finding the same issue only with an ejb packed in an ear. I opened a bounty as I'd really like to hear some good answers to this without having to duplicate the question, hence my edits. — javamonkey79, Aug 15 '11 at 22:19
+1: This is a bad feature of Glassfish that I am currently facing with `jsf`: Glassfish has built in jsf libraries and these generate conflicts about a code having jsf in it. Really annoying and the solution is worth of the bounty that is open! I absolutely want to know also the solution! — mico, Aug 18 '11 at 17:55
Also [this post](http://www.shareyourwork.org/roller/ralphsjavablog/entry/axiom_jar_conflict_in_glassfish) is telling how things work only in some Glassfish version and in some not. — mico, Aug 18 '11 at 18:15

score 6 · Answer 1 · answered Dec 09 '10 at 15:33

6

Add a sun-web.xml and set delegate=false to the class-loader:

<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE sun-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD 
Application Server 9.0 Servlet 2.5//EN' 
'http://www.sun.com/software/appserver/dtds/sun-web-app_2_5-0.dtd'> 
<sun-web-app> 
    <class-loader delegate="false"/> 
</sun-web-app>

answered Dec 09 '10 at 15:33

Nightwolf

4,495
2
21
29

Adding this file to the war web-inf directory worked for me. Thanks! – sdoca Apr 18 '11 at 16:37
Do you know where to put it in springboot app? I tried `resources` folder but it didn't work. – makozaki Mar 24 '22 at 10:26

score 1 · Answer 2 · edited Jan 18 '10 at 14:33

1

The Metro (Glassfish's JAX-WS implementation) jars are probably being included with Glassfish, can you exclude them from the classpath? Since you're using maven, you should analyze the glassfish dependencies and using an exclusion for the metro jars.

It seems that you need to have the CXF jars on the applications classpath before the Metro jars. You probably can't modify the system classloader/classpath but you can change the Thread.currentThread().getContextClassLoader() such that it loads CXF first. There also might a classpath settings in Glassfish you can modify

Check out the source for javax.xml.ws.spi.FactoryFinder#find() to see how the provider is actually loaded

edited Jan 18 '10 at 14:33

Tim

19,793
8
70
95

answered Jan 14 '10 at 14:12

Kevin

30,111
9
76
83

This could very well be the case, but I'm unsure as to how to remedy this.. It's a compiled .war that I'm uploading to GlassFish, so will Maven excludes still have any effect after compilation? (Ie: will these excludes be passed along to the war and used on the server?) – Tim Jan 14 '10 at 14:25
So its picking up the Metro provider when you're application is deployed in to Glassfish, not during development? – Kevin Jan 14 '10 at 14:30
I misunderstood your situation, sorry. I've updated my posting – Kevin Jan 14 '10 at 15:00
Hmm, the above linked FactoryFinder is helpfull in understanding the problem, but I'm as of yet unable to solve my problem using any of the described methods.. (.Provider & .properties files & system property) – Tim Jan 18 '10 at 14:35

score 0 · Answer 3 · edited Mar 24 '22 at 10:23

The solution I came up with (and am unsatisfied with) is to use JaxWsProxyFactoryBean. There is an example here.

This is the jist of what you have to do:

public static void main(String args[]) throws Exception {

    JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();

    // I didn't need these next 2 calls, but I doubt they hurt
    factory.getInInterceptors().add(new LoggingInInterceptor());
    factory.getOutInterceptors().add(new LoggingOutInterceptor());

    factory.setServiceClass(AuthService.class);
    factory.setAddress("http://localhost:7001/authManager/services/cxfAuth");

    // 'AuthService' is whatever your interface type is
    AuthService client = (AuthService) factory.create();

    Employee employee = client.getEmployee("0223938");
    System.out.println("Server said: " + employee.getLastName() + ", " + employee.getFirstName());
    System.exit(0);

}

Could you copy over the relevant parts of the solution? External links tend to break over time.. — Tim, Aug 17 '11 at 07:27

score 0 · Answer 4 · answered Mar 24 '22 at 13:57

0

For SpringBoot application I needed to add following file:

src/main/resources/META-INF/services/javax.xml.ws.spi.Provider

with content:

org.apache.cxf.jaxws.spi.ProviderImpl

answered Mar 24 '22 at 13:57

makozaki

3,772
4
23
47

How to pick CXF over Metro on Glassfish

4 Answers4

Linked