+1 on SessionAware. It doesn't get much easier than:
public void setSession(Map<String, Object> stringObjectMap) {
}
to mock for testing.
Session use as a design pattern is a different issue. Struts2's conversion
and parameter handling makes it pretty easy to make each transaction as
stateless as possible, eliminating the need for a lot of the Noob Crutch.
newton.dave wrote:
>
> --- On Wed, 12/3/08, Fogleson, Allen wrote:
>> IMHO - I don't like tying myself down to Sessions.
>
> Hmm, I guess my opinion is that in S2's case you're really only tied to a
> Map, but I understand where you're coming from.
>
> Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/session-handling-tp20809961p20826760.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
