[ https://issues.apache.org/jira/browse/TOMAHAWK-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096530#comment-15096530 ]
Mike Kienenberger commented on TOMAHAWK-1679: --------------------------------------------- It would be better to ask questions on the MyFaces Discussion <us...@myfaces.apache.org> mailing list rather than in JIRA, especially since no one is actively working on Tomahawk development currently. Closing this as it's a question rather than an issue. > validateRegExpr Not Working in Weblogic 10.3.6 > ---------------------------------------------- > > Key: TOMAHAWK-1679 > URL: https://issues.apache.org/jira/browse/TOMAHAWK-1679 > Project: MyFaces Tomahawk > Issue Type: Bug > Components: Validators > Affects Versions: 1.1.9 > Environment: JDK 1.7, Weblogic 11g (10.3.6), tomahawk-1.1.9, > myfaces-api-1.1.6, myfaces-impl-1.1.6, jstl-1.1.0 > Reporter: Julie Luo > > We have an existing application that uses the Tomahawk t:validateRegExpr > validator to validate a numeric field. > The following code is working successfully in the OC4J application server. > After we migrated the application to weblogic 11g (10.3.6), the same code > no longer works. > <h:panelGroup> > <h:inputText id="Batch_Size" value="#{managePropertiesBean.batchSize}" > size="15" maxlength="3" required="true"> > <t:validateRegExpr pattern='^([1-9]|[1-9][0-9]|[1-9][0-9][0-9])\$' > detailMessage='#{"{0} is not valid in this field." }'/> > > </h:inputText> > <f:verbatim> </f:verbatim> > <t:message id="batchSizeValueError" for="Batch_Size" > styleClass="errorSpecific"/> > </h:panelGroup> > No matter what I type in this field, it fails the validation even when it's a > number like 11. It's almost like validateRegExpr is not functioning at all. > I have also tried using a newer version of Tomahawk > (tomahawk20-1.1.15-20130903.221103-12), the problem still exists. > Can someone provide some advice/suggestions about this? > Thank you. > Julie -- This message was sent by Atlassian JIRA (v6.3.4#6332)