Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of liucong07@gmail.com designates
 209.85.200.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type;
        b=RXVBSKcEpR+jbKmbDZ8EQv+yUsblc996fl+mZ4c2T4roEDwBeHhFUw8ERitiewTEiT
         YFwdVBXNQM1OQtM6vbum5X9p7LPjpo273yZTmFLSBwAJ2qrm9YMZP4CNbFIa/RPnBFGP
         5EW9kaLv8mZA+SqC9srAIwLIXtu3v01LbYpxc=
Message-ID: <4A520B24.2030107@gmail.com>
Date: Mon, 06 Jul 2009 22:33:08 +0800
From: liucong <liucong07@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: dev@cxf.apache.org
CC: Daniel Kulp <dkulp@apache.org>
Subject: Re: An Exception occurs when use wsdl extension in the port
References: <4A4F424C.8060903@gmail.com> <200907061026.29817.dkulp@apache.org>
In-Reply-To: <200907061026.29817.dkulp@apache.org>
Content-Type: multipart/alternative;
 boundary="------------020900080501050709010604"

--------------020900080501050709010604
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit

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 (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 would be "soap" and thus would match the 
> "soap" transport.
>
> In the second, it would be "soapjms" and thus probably matches the JMS 
> transport and not the soap transport.   The jms transport probably doesn't 
> look for "soap:address".
>
> Not sure on the best course of action to solve this.   :-(     Possibly the 
> soap binding could reset the address on the transport or something.   Would be 
> good to check if this is the case before diving in too deep.  
>
> Dan
>
>
>
>
>
> On Sat July 4 2009 7:51:40 am 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 looks like this[1] :
>> <wsdl:definitions>
>> <wsdl:service name="JMSGreeterService">
>> <wsdl:port binding="tns:JMSGreeterPortBinding" name="GreeterPort">
>> <soap:address
>> location="jms:jndi:dynamicQueues/test.cxf.jmstransport.queue?jndiInitialCon
>> textFactory=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;jndiC
>> onnectionFactoryName=ConnectionFactory&amp;jndiURL=tcp://localhost:61616&amp
>> ;targetService=greeterService" />
>> <soapjms:timeToLive>1000</soapjms:timeToLive>
>> </wsdl:port>
>> </wsdl:service>
>> </wsdl:definitions>
>>
>> This service works well.
>>
>> But if the wsdl file looks like this[2] :
>> <wsdl:definitions>
>> <wsdl:service name="JMSGreeterService">
>> <wsdl:port binding="tns:JMSGreeterPortBinding" name="GreeterPort">
>> <soapjms:timeToLive>1000</soapjms:timeToLive>
>> <soap:address
>> location="jms:jndi:dynamicQueues/test.cxf.jmstransport.queue?jndiInitialCon
>> textFactory=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;jndiC
>> onnectionFactoryName=ConnectionFactory&amp;jndiURL=tcp://localhost:61616&amp
>> ;targetService=greeterService" />
>> </wsdl:port>
>> </wsdl:service>
>> </wsdl:definitions>
>>
>> The service is created correctly, but there is an error happen when I
>> invoke this service.
>> By debugging, I find that JMSTransportFactory.getConduit(EndpointInfo
>> endpointInfo, EndpointReferenceType target)'s target parameter is null.
>> It should be
>> "jms:jndi:dynamicQueues/test.cxf.jmstransport.queue?jndiInitialContextFacto
>> ry=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;jndiConnection
>> FactoryName=ConnectionFactory&amp;jndiURL=tcp://localhost:61616&amp;targetSe
>> rvice=greeterService".
>>
>> I think there are someting wrong with port parsing in wsdl.
>> Any ideas?
>>
>> best regards
>> liu
>>     
>
>   


--------------020900080501050709010604--