> -----Original Message----- > From: Joseph Ottinger [mailto:[EMAIL PROTECTED]] > > > I'm one of those against extra dependencies. As I said in the > mailing list previously (see > http://sourceforge.net/mailarchive/message.php?msg_id=3757306 > regarding your question on JELLY dependency!) every > dependency adds extra complexity. Formproc, in particular, > means adding configuration to an extra location. XWork and WW > config can be merged together (a WW config would include the > accompanying XW config), and requiring formproc means we have > a minimum of two config files... in one product. Bad, > especially when we can do it ourselves. > > Why do you keep wanting to tie WebWork to other projects so > badly? This is the second time I've seen you wish for extra > dependency (the url above was expressing your desire for > using JEXL as core WebWork, and your message now is for > FormProc for form validation...) >
Let's remember the ugliness of the discussions when things like hidden form fields were suggested. Ideas and curiosity are OK, and should be encouraged. A lot of these extra integrations can be built as an optional jar, I think, the way that Ant does. They can also be added to the other library (for instance FormProc). The Interceptor framework makes it very easy to plug in Interceptor classes dynamically without having to be bundled with Xwork. Jason ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
