[
https://issues.apache.org/jira/browse/AXIS2-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513498
]
Dennis Sosnoski commented on AXIS2-2964:
----------------------------------------
The problem I was seeing was that the conversion of the exception data was not
handled properly, in which case you wouldn't get the failure message you're
showing.
I believe I tried this with the svn code last Friday, well after RC1 - but if
it works for you now it sounds like the problem has been corrected. I'll try
again using the current svn code tomorrow.
> XMLBeans fault handling not sending data to client
> --------------------------------------------------
>
> Key: AXIS2-2964
> URL: https://issues.apache.org/jira/browse/AXIS2-2964
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: databinding
> Affects Versions: 1.2, nightly
> Reporter: Dennis Sosnoski
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Critical
> Attachments: xmlbeans-sample.zip
>
>
> The attached project builds and executes properly under Axis2 1.1.1. Under
> 1.2 and the current 1.3 code the exception data is not sent back from the
> server, resulting in an unhandled exception on the client.
> To try this out, edit the build.properties file to set the axis2 installation
> location, then run "ant" to build and "ant run" to run a test after the
> generated aar has been deployed (note that as currently set up the "ant run"
> task will use port 8800 in order to show the conversation on TCPMon).
> To demonstrate the failure, use the supplied code directly with Axis2 1.2 or
> edit the code and change all instances of AddDuplicateFaultException to
> AddDuplicateFault for Axis2 1.3.
--
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]
