Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Mime-Version: 1.0
Message-Id: <a062007f2bde64f48de4b@[192.168.2.93]>
In-Reply-To: <2387fbc504121510183c3969f4@mail.gmail.com>
References: <BDE4BDC6.19CF0%salgado.pc@04web.com>
 <2387fbc504121510183c3969f4@mail.gmail.com>
Date: Wed, 15 Dec 2004 14:46:09 -0600
To: Sean Schofield <sean.schofield@gmail.com>,
 Jakarta Commons Users List <commons-user@jakarta.apache.org>
From: Joe Germuska <Joe@Germuska.com>
Subject: Re: commons-chain: joining with struts
Cc: Struts Developers List <dev@struts.apache.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

As one of the Struts developers who is very keen on moving 
chain-integration forward, I'll say a few brief words.  I'm not on 
the commons-user list, but I will say that Sean's right that this 
discussion is best suited to struts-dev.   (I'll leave commons-user 
on this message, but I'd encourage anyone else who responds to only 
reply to dev@struts.apache.org)

Anyway, we've talked about a StrutsWebContext, and in fact, we've 
talked about a few different subclasses of o.a.c.chain.Context for 
use in different phases of the request process.  You may want to look 
through the mailing list archives, as this has been a pretty active 
topic of discussion in the last 2-3 months.

Now that Chain has hit a full release, we are definitely planning on 
moving ahead with changing the default request processor in Struts to 
be based on commons-chain.  The struts-chain project which is 
currently available from the subversion repository is a very healthy 
working implementation.  The migration to the Struts core will mostly 
involve building in a mechanism for initializing any number of 
catalogs (obsoleting a Plugin class which does it in struts-chain).

But I absolutely agree that it makes sense to make type-safe 
subclasses of Context which clarify the names and types of important 
participants in the Struts request processing chain.  I would only 
argue that we'd probably like to keep "Web" from being too visible, 
as we feel in Struts that it would be good to decrease explicit 
dependencies on the Servlet API.

Best,
	Joe

At 1:18 PM -0500 12/15/04, Sean Schofield wrote:
>Pedro,
>
>A StrutsWebContext class might be an interesting idea.  If adopted, it
>should go in the struts-chain project as opposed to commons-chain.  (I
>am sending a copy of this response to the struts-dev mailing list
>which is probably the best place to propose this kind of enhancement).
>
>I'm not sure how useful it would be to have the ActionForm in your
>commands but I don't work a lot on struts-chain so maybe others have
>an opinion on that.
>
>If you decide to go ahead with submitting an official patch (or just
>using it in your own projects) the code should probably be modified to
>take advantage of recent changes to commons-chain.
>
>Specifically, you can now use CatalogFactory to get a copy of the
>catalog you're interested in.  Just make sure to setup the
>o.a.c.c.w.ChainListener with the appropriate parameters, and it will
>configure the catalog when the webapp starts and it will automatically
>be available to any java class using the same class loader (including
>your proposed CommandAction).

-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
"Narrow minds are weapons made for mass destruction"  -The Ex

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org