Re: Terracotta and PatternValidator
> I have run into the same issue. I solved it with brute force by > writing a regexp to capture all the inner classes from the Pattern > class and inserting them into my terracotta config's dso section. It > is not the most elegant solution but it will get you past this issue. Why not just writing a validator that keeps a reference to the regex string rather than the Pattern, and create the pattern object just when you need it? There is some overhead in that, but it shouldn't be too bad considering that you'll only use a few of those objects a request at most? Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Terracotta and PatternValidator
Richard, I have run into the same issue. I solved it with brute force by writing a regexp to capture all the inner classes from the Pattern class and inserting them into my terracotta config's dso section. It is not the most elegant solution but it will get you past this issue. Good luck, Ryan On Mon, May 12, 2008 at 11:44 AM, richardwilko <[EMAIL PROTECTED]> wrote: > > Hi, > > I've come across a problem with the wicket-terracotta intergration. > > If you have a PatternValidator (like EmailAddressValidator) attached to an > input then terracotta throws a non portable exception because > java.util.regex.Pattern isnt in the additional-boot-jar-classes bit of the > config xml. > > I tried to add this myself but it turns out that Pattern has loads of > internal classes that it uses and so it is a pain. > > As PatternValidator is a wicket class it would seem that these changes > should either go into the wicket-terracotta integration project's xml config > or that the Pattern in PatternValidator should be made transient and the > code adapted to take care of it. > > Has anyone else got round this problem? I'm thinking for now I should write > my own Validator that does hold the Pattern object. > > Cheers Richard > -- > View this message in context: > http://www.nabble.com/Terracotta-and-PatternValidator-tp17189868p17189868.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Terracotta and PatternValidator
Hi, I've come across a problem with the wicket-terracotta intergration. If you have a PatternValidator (like EmailAddressValidator) attached to an input then terracotta throws a non portable exception because java.util.regex.Pattern isnt in the additional-boot-jar-classes bit of the config xml. I tried to add this myself but it turns out that Pattern has loads of internal classes that it uses and so it is a pain. As PatternValidator is a wicket class it would seem that these changes should either go into the wicket-terracotta integration project's xml config or that the Pattern in PatternValidator should be made transient and the code adapted to take care of it. Has anyone else got round this problem? I'm thinking for now I should write my own Validator that does hold the Pattern object. Cheers Richard -- View this message in context: http://www.nabble.com/Terracotta-and-PatternValidator-tp17189868p17189868.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
