[
http://jira.codehaus.org/browse/XFIRE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96033
]
Eric Le Bail commented on XFIRE-971:
------------------------------------
Hi,
I have the same problem on Version 1.2.6.
The provided patch also work on 1.2.6.
But on my service the SOAP request looks like
<%methodName%in0>value<\%methodName%in0>.
As a consequence I had to add a testing part that compare the MessagePart to
the operation name ignoring the last 3 characters.
As I don't know How to make a "Patch" file I Attach the modified version of the
"AbstractBinding" class.
Regards
Eric
> Wrong service method call
> -------------------------
>
> Key: XFIRE-971
> URL: http://jira.codehaus.org/browse/XFIRE-971
> Project: XFire
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.5
> Reporter: Marc Giger
> Assignee: Dan Diephouse
> Attachments: xfire-1.2.5-operation-selection.patch
>
>
> If I haven't overseen something there is a bug in the AbstractBinding class
> under the following condition:
> - Jaxb / XmlBean (other?) binding
> - The service class implements two service methods which have the same method
> parameters
> The code in the AbstractBinding class first iterates over the webservice
> definitions and looks for a matching operation.
> If a matching operation was found it iterates over the message parts and
> searches for equality.
> The iteration over the message part doesn't take into account the operation
> and returns the first matching message-part.
> Attached is a q&d patch which shows you the problematic code and solves my
> problem:-)
> Thanks
> Marc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
