[ 
https://issues.apache.org/jira/browse/JSPWIKI-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728548#comment-13728548
 ] 

Glen Mazza commented on JSPWIKI-796:
------------------------------------

Dirk, that you were using Tomcat 5 is quite pertinent information you should 
have stated in this bug report.  I upped us a few months back to Servlet 2.5 
(Tomcat 6) and removed the Tomcat 5 crud in our old Ant build.xml.  The 
"JSPWiki site" you referenced is not the official source of information for the 
Apache JSPWiki project, it was largely last updated in 2007 and we have no 
control over its text--while Janne may opt to give some JSPWiki team members 
write access to it (I don't have it, although I haven't asked) write access to 
that site is not an automatic function of being a JSPWiki team member, and so 
it remains unofficial until it's moved over to Apache and all team members can 
update it.

Tomcat 5 is dead and unsupported, even by the Tomcat team -- it's not even on 
their website today: http://tomcat.apache.org/.  As it's unsupported, you 
cannot base a secure solution on it today.  Minimum is Tomcat 6.

More importantly, we cannot attract committers when we tell them they have to 
work with obsolete products like Tomcat 5, we can, should and will lose them 
instead to other projects that allow them to develop modern skills they can use 
in their careers.  It's difficult enough trying to compete with the Hadoops and 
Cloudstacks for committers without us further requiring volunteers to work with 
Tomcat 5.  For the open source model to work, *both* the volunteer developers 
and the users have to benefit, and committers just don't benefit working with 
that product today.  If you disagree, feel free to move the discussion over to 
the dev list.
                
> UserPreferences is broken
> -------------------------
>
>                 Key: JSPWIKI-796
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-796
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Default template
>    Affects Versions: 2.10
>            Reporter: brushed
>            Assignee: Glen Mazza
>
> (detected on v2.10.0-svn-22)
> The new JSTL version, upgraded to version 1.2 since the MAVEN update, is 
> giving problems in resolving certain EL expressions.
> EG, the UserPreference page is throwing an error when evaluating a forEach 
> loop.
> {noformat} 
> java.lang.NoClassDefFoundError: javax/el/ValueExpression
>       at java.lang.Class.getDeclaredMethods0(Native Method)
>       at java.lang.Class.privateGetDeclaredMethods(Class.java:2475)
>       at java.lang.Class.privateGetPublicMethods(Class.java:2595)
>       at java.lang.Class.getMethods(Class.java:1437)
> {noformat} 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to