"Mark Lybarger" <[EMAIL PROTECTED]> writes:

I admit that I've looked at the validator some time ago and then it
looked to me like one big kludge. I don't know whether this has
changed (this was long before the first validator release) but the
fact that it seems to have been a part of Struts suggests, that it
should be stable and proven.

I don't know if someone has already combined commons-validator and
Turbine but I would be interested in code examples.

        Regards
                Henning

>doh, sorry.  s/commons-logging/commons-validator

>> -----Original Message-----
>> From: Mark Lybarger 
>> Sent: Tuesday, July 06, 2004 10:11 AM
>> To: 'Turbine Users List' (E-mail)
>> Subject: commons-logging with turbine
>> 
>> 
>> We're interested in using commons-logging flexability with 
>> our turbine applications. We're currently using intake for 
>> validating our form information, but need more robust 
>> validation (cross field validations, etc).  Is the validator 
>> easily swapable? Is there documentation/experience out there 
>> of easily using the commons-validator (or a derivitive) with 
>> turbine?  Our velocity templates would also need to easily 
>> identify if a particular field is valid or not... thoughts? 
>> suggestions?
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> 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]


-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
[EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/

RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
   Linux, Java, perl, Solaris -- Consulting, Training, Development

"Fighting for one's political stand is an honorable action, but re-
 fusing to acknowledge that there might be weaknesses in one's
 position - in order to identify them so that they can be remedied -
 is a large enough problem with the Open Source movement that it
 deserves to be on this list of the top five problems."
                       -- Michelle Levesque, "Fundamental Issues with
                                    Open Source Software Development"

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to