-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frank,

Frank W. Zammetti wrote:
> On Tue, August 26, 2008 12:33 pm, Christopher Schultz wrote:
>> With respect to Frank's comments, S2 specifically encourages you to
>> separate your own code from the framework, so that you can even
>> implement your logic as framework-agnostic controllers that are simply
>> auto-filled by the framework. Unit testing couldn't be easier: you don't
>> even need to worry about the servlet API because S2 completely hides it
>> from you (even for things like session attributes).
> 
> I think that *can* be true... but my observation is that most developers
> start getting so many marker interfaces and interceptors into the mix, and
> some start to tie you to the servlet API, that all of a sudden you're in
> the same "mock" boat as you are otherwise... I've always thought the S2
> claim that Actions are POJOs, while *technically* true (or at least, *can*
> be technically true) is a little bit of a red herring.

Er, I think I misspoke a bit... you're right: you do need the marker
interfaces for things like "SessionAware". It /does/ untie you from the
servlet API, though.

> However, I'll be fair and admit I haven't done a full-scale S2 project in
> a real-world environment, so this conclusion is based on a somewhat
> limited data set.  I don't think the situation is any worse than any other
> framework though.

Neither have I... I've only reviewed a book on S2. Making a switch (we
currently use S1 in production) is a big step, although you can run them
side-by-side, which is /really/ nice.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAki0bIsACgkQ9CaO5/Lv0PBtqgCgqfCDEwaJHdacbsC8A1/bbT30
zI0AoIeNPfBfG9xucuoR7zHzddQKmgvw
=OqVi
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to