Sorry, read "logicsheet" instead of "action". Don't know where my mind has gone ...
Lajos Lajos Moczar wrote: > There is already an action included in Cocoon that does validation. > What's nice is that you define the validation parameters in a definition > files and the action takes care of applying them. I suppose you might > need to define your own action to actually send the data where you want it. > > Lajos > > galatea.com > Cocoon training, consulting & support > > > [EMAIL PROTECTED] wrote: > >> So how would I accomplish this with Cocoon. Could I just create a >> component for doing that validation and treat it as a self contained >> pipe? >> >> -Adam >> >> >> > >> >> "Hunsberger, > >> Peter" To: >> "'[EMAIL PROTECTED]'" >> <[EMAIL PROTECTED]> >> <Peter.Hunsberger@ >> cc: > >> stjude.org> Subject: RE: Logging >> and Form Validation >> > >> 06/07/02 12:06 >> PM > >> Please respond >> to > >> >> cocoon-users > >> > >> > >> >> >> >> >> >>> This is a major >>> sticking point for my developers that like and are comfortable with jsp >>> with javascript embedded. >>> They want to keep it at the client and I am trying to build a case for >>> >> the >> >>> server through cocoon. >>> >> >> IMNSHO, the only way you can justify client side validation is if you are >> running an Intranet and you have an organization that somehow >> restricts the >> users capability to modify browsers settings so that you can ensure >> JavaScript is enabled. Otherwise, you can receive unvalidated data... >> >> If you're running over the Internet it's fine to use client side >> validation >> in addition to server side if you want to have some extra performance >> benefits for those who have JavaScript enabled. However, who wants to >> maintain both? >> >> Even if you have an Intranet and locked down browser settings, client >> side >> validation can be a real pain to maintain over time. In particular, >> there >> is (usually) no good coupling between the validation and the rest of the >> server side code. The exception is if you generate your client side >> validation code from server side templates. That's quite possible, but I >> suspect that once you developers jump through the hoops of embedding >> JavaScript within XML ( lot's of escaping and/or CDATA) they won't >> object >> to server side validation nearly so much... >> >> >> --------------------------------------------------------------------- >> Please check that your question has not already been answered in the >> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> >> >> To unsubscribe, e-mail: <[EMAIL PROTECTED]> >> For additional commands, e-mail: <[EMAIL PROTECTED]> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> Please check that your question has not already been answered in the >> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> >> >> To unsubscribe, e-mail: <[EMAIL PROTECTED]> >> For additional commands, e-mail: <[EMAIL PROTECTED]> >> >> > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
