Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 /*
Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes;
mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in;
mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan;
font-size:11.0pt; font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;} We want to run a JAX-WS web service client
based on CXF, inside Glassfish 3.1.1. The application is packaged in an EAR.
The CXF libraries are packaged in the lib directory at the root of the EAR
(standard Java EE 5/6 lib packaging). When we call the WS client, the JAX-WS
implementation that is systematically picked up is Metro, whereas we want to
use the CXF implementation.
It would seem that the ContextClassloader is picking up the Metro libraries
from the server instead of the CXF libs in the EAR. We have tried to include
a javax.xml.ws.spi.Provider file under META-INF/services in the EAR, but that
didn’t solve the problem.
Any ideas ?
--
[Message sent by forum member 'sonicfab']
View Post: http://forums.java.net/node/881765