June 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13661?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13661: ------------------------------- Description: Investigate whether we can de-couple a {{RichFaces.BaseComponent}} based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. (was: Investigate whether we can de-couple a RichFaces.BaseComponent based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC.) > De-couple the RichFaces.BaseComponent implementation from its JSF backend > ------------------------------------------------------------------------- > > Key: RF-13661 > URL: https://issues.jboss.org/browse/RF-13661 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5-Tracking > > > Investigate whether we can de-couple a {{RichFaces.BaseComponent}} based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13661?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13661: ------------------------------------ Fortunately {{RichFaces.BaseComponent}} itself doesn't contain any jsf.js integration. De-coupling a component for its JSF backend then should simply involve replacing direct {{RichFaces.ajax}} calls with an event mechanism. On a related note, much of the {{RichFaces.BaseComponent}} merely wraps some specific jQuery functionality. The client-side codebase could conceivably be simplified by removing the unused and redundant abstractions. > De-couple the RichFaces.BaseComponent implementation from its JSF backend > ------------------------------------------------------------------------- > > Key: RF-13661 > URL: https://issues.jboss.org/browse/RF-13661 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5-Tracking > > > Investigate whether we can de-couple a RichFaces.BaseComponent based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend

by Brian Leathem (JIRA)

Brian Leathem created RF-13661: ---------------------------------- Summary: De-couple the RichFaces.BaseComponent implementation from its JSF backend Key: RF-13661 URL: https://issues.jboss.org/browse/RF-13661 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.5-Tracking Investigate whether we can de-couple a RichFaces.BaseComponent based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request on WildFly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13600: ------------------------------------ RichFaces 4.3 does not work with JSF 2.2 and isnot expected to work on WildFly - there is no sense in testing that configuration. WildFly should be tested with RichFaces 4.5 / 5.0 where we support JSF 2.2. > metamer: malformedXML error on each ajax request on WildFly > ----------------------------------------------------------- > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5, 4.3.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, (works on EAP 6.2) > Reporter: Jiří Štefek > Assignee: Jiří Štefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3.x . > On every ajax request there is malformedXML error and the metamer status is set to ERROR. But all the outputs are updated and it seems that all is working (except the status and autocomplete) as expected. > # open e.g. http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml > # click on the submit button > # see the status 'ERROR' > # open log, at the end you can see: > {code} > error[09:58:23.320]: Received 'error@malformedXML' event from <input id=form:commandButton ...> > error[09:58:23.322]: [status=200] During update: javax.faces.ViewState not found > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13644. -------------------------------- Assignee: Lukáš Fryč (was: Jiří Štefek) Fix Version/s: 4.5.0.Alpha3 Resolution: Done Resolved with CKeditor upgrade. > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Lukáš Fryč > Labels: IE11 > Fix For: 4.5.0.Alpha3 > > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.s... ] Jiří Štefek updated RF-13644: ----------------------------- Labels: IE11 (was: ) > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Jiří Štefek > Labels: IE11 > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.s... ] Jiří Štefek commented on RF-13644: ---------------------------------- I can confirm, that there are no JS errors in browser console in 4.5.0-SNAPSHOT. Verified in Metamer. > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Jiří Štefek > Labels: IE11 > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-13644: ---------------------------------- Assignee: Jiří Štefek (was: Pavol Pitonak) > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Jiří Štefek > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request on WildFly

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.s... ] Jiří Štefek commented on RF-13600: ---------------------------------- Problem still occurs in 4.3.x Metamer on WildFly (tried 8.0.0.Final and 8.1.0.Final). But I can't reproduce this behavior with 5.0.x Metamer on AS 7.1.1. > metamer: malformedXML error on each ajax request on WildFly > ----------------------------------------------------------- > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5, 4.3.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, (works on EAP 6.2) > Reporter: Jiří Štefek > Assignee: Jiří Štefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3.x . > On every ajax request there is malformedXML error and the metamer status is set to ERROR. But all the outputs are updated and it seems that all is working (except the status and autocomplete) as expected. > # open e.g. http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml > # click on the submit button > # see the status 'ERROR' > # open log, at the end you can see: > {code} > error[09:58:23.320]: Received 'error@malformedXML' event from <input id=form:commandButton ...> > error[09:58:23.322]: [status=200] During update: javax.faces.ViewState not found > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12764?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12764: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5-Tracking) > rich:select - javascript error when using myfaces with french locale > -------------------------------------------------------------------- > > Key: RF-12764 > URL: https://issues.jboss.org/browse/RF-12764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR2 > Reporter: Dupont Dupont > Labels: patch_proposed > Fix For: 4.5-Tracking > > > Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error : > {code} > Uncaught SyntaxError: Unexpected identifier. > {code} > It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote. > To reproduce it, just add the following line in your jsf messages properties : > {code} > javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide. > {code} > And add a rich:select in your JSF page. > We end up with the javascript : > {code} > RichFaces.csv.addMessage({ 'UISELECTONE_INVALID': {detail:'{0} : Erreur de validation : la valeur n'est pas valide.',summary:'{0} : Erreur de validation : la valeur n'est pas valide.',severity:2} }); > {code} > This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes). > Resolved locally by modifying AddCSVMessageScript#appendcript > But perhaps I've missed some side effects. > {code:java} > @Override > public void appendScript(Appendable target) throws IOException { > String summary = facesMessage.getSummary(); > String detail = facesMessage.getDetail(); > int severity = facesMessage.getSeverity().getOrdinal(); > StringBuilder builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, summary); > summary = builder.toString(); > builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, detail); > detail = builder.toString(); > > String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity); > target.append(script); > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2014