Hi Jeff,
Is it possible that theWeblogic server uses a different implementation
of javax.xml.ws.spi.Provider, i.e. is there another
META-INF/services/javax.xml.ws.Provider file on the classpath, before
the one in the cxf-rt-frontend-jaxws jar?
This would not affect the creation of a JAX-WS endpoint as in that case
the implementation class is defined by the BeanDefinitionParser for the
jaxws:endpoint elements in your cxf-servlet.xml file, but it would
impact the creation of a proxy if it's done as outlined below.
Andrea.
Tchang, Jeffrey (Genworth) wrote:
Hi Andrea,
I noticed that you gave the following example to get a reference to the
underlying CXF client object:
You can obtain a reference to the underlying CXF client object using the
ClientProxy helper, for example:
GreeterService gs = new GreeterService();
Greeter greeter = gs.getGreeterPort();
org.apache.cxf.endpoint.Client client =
org.apache.cxf.frontend.ClientProxy.getClient(greeter);
org.apache.cxf.endpoint.Endpoint cxfEndpoint = client.getEndpoint();
cxfEndpoint.getOutInterceptors().add(...);
Regards,
Andrea.
This works fine locally but when I attempt to deploy to BEA Weblogic 10.0 I
am having issues.
java.lang.reflect.InvocationHandler h =
java.lang.reflect.Proxy.getInvocationHandler(membershipInquiryPort);
System.out.println("InvocationHandler Object: " + h);
org.apache.cxf.jaxws.JaxWsClientProxy jaxClient =
(org.apache.cxf.jaxws.JaxWsClientProxy)h;
Locally this prints out:
[EMAIL PROTECTED]
On the WebLogic Server:
InvocationHandler Object: unknown: Stub for http://blah/
Anyone have any ideas why this is?
-Jeff
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
