I completely agree. The only caveat I'll add is that we should be
careful to remember that apps built with the NameBasedActionResolver
currently use URLs like:
/foo/Bar.action
unless otherwise configured. So we should be careful to think about
backwards compatibility when we do this.
-t
On May 29, 2007, at 3:13 AM, Jeppe Cramon wrote:
Hi
I like the fact that Stripes has a well designed core set of
components that handles what is core or in the nature of Stripes.
To me these changes belongs in the core and not in an Interceptor,
which to me are more for afterthoughts or things that are not core :)
/Jeppe
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Ben Gunter
Sent: 29. maj 2007 05:14
To: Stripes Development List
Subject: Re: [Stripes-dev] clean URLs
Since this is going to be so tightly integrated into Stripes
(changes to s:url, s:link, interpretation of @UrlBinding, etc.)
should I bother to implement this as an Interceptor or should I
just modify the existing ActionResolver and whatever else? It
likely will be more efficient to modify the core classes.
-Ben
----------------------------------------------------------------------
---
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
