cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <>
Subject Re: HEADS UP - cocoon form handling (long!!)
Date Fri, 12 Apr 2002 08:05:31 GMT
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)


To unsubscribe, e-mail:
For additional commands, email:

View raw message