August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13033) inputNumberSlider, inputNumberSpinner: @label is not working

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13033?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13033: ------------------------------- Sprint: RichFaces 4.3.4 Sprint 1 > inputNumberSlider, inputNumberSpinner: @label is not working > ------------------------------------------------------------ > > Key: RF-13033 > URL: https://issues.jboss.org/browse/RF-13033 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, doc > Affects Versions: 3.3.2.CR1, 4.3.2, 5.0.0.Alpha1 > Reporter: Jiří Štefek > Fix For: 4.3.4 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > These two components have attribute @label. > And it doesn't work -- there is no sign of it on the page source. > Where should it be displayed? Should it replace the default value? > Or should this attribute be deleted? > Please also update the VDL-DOC in all cases. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13017: ------------------------------- Sprint: RichFaces 4.3.4 Sprint 1 > richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible > ------------------------------------------------------- > > Key: RF-13017 > URL: https://issues.jboss.org/browse/RF-13017 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.2 > Reporter: Himanshu Bhardwaj > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > In the bom of RichFaces, the version of JSF-API being used is > {code} > <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api> > {code} > > but the version of JSF-IMPL put in use is: > {code} > <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl> > {code} > > Both the version don't seem to go together. Got the following stack-trace: > > {code} > SEVERE: ContainerBase.addChild: start: > org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]] > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977) > at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655) > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > Caused by: java.lang.NullPointerException > at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281) > at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107) > at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115) > at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > ... 11 more > > > May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR > SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war > java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]] > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977) > at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655) > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > {code} > > I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this error. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13016) Archetypes should be removed from 4.3 build and dist

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13016?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13016: ------------------------------- Sprint: RichFaces 4.3.4 Sprint 1 > Archetypes should be removed from 4.3 build and dist > ---------------------------------------------------- > > Key: RF-13016 > URL: https://issues.jboss.org/browse/RF-13016 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 4.3.2 > Reporter: Lukáš Fryč > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Archetypes will now have independent release cycle. -- 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, 3 months

1
0
0 / 0

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

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12784: ------------------------------- Sprint: 4.3.1 Sprint - Fixes, 4.3.2 Sprint 1, RichFaces 4.3.4 Sprint 1 (was: 4.3.1 Sprint - Fixes, 4.3.2 Sprint 1) > 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.4, 5.0.0.Alpha2 > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11469: ------------------------------- Sprint: RichFaces 4.3.4 Sprint 1 > autocomplete method does not resolve bean if ui:included > -------------------------------------------------------- > > Key: RF-11469 > URL: https://issues.jboss.org/browse/RF-11469 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Final > Reporter: u j > Priority: Minor > Fix For: 4.3.4, 5-Tracking > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include. > {code} > <ui:include src="/searchlocation.xhtml"> > <ui:param name="bean" value="#{searchBean}" /> > </ui:include> > {code} > searchlocation.xhtml contains: > {code} > <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" /> > {code} > The value binding works, but the binding in the autocompleteMethod gives: > {code} > 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null > at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13125: ------------------------------- Component/s: component-a4j-core > a4j:log does swallow the message from jsf.js's sendError method > --------------------------------------------------------------- > > Key: RF-13125 > URL: https://issues.jboss.org/browse/RF-13125 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.3, 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Fix For: 4.3.4, 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > {code:title=jsf.js:2220} > } catch (ex) { > sendError(request, context, "malformedXML", ex.message); > return; > } > {code} > The ex.message is not shown in output of a4j:log. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13125: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > a4j:log does swallow the message from jsf.js's sendError method > --------------------------------------------------------------- > > Key: RF-13125 > URL: https://issues.jboss.org/browse/RF-13125 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.3, 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Fix For: 4.3.4, 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > {code:title=jsf.js:2220} > } catch (ex) { > sendError(request, context, "malformedXML", ex.message); > return; > } > {code} > The ex.message is not shown in output of a4j:log. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13119) kitchensink-rf test-ds.xml does not use a unique datasource JNDI name

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13119?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13119: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > kitchensink-rf test-ds.xml does not use a unique datasource JNDI name > --------------------------------------------------------------------- > > Key: RF-13119 > URL: https://issues.jboss.org/browse/RF-13119 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Fix For: 4.3.4 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The richfaces-quickstarts/kitchensink-rf/src/test/resources/test-ds.xml uses the same datasource JNDI name and connection URL that the kitchensink quickstart test file uses: > <datasource jndi-name="java:jboss/datasources/KitchensinkQuickstartTestDS" > <connection-url>jdbc:h2:mem:kitchensink-quickstart-test;DB_CLOSE_DELAY=-1</connection-url> > This should be changed to a unique name, for example: > <datasource jndi-name="java:jboss/datasources/KitchensinkrfQuickstartTestDS" > <connection-url>jdbc:h2:mem:kitchensink-rf-quickstart-test;DB_CLOSE_DELAY=-1</connection-url> -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13107: ------------------------------- Original Estimate: 1 hour, 30 minutes Remaining Estimate: 1 hour, 30 minutes > rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error > ----------------------------------------------------------------------------------------------------------------------- > > Key: RF-13107 > URL: https://issues.jboss.org/browse/RF-13107 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.2 > Reporter: Jonáš Trantina > Assignee: Brian Leathem > Fix For: 4.3.4 > > Attachments: bug_reproducer.zip, reproducer_ajax.zip > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown. > Note that: > 1) switchType must be set to server to ensure the A's rich:message is really not on the page. > 2) button in B must re-render only content of B > This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered). > Please find the enclosed reproducer. > Snipper: > {code:xml} > <h:form> > <rich:tabPanel switchType="server"> > <rich:tab> > <h:inputText id="surname" value="#{richBean.surname}"> > <f:validateLength minimum="10"/> > </h:inputText> > <rich:message for="surname"/> > </rich:tab> > <rich:tab> > <h:panelGroup id="content"> > <h:inputText id="name" value="#{richBean.name}"> > <f:validateLength minimum="6"/> > </h:inputText> > <rich:message for="name"/> > </h:panelGroup> > <a4j:commandButton value="Submit" execute="content" render="content" /> > </rich:tab> > </rich:tabPanel> > </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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13113) org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13113?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13113: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0 > ----------------------------------------------------------------------------- > > Key: RF-13113 > URL: https://issues.jboss.org/browse/RF-13113 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Tomas Repel > Assignee: Brian Leathem > Fix For: 4.3.4 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Description of problem: > org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0:3.0.1.Final-redhat-1, which is available only in jboss-eap-6.0.1-maven repository. > This causes failure when building Seam distribution from sources. In EAP 6.1 repository there is available org.jboss.spec : jboss-javaee-web-6.0 : 3.0.2.Final-redhat-3 -- 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, 3 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 August 2013