[JBoss JIRA] Created: (JBESB-3259) SOAP Invocation selects the first (wrong) endpoint

[JBoss JIRA] Created: (JBESB-3320)...

[JBoss JIRA] Created: (JBESB-3084)...

Kurt Stam (JIRA)

Wednesday, 31 March 2010 Wed, 31 Mar '10

5:05 p.m.

SOAP Invocation selects the first (wrong) endpoint -------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/jira/browse/JBESB-3259 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kurt Stam 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

Show replies by date

Kevin Conner (JIRA)

Thursday, 1 April Thu, 1 Apr

6:05 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-3259) SOAP Invocation selects the first (wrong) endpoint

...

SOAP Invocation selects the first (wrong) endpoint -------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/jira/browse/JBESB-3259 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kurt Stam 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

Kevin Conner (JIRA)

6:10 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

[ https://jira.jboss.org/jira/browse/JBESB-3259?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-3259: -------------------------------- Summary: Add support for multiple wsdl services to SoapUIClientService (was: SOAP Invocation selects the first (wrong) endpoint) Issue Type: Feature Request (was: Bug)

...

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 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

Kevin Conner (JIRA)

6:22 a.m.

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

[ https://jira.jboss.org/jira/browse/JBESB-3259?page=com.atlassian.jira.plu... ] 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

Kevin Conner (JIRA)

6:22 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

[ https://jira.jboss.org/jira/browse/JBESB-3259?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-3259: -------------------------------- Fix Version/s: 4.9

...

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

Tom Fennelly (JIRA)

Tuesday, 25 May Tue, 25 May

2:09 a.m.

New subject: [JBoss JIRA] Assigned: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

[ https://jira.jboss.org/browse/JBESB-3259?page=com.atlassian.jira.plugin.s... ] Tom Fennelly reassigned JBESB-3259: ----------------------------------- Assignee: Tom Fennelly

...

Add support for multiple wsdl services to SoapUIClientService ------------------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/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 Assignee: Tom Fennelly 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Tom Fennelly (JIRA)

Wednesday, 26 May Wed, 26 May

9:15 a.m.

New subject: [JBoss JIRA] Resolved: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

[ https://jira.jboss.org/browse/JBESB-3259?page=com.atlassian.jira.plugin.s... ] Tom Fennelly resolved JBESB-3259. --------------------------------- Resolution: Done trunk: 33091

...

Add support for multiple wsdl services to SoapUIClientService ------------------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/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 Assignee: Tom Fennelly 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

Kevin Conner (JIRA)

12:41 p.m.

New subject: [JBoss JIRA] Reopened: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

[ https://jira.jboss.org/browse/JBESB-3259?page=com.atlassian.jira.plugin.s... ] Kevin Conner reopened JBESB-3259: --------------------------------- Tom, looks like this is broken under jdk5.

...

Add support for multiple wsdl services to SoapUIClientService ------------------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/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 Assignee: Tom Fennelly 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

Tom Fennelly (JIRA)

2:07 p.m.

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

[ https://jira.jboss.org/browse/JBESB-3259?page=com.atlassian.jira.plugin.s... ] Tom Fennelly commented on JBESB-3259: ------------------------------------- Argggg.... OK... will need to get 1.5 working on my machine again. Sorry about that guys :(

...

Add support for multiple wsdl services to SoapUIClientService ------------------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/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 Assignee: Tom Fennelly 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

Tom Fennelly (JIRA)

3:31 p.m.

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

[ https://jira.jboss.org/browse/JBESB-3259?page=com.atlassian.jira.plugin.s... ] Tom Fennelly commented on JBESB-3259: ------------------------------------- Rolled back 33091 in 33101.

...

Add support for multiple wsdl services to SoapUIClientService ------------------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/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 Assignee: Tom Fennelly 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

Tom Fennelly (JIRA)

Monday, 31 May Mon, 31 May

9:11 a.m.

New subject: [JBoss JIRA] Resolved: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

[ https://jira.jboss.org/browse/JBESB-3259?page=com.atlassian.jira.plugin.s... ] Tom Fennelly resolved JBESB-3259. --------------------------------- Resolution: Done trunk: 33212

...

Add support for multiple wsdl services to SoapUIClientService ------------------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/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 Assignee: Tom Fennelly 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

Tom Fennelly (JIRA)

Wednesday, 2 June Wed, 2 Jun

8:43 a.m.

New subject: [JBoss JIRA] Reopened: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

[ https://jira.jboss.org/browse/JBESB-3259?page=com.atlassian.jira.plugin.s... ] Tom Fennelly reopened JBESB-3259: --------------------------------- Reopening again.... Magesh spotted something that I missed

...

Add support for multiple wsdl services to SoapUIClientService ------------------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/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 Assignee: Tom Fennelly 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

Tom Fennelly (JIRA)

Saturday, 5 June Sat, 5 Jun

2:46 a.m.

New subject: [JBoss JIRA] Resolved: (JBESB-3259) Add support for multiple wsdl services to SoapUIClientService

[ https://jira.jboss.org/browse/JBESB-3259?page=com.atlassian.jira.plugin.s... ] Tom Fennelly resolved JBESB-3259. --------------------------------- Resolution: Done trunk: 33363 added serviceName to getContentType and getEndpoint methods.

...

Add support for multiple wsdl services to SoapUIClientService ------------------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/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 Assignee: Tom Fennelly 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

5228

days inactive

5294

days old

esb-issues@lists.jboss.org

Manage subscription

12 comments

3 participants

tags (0)

participants (3)

Kevin Conner (JIRA)
Kurt Stam (JIRA)
Tom Fennelly (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

[JBoss JIRA] Created: (JBESB-3259) SOAP Invocation selects the first (wrong) endpoint