January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12727) Metamer: rich:autocomplete: validationMessages example: ERROR status on submit, but missing validation messages [myFaces]

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-12727?page=com.atlassian.jira.plugin.s... ] Ján Jamrich updated RF-12727: ----------------------------- Labels: myfaces (was: ) > Metamer: rich:autocomplete: validationMessages example: ERROR status on submit, but missing validation messages [myFaces] > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12727 > URL: https://issues.jboss.org/browse/RF-12727 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0.CR1 > Metamer 4.3.0.20130114-CR1 > Weld Servlet (Uber Jar) 20120106-1159 > Apache Tomcat 7.0.32 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.95 @ Linux i686 > Metamer: > 2023898d4b163a889955c1d028149a31 metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war > Reporter: Ján Jamrich > Labels: myfaces > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12727) Metamer: rich:autocomplete: validationMessages example: ERROR status on submit, but missing validation messages [myFaces]

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-12727?page=com.atlassian.jira.plugin.s... ] Ján Jamrich updated RF-12727: ----------------------------- Summary: Metamer: rich:autocomplete: validationMessages example: ERROR status on submit, but missing validation messages [myFaces] (was: Metamer: rich:autocomplete: validationMessages example: ERROR status on submit, but missing validation messages) > Metamer: rich:autocomplete: validationMessages example: ERROR status on submit, but missing validation messages [myFaces] > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12727 > URL: https://issues.jboss.org/browse/RF-12727 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0.CR1 > Metamer 4.3.0.20130114-CR1 > Weld Servlet (Uber Jar) 20120106-1159 > Apache Tomcat 7.0.32 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.95 @ Linux i686 > Metamer: > 2023898d4b163a889955c1d028149a31 metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war > Reporter: Ján Jamrich > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12727) Metamer: rich:autocomplete: validationMessages example: ERROR status on submit, but missing validation messages

by Ján Jamrich (JIRA)

Ján Jamrich created RF-12727: -------------------------------- Summary: Metamer: rich:autocomplete: validationMessages example: ERROR status on submit, but missing validation messages Key: RF-12727 URL: https://issues.jboss.org/browse/RF-12727 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.3.0.CR1 Environment: RichFaces 4.3.0.CR1 Metamer 4.3.0.20130114-CR1 Weld Servlet (Uber Jar) 20120106-1159 Apache Tomcat 7.0.32 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 23.0.1271.95 @ Linux i686 Metamer: 2023898d4b163a889955c1d028149a31 metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war Reporter: Ján Jamrich -- 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, 11 months

1
0
0 / 0

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

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12649?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12649. ---------------------------- Verified that tests were added. > 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.CR1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12670. ---------------------------- > JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION > --------------------------------------------------------------------------------------------------- > > Key: RF-12670 > URL: https://issues.jboss.org/browse/RF-12670 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.0.M3 > Reporter: Dupont Dupont > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a > {code} > java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION > at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387) > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at javax.faces.component.UIForm.visitTree(UIForm.java:269) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90) > at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at > {code} > RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor. > See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-12670: ---------------------------------- Verified with showcase being deployed on {{JBoss AS 6}}. I did not notice the mentioned error. Thus closing. > JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION > --------------------------------------------------------------------------------------------------- > > Key: RF-12670 > URL: https://issues.jboss.org/browse/RF-12670 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.0.M3 > Reporter: Dupont Dupont > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a > {code} > java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION > at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387) > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at javax.faces.component.UIForm.visitTree(UIForm.java:269) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90) > at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at > {code} > RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor. > See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-12671: ---------------------------------- Verified on the user provided sample code. Therefore closing. > dropTarget does not work inside dynamic tabs when switchType is ajax or server > ------------------------------------------------------------------------------ > > Key: RF-12671 > URL: https://issues.jboss.org/browse/RF-12671 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.3.0.M3 > Reporter: Ken H > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > The following works fine: > {code} > <rich:tabPanel switchType="client"> > <a4j:repeat value="#{bean.thingsToIterate}" var="thing"> > <rich:tab header="Tab #{thing}"> > <rich:panel style="width: 100px;"> > <rich:dragSource dragValue="drag-#{thing}" type="term" /> > drag #{thing} > </rich:panel> > <rich:panel style="width: 100px;"> > <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" /> > drop #{thing} > </rich:panel> > </rich:tab> > </a4j:repeat> > </rich:tabPanel> > public void processDrop(DropEvent evt) { > log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue()); > } > {code} > However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12671) dropTarget does not work inside dynamic tabs when switchType is ajax or server

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12671. ---------------------------- > dropTarget does not work inside dynamic tabs when switchType is ajax or server > ------------------------------------------------------------------------------ > > Key: RF-12671 > URL: https://issues.jboss.org/browse/RF-12671 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.3.0.M3 > Reporter: Ken H > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > The following works fine: > {code} > <rich:tabPanel switchType="client"> > <a4j:repeat value="#{bean.thingsToIterate}" var="thing"> > <rich:tab header="Tab #{thing}"> > <rich:panel style="width: 100px;"> > <rich:dragSource dragValue="drag-#{thing}" type="term" /> > drag #{thing} > </rich:panel> > <rich:panel style="width: 100px;"> > <rich:dropTarget dropValue="drop-#{thing}" acceptedTypes="term" dropListener="#{bean.processDrop}" execute="@form" render="@form" /> > drop #{thing} > </rich:panel> > </rich:tab> > </a4j:repeat> > </rich:tabPanel> > public void processDrop(DropEvent evt) { > log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal: "+evt.getDropValue()); > } > {code} > However, changing the switch type to ajax or server results in processDrop not being called. The POST data appears to be identical. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12726) Metamer: rich:placeholder & input and textarea: error status on submit, output not updated

by Ján Jamrich (JIRA)

Ján Jamrich created RF-12726: -------------------------------- Summary: Metamer: rich:placeholder & input and textarea: error status on submit, output not updated Key: RF-12726 URL: https://issues.jboss.org/browse/RF-12726 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.0.CR1 Environment: RichFaces 4.3.0.CR1 Metamer 4.3.0.20130114-CR1 JBoss Application Server: Weld Integration 7.1.1.Final JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 23.0.1271.95 @ Linux i686 Metamer: cfd26771e2c1d9e693fe6844055eba27 metamer-4.3.0.20130114-CR1-jbas71.war NOTE: it is working correctly with MyFaces Reporter: Ján Jamrich Input and textarea examples using placeholder doesn't work correctly. When submit empty form, the Error status appears in Metamer. When submit non empty form, output values are not updated, and the Error status appears instead. But using MyFaces, textarea works correctly, and for input example no Error status, but output values are not update (but have to make sure that there is nothing wrong with outputs, since there are 3 inputs and just 2 outputs, which is a little bit confusing for me) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12726) Metamer: rich:placeholder & input and textarea: error status on submit, output not updated

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-12726?page=com.atlassian.jira.plugin.s... ] Ján Jamrich updated RF-12726: ----------------------------- Steps to Reproduce: 1. open faces/components/richPlaceholder/input.xhtml 2. open faces/components/richPlaceholder/inputTextarea.xhtml > Metamer: rich:placeholder & input and textarea: error status on submit, output not updated > ------------------------------------------------------------------------------------------ > > Key: RF-12726 > URL: https://issues.jboss.org/browse/RF-12726 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0.CR1 > Metamer 4.3.0.20130114-CR1 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.95 @ Linux i686 > Metamer: > cfd26771e2c1d9e693fe6844055eba27 metamer-4.3.0.20130114-CR1-jbas71.war > NOTE: it is working correctly with MyFaces > Reporter: Ján Jamrich > > Input and textarea examples using placeholder doesn't work correctly. > When submit empty form, the Error status appears in Metamer. > When submit non empty form, output values are not updated, and the Error status appears instead. > But using MyFaces, textarea works correctly, and for input example no Error status, but output values are not update (but have to make sure that there is nothing wrong with outputs, since there are 3 inputs and just 2 outputs, which is a little bit confusing for me) -- 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, 11 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 January 2013