Sorry forgot to mention, I set it up with struts 1.1 (not the beta tho!)

Yes you can use bugzilla to look for an old bug. A key word search is probably easiest but the search parameters on bugzilla can be set quite extensively.

Sympathy for your situation. What a pain.

Adam

[EMAIL PROTECTED] on 13/10/05 10:50, wrote:
Thanks Adam.

I'm sure no one will be able to verify whether this was a bug in 1.1b2 (why I'm using b2 is a looong story, but I'm stuck with it).

Is there a way I can find out from Bugzilla whether this was a bug that was fixed in later versions?


----- Original Message -----
From Adam Hardy <[EMAIL PROTECTED]>
Date Wed, 12 Oct 2005 21:02:00 +0100 To Struts Users Mailing List <user@struts.apache.org> Subject Re: Validation Configuration for Multiple Modules

[EMAIL PROTECTED] on 11/10/05 07:20, wrote:

I'm using *Struts 1.1* to build an application with multiple Struts modules.

I put my validations for each module in a seperate validations.xml file. For example, I have validations-a.xml for module a and validations-b.xml for module b. I then found out that although the validations are working perfectly for module a, they're not working

at
all for module b.

I kept tracing the problem even in the Struts source code, and

reached
the conclusion that the validations for one module overwrite the

other.
It seems that the FormSet objects are stored in a HashMap with the locale as the key, and since both formsets have the same locale, one

of
them overwrites the other. Are my conclusions correct or am I doing something wrong? Does that mean I have to put all my validations for the whole application in one file?


Presumably in each module's struts-config, your validator plugin node refers to the correct validation.xml?

I doubt it's a bug since I successfully set up modularised struts with seperate validation.xml for each.



Adam




---------------------------------------------------------------------
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]

Reply via email to