April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12945) Dynamic tab panels don't work in ajax mode

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12945?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-12945: ------------------------------- Description: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTabPanel/addTab2.xhtml # click the button with label "[h] Create tab" # switch to second tab (content of tab will change) # switch to tab 6 result: * ajax request is performed but tab panel's content doesn't change (it's still tab2) * worked fine in RichFaces 4.3.1.Final * dynamic panel can't be removed, there is an error message in browser console: {quote} Uncaught TypeError: Cannot call method 'onCompleteHandler' of undefined {quote} This issue might be related to RF-11081 or RF-12513. was: # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTabPanel/addTab2.xhtml # click the button with label "[h] Create tab" # switch to second tab (content of tab will change) # switch to tab 6 result: * ajax request is performed but tab panel's content doesn't change (it's still tab2) * worked fine in RichFaces 4.3.1.Final * dynamic panel can't be removed, there is an error message in browser console: {quote} Uncaught TypeError: Cannot call method 'onCompleteHandler' of undefined {quote} > Dynamic tab panels don't work in ajax mode > ------------------------------------------ > > Key: RF-12945 > URL: https://issues.jboss.org/browse/RF-12945 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes, regression > Affects Versions: 4.3.2 > Environment: RichFaces 4.3.2.CR1 > Metamer 4.3.2-SNAPSHOT > JBoss AS 7.1.3.Final-redhat-4 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 26.0.1410.63 @ Linux x86_64, Firefox 20 > Reporter: Pavol Pitonak > Priority: Critical > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTabPanel/addTab2.xhtml > # click the button with label "[h] Create tab" > # switch to second tab (content of tab will change) > # switch to tab 6 > result: > * ajax request is performed but tab panel's content doesn't change (it's still tab2) > * worked fine in RichFaces 4.3.1.Final > * dynamic panel can't be removed, there is an error message in browser console: > {quote} > Uncaught TypeError: Cannot call method 'onCompleteHandler' of undefined > {quote} > This issue might be related to RF-11081 or RF-12513. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12945) Dynamic tab panels don't work in ajax mode

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-12945: ---------------------------------- Summary: Dynamic tab panels don't work in ajax mode Key: RF-12945 URL: https://issues.jboss.org/browse/RF-12945 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-panels-layout-themes, regression Affects Versions: 4.3.2 Environment: RichFaces 4.3.2.CR1 Metamer 4.3.2-SNAPSHOT JBoss AS 7.1.3.Final-redhat-4 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 26.0.1410.63 @ Linux x86_64, Firefox 20 Reporter: Pavol Pitonak Priority: Critical # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTabPanel/addTab2.xhtml # click the button with label "[h] Create tab" # switch to second tab (content of tab will change) # switch to tab 6 result: * ajax request is performed but tab panel's content doesn't change (it's still tab2) * worked fine in RichFaces 4.3.1.Final * dynamic panel can't be removed, there is an error message in browser console: {quote} Uncaught TypeError: Cannot call method 'onCompleteHandler' of undefined {quote} -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ] Jan Papousek closed RF-12765. ----------------------------- Closing. As I understand the discussion. The issue isn't solved, but the samples were updated according to the specification. > Rich:tabPanel not possible to switch tabs when only dynamic tabs are present > ---------------------------------------------------------------------------- > > Key: RF-12765 > URL: https://issues.jboss.org/browse/RF-12765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.M3, 4.3.0.CR2, 4.3.0.Final, 4.3.1 > Environment: Linux, windows any browser Chrom, Mozilla > Reporter: Tali Han > Assignee: Lukáš Fryč > Fix For: 4.3.2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Rih:Tab panel functionality is broken. > If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. > Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. > richfaces/tabPanel/samples/dynamic-sample.xhtml > {code} > <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> > <ui:remove> > <rich:tab header="Static"> > This tab is static one. > > All of the following tabs are dynamically generated using a4j:repeat. > </rich:tab> > </ui:remove> > <a4j:repeat value="#{skinBean.skins}" var="skinName"> > > <rich:tab header="#{skinName}" name="#{skinName}"> > <f:facet name="header">#{skinName}</f:facet> > All the controls below are just standard JSF components skinned with RichFaces: > <hr /> > <h:form> > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-11000) Hit miss for class loader cost performance problem in Richfaces 4.1.0.

by Benoit VI (JIRA)

[ https://issues.jboss.org/browse/RF-11000?page=com.atlassian.jira.plugin.s... ] Benoit VI commented on RF-11000: -------------------------------- As Rohit, using richfaces with high volume application, I would also appreciate a priority change.... > Hit miss for class loader cost performance problem in Richfaces 4.1.0. > ---------------------------------------------------------------------- > > Key: RF-11000 > URL: https://issues.jboss.org/browse/RF-11000 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Milestone1 > Environment: Linux, Java 6 > Reporter: Pawel J. > Assignee: Brian Leathem > Labels: patch_proposed > Fix For: 5-Future > > Attachments: ResourceFactoryImpl-patch.txt > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > There are scenarios when resources are retrieved during no partial > request processing: > # JSF html renderer (such as ScriptRenderer from faces) require to > know resources names to include them to html/head, > # Resources content request. > We have two types of resources: dynamic and static. Predefined dynamic > resources (such as StateHolderResource) are read using class loader as > they are java classes. Static resources are kept in resources folder > as part of richfaces release jars (jquery.js, richfaces.js, etc). > There is a special case with compiled css that is consider as dynamic > resources but is not important in our case. > The problem appears when we try to load static resources using dynamic > loader. This make unnecessary lookup in java class loader space which > cost time and of course we miss the call as static resources not > exists there. > Statistics that shows class loader hits for every richfaces/ajax4jsf no partial request that will be eliminated after patch: > {code} > Resource::jquery.js ::loading::timens:: 558000 ns::timems::0.558 ms::all::1.561496 sec > Resource::richfaces.js ::loading::timens:: 490000 ns::timems::0.490 ms::all::1.561986 sec > Resource::richfaces-base-component.js::loading::timens:: 593000 ns::timems::0.593 ms::all::1.563672 sec > Resource::richfaces-queue.js ::loading::timens:: 672000 ns::timems::0.672 ms::all::1.564350 sec > Resource::richfaces-event.js ::loading::timens::3292000 ns::timems::3.292 ms::all::1.569386 sec > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12851) The RichFaces kitchensink-rf quickstart/archetype incorrectly depend on the AS google guava module

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12851?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-12851: ---------------------------------- Verified. Closing. > The RichFaces kitchensink-rf quickstart/archetype incorrectly depend on the AS google guava module > -------------------------------------------------------------------------------------------------- > > Key: RF-12851 > URL: https://issues.jboss.org/browse/RF-12851 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, examples > Reporter: Stefan Miklosovic > Assignee: Brian Leathem > Fix For: 4.3.2 > > > The error: "Caused by: java.lang.NoClassDefFoundError: com/google/common/base/Function" is likely due to the quickstart relying on the JBoss AS google guava module [1], which is a bad idea for modules that are considered "internal" to AS. > We should remove the [manifest.mf entries|https://github.com/richfaces/as-quickstarts/blob/master/kitchensi...] that expose these modules and include the dependencies in the kitchensink-rf war. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12851) The RichFaces kitchensink-rf quickstart/archetype incorrectly depend on the AS google guava module

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12851?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12851. ---------------------------- > The RichFaces kitchensink-rf quickstart/archetype incorrectly depend on the AS google guava module > -------------------------------------------------------------------------------------------------- > > Key: RF-12851 > URL: https://issues.jboss.org/browse/RF-12851 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, examples > Reporter: Stefan Miklosovic > Assignee: Brian Leathem > Fix For: 4.3.2 > > > The error: "Caused by: java.lang.NoClassDefFoundError: com/google/common/base/Function" is likely due to the quickstart relying on the JBoss AS google guava module [1], which is a bad idea for modules that are considered "internal" to AS. > We should remove the [manifest.mf entries|https://github.com/richfaces/as-quickstarts/blob/master/kitchensi...] that expose these modules and include the dependencies in the kitchensink-rf war. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12784) Showcase readme - update deployment from eclipse part

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ] Jan Papousek closed RF-12784. ----------------------------- > Showcase readme - update deployment from eclipse part > ----------------------------------------------------- > > Key: RF-12784 > URL: https://issues.jboss.org/browse/RF-12784 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.0.Final, 5-Tracking > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Trivial > Fix For: 4.3.2, 5.0.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial: > An user needs to be aware of: > * select correct maven profile > * alter the deployment assembly > * be aware of wrong context root load in the eclipse browser > I will send pull request for this one. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12858) rich:calendar dateselect event is fired twice

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12858?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12858. ---------------------------- Verified on Metamer. Closing. > rich:calendar dateselect event is fired twice > --------------------------------------------- > > Key: RF-12858 > URL: https://issues.jboss.org/browse/RF-12858 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.1 > Reporter: Michal Petrov > Assignee: Domenico Giannotta > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > <rich:calendar oncurrentdateselect="alert('Date selected')" /> > 1. open the calendar popup > 2. click on the month in the header > 3. select month/year and click "OK" > The alert will pop up twice. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12868) Update the Summary of the RichFaces kitchensink quickstart

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12868?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12868. ---------------------------- Verified that the summary was updated in our repositories. https://github.com/richfaces/as-quickstarts/commit/a71bc2dfc8e6801514a71d... JDF needs to pull it in to see the difference on the quickstart page. Closing. > Update the Summary of the RichFaces kitchensink quickstart > ---------------------------------------------------------- > > Key: RF-12868 > URL: https://issues.jboss.org/browse/RF-12868 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.3.2 > > > Searching for "RichFaces" on the JDF quickstart page does not list the kitchensink-rf quickstart: > On the [JDF quickstart page|http://www.jboss.org/jdf/quickstarts/get-started/], if I search for "RichFaces", the results list does not include the kitchensink-rf project. It should, as this is the only example we have right now showcasing our mobile approach. -- 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

11 years, 7 months

1
0
0 / 0

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

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12893?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12893. ---------------------------- Verified by running framework test. Closing. > 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

11 years, 7 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 April 2013