I had some email validation code and it would die on strings larger than
30-45 characters in length with my pattern match with regexp-1.3
String basicAddress = "^\\w+([_]*[\\-\\.]?[_]*\\w+[_]*)[EMAIL
PROTECTED]([_]*[\\-\\.]?[_]*\\w+[_]*)*(\\.\\w{1}\\w+)+$";
no more problems with the ORO class
I also finished merging in the org.xbill.DNS.*; package for domain
validation now the same as scarab is using.
works like a charm
Jeff Painter
On Thu, 27 May 2004, Mark Lybarger wrote:
> could you elaborate on the "pesky old problem"?
>
> > -----Original Message-----
> > From: Jeffery Painter [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, May 27, 2004 10:54 AM
> > To: Turbine Users List; [EMAIL PROTECTED]
> > Subject: Re: turbine regexp library usage
> >
> >
> >
> > Thanks for the ORO tip... I had not really looked at ORO
> > before but it was
> > a pretty simple switch to move all my regexp code to use ORO
> > libraries
> > instead and got rid of a pesky old problem that had been
> > lingering for
> > sometime now.
> >
> > I swapped out the regexp libs and put ORO in my old 2.2 app
> > without any
> > hiccups
> >
> > YMMV!
> >
> > Jeff Painter
> >
> >
> > On Thu, 27 May 2004, Henning P. Schmiedehausen wrote:
> >
> > > "Mark Lybarger" <[EMAIL PROTECTED]> writes:
> > >
> > > >i noticed that (i believe) the tdk 2.1 included the
> > jakarta regexp library:
> > >
> > > >jakarta-regexp-1.3-dev.jar
> > >
> > > As far as I know, regexp is dead and for 2.3 I replaced it
> > with oro in
> > > the intake service. Don't know if it is actually still used anywhere
> > > else in the code.
> > >
> > > > while the tdk 2.2_01 seems to include the 1.2 version of that
> > > > library. It's in the server/lib area, but seems to be used by the
> > > > intake stuff for handling regular expression type rules. we're
> > > > using the tdk 2.1, and notice sporadic error message
> > related to this
> > > > library (using the 1.3-dev.jar). the error message seem to be
> > > > logged when attempting to parse or compile a regular expression in
> > > > our intake.xml, and only are noticed when we have multiple users
> > > > hitting the system (during performance/load testing).
> > >
> > > When I was working on the 2.2 code, I wasn't able to get
> > anywhere with
> > > regexp and it was IMHO a constant source of problems, exceptions and
> > > general grief without any response from the (then) still semi-active
> > > project. So at some point we discussed this briefly on the dev-list
> > > and found a consent to drop it in favour of oro.
> > >
> > > For the 2.2 code, sorry. Don't know about this anymore,
> > it's already too
> > > far in the past. 8-/
> > >
> > > Regards
> > > Henning
> > >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
