Inline... On Fri, 14 Feb 2003, Kelvin Tan wrote:
> See inline reply. > > On Fri, 14 Feb 2003 05:01:12 -0500 (EST), Joseph Ottinger said: > >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 Extra complexity is a crucial point. > > There's alot of stuff we can do ourselves, but doing so also means having to > maintain both code and documentation. Isn't that one of the reasons we choose > to use 3rd-party code (read: webwork) in the first place? Because it > a) provides functionality not _absolutely core_ to what one does > b) has a tried-and-tested codebase > c) has well-documented code and good documentation > d) gets maintained Sure. Third party code, no problem... except webwork dependencies turn into FOURTH-party code. Plus, you end up handing your requirements to someone else: "FormProc does it this way, so I guess we have to do it too." I already mentioned the versioning hell I've seen regarding such lovelies as Xerces. > >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...) > > If you re-read the threads, you will find that I neither asked for Jexl as part > of core (I was throwing the idea of using Jelly around), nor did I ask for > FormProc for form validation (Jason mentioned it). I was interested to know the > rationale behind the decision to develop another form validation framework. Well, the "form validation" framework itself is sort of a tack-on, since WW has traditionally had a validation hook. It'd be fairly simple to use formproc there, for example, without binding WW to formproc (and its two or more configuration files...) or Jelly. Nobody is saying you can't use formproc or jelly with webwork. I personally wouldn't care if you did... but I don't use them myself, and having jar after jar after jar after jar foisted upon me by a simple command framework would get really, really old quickly. Sure, it's a little more work for Jason and Pat to add an actual validation framework... but that means that the validation framework gets to stay where it should: out of the way of those who don't want to be tied to it (i.e., those who do their own validation, by whatever means they choose.) ------------------------------------------------------- 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
