Yes and no.
Yes: The REST plugin uses CodeBehind. If appropriate, CodeBehind will be
replaced by the Convention plugin. SmartURLs is being merged into the
Convention plugin. That's a nice convergence.
No: REST involves more than URL mapping. However, it's not unreasonable
that a single Str
hi all
is there a plan for REST, so we can mixed all become one, SmartURL,
original method and new REST model
i have hugh code and love to try REST
F
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [
AM
Subject: Re: REST vs Original
> --- Martin Gainty <[EMAIL PROTECTED]> wrote:
> > SmartURLs..Are there situations where using action-name based results
are
> > preferable over a declared result?
>
> Sure, if you don't want to configure a result manu
--- Martin Gainty <[EMAIL PROTECTED]> wrote:
> SmartURLs..Are there situations where using action-name based results are
> preferable over a declared result?
Sure, if you don't want to configure a result manually.
> Where can I get the source for
> org.texturemedia.smarturls.SmartURLsConfiguratio
>
To: "Struts Users Mailing List"
Sent: Friday, January 18, 2008 7:28 PM
Subject: Re: REST vs Original
> Hi Frans,
>
> Unfortunately at the moment you can't mix conventions within the same
> Struts2 webapp. The trouble is the REST plugin overrides a lot of the
&g
On Jan 19, 2008 7:28 AM, Jeromy Evans <[EMAIL PROTECTED]> wrote:
> Hi Frans,
>
> Unfortunately at the moment you can't mix conventions within the same
> Struts2 webapp.
hi there
so what should i do if I am intersting with REST, but have a hugh code
using S2 old way.
i think that is not good to re
Hi Frans,
Unfortunately at the moment you can't mix conventions within the same
Struts2 webapp. The trouble is the REST plugin overrides a lot of the
default behaviour rather than augmenting it. Right now if your commit to
REST conventions it'll apply to the entire webapp. With some effort i
7 matches
Mail list logo
