Bug 777717 (SOA-233)

Summary: Changing a WS needs server restart
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Jaroslaw Kijanowski <kijanowski>
Component: JBossWSAssignee: tcunning
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 IR8   
Target Milestone: ---   
Target Release: 4.2 Beta 2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-233
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-21 19:03:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jaroslaw Kijanowski 2007-12-13 15:54:06 UTC
Date of First Response: 2007-12-13 12:26:56
project_key: SOA

I have annotated a POJO to expose a WS ( getCustomer() ). Then I deploy it as an ESB archive and check the WSDL. Next I change the WS, let's say the method name ( to getustomer() ), change jboss-esb.xml to invoke the new command, redeploy the esb archive, check the WSDL, it's fine - new method name is shown. But when I try to use the SOAPClient to consume the WS I get:

javax.management.RuntimeMBeanException
        at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:176)
.
.
.
Caused by: java.lang.UnsupportedOperationException: Operation 'getustomer' not supported by WSDL 'http://localhost:8080/Quickstart_webservice_drools_ext_intg/MyPOJOWS?wsdl'.
        at org.jboss.soa.esb.services.soapui.SoapUIClientService.getOperation(SoapUIClientService.java:148)
        at org.jboss.soa.esb.services.soapui.SoapUIClientService.buildRequest(SoapUIClientService.java:102)


I need to restart the server to be able to consume the changed WS again.

Comment 1 Mark Little 2007-12-13 17:26:56 UTC
Please create a ESB JIRA and link it to this.

Comment 2 Jaroslaw Kijanowski 2007-12-13 17:42:57 UTC
Link: Added: This issue is a dependency of JBESB-1407


Comment 3 tcunning 2007-12-20 21:16:38 UTC
This was fixed in the ESB CP branch, revision 17347.     See attached bug for details.

Comment 4 Jaroslaw Kijanowski 2007-12-21 16:38:04 UTC
This fix has been verified by the RedeployExtJMSTest QS.