You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Dominik Drzewiecki (JIRA)" <ji...@apache.org> on 2010/11/05 12:13:45 UTC
[jira] Created: (WICKET-3148) Dropped support for Servlet 2.5
inadvertently
Dropped support for Servlet 2.5 inadvertently
---------------------------------------------
Key: WICKET-3148
URL: https://issues.apache.org/jira/browse/WICKET-3148
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.5-M3
Reporter: Dominik Drzewiecki
Priority: Critical
Fixing 3146 in r1031086 resulted in introducing a dependency on javax.servlet.annotation.* thus rendering WicketFilter unusable in pre-3.0 servlet containers.
If pruning the large base of 2.5-compatible containers was intentional then I'd also suggest switching to java 6 (Although servlet 3.0 specs does not explicitly indicate java 6 as a requirement, all 3.0 compliant containers that I'm aware of - namely Jetty 8, Websphere 8, tomcat 7, glassfish 3 - require java 6). Not to mention that this should be spoken out loud (https://cwiki.apache.org/WICKET/migration-to-wicket-15.html does not mention anything about container compliance)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3148) Dropped support for Servlet 2.5
inadvertently
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-3148.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M4
Assignee: Igor Vaynberg
> Dropped support for Servlet 2.5 inadvertently
> ---------------------------------------------
>
> Key: WICKET-3148
> URL: https://issues.apache.org/jira/browse/WICKET-3148
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Dominik Drzewiecki
> Assignee: Igor Vaynberg
> Priority: Critical
> Fix For: 1.5-M4
>
>
> Fixing 3146 in r1031086 resulted in introducing a dependency on javax.servlet.annotation.* thus rendering WicketFilter unusable in pre-3.0 servlet containers.
> If pruning the large base of 2.5-compatible containers was intentional then I'd also suggest switching to java 6 (Although servlet 3.0 specs does not explicitly indicate java 6 as a requirement, all 3.0 compliant containers that I'm aware of - namely Jetty 8, Websphere 8, tomcat 7, glassfish 3 - require java 6). Not to mention that this should be spoken out loud (https://cwiki.apache.org/WICKET/migration-to-wicket-15.html does not mention anything about container compliance)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3148) Dropped support for Servlet 2.5
inadvertently
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928950#action_12928950 ]
Hudson commented on WICKET-3148:
--------------------------------
Integrated in Apache Wicket 1.5.x #488 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/488/])
> Dropped support for Servlet 2.5 inadvertently
> ---------------------------------------------
>
> Key: WICKET-3148
> URL: https://issues.apache.org/jira/browse/WICKET-3148
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Dominik Drzewiecki
> Assignee: Igor Vaynberg
> Priority: Critical
> Fix For: 1.5-M4
>
>
> Fixing 3146 in r1031086 resulted in introducing a dependency on javax.servlet.annotation.* thus rendering WicketFilter unusable in pre-3.0 servlet containers.
> If pruning the large base of 2.5-compatible containers was intentional then I'd also suggest switching to java 6 (Although servlet 3.0 specs does not explicitly indicate java 6 as a requirement, all 3.0 compliant containers that I'm aware of - namely Jetty 8, Websphere 8, tomcat 7, glassfish 3 - require java 6). Not to mention that this should be spoken out loud (https://cwiki.apache.org/WICKET/migration-to-wicket-15.html does not mention anything about container compliance)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3148) Dropped support for Servlet 2.5
inadvertently
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928599#action_12928599 ]
Igor Vaynberg commented on WICKET-3148:
---------------------------------------
better with r1031572?
> Dropped support for Servlet 2.5 inadvertently
> ---------------------------------------------
>
> Key: WICKET-3148
> URL: https://issues.apache.org/jira/browse/WICKET-3148
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Reporter: Dominik Drzewiecki
> Priority: Critical
>
> Fixing 3146 in r1031086 resulted in introducing a dependency on javax.servlet.annotation.* thus rendering WicketFilter unusable in pre-3.0 servlet containers.
> If pruning the large base of 2.5-compatible containers was intentional then I'd also suggest switching to java 6 (Although servlet 3.0 specs does not explicitly indicate java 6 as a requirement, all 3.0 compliant containers that I'm aware of - namely Jetty 8, Websphere 8, tomcat 7, glassfish 3 - require java 6). Not to mention that this should be spoken out loud (https://cwiki.apache.org/WICKET/migration-to-wicket-15.html does not mention anything about container compliance)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.