[
https://issues.apache.org/jira/browse/JSPWIKI-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802670#action_12802670
]
Andrew Jaquith commented on JSPWIKI-578:
----------------------------------------
Murray --
It's easy to take a look in the factory while the sausage is getting made, and
think to yourself: there's no way I am going to eat this.
To provide some context: most of what's being discussed in this particular
thread isn't meant to make JSPs more complicated. Indeed, it is about making
things simpler.
Probably 90% of the scriptlet code in 2.8 and earlier dealt with stuff that was
frankly just gruntwork: extracting, parsing and casting request parameters ;
validating and sanitizing user input; checking for authorization; etc. It's all
error-prone stuff, and often a security risk. If somebody told me that they
preferred to do all that stuff "by hand" in scriptlet code, I'd tell them that
they are wasting a lot of time and effort.
The goal in 3.0 is to eliminate all of the crappy mundane stuff from the JSPs,
to free developers to focus on the things that really make their wikis
valuable. If you take the simple step of moving your business logic to
ActionBeans (really, just JavaBeans with a few extra annotations), you get all
the parsing/binding/casting/security/validation stuff taken care of for free.
Backward compatibility is important. We expect to be able to drop in most JSPs
from 2.8 without any trouble. While we haven't fully tested the complete set of
2.8 JSPs, you should know that the "new" (Stripes-enabled) and "old" (2.8) have
been running side-by side, mixed together in the trunk, for a while. I have
also written a clean-room JSP parser and transformer to help ease the
transition to Stripes tags.
Bottom line is that the design of 3.0 isn't about "elegance." The design, as
always, is in service of one goal: to make things simpler. Good design is
simple design. But making things simpler is complicated -- at least for the
designers. Hopefully not for the ultimate users and deployers. Hence the
sausage-making that you are observing.
All this is another way of saying: I feel certain that you will like what you
see, once the code settles down and you are able to roll up your sleeves a bit.
I think you will find that, yes, there will be a few new rules to get used to,
but after that you will be pleased at how much more extensible the 3.0 system
really is.
> 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
> 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.
