I've enjoyed reading the thread on Pagelets, but I'm not convinced the whole
of the Pagelet proposal is needed. But I could well be missing something
here (all clues appreciated!)
From what I can gather, all you require is for a bean to have a destroy()
method called, if it has one. I.e., if
-
From: Christopher Cobb [SMTP:[EMAIL PROTECTED]]
Sent: Saturday, 8 May 1999 3:44
To: Drew Cox
Cc: [EMAIL PROTECTED]
Subject: Re: Pagelets Proposal
Drew Cox wrote:
...
I firmly believe your "model" classes should not be tied to a
particular
presentation format
Drew Cox wrote:
...
I firmly believe your "model" classes should not be tied to a particular
presentation format (JSP, GUI, ??). But remember, this is just a class,
not a bean. This "model" class can be composited into, or inherited
from, in a JSP-aware bean that handles creating a
I'm using templates that provide bean access, not JSP, but I find I'm
doing what Chris is -- there are the real business objects that are
beans, then there are Displayedthing beans that handle presentation
issues. They don't do HTML generation but things like getting a menu of
objects filtered
I think that the processRequest did provide some benefits. Although it
really left me wanting a little bit more.
The main benefit of processRequest as I see it, is the beginning of
some structure and definition of what a JSP bean is. Unfortunately, it
seems that some are very against any kind of
I like this idea a lot. It helps to have a page-level
component in which certain events trigger methods at
various times in the request-response loop. This idea
is somewhat like the "components" in WebObjects. Every
template is bound to a component class, and all the
components have a common
Agreed.
- Original Message -
From: James Klicman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 06, 1999 10:01 PM
Subject: Pagelets Proposal
I think that the processRequest did provide some benefits. Although it
really left me wanting a little bit more.
The main
t: Friday, 7 May 1999 10:32
To: [EMAIL PROTECTED]
Subject: Re: Pagelets Proposal
I like this idea a lot. It helps to have a page-level
component in which certain events trigger methods at
various times in the request-response loop. This idea
is somewhat like the "components" in We
