June 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12783) Upgrade compiler plugin to >3.1 (once released)

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12783?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12783: ------------------------------------ {{[MCOMPILER-205|https://jira.codehaus.org/browse/MCOMPILER-205]}} is still open, scheduling this to 4.5-Tracking for follow-up. > Upgrade compiler plugin to >3.1 (once released) > ----------------------------------------------- > > Key: RF-12783 > URL: https://issues.jboss.org/browse/RF-12783 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Fix For: 4.5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > As tracked in JBBUILD-725, it was necessary to downgrade compiler plugin version from 3.0 to 2.3.2. > We need to upgrade to 3.1 (once released) or upgrade JBoss Parent (if upgrade will be available there). > Upstream issue: http://jira.codehaus.org/browse/MCOMPILER-187 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12783) Upgrade compiler plugin to >3.1 (once released)

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12783?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12783: ------------------------------- Assignee: (was: Lukáš Fryč) > Upgrade compiler plugin to >3.1 (once released) > ----------------------------------------------- > > Key: RF-12783 > URL: https://issues.jboss.org/browse/RF-12783 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > As tracked in JBBUILD-725, it was necessary to downgrade compiler plugin version from 3.0 to 2.3.2. > We need to upgrade to 3.1 (once released) or upgrade JBoss Parent (if upgrade will be available there). > Upstream issue: http://jira.codehaus.org/browse/MCOMPILER-187 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13168. -------------------------------- Resolution: Done > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Lukáš Fryč > Labels: interop, jsf22 > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, Jira-WFLY-UT.tar, xaa, xaa, xab, xab, xac, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13203) a4j:queue should have status attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13203?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13203: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5-Tracking) > a4j:queue should have status attribute > -------------------------------------- > > Key: RF-13203 > URL: https://issues.jboss.org/browse/RF-13203 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2 > Reporter: Jonáš Trantina > Labels: gss, queue > Fix For: 4.5-Tracking > > Original Estimate: 2 days > Remaining Estimate: 2 days > > a4j:queue should have status attribute, so it can connect to a4j:status. Consider the following example: > {noformat} > <a4j:queue name="quick" requestDelay="200" /> > <a4j:queue name="slow" requestDelay="1000" /> > <a4j:status name="quickStatus" startText="Started!" stopText="Stopped"/> > <br/> > <a4j:statusname="slowStatus" startText="Started!" stopText="Stopped" /> > > <h:form> > <a4j:commandButton action="#{test.dummy}" value="Quick"> > <a4j:attachQueue name="quick"/> > </a4j:commandButton> > </h:form> > <br/> > <h:form> > <a4j:commandButton action="#{test.dummy}" value="Slow"> > <a4j:attachQueue name="slow"/> > </a4j:commandButton> > </h:form> > {noformat} > By using the status attr. of a4j:queue, it would be possible to connect "slow" queue to "slowStatus" and thus every component that would be connected to the queue, would also be connected to the status. > Note in this example it would be simpler to set status attr. on the components themselves, but imagine there are more components connected to the queue. > I was also informed, that this functionality was present in RF 3.3. > Workarounds: > - set status attr on every component instead of on the queue- in larger applications this is not doable. > - use a4j:status JS API and a4j:queues' onsubmit and oncomplete methods- onsubmit and oncomplete a4j:queue are not implemented, so not working now -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13391) jsf.ajax.addOnEvent not fired after r:ajax completes

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13391?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13391: ------------------------------------ Is this still an issue? > jsf.ajax.addOnEvent not fired after r:ajax completes > ---------------------------------------------------- > > Key: RF-13391 > URL: https://issues.jboss.org/browse/RF-13391 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha2 > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Labels: waiting_on_user > > Unsure if this is a bug or a limiation of using the r:ajax but with f:ajax I am able to listen for jsf.ajax events and for example > {code} > jsf.ajax.addOnEvent(function(data) { > if (data.status == 'success') > addFormGroupClasses(); > }); > {code} > This code is called after completion of an f:ajax but not for an r:ajax -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 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 updated RF-13600: ------------------------------- Assignee: Jiří Štefek > 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, 5 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 reassigned RF-13644: ---------------------------------- Assignee: Pavol Pitonak QE can you verify this issue was resolved in 4.5.0-SNAPSHOT with the recent 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: Pavol Pitonak > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13607) Tables/Menus logged warnings for invalid children

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13607?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13607. -------------------------------- Resolution: Incomplete Description > Tables/Menus logged warnings for invalid children > ------------------------------------------------- > > Key: RF-13607 > URL: https://issues.jboss.org/browse/RF-13607 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu, component-tables > Affects Versions: 4.3.4 > Environment: JBoss EAP 6.1.1 > Reporter: Michael Colin > > Whenever you put an invalid child into a component like the rich:extendedDataTable I would expect to get an exception or a warning at the very least. Currently the component just seems to ignore those false children which makes debugging difficult (when trying to create a composite component of rich:column, for example) and might lead to false code to just stay where it is because it doesn't generate an error and is simply "forgotten". > Wrong code should generate harsh exceptions so it shows and can be fixed in a timely manner. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 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: ------------------------------------ Is this still an issue? > 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 > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13578) RF5 Editor Showcase console errors

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13578?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13578: ------------------------------- Fix Version/s: 5-Tracking > RF5 Editor Showcase console errors > ---------------------------------- > > Key: RF-13578 > URL: https://issues.jboss.org/browse/RF-13578 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha4 > Reporter: Matej Novotny > Fix For: 5-Tracking > > > When accessing RF 5 showcase (for instance latest showcase [here|http://showcase-latest.richfaces.org/], you can notice that in web console there is following error: > {code} > ReferenceError: CKEDITOR is not defined ui.js:8774 > {code} > I believe this error started to appear after latest editor update and it might refer to [this|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...] code. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2014