Deploying WAR with CXF in Glassfish V3?

I had a similar problem with my glassfish3.1. Below is a stack trace.

I had a similar problem with my glassfish3.1. Below is a stack trace Caused by: com.sun.xml.ws.util. ServiceConfigurationError: com.sun.xml.ws.api.pipe. TransportPipeFactory: Provider com.sun.enterprise.jbi.serviceengine.bridge.transport.

JBITransportPipeFactory is specified in bundle://96.0:0/META-INF/services/com.sun.xml.ws.api.pipe. TransportPipeFactory but not found at com.sun.xml.ws.util.ServiceFinder. Fail(ServiceFinder.

Java:245) at com.sun.xml.ws.util.ServiceFinder. Access$100(ServiceFinder. Java:145) at com.sun.xml.ws.util.

ServiceFinder$LazyIterator. Next(ServiceFinder. Java:380) at com.sun.xml.ws.api.pipe.

TransportTubeFactory. Create(TransportTubeFactory. Java:133) at com.sun.xml.ws.transport.

DeferredTransportPipe.(DeferredTransportPipe. Java:86) at com.sun.xml.ws.api.pipe. ClientTubeAssemblerContext.

CreateTransportTube(ClientTubeAssemblerContext. Java:315) at com.sun.xml.ws.assembler.jaxws. TransportTubeFactory.

CreateTube(TransportTubeFactory. Java:67) at com.sun.xml.ws.assembler.TubeCreator. CreateTube(TubeCreator.

Java:84) at com.sun.xml.ws.assembler. TubelineAssemblerFactoryImpl$MetroTubelineAssembler. CreateClient(TubelineAssemblerFactoryImpl.

Java:130) at com.sun.xml.ws.client.Stub. CreatePipeline(Stub. Java:228) at com.sun.xml.ws.client.Stub.(Stub.

Java:205) at com.sun.xml.ws.client.Stub.(Stub. Java:178) at com.sun.xml.ws.client.sei.SEIStub.(SEIStub. Java:85) at com.sun.xml.ws.client.

WSServiceDelegate. CreateEndpointIFBaseProxy(WSServiceDelegate. Java:608) at com.sun.xml.ws.client.

WSServiceDelegate. GetPort(WSServiceDelegate. Java:348) at com.sun.xml.ws.client.

WSServiceDelegate. GetPort(WSServiceDelegate. Java:330) at com.sun.xml.ws.client.

WSServiceDelegate. GetPort(WSServiceDelegate. Java:312) at com.sun.xml.

Ws1.Service. GetPort(Service. Java:134) at org.glassfish.webservices.monitoring.

WebServiceTesterServlet. InitializePort(WebServiceTesterServlet. Java:563) at org.glassfish.webservices.monitoring.

WebServiceTesterServlet. DoGet(WebServiceTesterServlet. Java:169) at org.glassfish.webservices.monitoring.

WebServiceTesterServlet. Invoke(WebServiceTesterServlet. Java:104) at org.glassfish.webservices.

EjbWebServiceServlet. Service(EjbWebServiceServlet. Java:114) at javax.servlet.http.HttpServlet.

Service(HttpServlet. Java:848) at com.sun.grizzly.http.servlet. ServletAdapter$FilterChainImpl.

DoFilter(ServletAdapter. Java:1002) ... 20 more The problem was traced to the conflicting mappings for "com.sun.xml.ws.api.pipe. TransportPipeFactory" inside two different modules.

Prompt> grep -rl com.sun.xml.ws.api.pipe. TransportPipeFactory /usr/local/glassfish-3.1/glassfish/domains/modules* modules/webservices-osgi. Jar modules/sun-javaee-engine.

Jar prompt> grep -rl com.sun.enterprise.jbi.serviceengine.bridge.transport. JBITransportPipeFactory /usr/local/glassfish-3.1/glassfish/domains/modules/* modules/sun-javaee-engine. Jar Clearly, the required file was sitting in the wrong jar "sun-javaee-engine.

Jar". Above, "sun-javaee-engine. Jar" is loaded by the "Java EE Service Engine Module".

Once I removed the module (using glassfish update tool) everything started working fine. EDIT #1: Here is how to remove the module using the update tool on the Unix command line: sudo . /pkg uninstall sun-javaee-engine.

Sweet, thanks! I struggled with this for far too long. – javamonkey79 Aug 12 at 0:19.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.