I like where SmartURLs is going, but, as it stands, I'd still call it incomplete and experimental. For an approach like SmartURLs (or ZeroConfiguration/CodeBehind) to be truly useful, we should be able to at least write something like the MailReader with a bare number of ActionName annotations (ideally, 0). I'd also like to try a zero-config ShowCase application.
I'm trying to find time to review the source code and come up with some patches. I think if the current list of issues were resolved, I think it would be a great idea to merge SmartURLs with the new ZeroConfig/CodeBehind plugin. Here's a summary list of the missing features I came across trying to implement MailReader: SU-5 Support ReST-style parameters * hello-world/save?message=Howdy == hello-world/save/message/Howdy SU-6 Extend result-type search scope * /foo/bar/hello-error.jsp, /foo/bar/error.jsp, /error.jsp, and then fall back to /foo/bar/hello.jsp SU-7 Automatically chain action (if any) when branching to other pages * If Foo.execute returns "bar", we check for FooBar.class SU-16 Heuristic alias matching * for hello-input, (1) HelloInput.execute, (2) Hello.input I'd also like to review the validation annotations tickets, since there were some glitches there too (especially with Skip). (Has anyone compared the XWork validation annotations with the Hibernate annotations? Are we compatible?) -Ted. On 10/8/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote: > > So, should I go ahead and start promoting SmartURLs or should we > continue to attempt to collapse the zero-conf/codebehind stuff into > SmartURLs? > > -bp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
