[ http://issues.apache.org/jira/browse/AXIS2-891?page=comments#action_12421544 ] Eran Chinthaka commented on AXIS2-891: --------------------------------------
Hi Brian, Cool. Let me give you one simple suggestion and rest I'm fine with it. Rather than putting a method in Options to set this useSOAPAction, shall we just introduce a property. This will enable 1. not to change the current Options api, so that the existing client code will continue to compile/work even after this change. 2. we will not fill Options with hundreds of methods, whenever we wanna add a new option. 3. so far we did these kinds of switches by setting properties. So I'd like to suggest something like, options.setProperty(IS_USE_SOAP_ACTION, Boolean.TRUE) to do the same thing. BTW, I just fixed the SOAPAction bug and will committing soon. > Allow the WS-Addressing action to be set, in the client, without also setting > the SOAP action > --------------------------------------------------------------------------------------------- > > Key: AXIS2-891 > URL: http://issues.apache.org/jira/browse/AXIS2-891 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core > Reporter: Brian DePradine > Attachments: patch.txt > > > Modify the Options class to allow a user to set the WS-Addressing action > without also setting the soap action. This is important as, according to the > WS-Addressing 1.0 SOAP Binding Spec, it will allow the ability to obscure the > action through SOAP-level security mechanisms, without having to resort to > transport level security mechanisms. Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
