Re: An Exception occurs when use wsdl extension in the port

Hi Dan, Thank you for your good advice. I think keeping the "soap" stuff in the soap binding is a very good idea. https://issues.apache.org/jira/browse/CXF-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727756#action_12727756

Re: An Exception occurs when use wsdl extension in the port

Thank you, Dan. I just found the problem as you said. I can make the JMSTransportFactory implement WSDLEndpointFactory interface. And then the SOAPAddress can be used to create createEndpointInfo. Then the problem will be solved. I'm trying to do this. liu Daniel Kulp wrote: > A test case (attac

Re: An Exception occurs when use wsdl extension in the port

A test case (attached to a JIRA) would be good if you cannot figure this out. However, here is a pointer: When CXF looks in the WSDL to determine the transport factory, it looks at the FIRST extensor on the port that has a namespace that matches a transport factory. In your first example, it w

Re: An Exception occurs when use wsdl extension in the port

Hi, Can you submit a test case for it ? BTW, is there anything wrong with creating the server from this WSDL ? Willem liucong wrote: > Hi all, > When I implement the WSDL usage for SOAP/JMS, I encountered an exception. > I create an service and invoke it using wsdl-first. > > If the wsdl file l

An Exception occurs when use wsdl extension in the port

Hi all, When I implement the WSDL usage for SOAP/JMS, I encountered an exception. I create an service and invoke it using wsdl-first. If the wsdl file looks like this[1] : 1000 This service works well. But if the wsdl file looks like this[2] : 1000 The service is created correctly