[ https://jira.jboss.org/jira/browse/JBAS-6572?page=com.atlassian.jira.plug... ] Stan Silvert commented on JBAS-6572: ------------------------------------ Can you post some more information on this? Where did you see this error? Please post the full message or stack trace in context. Thanks, Stan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6572?page=com.atlassian.jira.plug... ] Stan Silvert resolved JBAS-6572. -------------------------------- Resolution: Won't Fix In JSF 1.2_10 there was no serialVersionUID on the class. The serialVersionUID was added in JSF 1.2_11. So this kind of comparison is bound to fail whenever JSF is upgraded. For instance, if we upgraded JSF in the 4.2.x series it would become incompatible with an older version of 4.2.x. I don't think there is much we can do about this except know that going forward, the class will be compatible because the serialVersionUID has now been set. This particular validator is an add-on extension that happens to get bundled with Mojarra. It's not part of the JSF spec. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6572?page=com.atlassian.jira.plug... ] Shelly McGowan updated JBAS-6572: --------------------------------- I've excluded this class in the test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira