April 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12099) Kitchensink archetype - mobile demo - loading the about page causes error on the server side

by Juraj Huska (JIRA)

Juraj Huska created RF-12099: -------------------------------- Summary: Kitchensink archetype - mobile demo - loading the about page causes error on the server side Key: RF-12099 URL: https://issues.jboss.org/browse/RF-12099 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Environment: mobile demo for project generated by Kitchensink archetype Reporter: Juraj Huska Priority: Minor After clicking on the link(small blue i in white circle) which should point to the about page, following error is thrown on the server side: {code} 16:15:07,894 SEVERE [org.richfaces.log.Context] (http--0.0.0.0-8080-4) /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null: javax.el.PropertyNotFoundException: /resources/components/memberForm.xhtml @19,62 value="#{cc.attrs.member.name}": Target Unreachable, 'member' returned null at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:100) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getConvertedValue(HtmlBasicInputRenderer.java:95) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.component.UIInput.getConvertedValue(UIInput.java:1030) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.validate(UIInput.java:960) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.executeValidate(UIInput.java:1233) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIInput.processValidators(UIInput.java:698) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:1214) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIForm.processValidators(UIForm.java:253) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.richfaces.context.PartialViewExecuteVisitCallback.visit(PartialViewExecuteVisitCallback.java:55) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at javax.faces.component.UIForm.visitTree(UIForm.java:381) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.richfaces.context.ExtendedPartialViewContextImpl.executeComponents(ExtendedPartialViewContextImpl.java:237) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialExecutePhase(ExtendedPartialViewContextImpl.java:217) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:196) [richfaces-core-impl-4.3.0-20120302.170417-5.jar:4.3.0-SNAPSHOT] at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1170) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:76) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22] {code} The about page is loaded successfully, however after next attempts to click on the same link results in loading blank page. -- 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

2
4
0 / 0

[JBoss JIRA] (RF-12101) Kitchensink example - rendering of the rich:messages is quite inconsistent

by Juraj Huska (JIRA)

Juraj Huska created RF-12101: -------------------------------- Summary: Kitchensink example - rendering of the rich:messages is quite inconsistent Key: RF-12101 URL: https://issues.jboss.org/browse/RF-12101 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Environment: app generated by the kitchensink archetype browser: Chrome, Firefox, mobile devices browser(iPhone) Reporter: Juraj Huska Priority: Minor The rich:messages tag generates messages on an inconsistent way, I think. They are rendered after BLUR event is done on the input, and the problem is that sometimes they are rendered and sometimes not. They also tend to disappear after clicking on Register button, another problem is that they are sometimes stacked, so in some cases there are more messages than inputs. IMHO the rich:messages tag should be removed, since there is already rich:message generated for every input, and they are not giving additional information, on the contrary they are misleading. -- 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

2
6
0 / 0

[JBoss JIRA] (RF-12155) Kitchensink archetype - missing org.richfaces.bom.version property in generated pom.xml

by Juraj Huska (JIRA)

Juraj Huska created RF-12155: -------------------------------- Summary: Kitchensink archetype - missing org.richfaces.bom.version property in generated pom.xml Key: RF-12155 URL: https://issues.jboss.org/browse/RF-12155 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.1.CR1 Environment: app generated by the kitchensink archetype 4.2.1-SNAPSHOT Reporter: Juraj Huska There is missing {code:xml}org.richfaces.bom.version{code} property in pom.xml generated by kitchensink archetype 4.2.1-SNAPSHOT. This change was introduced by [this|https://github.com/richfaces/archetypes/commit/f39c7fdd3002cf77259d9...] commit. The generated project can not be build without passing additional parameter, which was not the intention, I guess. -- 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

2
4
0 / 0

[JBoss JIRA] (RF-12100) Kitchensink archetype - mobile demo - adding new member causes rendering blank page

by Juraj Huska (JIRA)

Juraj Huska created RF-12100: -------------------------------- Summary: Kitchensink archetype - mobile demo - adding new member causes rendering blank page Key: RF-12100 URL: https://issues.jboss.org/browse/RF-12100 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: archetype Affects Versions: 4.2.0.Final Environment: mobile demo for Kitchensink archetype Reporter: Juraj Huska Attachments: blank.png When you add new member, either from mobile or from desktop kitchensink demo, *all loaded mobile demos* will be (after retrieving the push from the server) rendering the blank page. As blank, I mean just the header of the page, please see the screenshot. -- 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

2
5
0 / 0

[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

2
3
0 / 0

[JBoss JIRA] (RF-12128) mobile showcase - rich:dropDownMenu - can not select an item from menu on Android tablet

by Juraj Huska (JIRA)

Juraj Huska created RF-12128: -------------------------------- Summary: mobile showcase - rich:dropDownMenu - can not select an item from menu on Android tablet Key: RF-12128 URL: https://issues.jboss.org/browse/RF-12128 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu, mobile, showcase Affects Versions: 4.2.1.CR1 Environment: mobile device: Motorola Xoom Reporter: Juraj Huska It is not possible to select an item from rich:dropDownMenu, since when it is invoked, the menu is rendered only for a second, then it is collapsed again. Note that it works good at the same device correctly, with older releases, for example [here|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=dr...] -- 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

2
5
0 / 0

[JBoss JIRA] (RF-12129) mobile showcase - rich:contextMenu - selecting an item from menu causes JS error

by Juraj Huska (JIRA)

Juraj Huska created RF-12129: -------------------------------- Summary: mobile showcase - rich:contextMenu - selecting an item from menu causes JS error Key: RF-12129 URL: https://issues.jboss.org/browse/RF-12129 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.2.1.CR1 Environment: mobile devices: Motorola Xoom, iPad Reporter: Juraj Huska Selecting an item from rich:contextMenu causes a JS error, and the expected action is not done. The error: {code} JavaScript Error on Line 4 http://10.200.130.149:8080/showcase/#contextMenu:simple TypeError: Result of expresion 'pic' [null] is not a object. {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

3
5
0 / 0

[JBoss JIRA] (RF-12127) mobile showcase - rich:accordion - accordionItems have fixed height instead of reflecting the actual content height

by Juraj Huska (JIRA)

Juraj Huska created RF-12127: -------------------------------- Summary: mobile showcase - rich:accordion - accordionItems have fixed height instead of reflecting the actual content height Key: RF-12127 URL: https://issues.jboss.org/browse/RF-12127 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-output, mobile, showcase Affects Versions: 4.2.1.CR1 Environment: mobile devices: iPhone, Motorola Xoom Reporter: Juraj Huska Priority: Trivial The accordionItems in the demo for rich:accordion component have fixed height and do not reflect the height of the nested content. Then it looks a little bit ugly. Please see the screenshot. -- 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

2
8
0 / 0

[JBoss JIRA] (RF-12162) Mobile Showcase: long page loading because of widdit.com

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12162?page=com.atlassian.jira.plugin.s... ] Jan Papousek deleted RF-12162: ------------------------------ > Mobile Showcase: long page loading because of widdit.com > -------------------------------------------------------- > > Key: RF-12162 > URL: https://issues.jboss.org/browse/RF-12162 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Jan Papousek > > It happens ofthen when I try to look at mobile version of Showcase in desktop browser. The page loading takes a big amount of time (10+ seconds) because of connection to widdit.com. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12162) Mobile Showcase: long page loading because of widdit.com

by Jan Papousek (JIRA)

Jan Papousek created RF-12162: --------------------------------- Summary: Mobile Showcase: long page loading because of widdit.com Key: RF-12162 URL: https://issues.jboss.org/browse/RF-12162 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.2.1.Final Reporter: Jan Papousek Attachments: mobile-showcase-page-loading.png It happens ofthen when I try to look at mobile version of Showcase in desktop browser. The page loading takes a big amount of time (10+ seconds) because of connection to widdit.com. -- 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

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2012