[ 
https://issues.apache.org/jira/browse/AXIS2-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Rheinheimer updated AXIS2-3730:
------------------------------------

    Attachment: patch_candidate01.txt

> sandesha needs to be able to recognize jaxws-originated anon operations
> -----------------------------------------------------------------------
>
>                 Key: AXIS2-3730
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3730
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: jaxws
>            Reporter: Mike Rheinheimer
>         Attachments: patch_candidate01.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.
> http://java.sun.com/j2ee/1.4/docs/api/javax/xml/namespace/QName.html#QName(java.lang.String,%20java.lang.String,%20java.lang.String)
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to