Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v609)
To: users@cocoon.apache.org
Message-Id: <DF4D6C52-7221-11D8-8979-000A95908E0E@wrinkledog.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-2--363850077
From: Mark Lundquist <ml@wrinkledog.com>
Subject: cocoon.createObject()
Date: Tue, 9 Mar 2004 15:31:21 -0800

--Apple-Mail-2--363850077
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed

OK, I've picked up on a few email threads about the new createObject() 
and disposeObject() methods.  There's something in the release notes 
about them too, but not enough to make it clear to me how or why to use 
them.

I just started really learning Cocoon a couple of months ago, and all 
the Avalon stuff under the bonnet is really still terra incognita to 
me.  So when the docs say, "it goes through all the Avalon lifecycle 
interfaces" or whatever it says, I'm sure that means something to 
somebody, but I'm still waiting for a clue to strike.

But... as I've been writing the Java business objects for this app, I 
sometimes get this feeling that they maybe really ought to be Avalon 
components.  I don't know why I get that feeling, because I don't 
really dig Avalon yet, so it's just a feeling :-).

So... if somebody could give a brief overview, or point us to one, 
that'd be great.  It seems like these methods were added because the 
Cocoon devs want the community to move more towards some style of 
development, and if so I'm sure it would speed adoption if something 
could be done to evangelize the Avalon-unhip crowd.

~ Mark

--Apple-Mail-2--363850077
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
	charset=US-ASCII

OK, I've picked up on a few email threads about the new createObject()
and disposeObject() methods.  There's something in the release notes
about them too, but not enough to make it clear to me how or why to
use them.


I just started really learning Cocoon a couple of months ago, and all
the Avalon stuff under the bonnet is really still <italic>terra
incognita</italic> to me.  So when the docs say, "it goes through all
the Avalon lifecycle interfaces" or whatever it says, I'm sure that
means something to somebody, but I'm still waiting for a clue to
strike.


But... as I've been writing the Java business objects for this app, I
sometimes get this feeling that they maybe really ought to be Avalon
components.  I don't know why I get that feeling, because I don't
really dig Avalon yet, so it's just a feeling :-).


So... if somebody could give a brief overview, or point us to one,
that'd be great.  It seems like these methods were added because the
Cocoon devs want the community to move more towards some style of
development, and if so I'm sure it would speed adoption if something
could be done to evangelize the Avalon-unhip crowd.


~ Mark


--Apple-Mail-2--363850077--