Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (hermes.apache.org: domain of sean.schofield@gmail.com
 designates 64.233.184.207 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=eU04oFEL5H66mK8wE+7kevmW0wO3CGQU7kDXuc6WA8eknoSgmDVfgy4CEUjKHKaLWRYRnX7LaG5488N9SX+Di46tRQ0ZDO5RzBjk/Ag6a968aOuipS90aevldg0+PeeWHCuUg8iiRAZihpXkM2wJ8RfiUMp+8t5OZOxTqood64o=
Message-ID: <2387fbc50501040744ed84358@mail.gmail.com>
Date: Tue, 4 Jan 2005 10:44:11 -0500
From: Sean Schofield <sean.schofield@gmail.com>
Reply-To: Sean Schofield <sean.schofield@gmail.com>
To: Struts Developers List <dev@struts.apache.org>
Subject: Re: Coupling, Struts and JSF
In-Reply-To: <70040413C055E64198177733CAE9F5D711F6E1@pepwmu00057.cww.pep.pvt>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <70040413C055E64198177733CAE9F5D711F6E1@pepwmu00057.cww.pep.pvt>

> A use case is:
> 
> - Two struts actions (say CreateAction and EditAction call the same jsp
> to view the result (say result.jsp).
> - This result.jsp needs some setup (eg. a list of items for a selection
> box).
> - The natural way to populate such a list in struts, is in the action.
> - To prevent having the logic to populate the list both in CreateAction
> and in EditAction,
>  some users create a new ResultAction, where they do the view
> preparation.
> - Then they chain the action (this is controversal stuff):
>  . In CreateAction they do creation logic, and than forward to
> ResultAction.
>  . In EditAction they do edit logic, and than forward to ResultAction.
> 
> As discussed in bug 16107:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16107

I guess JSF deals with this by having a single jsf page that has a
single "backing bean" to populate itself.  Right?

I suppose one implication of this is that the logic necessary to
"populate" a page is coupled with the page itself (or at least the
choice of logic).  There's probably not really a way to avoid this.  I
guess Struts really does this too but the binding takes place in
struts-config.xml.  The more that I think about it, it's easier to
find the logic in the page itself instead of hunting around
struts-config looking for it. :-)
 
> Regards, Jan

sean

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