> ---------- > From: Torsten Curdt[SMTP:[EMAIL PROTECTED]] > Reply To: [EMAIL PROTECTED] > Sent: Friday, April 12, 2002 4:05 AM > To: [EMAIL PROTECTED] > Subject: Re: HEADS UP - cocoon form handling (long!!) > > On Thu, 11 Apr 2002, Ivelin Ivanov wrote: > > > <snip/> > > > > > > Again, I agree. Beans are high maintenance for, what is in this case, > > > little advantage. I spent a week coming up with a bean framework for > > > a webapp, and had little progress on the webapp. It is sad, but that > > > is what happened. SOmetimes it is enough to have a maleable model and > > > let the form framework take care of the rest. > > > > Would you scetch an example of a non-trivial app which does not use > > JavaBeans? > > May I jump in here, Berin? > > If you have a well defined preceptor (that might even support relevance / > data dependencies) all you need to code is your submit action that takes > the form data and saves it (or whatever you want). If you really need more > you should be able to write some code that works on the instance on given > circumstances and you will be fine again. This will save you lot's of > implementation time in the end. (...and the need for programmers) > > cheers > -- > Torsten > That ONLY works when your logic is simple. There is an application complexity threshold where you really need beans or something like beans to address the logic. Most webapps really never hit the point where this is truely a requirement....
> --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
