[prev in list] [next in list] [prev in thread] [next in thread] 

List:       muse-dev
Subject:    [jira] Created: (MUSE-239) response name should come from the wsdl
From:       "Vinh Nguyen (JIRA)" <jira () apache ! org>
Date:       2007-06-27 0:08:25
Message-ID: 16250190.1182902905942.JavaMail.jira () brutus
[Download RAW message or body]

response name should come from the wsdl
---------------------------------------

                 Key: MUSE-239
                 URL: https://issues.apache.org/jira/browse/MUSE-239
             Project: Muse
          Issue Type: Bug
          Components: Core Engine - Routing and Serialization
         Environment: Muse 2.2.0, Eclipse 3.2.1
            Reporter: Vinh Nguyen
            Assignee: Dan Jemiolo


When generating the client proxies, wsdl2java properly reads the response names from \
the wsdl and stores them in the proxy metadata section.  But on the server, Muse \
actually creates the response name based on the request name, and doesn't look at the \
wsdl for the actual response name.

I found this error when not using the "normal" naming convention like \
MyOperationRequest and MyOperationResponse.  Instead, I had it as SomeResponse, so \
the client threw an error because the server was returning a different response name \
than expected.

The bug is in AbstractMessageHandler.createResponseName().  It takes the properties \
from the request QName, and then creates a new one with "Response" appended.

Also, the method's javadoc says that "users can override this method to change the \
response name", but the method itself is private.  So to override, users must \
override the class constructor itself.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]