You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Adrian Price (JIRA)" <ax...@ws.apache.org> on 2005/09/03 19:56:30 UTC
[jira] Created: (AXIS-2209) Axis org.apache.axis.client.Call setter methods do not set corresponding javax.xml.rpc.* properties
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
[jira] Commented: (AXIS-2209) Axis org.apache.axis.client.Call setter methods do not set corresponding javax.xml.rpc.* properties
Posted by "Adrian Price (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2209?page=comments#action_12323122 ]
Adrian Price commented on AXIS-2209:
------------------------------------
Guillaume: My point was that this problem makes it impossible to write a pure JAX-RPC client, precisely because Axis doesn't set the standard JAX-RPC Call properties when it constructs a Call from WSDL. I tried, and it didn't work!
Tom: I'd be happy to help out with a patch for this and the various other Axis 1.2.1 issues I've logged recently. However, none of the issues are blockers for me and I'm on a tight schedule to get Release 1.0 of my Open Business Engine out of the door, because it's heavily referenced from a new book that's coming out this month (Sept. '05).
> 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
[jira] Commented: (AXIS-2209) Axis org.apache.axis.client.Call setter methods do not set corresponding javax.xml.rpc.* properties
Posted by "Adrian Price (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2209?page=comments#action_12323121 ]
Adrian Price commented on AXIS-2209:
------------------------------------
Guillaume: My point was that this problem makes it impossible to write a pure JAX-RPC client, precisely because Axis doesn't set the standard JAX-RPC Call properties when it constructs a Call from WSDL. I tried, and it didn't work!
Tom: I'd be happy to help out with a patch for this and the various other Axis 1.2.1 issues I've logged recently. However, none of the issues are blockers for me and I'm on a tight schedule to get Release 1.0 of my Open Business Engine out of the door, because it's heavily referenced from a new book that's coming out this month (Sept. '05).
> 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
[jira] Commented: (AXIS-2209) Axis org.apache.axis.client.Call setter methods do not set corresponding javax.xml.rpc.* properties
Posted by "Guillaume Sauthier (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2209?page=comments#action_12322634 ]
Guillaume Sauthier commented on AXIS-2209:
------------------------------------------
If you want to create a portable client, you shouldn't use axis Client implementation !
You should only use Call.setProperty("javax.xml.rpc....").
> 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
[jira] Commented: (AXIS-2209) Axis org.apache.axis.client.Call setter methods do not set corresponding javax.xml.rpc.* properties
Posted by "Tom Jordahl (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2209?page=comments#action_12322769 ]
Tom Jordahl commented on AXIS-2209:
-----------------------------------
Still it would be good to make sure that the JAX-RPC standard properties are set when the Axis convenience methods are called.
Adrian, would you be willing to help us out with a patch?
> 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
[jira] Commented: (AXIS-2209) Axis org.apache.axis.client.Call setter methods do not set corresponding javax.xml.rpc.* properties
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ 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