Adam Hardy on 27/06/05 01:30, wrote:
Ted Husted wrote On 26/06/05 13:25:
* http://struts.apache.org/roadmap.html
on a related note I see that merging the DTDs for validator and forms
has been mooted. My desired strategy would be to have a form bean that
knows what type its members are.
I
akota Jack" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" ; "Michael
Jouravlev" <[EMAIL PROTECTED]>
Sent: Monday, June 27, 2005 12:50 AM
Subject: Re: Form-Action combo
This is just like the intentional "mistake" made in JSF. There are
real rea
This is just like the intentional "mistake" made in JSF. There are
real reasons for the MVC architecture. I am for flexibility but not
for couping things together into spaghetti code once again.
On 6/23/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> WebWork actions are somewhat like Struts
Ted Husted wrote On 26/06/05 13:25:
* http://struts.apache.org/roadmap.html
[snip]
With features like "extends", it becomes even easier to customize
Struts to use your own default classes and implementation strategies.
Once 1.3.x starts to ship, it will become even easier to use Struts
like
Support for this idea on the RoadMap for the 1.5.x zone under:
"Consider a "smart" action type. The idea is that a command in Struts
chain could look at the type indicated by the ActionMapping so both
Action classes and ActionCommand implementations are supported. People
could then mix-and-match
On 6/23/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> WebWork actions are somewhat like Struts Action and ActionForm
> combined: they can transfer request parameters and can be stateful,
> like ActionForm, but they also can process input events, like Action.
>
You'll also see this pattern im
I happened to initiate a private discussion on the topic, so if
someone interested, I am sharing it, with Michael Oliver's consent.
Hopefully, it is readable ;-)
> On 6/23/05, Michael Oliver <[EMAIL PROTECTED]> > > > wrote:
> > On 6/23/05, Michael Jouravlev <[EMAIL PROTECTED]> > > > wrote:
> > > O
I don't see the need for a new type of Action, there is no limitation to
what methods you ADD to an ActionForm, so you may choose to do your business
logic implementations in the ActionForm itself and then the various
Action::execute() methods would just marshal the arguments and call the
methods o
8 matches
Mail list logo
