Martin Gainty wrote:
is this what jeromy refers to as 'sub-package'?
I'd said/meant subclasses of the action. SmartURLs is convention and
annotation-based. The namespace of the action is derived from the
package of the action or the @Namespace annotation on the class. In
Dale's case he had one action class providing several actions, so if he
were using SmartURLs I believe he'd have to create subclasses of the
parent action so each action can be uniquely identified.
I would be very interested to see how this category/subcategory algorithm is
REST-ful
SmartURLs is not REST-ful. It's only provides a
convention-over-configuration approach to defining your actions and
action namespaces that result in friendly urls. My point was that
though carefully constructing your actions you can at least achieve a
distinct URL to each resource type which is better than the original
proposed single URL for every resource type.
Thanks!
Martin-
----- Original Message -----
From: "Dale Newfield" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <user@struts.apache.org>
Sent: Saturday, December 08, 2007 9:40 AM
Subject: Re: [struts] params and staticParams
Martin Gainty wrote:
Could you give us a definition of SmartURL ?
I'm fuzzy on this, but the best I've got is:
http://cwiki.apache.org/S2PLUGINS/smarturls-plugin.html
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
