struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Lee" <crazy...@crazybob.org>
Subject Re: Returning Result directly (was Re: DefaultActionMapper compatablity
Date Wed, 26 Jul 2006 05:51:06 GMT
I actually didn't understand the * scheme until someone explained it to me.
On the other hand, I think I'd grok a scheme which used explicit names
pretty quickly.

Ant may use "*/**" for paths, but you don't reference indexed parts of the
match, do you?

Bob

On 7/25/06, Don Brown <mrdon@twdata.org> wrote:
>
> Good ideas.  The question is really what would be most intuitive and
> cover the most common use cases.  The */** syntax seems pretty common,
> and, IMO, very intuitive used in tools like Ant.  If we abstract the
> wildcard handling, we could allow users to switch in a new impl easily
> for more advanced cases.  That said, I'm open to changing the default
> wildcard pattern style if we find one that is more powerful, yet still
> easy and intuitive.
>
> Don
>
> Bob Lee wrote:
> > {foo*} could match slashes. Or {/foo}. Or {{foo}}.
> >
> > We could also use regular expressions--they support this sort of group
> > matching and results.
> >
> > Bob
> >
> > On 7/25/06, Don Brown <mrdon@twdata.org> wrote:
> >>
> >> Struts 2 (XWork 2 actually) currently does not support this
> syntax.  The
> >> main advantage the current "*" token scheme has is "**" which can match
> >> any character including '/' while "*" matches all characters except
> >> '/'.  Now, it should be possible to abstract the wildcard
> >> handling/processing so that you could plug in new wildcard handlers.
> >>
> >> Don
> >>
> >> tm jee wrote:
> >> > Just out of curiosity, the "invoice/{method}" and "{method}" pair,
> >> does
> >> the current implementation of Struts2 wildcard supports this? Looks a
> >> lot
> >> more clearer than the "invoice/*" and "{1}" pair.
> >> >
> >> >  rgds
> >> >
> >> > ----- Original Message ----
> >> > From: Bob Lee <crazybob@crazybob.org>
> >> > To: Struts Developers List <dev@struts.apache.org>
> >> > Sent: Wednesday, 26 July, 2006 12:01:50 PM
> >> > Subject: Re: Returning Result directly (was Re: DefaultActionMapper
> >> compatablity
> >> >
> >> > On 7/25/06, Don Brown <mrdon@twdata.org> wrote:
> >> >
> >> >> <action name="invoice/*"
> >> >> class="com.eplus.app.invoice.action.InvoiceCrudAction" method="{1}">
> >> >>   <result name="list"
> >> >> type="freemarker">/template/eplus/metaDataList.ftl</result>
> >> >>   ...
> >> >> </action>
> >> >>
> >> >
> >> > Or:
> >> >
> >> > <action name="invoice/{method}"
> >> >     class="com.eplus.app.invoice.action.InvoiceCrudAction"
> >> method="{method}">
> >> >  <result name="list"
> >> type="freemarker">/template/eplus/metaDataList.ftl</result>
> >> >  ...
> >> > </action>
> >> >
> >> > Bob
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > For additional commands, e-mail: dev-help@struts.apache.org
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message