Hi Niall, Thanks for responding.. I thought more people would have done so but perhaps I am asking an obvious question to which I have missed the answer?
The client is determined using the user's ID and Role.. It's a fairly typical authentication system where a user has roles and privileges. If they are in the CLIENT role, a link table determines which client the user is associated with. At this time, each user can have only one role and a single client but the system was designed to allow each user to have multiple roles (ADMIN, CLIENT, etc) and then multiple associations to each role.. >From what I have read so far, it looks like Struts' model may be a little tied to a certain way of thinking to implement this level of flexibility. I have looked at another project from Open Symphony that appears to allow for this though... I would obviously rather use struts due to it being the most widely used and documented... Matthew. -----Original Message----- From: Niall Pemberton [mailto:[EMAIL PROTECTED] Sent: 24 March 2004 11:31 To: Struts Users Mailing List Subject: Re: Struts Validator Whats missing from your question is how are you identifying which "client" a user belongs to? Niall ----- Original Message ----- From: "Matthew Clark" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 22, 2004 12:09 PM Subject: Struts Validator Hi there, I am new to Struts and this mailing list but by no means new to Java. I have been reading the "Struts in Action" book and taken a quick look at the API etc and have a simple question regarding the Validator in my environment. We are an Application Service Provider and serve well over 1000 clients (who in turn each have between 5 and 1000 end users using the system). Although each client uses the same core application, they can have very different views of data and input forms and may have very different validation requirements. Is it possible to specify validation config at runtime when using the struts validator? So each of our clients could have a configuration file that specified which validation XML file to use for a given input form? We could use a different form for each user but that would be inefficient and a maintenance nightmare.. I want to call the same form/servlet but have it display a different look & feel and have different validation rules client side and server side. At the moment, the validation is very much tied to the presentation layer and I want to decouple it. This is really the last obstacle standing in the way of our migration to a pure java solution using Struts.. The use of the validator would simplify our solution a great deal and I will also be looking into the possibility of our clients creating their own validation configuration files (using a web interface of some sort) any help or advice would be appreciated. Regards, Matthew --------------------------------------------------------------------- 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]
