[jira] Resolved: (SM-359) Missing destinationEndpoint and destinationOperation extensibility elements for wsdl support in servicemix-jms component.

["Guillaume Nodet (JIRA)" <ji...@activemq.org>]

     [ http://jira.activemq.org/jira//browse/SM-359?page=all ]
     
Guillaume Nodet resolved SM-359:
--------------------------------

      Assign To: Guillaume Nodet
     Resolution: Fixed
    Fix Version: 3.0-M1

The destinationEndpoint is specified by the endpoint name of the consumer.
The defaultOperation can now be specified on the jbi extensibility element in the wsdl port.

Author: gnodet
Date: Wed Mar 22 02:58:01 2006
New Revision: 387827
URL: http://svn.apache.org/viewcvs?rev=387827&view=rev



> Missing destinationEndpoint and destinationOperation extensibility elements for wsdl support in servicemix-jms component.
> -------------------------------------------------------------------------------------------------------------------------
>
>          Key: SM-359
>          URL: http://jira.activemq.org/jira//browse/SM-359
>      Project: ServiceMix
>         Type: Bug

>   Components: servicemix-jms
>     Versions: incubation
>  Environment: Linux Debian, svn head of the 20 th of March 2006
>     Reporter: Charles Souillard
>     Assignee: Guillaume Nodet
>      Fix For: 3.0-M1

>
> Original Estimate: 4 hours
>         Remaining: 4 hours
>
> When deploying a new SU in sm-jms using a servicemix.xml file, I can specify the destinationService, the destinationEndPoint and the destinationOperation (see bpel example with pxe).
> I have not found the way to define the destinationEndPoint and the destinationOperation with the wsdl method.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira