> > - zero configuration (using conventions instead) > for actions and results > > OK, now define the ideal conventions. :)
Heh - alright. I'll give it a stab. This comes from the conventions I've used in WebWork for two apps (HostedQA and www.bigbark.net). - A single package (or set of packages) that your actions exist in, such as "com.acme.actions" - Classes named FooAction map to the action named "foo" - Paths come from sub-packages inside of com.acme.actions. Ex: com.acme.actions.foo.BarAction -> /foo/bar - Results map to the same directory path with the addition of "-success" and are JSP only. Ex: com.acme.actions.foo.BarAction with a SUCCESS result maps to /foo/bar-success.jsp. - If bar-success.jsp can't be found, try bar.jsp. - Results can be overridden using a @Result annotation at the class or method level, or both. There you can specify basically what you can specify in XML today. I think that's it. Does that make sense? --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=39135&messageID=77653#77653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
