incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Jaquith (JIRA)" <>
Subject [jira] Commented: (JSPWIKI-578) Get rid of *.action URLs.
Date Wed, 20 Jan 2010 19:20:54 GMT


Andrew Jaquith commented on JSPWIKI-578:

Ok, cool. #2 it is, then. 

Yes, I like this. By moving (what's left of) the top-level JSPs into the template JSPs, the
top-level JSPs go away entirely. The template JSPs become 100% presentation ("templating").
It should be enormously simpler for JSP developers.

The trick, Janne, as you correctly pointed out, is that the current FileBasedActionResolver
doesn't allow multiple URL bindings for a single ActionBean. So a "custom" URL for a particular
ActionBean would preclude it being addressed by a ".jsp" path. I'm not too worried about this
in the short term, but for the 3.1 timeframe we'll want to do something better. Fortunately
this request has come up on the Stripes lists too, so it's likely it will be solved for us.

After I check in my current batch of code, I'll start experimenting with JSP consolidation
(and write a TemplateForwardResolution class).

> Get rid of *.action URLs.
> -------------------------
>                 Key: JSPWIKI-578
>                 URL:
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage, Default template
>            Reporter: Janne Jalkanen
>             Fix For: 3.0
> We currently have two URLs for each ActionBean - both the Wiki.jsp and Wiki.action are
available. Now, since the URLs are different, it has some nasty side-effects:
> * Users don't know which URL to bookmark, or they end up bookmarking both pages
> * Browsers don't know which pages are equal, and therefore both caching and page highlights
work inconsistently
> * Bots will index both pages, therefore giving odd results
> Since one of the design maxims of 3.0 is that URLs should not change, we should figure
out a way to get rid of the Stripes-induced *.action URLs.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message