March 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12073) Kitchensink archetype - creating enterprise project requires also community richfaces version

by Juraj Huska (JIRA)

Juraj Huska created RF-12073: -------------------------------- Summary: Kitchensink archetype - creating enterprise project requires also community richfaces version Key: RF-12073 URL: https://issues.jboss.org/browse/RF-12073 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Optional When generating enterprise richfaces maven project from kitchensink archetype, it is also prompting for community richfaces version. And then the community version is not used in the generated pom.xml The log from this: {noformat} [INFO] Using property: groupId = bla.bla [INFO] Using property: artifactId = foo_bla Define value for property 'version': 1.0-SNAPSHOT: : [INFO] Using property: package = bla.bla [INFO] Using property: enterprise = n [INFO] Using property: richfaces-enterprise-version = 4.2.0.Final-redhat-1 [INFO] Using property: richfaces-version = 4.3.0-SNAPSHOT Confirm properties configuration: groupId: bla.bla artifactId: foo_bla version: 1.0-SNAPSHOT package: bla.bla enterprise: n richfaces-enterprise-version: 4.2.0.Final-redhat-1 richfaces-version: 4.3.0-SNAPSHOT Y: : N [INFO] Using property: groupId = bla.bla [INFO] Using property: artifactId = foo_bla Define value for property 'version': 1.0-SNAPSHOT: : Define value for property 'package': bla.bla: : Define value for property 'enterprise': n: : y Define value for property 'richfaces-enterprise-version': 4.2.0.Final-redhat-1: : Define value for property 'richfaces-version': 4.3.0-SNAPSHOT: : Confirm properties configuration: groupId: bla.bla artifactId: foo_bla version: 1.0-SNAPSHOT package: bla.bla enterprise: y richfaces-enterprise-version: 4.2.0.Final-redhat-1 richfaces-version: 4.3.0-SNAPSHOT Y: : y [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 54.442s [INFO] Finished at: Wed Mar 21 16:38:02 CET 2012 [INFO] Final Memory: 9M/129M [INFO] ------------------------------------------------------------------------ jhuska@laptop:~/workspace_jbossTools33M5$ {noformat} *Steps to reproduce:* 1. _mvn archetype:generate -DarchetypeGroupId=org.richfaces.archetypes -DarchetypeArtifactId=richfaces-archetype-kitchensink -DarchetypeVersion=4.3.0-SNAPSHOT -DgroupId=bla.bla -DartifactId=foo_bla_ 2. When prompting: ?Define value for property 'version': 1.0-SNAPSHOT:_, press just enter. 3. When prompting for confirming predefined values: type N 4. When prompting for _Define value for property 'version': 1.0-SNAPSHOT: :_ press just enter. 5. _Define value for property 'package': bla.bla: : _ just enter 6. _Define value for property 'enterprise': n: :_ type y 7. _Define value for property 'richfaces-enterprise-version': 4.2.0.Final-redhat-1: :_ just enter 8. now you should be prompted for _Define value for property 'richfaces-version': 4.3.0-SNAPSHOT: :_, which you should not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] (RF-11737) WARNING: Queue with name 'xxx' has already been registered

by Milo van der Zee (Created) (JIRA)

WARNING: Queue with name 'xxx' has already been registered ---------------------------------------------------------- Key: RF-11737 URL: https://issues.jboss.org/browse/RF-11737 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.1.0.CR1 Environment: RF4.0.1.20111111RC1, Mojarry 2.1.4, Tomcat 7.0.21, Gentoo Linux Reporter: Milo van der Zee As soon as a component with a queue is put inside a composite it will create a continues stream of warnings. Even if components outside the composite are used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

10
14
0 / 0

[JBoss JIRA] (RF-11975) Prototype script error in Portal

by Ken Finnigan (JIRA)

Ken Finnigan created RF-11975: --------------------------------- Summary: Prototype script error in Portal Key: RF-11975 URL: https://issues.jboss.org/browse/RF-11975 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: third-party Affects Versions: 3.3.3.Final Environment: GateIn v3.2 JBoss PortletBridge v2.2.0.Final Firefox Reporter: Ken Finnigan Priority: Minor When a user wants to add two separate portlets to the same portal page, with both portlets using RichFaces components, the JBoss PortletBridge needs to have the context parameter "org.jboss.portletbridge.WRAP_SCRIPTS" set to true. This wraps the RichFaces JavaScript files with a check to prevent the same file being loaded twice on the one page, as there are two portlets with RichFaces scripts being loaded. In this situation, the prototype.js script (or framework_pack.js when LoadScriptStrategy is ALL) returns "$A() is not defined" within Firefox, but in Chrome and IE it works fine. This JS error in Firefox can be resolved by moving the $A function to the very top of the file to ensure it is defined when needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] (RF-12106) panelToggleListener attribute @for does not work

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12106: -------------------------------- Summary: panelToggleListener attribute @for does not work Key: RF-12106 URL: https://issues.jboss.org/browse/RF-12106 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 11.0 @ Linux x86_64 Reporter: Jiří Štefek # Deploy Metamer. # Open http://localhost:8080/metamer/faces/components/richPanelToggleListener/RF... //will fix the address soon -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
7
0 / 0

[JBoss JIRA] (RF-11486) Mobile Showcase: size of icons in rich:tree

by Jan Papousek (Created) (JIRA)

Mobile Showcase: size of icons in rich:tree ------------------------------------------- Key: RF-11486 URL: https://issues.jboss.org/browse/RF-11486 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Jan Papousek Priority: Minor Attachments: android-rich_tree.png Icons in rich:tree should be larger. Sometimes it's really difficult to click on the plus/minus. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

11
17
0 / 0

[JBoss JIRA] (RF-12080) rich:hotKey usage clears body onload attribute

by Michael Heinen (JIRA)

Michael Heinen created RF-12080: ----------------------------------- Summary: rich:hotKey usage clears body onload attribute Key: RF-12080 URL: https://issues.jboss.org/browse/RF-12080 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.2.0.Final Environment: myfaces 2.1.6, tomahawk 1.1.11 Reporter: Michael Heinen Priority: Minor I'm happy to see rich:hotKey in richfaces 4.2, I used it already with richfaces 3.3.3. One thing I noticed now is that the onload attribute of t:documentboy is cleared on clientside as soon as rich:hotKey is used on a page. Maybe caused by jquery usage? >From my pov this should be either fixed or documented in the component guide as well as in the showcase sample. Workaround is obvious: Instead of onload use document.ready -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
15
0 / 0

[JBoss JIRA] (RF-12116) RF 4.2 : jquery not generated for function

by Adrien Adrien (JIRA)

Adrien Adrien created RF-12116: ---------------------------------- Summary: RF 4.2 : jquery not generated for function Key: RF-12116 URL: https://issues.jboss.org/browse/RF-12116 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: JBoss 7.1 /RF4.2 Reporter: Adrien Adrien This code doesn t generate javascript expected <rich:jQuery name="selectNewMsg" query="addClass('curmsg');" /> Code generated in html page <script type="text/javascript">selectNewMsgee = RichFaces.jQuery.createFunction({"query":"addClass('curmsg');"} );</script> Expected something like : <script type="text/javascript">//<![CDATA[ function selectNewMsg(elm, param) { var selector = ""; try { selector = eval(""); } catch (e) {} jQuery(elm || selector).parent().parent().addClass('curmsg'); } //]]></script> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
7
0 / 0

[JBoss JIRA] (RF-12071) a4j:outputPanel h:inputText render problem

by Abdullah İlhanlı (JIRA)

Abdullah İlhanlı created RF-12071: ------------------------------------- Summary: a4j:outputPanel h:inputText render problem Key: RF-12071 URL: https://issues.jboss.org/browse/RF-12071 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Abdullah İlhanlı Create dynamic screen with JSF is so hard and painfull. I used a4j:outputPanel so many times. Today i am trying to create dynamic screen based on combo selected value. When value is for example option1 it generate inputText, otherwise comboBox. But i face to rendered problem son many times. Problem is on submited object value. My problem code like these: <h:panelGrid columns="2" id="conditionKeyGrid"> <h:outputLabel value="#{msg['key.type.form']}" /> <h:selectOneMenu value="#{conditionKeyBean.conditionKey.compType}" valueChangeListener="#{conditionKeyBean.compTypeChanged}"> <f:selectItems value="#{conditionKeyBean.compTypeItem}" /> <a4j:ajax event="change" execute="@this" render="checkableLabel,checkableField" /> </h:selectOneMenu> <a4j:outputPanel id="checkableLabel"> <h:outputLabel value="#{msg['key.caption.form']}" rendered="#{conditionKeyBean.checkable}" /> </a4j:outputPanel> <a4j:outputPanel id="checkableField"> <h:panelGrid rendered="#{conditionKeyBean.checkable}"> <h:inputText value="#{conditionKeyBean.captionValue}" /> </h:panelGrid> </a4j:outputPanel> <h:panelGrid/> Problem detail: Captionvalue is unique in database. When exception is throwed from back end(JPA uniquness error). I pops up error to user. Then user edit captionValue and try to resubmit. But captionValue is not change, even user changed it. When i remove rendered="#{conditionKeyBean.checkable}" problem is solved. rendered is not working correctly i think. How can i solve this problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
7
0 / 0

[JBoss JIRA] (RF-12075) Kitchensink archetype - link for JBoss AS 7 project site is broken

by Juraj Huska (JIRA)

Juraj Huska created RF-12075: -------------------------------- Summary: Kitchensink archetype - link for JBoss AS 7 project site is broken Key: RF-12075 URL: https://issues.jboss.org/browse/RF-12075 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Trivial The link for JBoss AS 7 project site, which is suited in the find out more section is broken, and points to the: {noformat}http://localhost:8080/kitchen-sink-community/jboss.org/jbossas{noformat} It should point to _http://www.jboss.org/jbossas_ It is caused by missing http://www prefix. It is in the facelet page (about.xhtml), particularly line 16: {code:xml} <li><a href="jboss.org/jbossas">JBoss AS 7 project site</a></li> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
4
0 / 0

[JBoss JIRA] (RF-12066) Kitchensink archetype is not listed in the modules of the parent pom

by Juraj Huska (JIRA)

Juraj Huska created RF-12066: -------------------------------- Summary: Kitchensink archetype is not listed in the modules of the parent pom Key: RF-12066 URL: https://issues.jboss.org/browse/RF-12066 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Reporter: Juraj Huska Priority: Trivial The maven module `richfaces-archetype-kitchensink` is not listed in the parent pom.xml in the modules section. Therefore, can not be installed from the parent pom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2012