On Sat, 30 Oct 2004 14:18:19 -0400, Rob Leland <[EMAIL PROTECTED]> wrote: > Craig McClanahan wrote: > > >On Fri, 29 Oct 2004 21:28:52 -0400, Ted Husted <[EMAIL PROTECTED]> wrote: > > > > > >>That sounds great to me, Don. :) > >> > >>We already have Struts-Faces and Struts-Examples on the trunk. We might as well > >>add Struts-BSF and Struts-Flow to the mix. > >> > >> > > > >+1. > > > > > > > >>Struts-BSF and Struts-Flow are not part of the core, so they would be not affected > >>by a 1.2.x branch. > >> > >>-Ted. > >> > >> > >> > > > >Note that there have been two overlapping discussions about scripting > >on the lists today ... Don's stuff in Struts Flow uses a modified > >Rhino (with continutations) to do scripting on the *server* side, > > > > > A while back I suggested using Rhino to consolidate all validations so > server side & client side > validations were the same core code written in JS. It this more viable > now ? Maintaining 2 sets of > validations in java & javascript items tend to get out of sync. This > could be done as a new plugin to demonstrate.
Interesting idea. (I must have missed it when you suggested it before.) I think a demonstration would be a good thing, and an interesting experiment. One thing I'd encourage, if we go down this path, is the creation of one validator object in JavaScript that has the various validators as methods, rather than creating a bunch of methods in the global namespace. What we have now in Commons Validator does not scale, and is increasingly likely to cause problems in applications that make use of a lot of client side JavaScript. (This last is a Commons Validator itch I've had for a while that hasn't quite bubbled to the top of my itch list yet. ;) -- Martin Cooper > >while the earlier conversation about serializing a JavaScript object > >and converting it is about scripting on the *client* side, using a > >serialized form of JavaScript objects to pass data back and forth > >through a hidden field. > > > >Both ideas are quite cool. > > > >Craig > > > >--------------------------------------------------------------------- > >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]
