Ok, this issue breaks down like this in my mind: 1. Should our tags (url, form, etc) have attributes for the namespace, action, and method, or just have one for the url? 2. Should our default ActionMapper allow the method to be specified in the url?
Issue #1 goes back to the more fundamental issue of whether Struts 2 is a _web_ framework that treats URLs as king or a more general app framework that hides the URL from the developer. Personally, I think Struts 2 should be centered around the concept of the URL and not be hidden. Even in the case of portlets, the concept of a identifying string for the controller is important. If you want the framework hide the HTTP and HTML from you, JSF or Wicket might be a better framework than Struts. Issue #2 I think is moot because of the new Able stuff Patrick has done, which contains an ActionMapper that works without any configuration. He's opening a ticket and I'm sure we'll be discussing it further at a later time. Therefore, the main issue at hand is #1, whether to hide the URL from the user by breaking it down into defined components, or to expose the URL, as a whole, to the developer. I think we should remove the method and namespace attributes on the tags and elevate the status of the URL in Struts 2. Don The core issue here is whether we want to allow tags to specify the method and therefore the URL. If there are legimate benefits to continuing to support explicit method naming, and from Patrick's Able stuff it seems there are, I'm fine with reverting those changes. Wildcards can still be used and On 8/21/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote:
Ted, I'm still not yet on board with removing the ! syntax until we have a solid replacement. I don't think pointing to wildcards is enough, especially since you would have to create a wildcard for every namespace. That is more configuration than I'm willing to recommend to our users. I would, however, be open to introducing the type of action mapping and convention-based configuration I have put in to Able, while still also supporting struts.xml: http://svn.opensymphony.com/fisheye/browse/sandbox/able/src/main/java/com/opensymphony/able/webwork/AbleActionMapper.java?r=7 http://svn.opensymphony.com/fisheye/browse/sandbox/able/src/main/java/com/opensymphony/able/webwork/AbleConfiguration.java?r=4 But without something like the above, or with a way to use wildcards for multiple namespaces, I cannot readily agree to dropping the ! syntax. I know that the overriding concern is "security". I have a few thoughts on that: 1) I would suggest reaching out to the big WebWork users (Jive, Atlassian, Google, others) to see if this is something that has concerned them in the past. My feeling is that it isn't a big concern, because they understand anything in an action is "fair game" to URL manipulators and that that has always been clearly understood. 2) Assuming we want to make method invocation more obvious, we could require an annotation or a convention such as as doXxx, such as RIFE does. --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=40884&messageID=81481#81481 --------------------------------------------------------------------- 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]
