[ http://issues.apache.org/jira/browse/AXIS-2209?page=comments#action_12329938 ]
Davanum Srinivas commented on AXIS-2209: ---------------------------------------- Adrian, Please go ahead and submit patches for all the issues that you logged. thanks, dims > Axis org.apache.axis.client.Call setter methods do not set corresponding > javax.xml.rpc.* properties > --------------------------------------------------------------------------------------------------- > > Key: AXIS-2209 > URL: http://issues.apache.org/jira/browse/AXIS-2209 > Project: Apache Axis > Type: Bug > Components: Basic Architecture > Versions: 1.2.1 > Reporter: Adrian Price > > The Axis implementations of Call.setUsername(), setPassword(), > setOperationStyle(), setUseSOAPAction(), setSOAPActionURI(), > setEncodingStyle(), setMaintainSession() do not set the corresponding JAX-RPC > Call properties "javax.xml.rpc.security.auth.username", > "javax.xml.rpc.security.auth.password", "javax.xml.rpc.soap.operation.style", > "javax.xml.rpc.soap.http.soapaction.use", > "javax.xml.rpc.soap.http.soapaction.uri", > "javax.xml.rpc.encodingstyle.namespace.uri", > "javax.xml.rpc.session.maintain". This makes it impossible to write a > portable JAX-RPC dynamic invocation client - you're forced to cast to the > Axis implementation classes. Not good. > For example, whilst Call.setProperty() handles property > "javax.xml.rpc.soap.operation.style" by calling setOperationStyle() but the > converse is not true; i.e., Call.setOperationStyle() does not set the > "javax.xml.rpc.soap.operation.style" property. One nasty consequence of this > is that since the WSDL-based Service constructor (the one which takes a URL) > has been used (which configures the Call by calling setters not by setting > JAX-RPC Call properties), getProperty("javax.xml.rpc.soap.operation.style") > returns null instead of either "document" or "rpc". In fact, debugging > reveals that the only two properties were "sendMultiRefs" and "sendXsiTypes" > - none of the standard JAX-RPC Call properties were set. Should be very easy > to rectify by changing each setter method to set any corresponding JAX-RPC > Call property. -- 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
