[esb-issues] [JBoss JIRA] Commented: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

Thu Apr 1 07:22:45 EDT 2010

    [ https://jira.jboss.org/jira/browse/JBESB-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12523381#action_12523381 ] 

Kevin Conner commented on JBESB-3259:
-------------------------------------

The SoapUIClientService currently supports a single service within the WSDL, so the *first* endpoint should be the only one.  We will add support for multiple services but, in the meantime, this should be possible using the *wise* SOAPClient as it allows the service name to be specified.

> Add support for multiple wsdl services to SoapUIClientService
> -------------------------------------------------------------
>
>                 Key: JBESB-3259
>                 URL: https://jira.jboss.org/jira/browse/JBESB-3259
>             Project: JBoss ESB
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: 4.7
>            Reporter: Kurt Stam
>             Fix For: 4.9
>
>
> This issue was discovered when running the "webservice_esb_bpel" quickstart which is part of the RiftSaw codebase. This quickstart is based on the ActiveBPEL quickstart, and it may make sense to move this quickstart from the RiftSaw codebase into the JBossESB codebase.
> In the final step notificationStep the MBeanSoapUIInvoker.getEndpoint(String wsdl, Properties httpClientProps) seems to simply pick the *first* endpoint, which is not the right one..
> For more details please see:
> https://jira.jboss.org/jira/browse/RIFTSAW-192

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