[ 
https://issues.apache.org/jira/browse/JSPWIKI-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Jaquith resolved JSPWIKI-578.
------------------------------------

    Resolution: Fixed

All done.

I just checked in 3.0.0-svn-204, which removes the last top-level JSPs, except 
for Error.jsp.

Although there are a few old JSP URLs that don't bind 1:1 to ActionBean URLs 
(such as PageInfo.jsp as described above), these can be fixed by splitting 
ActionBeans as needed.

With this checkin, I took the liberty of moving the various layout-related JSPs 
into their own templates/default/layout/ subdirectory. This includes 
DefaultLayout.jsp, the old familiar Header.jsp and related "common" JSPs. I 
also moved the reusable "tabs" JSPs into their own subdirectory, called 
(logically enough) templates/default/tabs/. These measures keep the 
non-"content" JSPs out of the way.

And finally, as with many of my previous JSP checkins in the 3.x branch, I have 
been steadily using more JSTL where possible.

> Get rid of *.action URLs.
> -------------------------
>
>                 Key: JSPWIKI-578
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-578
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Core & storage, Default template
>            Reporter: Janne Jalkanen
>            Assignee: Andrew Jaquith
>             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.

Reply via email to