[
https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799294#comment-12799294
]
Brian Leathem commented on RF-13125:
------------------------------------
From this commit against core:
https://github.com/richfaces4/core/commit/261cf1171e0368e920b1164936fa9f42a868b3ab
it looks like you can reproduce this by triggering a onError response from the
server. The onError response will have a description property that is not
picked up by richfaces-queue.js. The fix checks for and includes the
description property.
From this commit against components:
https://github.com/richfaces4/components/commit/ac9d025b6bdef54cb4e2ad68e9212516882f2e97
it also shows the description property would be ignored.
Finally, looking at the Mojarra jsf.js file, it clearly uses the description
property of the onError data paramenter:
https://github.com/jboss/mojarra/blob/2.1.21-jbossorg-1/jsf-api/src/main/resources/jsf.js#L1553
> a4j:log swallows the message from jsf.js's sendError method
> -----------------------------------------------------------
>
> Key: RF-13125
> URL: https://issues.jboss.org/browse/RF-13125
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3, 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> {code:title=jsf.js:2220}
> } catch (ex) {
> sendError(request, context, "malformedXML", ex.message);
> return;
> }
> {code}
> The ex.message is not shown in output of a4j:log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
