April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have a asynchronous way to notify all Topics (e.g. JMS)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12916: --------------------------------- Hey Luan, I don't understand the statement "a4j:push doesn't have a asynchronous way to notify all Topics". Push (backed by Atmosphere) is not configured to work in cluster environment, thus each of the application instances is independent system. However each of the instances is also connected to JMS and subscribed to topics you are interested in. If you update send a message to such topic, it will be delivered to all Push instances, which will notify all clients interested in (substribed to) particular topic. > a4j:push doesn't work in cluster and doesn't have a asynchronous way to notify all Topics (e.g. JMS) > ----------------------------------------------------------------------------------------------------- > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, for example) -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12848) Error "source is not defined" after richfaces-jsf-event.js merge

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12848?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-12848: ------------------------------- Assignee: Lukáš Fryč > Error "source is not defined" after richfaces-jsf-event.js merge > ---------------------------------------------------------------- > > Key: RF-12848 > URL: https://issues.jboss.org/browse/RF-12848 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Torben Greiser > Assignee: Lukáš Fryč > Priority: Critical > Labels: regression > Fix For: 4.3.2, 5-Tracking > > Attachments: rf12848_1.xhtml > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Commit 9255380d626227d909bbcd59ea3bc604966ea5bb breaks the following jsf.ajax.request: > {code} > jsf.ajax.request("MyContainer:MySelectionForm", "valueChange", {}); > {code} > In <a4j:log/> the following error is displayed: > {code} > richfaces.queue: ajax submit error: source is not defined > {code} > After inspecting richfaces.js I located the cause of the error: > {code} > var getFormElement = function(sourceElement) { > if ($(sourceElement).is('form')) { > return source; > } else { > return $('form').has(sourceElement).get(0); > } > }; > {code} > First if-statement evaluates to true, returning source, which itself is not defined: > {code} > ReferenceError: source is not defined > {code} -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12893) Partial response not ended correctly on exception

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12893?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-12893: ------------------------------- Assignee: Lukáš Fryč > Partial response not ended correctly on exception > ------------------------------------------------- > > Key: RF-12893 > URL: https://issues.jboss.org/browse/RF-12893 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Bernard Labno > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 4.3.2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When there is an exception during ajax request the DeferredEndingPartialResponseWriter.finallyEndDocument is not called. > This may be a bug of JSF http://grepcode.com/file/repo1.maven.org/maven2/com.sun.faces/jsf-impl/2.... > As there is no finallyEndDocument call. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12850) Popup panel: button's label is invisible in IE10

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12850?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12850: ---------------------------------- Assignee: Brian Leathem > Popup panel: button's label is invisible in IE10 > ------------------------------------------------ > > Key: RF-12850 > URL: https://issues.jboss.org/browse/RF-12850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.3.Final, 4.3.0.Final, 4.3.1 > Environment: RichFaces 4.3.2-SNAPSHOT > EAP 6.0.1, Tomcat 6.0.32, Tomcat 7.0.35 > Mojarra 2.1.7, 2.1.17, MyFaces 2.1.10 > Internet Explorer 9, 10 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.3.2 > > Attachments: buttonInPopupPanel.png > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > {code:xml} > <rich:popupPanel id="panel" show="true" header="xxx"> > <h:commandButton id="button" value="Submit" /> > </rich:popupPanel> > {code} > If a page with code snippet above is opened in IE9/IE10, the label "Submit" of button is not displayed until mouse over event. > Since it appears in all JSF implementations and on all runtime containers and works in browsers different from IE, it looks like a bug in IE interpretation of CSS classes. > Sample works fine when header of popup panel is not displayed (i.e. header attribute isn't set and no facet is defined). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12839) Toggle panels: ajax-related attributes don't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12839?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12839: ---------------------------------- Assignee: Brian Leathem > Toggle panels: ajax-related attributes don't work > ------------------------------------------------- > > Key: RF-12839 > URL: https://issues.jboss.org/browse/RF-12839 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.1 > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 4.3.2-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.3.Final-redhat-4 > JBoss AS 7.1.3.Final-redhat-4 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 25.0.1364.160 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # set oncomplete to "alert('complete')" > # switch to tab 2 and back to tab 1 > result: > * alert should be diplayed but isn't > * tabs are correctly switched > * worked fine in 4.2.3.Final > * several attributes don't work - onbegin, onbeforedomupdate, oncomplete, data, execute, immediate, render, limitRender, status > * affected components: tab, toggle panel item, accordion item -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12893) Partial response not ended correctly on exception

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12893?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12893: ------------------------------- Sprint: 4.3.2 Sprint 1 > Partial response not ended correctly on exception > ------------------------------------------------- > > Key: RF-12893 > URL: https://issues.jboss.org/browse/RF-12893 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Bernard Labno > Priority: Critical > Fix For: 4.3.2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When there is an exception during ajax request the DeferredEndingPartialResponseWriter.finallyEndDocument is not called. > This may be a bug of JSF http://grepcode.com/file/repo1.maven.org/maven2/com.sun.faces/jsf-impl/2.... > As there is no finallyEndDocument call. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12898) Tie RichFaces 4.3 to CDK 4.3.1.Final

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12898?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12898: ------------------------------- Sprint: 4.3.2 Sprint 1 > Tie RichFaces 4.3 to CDK 4.3.1.Final > ------------------------------------ > > Key: RF-12898 > URL: https://issues.jboss.org/browse/RF-12898 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The RichFaces CDK master is now 4.5.x development. > We need to stop using the master for a full build > and tie the framework build to latest released CDK: 4.3.1.Final. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12846?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12846: ---------------------------------- Assignee: Brian Leathem > a4j:commandLink accesskey attribute missing > ------------------------------------------- > > Key: RF-12846 > URL: https://issues.jboss.org/browse/RF-12846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1 > Reporter: John Yeary > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.2, 5-Tracking > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12850) Popup panel: button's label is invisible in IE10

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12850?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12850: ------------------------------- Sprint: 4.3.2 Sprint 1 > Popup panel: button's label is invisible in IE10 > ------------------------------------------------ > > Key: RF-12850 > URL: https://issues.jboss.org/browse/RF-12850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.3.Final, 4.3.0.Final, 4.3.1 > Environment: RichFaces 4.3.2-SNAPSHOT > EAP 6.0.1, Tomcat 6.0.32, Tomcat 7.0.35 > Mojarra 2.1.7, 2.1.17, MyFaces 2.1.10 > Internet Explorer 9, 10 > Reporter: Pavol Pitonak > Fix For: 4.3.2 > > Attachments: buttonInPopupPanel.png > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > {code:xml} > <rich:popupPanel id="panel" show="true" header="xxx"> > <h:commandButton id="button" value="Submit" /> > </rich:popupPanel> > {code} > If a page with code snippet above is opened in IE9/IE10, the label "Submit" of button is not displayed until mouse over event. > Since it appears in all JSF implementations and on all runtime containers and works in browsers different from IE, it looks like a bug in IE interpretation of CSS classes. > Sample works fine when header of popup panel is not displayed (i.e. header attribute isn't set and no facet is defined). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12849) Showcase - update readme - remove obsolete, add new

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12849?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12849: ------------------------------- Sprint: 4.3.2 Sprint 1 > Showcase - update readme - remove obsolete, add new > --------------------------------------------------- > > Key: RF-12849 > URL: https://issues.jboss.org/browse/RF-12849 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.1 > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 4.3.2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > After rewriting showcase readme to markdown syntax I would update it for example with following: > * reference to showcase online demo > * remove publishing to GAE and put there publishing to Openshift instead > * I would create small clickable TOC in the top of the page > * remove deploying on JBoss AS 6 and maybe add deploying on EAP 6 (it is now available to download) > * Mention JBDS as an option -- 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

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2013