[JBoss JIRA] (RF-13101) rich:select Method getSelectInputLabel is not working when using objects
by J W (JIRA)
[ https://issues.jboss.org/browse/RF-13101?page=com.atlassian.jira.plugin.s... ]
J W commented on RF-13101:
--------------------------
i have updated the workarround, because with the old one some errors could occur when using immediate buttons.
> rich:select Method getSelectInputLabel is not working when using objects
> ------------------------------------------------------------------------
>
> Key: RF-13101
> URL: https://issues.jboss.org/browse/RF-13101
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, component-selects
> Affects Versions: 4.3.2, 5.0.0.Alpha1
> Reporter: J W
> Labels: rich:select, select
> Fix For: 4.5.0.Alpha1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The condition of the if-statement in org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component) is not working with the string-representations of the items. If using cloned objects the equals method will return false, even if the items are the same, because the IDs are different.
> The method should use only the strings of the objects, similiar to how MyFaces has solved this (check workarround).
--
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
[JBoss JIRA] (RF-13101) rich:select Method getSelectInputLabel is not working when using objects
by J W (JIRA)
[ https://issues.jboss.org/browse/RF-13101?page=com.atlassian.jira.plugin.s... ]
J W updated RF-13101:
---------------------
Workaround Description:
Replace {code} AbstractSelectComponent select = (AbstractSelectComponent) component;
Object value = select.getSubmittedValue();
String label = null;
if (value == null) {
value = select.getValue();
if (value == null) {
value = ""; // Find Default-Values too.
}
}
value = value.toString(); // needed to compare string-sepresentations
Iterator<SelectItem> items = SelectUtils.getSelectItems(facesContext, component);
while (items.hasNext()) {
SelectItem item = items.next();
Object itemValue = item.getValue();
//prevent NPE
if (itemValue != null) {
if (value.equals(itemValue.toString())) {
label = item.getLabel();
break;
}
}
}
if (label == null) {
label = value.toString();
}
return label;
{code}
was:
Replace {code}org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component){code} with the following:
{code}public static String getSelectInputLabel(FacesContext facesContext, UIComponent component) {
String label = null;
String selectedValue = InputUtils.getInputValue(facesContext, component);
if (selectedValue != null) {
List<ClientSelectItem> convertedSelectItems = RichFacesSelectHelper.getConvertedSelectItems(facesContext, component);
for (ClientSelectItem clientSelectItem : convertedSelectItems) {
if (selectedValue.equals(clientSelectItem.getConvertedValue())) {
label = clientSelectItem.getLabel();
break;
}
}
}
return label;
{code}
> rich:select Method getSelectInputLabel is not working when using objects
> ------------------------------------------------------------------------
>
> Key: RF-13101
> URL: https://issues.jboss.org/browse/RF-13101
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, component-selects
> Affects Versions: 4.3.2, 5.0.0.Alpha1
> Reporter: J W
> Labels: rich:select, select
> Fix For: 4.5.0.Alpha1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The condition of the if-statement in org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component) is not working with the string-representations of the items. If using cloned objects the equals method will return false, even if the items are the same, because the IDs are different.
> The method should use only the strings of the objects, similiar to how MyFaces has solved this (check workarround).
--
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
[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 Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina commented on RF-13107:
-------------------------------------
I have attached reproducer, that shows the problem I described above. Tab panel with two tabs on each there is rich:message, when sending an ajax it says "During update: vertragsAuswahl:j_idt24 not found" where the ID is the rich:message in the non-visible tab.
> 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
>
>
> 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
[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 Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina updated RF-13107:
--------------------------------
Attachment: reproducer_ajax.zip
> 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
>
>
> 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
[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 Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina commented on RF-13107:
-------------------------------------
The customer is using switchType = "ajax" already and is experiencing the issue. However in a clean project it works just fine.
> 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
>
>
> 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
[JBoss JIRA] (RF-13098) Regression: mediaOutput broken for CDI MediaData beans
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13098?page=com.atlassian.jira.plugin.s... ]
Matej Novotny reassigned RF-13098:
----------------------------------
Assignee: (was: Matej Novotny)
> Regression: mediaOutput broken for CDI MediaData beans
> ------------------------------------------------------
>
> Key: RF-13098
> URL: https://issues.jboss.org/browse/RF-13098
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3
> Reporter: Marek Schmidt
> Labels: regression
>
> https://issues.jboss.org/browse/RF-13089 introduced a regression for a4j:mediaOutput component
> Having a
> {code}
> <a4j:mediaOutput element="img" cacheable="true" session="true" createContent="#{mediaBean.paint}" value="#{mediaData}" mimeType="image/jpeg"/>
> {code}
> with mediaData being a CDI bean, e.g.
> {code}
> @javax.inject.Named("mediaData")
> @javax.enterprise.context.RequestScoped
> public class MediaData implements Serializable
> {code}
> the following exception occurs:
> {code}10:39:27,997 SEVERE [org.richfaces.log.Resource] (http-/127.0.0.1:8080-1) Input error for deserialize data : java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.bean.proxy.util.SerializableClientProxy
> at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:93) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) [rt.jar:1.7.0_25]
> at org.richfaces.util.Util.decodeObjectData(Util.java:237) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {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
[JBoss JIRA] (RF-13098) Regression: mediaOutput broken for CDI MediaData beans
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13098?page=com.atlassian.jira.plugin.s... ]
Matej Novotny edited comment on RF-13098 at 8/12/13 3:18 AM:
-------------------------------------------------------------
I have verified this issue according to description on this page.
I have manages to reproduce the exception. CDI bean which extends Serializable throws the above mentioned expection. However CDI bean which extends SerializableResource does not throw any exception.
Source code can be found here: [https://github.com/richfaces/richfaces-qa/tree/RF-13098]
Steps to reproduce:
1) Deploy metamer on Jboss AS 7.1.1.Final
2) Load this page: [http://localhost:8080/metamer/faces/components/a4jMediaOutput/rf13098.xhtml]
3) Only one image shows, the other one causes exception. See the exception on the console.
Can I do something more with this issue?
was (Author: manovotn):
I have verified this issue according to description on this page.
I have manages to reproduce the exception. CDI bean which extends Serializable throws the above mentioned expection. However CDI bean which extends SerializableResource does not throw any exception.
Source code can be found here: [https://github.com/richfaces/richfaces-qa/tree/RF-13098]
Steps to reproduce:
1) Deploy metamer on Jboss AS 7.1.1.Final
2) Load this page: [http://localhost:8080/metamer/faces/components/a4jMediaOutput/rf13098.xhtml]
3) Only one image shows, the other one causes exception. See the exception on the console.
> Regression: mediaOutput broken for CDI MediaData beans
> ------------------------------------------------------
>
> Key: RF-13098
> URL: https://issues.jboss.org/browse/RF-13098
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3
> Reporter: Marek Schmidt
> Assignee: Matej Novotny
> Labels: regression
>
> https://issues.jboss.org/browse/RF-13089 introduced a regression for a4j:mediaOutput component
> Having a
> {code}
> <a4j:mediaOutput element="img" cacheable="true" session="true" createContent="#{mediaBean.paint}" value="#{mediaData}" mimeType="image/jpeg"/>
> {code}
> with mediaData being a CDI bean, e.g.
> {code}
> @javax.inject.Named("mediaData")
> @javax.enterprise.context.RequestScoped
> public class MediaData implements Serializable
> {code}
> the following exception occurs:
> {code}10:39:27,997 SEVERE [org.richfaces.log.Resource] (http-/127.0.0.1:8080-1) Input error for deserialize data : java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.bean.proxy.util.SerializableClientProxy
> at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:93) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) [rt.jar:1.7.0_25]
> at org.richfaces.util.Util.decodeObjectData(Util.java:237) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {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
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Louis Parisi (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Louis Parisi updated RF-13127:
------------------------------
Summary: onvalid and oninvalide pass wrong element when using rich:element with String field (was: onvalid and oninvalide pass wrong element when using rich:client with String field)
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but always returns the element from row zero when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> <h:inputText value="#\{myBean.myField}" id="myField">
> <rich:validator oninvalid="valueModifiedAndError(#\{rich:element('myField')})"
> onvalid="valueModified(#\{rich:element('myField')})"/>
> </h:inputText>
> Some other tests I did while trying to debug are:
> - I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> - The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:client with String field
by Louis Parisi (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Louis Parisi updated RF-13127:
------------------------------
Description:
I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but always returns the element from row zero when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
<h:inputText value="#\{myBean.myField}" id="myField">
<rich:validator oninvalid="valueModifiedAndError(#\{rich:element('myField')})"
onvalid="valueModified(#\{rich:element('myField')})"/>
</h:inputText>
Some other tests I did while trying to debug are:
- I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
- The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
was:
I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but always returns the element from row zero when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
<h:inputText value="#{myBean.myField}" id="myField">
<rich:validator oninvalid="valueModifiedAndError(#{rich:element('myField')})"
onvalid="valueModified(#{rich:element('myField')})"/>
</h:inputText>
Some other tests I did while trying to debug are:
- I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
- The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
> onvalid and oninvalide pass wrong element when using rich:client with String field
> ----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but always returns the element from row zero when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> <h:inputText value="#\{myBean.myField}" id="myField">
> <rich:validator oninvalid="valueModifiedAndError(#\{rich:element('myField')})"
> onvalid="valueModified(#\{rich:element('myField')})"/>
> </h:inputText>
> Some other tests I did while trying to debug are:
> - I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> - The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:client with String field
by Louis Parisi (JIRA)
Louis Parisi created RF-13127:
---------------------------------
Summary: onvalid and oninvalide pass wrong element when using rich:client with String field
Key: RF-13127
URL: https://issues.jboss.org/browse/RF-13127
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.3.3
Reporter: Louis Parisi
I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but always returns the element from row zero when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
<h:inputText value="#{myBean.myField}" id="myField">
<rich:validator oninvalid="valueModifiedAndError(#{rich:element('myField')})"
onvalid="valueModified(#{rich:element('myField')})"/>
</h:inputText>
Some other tests I did while trying to debug are:
- I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
- The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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