December 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12460) RF-11138 Tree does not invoke selectionChangeListener in popupPanel with 4.2.0 final also

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12460?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-12460: ------------------------------- Description: Rich Tree working fine below source code. But same code applied in Popup panel, unable to get selected Item. Popup div also within same form. Working Fine below code {code} <rich:tree value="#{typeList.root}" var="node" render="label2 label3" id="treeMul" selection="#{typeList.selectedNodes}" ajaxSubmitSelection="true" selectionType="ajax"> <rich:treeNode> <h:outputText value="#{node}" /> </rich:treeNode> </rich:tree> {code} Please provide solution ASAP. This is showstopper for me. Problem Here {code} <rich:popupPanel id="popup" modal="true" autosized="true" resizeable="false" overlapEmbedObjects="true"> <f:facet name="header"> <h:outputText value="Tree View" /> </f:facet> <f:facet name="controls"> <h:outputLink value="#" onclick="#{rich:component('popup')}.hide(); return false;">X</h:outputLink> </f:facet> <rich:tree value="#{typeList.root}" var="node" render="label2 label3" id="treeMul" selection="#{typeList.selectedNodes}" ajaxSubmitSelection="true" selectionType="ajax"> <rich:treeNode> <h:outputText value="#{node}" /> </rich:treeNode> </rich:tree> </rich:popupPanel {code} was: Rich Tree working fine below source code. But same code applied in Popup panel, unable to get selected Item. Popup div also within same form. Working Fine below code {code} <rich:tree value="#{typeList.root}" var="node" render="label2 label3" id="treeMul" selection="#{typeList.selectedNodes}" ajaxSubmitSelection="true" selectionType="ajax"> <rich:treeNode> <h:outputText value="#{node}" /> </rich:treeNode> </rich:tree> {code} Please provide solution ASAP. This is showstopper for me. Problem Here {code} <rich:popupPanel id="popup" modal="true" autosized="true" resizeable="false" overlapEmbedObjects="true"> <f:facet name="header"> <h:outputText value="Tree View" /> </f:facet> <f:facet name="controls"> <h:outputLink value="#" onclick="#{rich:component('popup')}.hide(); return false;">X</h:outputLink> </f:facet> <rich:tree value="#{typeList.root}" var="node" render="label2 label3" id="treeMul" selection="#{typeList.selectedNodes}" ajaxSubmitSelection="true" selectionType="ajax"> <rich:treeNode> <h:outputText value="#{node}" /> </rich:treeNode> </rich:tree> <rich:popupPanel {code} > RF-11138 Tree does not invoke selectionChangeListener in popupPanel with 4.2.0 final also > ----------------------------------------------------------------------------------------- > > Key: RF-12460 > URL: https://issues.jboss.org/browse/RF-12460 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.2.0.Final > Reporter: venkat kavali > Assignee: Pavol Pitonak > > Rich Tree working fine below source code. But same code applied in Popup panel, unable to get selected Item. Popup div also within same form. > Working Fine below code > {code} > <rich:tree value="#{typeList.root}" var="node" render="label2 label3" id="treeMul" > selection="#{typeList.selectedNodes}" ajaxSubmitSelection="true" selectionType="ajax"> > <rich:treeNode> > <h:outputText value="#{node}" /> > </rich:treeNode> > </rich:tree> > {code} > Please provide solution ASAP. This is showstopper for me. > Problem Here > {code} > <rich:popupPanel id="popup" modal="true" autosized="true" resizeable="false" overlapEmbedObjects="true"> > <f:facet name="header"> > <h:outputText value="Tree View" /> > </f:facet> > <f:facet name="controls"> > <h:outputLink value="#" onclick="#{rich:component('popup')}.hide(); return false;">X</h:outputLink> > </f:facet> > <rich:tree value="#{typeList.root}" var="node" render="label2 label3" id="treeMul" > selection="#{typeList.selectedNodes}" ajaxSubmitSelection="true" selectionType="ajax"> > <rich:treeNode> > <h:outputText value="#{node}" /> > </rich:treeNode> > </rich:tree> > </rich:popupPanel > {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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12651) rich:placeholder with RF inplace components: style is not binded to component's label

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12651: -------------------------------- Summary: rich:placeholder with RF inplace components: style is not binded to component's label Key: RF-12651 URL: https://issues.jboss.org/browse/RF-12651 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Reporter: Jiří Štefek For RichFaces inplace components (select and input) there are no styles from placeholder -- neither from attribute @styleClass nor default style (rf-plhdr). -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12650) rich:placeholder: when @rendered=false the placeholder is still rendered

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12650: -------------------------------- Summary: rich:placeholder: when @rendered=false the placeholder is still rendered Key: RF-12650 URL: https://issues.jboss.org/browse/RF-12650 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Reporter: Jiří Štefek See the steps to reproduce. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12144) Notify: taglib and faces-config.xml are not synced

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12144?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12144. ----------------------------- Resolution: Done > Notify: taglib and faces-config.xml are not synced > -------------------------------------------------- > > Key: RF-12144 > URL: https://issues.jboss.org/browse/RF-12144 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk, component > Affects Versions: 4.2.0.Final, 4.2.1.CR1, 4.3.0.M2 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Labels: needs-qe, vdl > Fix For: 4.3.0.M3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > RichFaces taglig [1] and faces-config.xml [2] should contain the same information about the components. However, notify, notifyMessage, notifyMessages and notifyStack are not synced in those two files. E.g. > * faces-config.xml is missing notifyMessages' attribute animationSpeed > * attribute styleClass in notifyMessages is missing description in faces-config.xml > https://repository.jboss.org/nexus/service/local/repositories/public/arch... > https://repository.jboss.org/nexus/service/local/repositories/public/arch... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12144) Notify: taglib and faces-config.xml are not synced

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12144?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12144: --------------------------------- Pavol, I have verified that all the mentioned attribute and attribute listed in mentioned "*props.xml" files are in full build of RF present, thus I'm resolving this issue. > Notify: taglib and faces-config.xml are not synced > -------------------------------------------------- > > Key: RF-12144 > URL: https://issues.jboss.org/browse/RF-12144 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk, component > Affects Versions: 4.2.0.Final, 4.2.1.CR1, 4.3.0.M2 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Labels: needs-qe, vdl > Fix For: 4.3.0.M3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > RichFaces taglig [1] and faces-config.xml [2] should contain the same information about the components. However, notify, notifyMessage, notifyMessages and notifyStack are not synced in those two files. E.g. > * faces-config.xml is missing notifyMessages' attribute animationSpeed > * attribute styleClass in notifyMessages is missing description in faces-config.xml > https://repository.jboss.org/nexus/service/local/repositories/public/arch... > https://repository.jboss.org/nexus/service/local/repositories/public/arch... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12608) pickList without collectionType results in failure to lazily load

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12608?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12608: ----------------------------- Labels: regression (was: regression waiting_on_user) > pickList without collectionType results in failure to lazily load > ----------------------------------------------------------------- > > Key: RF-12608 > URL: https://issues.jboss.org/browse/RF-12608 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final, 4.3.0.M2 > Reporter: Ken H > Assignee: Juraj Húska > Labels: regression > > Changes to the selectManyHelper class in 4.2.3+ causes a lazy loading exception in hibernate when the backing collection is persistent and is not eagerly loaded. > The problem seems to be that fetching the collection in SelectManyHelper.getConvertedValue bypasses the PersistentSet getter that would normally issue the lazy load request. > Defining the collectionType (e.g. java.util.ArrayList) bypasses this issue. > Ideally this method would detect Hibernate proxy collections and handle them appropriately. However, I realize that may cause a dependency so perhaps it would be enough to document this option and situation in the component reference. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12649) Placeholder: add fundamental tests for rich Input components

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12649?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-12649: ---------------------------------- Assignee: Jiří Štefek (was: Pavol Pitonak) > Placeholder: add fundamental tests for rich Input components > ------------------------------------------------------------ > > Key: RF-12649 > URL: https://issues.jboss.org/browse/RF-12649 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - unit > Affects Versions: 4.3.0.M3 > Reporter: Lukáš Fryč > Assignee: Jiří Štefek > Priority: Minor > Fix For: 4.3.0.M3 > > > Could you please extend Placeholder test suite by coverage for integration testing with following components: > * Calendar > * Autocomplete > * Select > * Inplace Input > * Inplace Select -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12021) Compilation of Input UI component logs 2 errors about faces-config.xml

by Immanuel Gregoire (JIRA)

[ https://issues.jboss.org/browse/RF-12021?page=com.atlassian.jira.plugin.s... ] Immanuel Gregoire commented on RF-12021: ---------------------------------------- Well, the build does abort on Netbeans 7.1.2 and Netbeans 7.2 when using JDK 1.7 (1.7.0_03) The build does indeed continue on JDK 1.6 (1.6.0_37) Can you reproduce it ? > Compilation of Input UI component logs 2 errors about faces-config.xml > ---------------------------------------------------------------------- > > Key: RF-12021 > URL: https://issues.jboss.org/browse/RF-12021 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.0.Final > Reporter: Marek Novotny > Assignee: Brian Leathem > > Compilation of RF UI Components specifically Input UI has got 2 errors in log - related to bad faces-config.xml on line number 29 and 240. > The following is snippet of log: > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces UI Components: Input UI 4.2.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-java-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-enforcer-plugin:1.0-redhat-1:enforce (enforce-maven-version) @ richfaces-ui-input-ui --- > [INFO] The requirePluginVersions rule is currently not compatible with Maven3. > [INFO] > [INFO] --- maven-cdk-plugin:4.2.0.Final-redhat-1:generate (cdk-generate-sources) @ richfaces-ui-input-ui --- > [Error] faces-config.xml:29:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > [Error] faces-config.xml:240:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xi:include'. One of '{"http://java.sun.com/xml/ns/javaee":property, "http://java.sun.com/xml/ns/javaee":component-extension}' is expected. > {noformat} -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12649) Placeholder: add fundamental tests for rich Input components

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12649: ------------------------------- Summary: Placeholder: add fundamental tests for rich Input components Key: RF-12649 URL: https://issues.jboss.org/browse/RF-12649 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: tests - unit Affects Versions: 4.3.0.M3 Reporter: Lukáš Fryč Assignee: Pavol Pitonak Priority: Minor Fix For: 4.3.0.M3 Could you please extend Placeholder test suite by coverage for integration testing with following components: * Calendar * Autocomplete * Select * Inplace Input * Inplace Select -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-12594) rich:calendar defaultLabel causes conversion error if not populated.

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12594?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12594: ---------------------------- Labels: waiting_on_user (was: ) > rich:calendar defaultLabel causes conversion error if not populated. > -------------------------------------------------------------------- > > Key: RF-12594 > URL: https://issues.jboss.org/browse/RF-12594 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.0.M2 > Reporter: Justin Rosenberg > Assignee: Lukáš Fryč > Labels: waiting_on_user > > If the defaultLabel attribute is set for a rich:calendar object and no value is entered, a conversion error occurs. It seems like the submission is trying to parse the defaultLabel value into a date. -- 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, 12 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 December 2012