Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <00bc01c4d0d5$fe3e1730$0302a8c0@mattlaptop>
From: "Matt Sgarlata" <matt.sgarlata@spiderstrategies.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
References: <20041121145254.T752@minotaur.apache.org>
 <009201c4d047$292fa420$0302a8c0@mattlaptop>
 <1c661f2f04112120114eb9b7c2@mail.gmail.com>
Subject: Re: [VOTE] Release Chain 1.0
Date: Mon, 22 Nov 2004 15:58:18 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Sorry, one more comment for ServletWebContext, below...
----- Original Message ----- 
From: "Don Brown" <donald.brown@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Sent: Sunday, November 21, 2004 11:11 PM
Subject: Re: [VOTE] Release Chain 1.0


> As for ServletWebContext, I see your point, but I'd argue that
> business classes would never see the actual ServletWebContext, but
> rather get passed an application-specific context, which may or may
> not contain ServletWebContext.  For Struts, I'm thinking we'd use an
> ActionContext, which would look for objects in the scope hierarchy on
> a get() as you suggest, if it detected a WebContext.  Otherwise, the
> value would come right out of the ActionContext.  I could see the
> value in bringing that scope logic to WebContext, however.

OK, assuming we like ServletWebContext as it currently stands, wouldn't it 
make more sense for getRequestScope(), getSessionScope(), etc. to return 
Context instead of Map?

> Don

Matt 


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