[
https://issues.jboss.org/browse/RF-11399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631753#comment-12631753
]
Lukáš Fryč commented on RF-11399:
---------------------------------
Hi Juergen, I have tried and your problem is caused by binding your editor to
controller: #{cust.binding}.
CustomerController (#{cust}) is @SessionScoped, so the editor is loaded
correctly for you at first load, then it stops to work (resource links are not
encoded properly. You should use @RequestScoped for storing bindings to on-page
components.
> rich:editor doesn't work with Mojarra 2.1.3 / JBossAS 7.1
> ---------------------------------------------------------
>
> Key: RF-11399
> URL: https://issues.jboss.org/browse/RF-11399
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.1.0.Milestone1
> Environment: JBossAS 7 Jenkins build 1605
> Reporter: Juergen Zimmermann
> Assignee: Lukáš Fryč
> Priority: Critical
> Attachments: editor.firebug.jpg, testcase-src.zip, testcase.ear.zip
>
>
> JBossAS 7 upgraded to Mojarra 2.1.3-b02. As long as Mojarra 2.0.4 was used,
> there was no problem with rich:editor. After the upgrade of Mojarra,
> rich:editor doesn't work any more: nothing is visible. I'll attach a
> screenshot of the generated HTML code as shown by Firebug.
--
This message is automatically generated by JIRA.
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
