[
https://issues.apache.org/jira/browse/JSPWIKI-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802597#action_12802597
]
Murray Altheim commented on JSPWIKI-578:
----------------------------------------
I realize this is minority view (at least within the developer team) but I hope
this can be taken constructively, as it's meant that way.
While the project is called JSPWiki there sometimes almost seems to be an
intense dislike of JSPs themselves. While browsing programming forums I often
read disparaging remarks about JSPs (and particularly scriptlets), citing all
sorts of issues, not being MVC blah blah blah. Earlier today I found "you
wouldn't want to open a URL connection in a scriptlet, would you?" as if by
doing so one were in danger of being excommunicated from the Church. Well, I
have no problem at all with opening a URLConnection in a scriptlet, and I don't
find JavaBeans any better a solution than straight Java code.
I realise there is enthusiasm for the approach in the new 3.0 code, and perhaps
very good reasons for it, but one of the reasons I began using JSPWiki was that
the JSP approach permitted a great deal of configuration flexibility and
extensibility. Most of you know I've taken full advantage of that. I'm sure
3.0 satisfies the desires of its designers, but not necessarily that of the
users (installers), or at least those such as myself who extend the features or
make significant template modifications. We may be in the minority and hence
ignorable.
This isn't to say I don't find much of the 3.0 very impressive. It is. But it's
also (to my understanding) removed much of the messy fun of JSPWiki 2.8 and
made some of the things I've been doing perhaps impossible. It'll certainly
make things a lot more complicated, and people will have to learn quite a few
new technologies to keep up with what you've done.
So while in terms of architectural soundness and programming elegance 3.0 would
certainly win, for people who actually like JSPs and use the extensibility in
the 2.8 codebase, 3.0 is perhaps where some of us actually stop upgrading and
stay with 2.8, then begin looking for a different wiki solution as the 2.8 code
goes stale. Not that I want to do that.
And I don't know that for sure. I haven't had the luxury of really getting down
and dirty with 3.0 yet, as I'm going to have to wait until things stabilise
before I consider trying to migrate any of my customisations to the new
platform. I'm not sure how much backwards compatibility has been a requirement
for the 3.0 work. In looking over 3.0 it certainly seems that my upgrade path
will be non-trivial, and time and resources are currently very tight. If it
looks like there will be considerable time requirements to migrate my code to
3.0 it probably won't happen, at least not soon.
All that said, decisions such as JSPWIKI-578 should be made not always on what
is elegant but on (a) what provides the simplest solution, and (b) what
provides the most extensibility and customisability. If we remove JSPs from the
processing loop entirely, it makes customisation of a site significantly more
difficult, and moves the developer requirements from JSPs and servlets into
beans and frameworks. To some that may be a boon; to me, a bane/pain.
There are some of us who really like JSPs. Okay, call us Luddites.
> 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.
