association between
requests/processing/response rather than defining the processing
steps.
I'd be interested
in what others think.
L.
-Original Message-From: Gernot
Koller [mailto:[EMAIL PROTECTED]]Sent: 12 September 2002
13:49To: [EMAIL PROTECTED]Subject: Is it a good
Hi Gernot -
Whether one method is a better or worse idea than another is largely
dependent on how you implement it. Yes, XSPs do somewhat violate
Separation of Concerns. And yes, you can compare XSPs to JSPs in terms
of pitfalls.
The fact is, that there are some things you can only do with XS
On Thu, 12 Sep 2002, Gernot Koller wrote:
>
> Hi!
>
> First, thanks for your very quick replies to my last question!
>
> After quite some time discussing and evaluating we made a decision in favor of
>cocoon as presentation framework. One major argument for cocoon and against struts
>was that i
Gernot Koller
To: [EMAIL PROTECTED]
Sent: Thursday, September 12, 2002 2:49
PM
Subject: Is it a good idea to avoid the
use of xsp ?
Hi!
First, thanks for your very quick replies to my last question!
After quite some time discussing and evaluating we made a decisio
Hi!
First, thanks for your very quick replies to my last question!
After quite some time discussing and evaluating we made a decision in favor of cocoon as presentation framework. One major argument for cocoon and against struts was that in jsp a strict seperation of logic (Java code) and presentat
