axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Rheinheimer (JIRA)" <>
Subject [jira] Resolved: (AXIS2-3730) sandesha needs to be able to recognize jaxws-originated anon operations
Date Thu, 24 Apr 2008 17:03:28 GMT


Mike Rheinheimer resolved AXIS2-3730.

    Resolution: Fixed

resolved:  SVN 651306

> sandesha needs to be able to recognize jaxws-originated anon operations
> -----------------------------------------------------------------------
>                 Key: AXIS2-3730
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: jaxws
>            Reporter: Mike Rheinheimer
>         Attachments: patch_candidate01.txt, patch_candidate02.txt
> From David Parsons:  "in RM I have to assume that an anon operation could be a user
> defined operation.  As an anonOutIn operation is always added it triggers some extra
RM logic which in some cases breaks our .NET interop scenario.  My suggestion was to prefix
the operations with something so that I can check for these and decide whether they are user
defined operations.  At the moment I check for operations prefixed with sandesha for example
as I know these are RM defined operations.  I'm not too bothered what you rename them to as
long as that limits a clash with any potential userdefined operations.  That way I can check
for them in RM."
> So, without spending a huge amount of time thinking about it, I simply added a prefix
to the "static final" QNames defined in org.apache.axis2.client.ServiceClient.  The QName
constructor will accept 'null' for the namespaceURI.
> So, is this an acceptable fix?  All of the tests passed in my environment, but I'm not
convinced this is enough.  See patch_candidate01.txt

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:
For additional commands, e-mail:

View raw message