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 "Lin Sun (JIRA)" <ji...@apache.org> on 2007/06/08 05:42:25 UTC
[jira] Created: (AXIS2-2784) When exception arises from
createMessageFromValue, create Protocol specific exception instead of the
generic WebserviceException
When exception arises from createMessageFromValue, create Protocol specific exception instead of the generic WebserviceException
--------------------------------------------------------------------------------------------------------------------------------
Key: AXIS2-2784
URL: https://issues.apache.org/jira/browse/AXIS2-2784
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Affects Versions: 1.3
Environment: win XP + SUn JDK 1.5
Reporter: Lin Sun
Fix For: 1.3
Attachments: Axis2-2784.patch
During dispatch.invoke, we create ProtocolException via createSystemException if the response has fault. However, we didn't create ProtocolException if there is any exception when executing createMessageFromValue. Protocol specific exception is required when throwing an exception as a result of the protocol level fault.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2784) When exception arises from
createMessageFromValue, create Protocol specific exception instead of the
generic WebserviceException
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-2784.
-----------------------------------
Resolution: Fixed
Committed revision 599492.
> When exception arises from createMessageFromValue, create Protocol specific exception instead of the generic WebserviceException
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2784
> URL: https://issues.apache.org/jira/browse/AXIS2-2784
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.3
> Environment: win XP + SUn JDK 1.5
> Reporter: Lin Sun
> Assignee: Rich Scheuerle
> Attachments: Axis2-2784.patch
>
>
> During dispatch.invoke, we create ProtocolException via createSystemException if the response has fault. However, we didn't create ProtocolException if there is any exception when executing createMessageFromValue. Protocol specific exception is required when throwing an exception as a result of the protocol level fault.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2784) When exception arises from
createMessageFromValue, create Protocol specific exception instead of the
generic WebserviceException
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502800 ]
Davanum Srinivas commented on AXIS2-2784:
-----------------------------------------
Applied in svn revision 545504
thanks,
dims
> When exception arises from createMessageFromValue, create Protocol specific exception instead of the generic WebserviceException
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2784
> URL: https://issues.apache.org/jira/browse/AXIS2-2784
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.3
> Environment: win XP + SUn JDK 1.5
> Reporter: Lin Sun
> Assignee: Davanum Srinivas
> Attachments: Axis2-2784.patch
>
>
> During dispatch.invoke, we create ProtocolException via createSystemException if the response has fault. However, we didn't create ProtocolException if there is any exception when executing createMessageFromValue. Protocol specific exception is required when throwing an exception as a result of the protocol level fault.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2784) When exception arises from
createMessageFromValue, create Protocol specific exception instead of the
generic WebserviceException
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2784:
------------------------------------
Assignee: Davanum Srinivas
> When exception arises from createMessageFromValue, create Protocol specific exception instead of the generic WebserviceException
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2784
> URL: https://issues.apache.org/jira/browse/AXIS2-2784
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.3
> Environment: win XP + SUn JDK 1.5
> Reporter: Lin Sun
> Assignee: Davanum Srinivas
> Fix For: 1.3
>
> Attachments: Axis2-2784.patch
>
>
> During dispatch.invoke, we create ProtocolException via createSystemException if the response has fault. However, we didn't create ProtocolException if there is any exception when executing createMessageFromValue. Protocol specific exception is required when throwing an exception as a result of the protocol level fault.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2784) When exception arises from
createMessageFromValue, create Protocol specific exception instead of the
generic WebserviceException
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun updated AXIS2-2784:
---------------------------
Attachment: Axis2-2784.patch
Tested in geronimo env.
> When exception arises from createMessageFromValue, create Protocol specific exception instead of the generic WebserviceException
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2784
> URL: https://issues.apache.org/jira/browse/AXIS2-2784
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.3
> Environment: win XP + SUn JDK 1.5
> Reporter: Lin Sun
> Fix For: 1.3
>
> Attachments: Axis2-2784.patch
>
>
> During dispatch.invoke, we create ProtocolException via createSystemException if the response has fault. However, we didn't create ProtocolException if there is any exception when executing createMessageFromValue. Protocol specific exception is required when throwing an exception as a result of the protocol level fault.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2784) When exception arises from
createMessageFromValue, create Protocol specific exception instead of the
generic WebserviceException
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved AXIS2-2784.
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.3)
> When exception arises from createMessageFromValue, create Protocol specific exception instead of the generic WebserviceException
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2784
> URL: https://issues.apache.org/jira/browse/AXIS2-2784
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.3
> Environment: win XP + SUn JDK 1.5
> Reporter: Lin Sun
> Assignee: Davanum Srinivas
> Attachments: Axis2-2784.patch
>
>
> During dispatch.invoke, we create ProtocolException via createSystemException if the response has fault. However, we didn't create ProtocolException if there is any exception when executing createMessageFromValue. Protocol specific exception is required when throwing an exception as a result of the protocol level fault.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Reopened: (AXIS2-2784) When exception arises from
createMessageFromValue, create Protocol specific exception instead of the
generic WebserviceException
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle reopened AXIS2-2784:
-----------------------------------
Assignee: Rich Scheuerle (was: Davanum Srinivas)
This solution is not correct.
-------
4.3.2 conformance indicates that a WSE should be thrown if there is a problem with Dispatch configuration. A ProtocolException should be thrown if there
is a error with the remote operation.
-------
Errors involved in the marshalling of the object are neither configuration or remote. So throwing a ProtocolException is not correct and it actually is contrary to 4.3.4.
-------
4.3.4 conformance indicates that a WSE should be thrown if a JAXBException occurs with marshalling or unmarshalling the object.
========
Next Step:
I am going to change the code in the following ways.
A) Make sure that the code throws complies with 4.3.2 and 4.3.4.
B) Make sure that the code behaves in a similar way for invoke and invokeAsync (the recent changes don't appear to be symmetric).
Thanks,
Rich
> When exception arises from createMessageFromValue, create Protocol specific exception instead of the generic WebserviceException
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2784
> URL: https://issues.apache.org/jira/browse/AXIS2-2784
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.3
> Environment: win XP + SUn JDK 1.5
> Reporter: Lin Sun
> Assignee: Rich Scheuerle
> Attachments: Axis2-2784.patch
>
>
> During dispatch.invoke, we create ProtocolException via createSystemException if the response has fault. However, we didn't create ProtocolException if there is any exception when executing createMessageFromValue. Protocol specific exception is required when throwing an exception as a result of the protocol level fault.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org