You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Nicolas Dutertry (JIRA)" <je...@portals.apache.org> on 2006/11/23 12:08:02 UTC
[jira] Created: (JS2-614) Jetspeed Deploy not compliant with
servlet spec 2.4
Jetspeed Deploy not compliant with servlet spec 2.4
---------------------------------------------------
Key: JS2-614
URL: http://issues.apache.org/jira/browse/JS2-614
Project: Jetspeed 2
Issue Type: Bug
Components: Project Build
Affects Versions: 2.1-dev
Reporter: Nicolas Dutertry
I'm using JetspeedDeploy to automatically make my portlet application ready for Jetspeed.
JetspeedDeploy adds the JetspeedContainerServlet and the portlet taglib in the web.xml. I works fine as long as I use the servlet specification 2.3.
But JetspeedDeploy is not able to be compliant with the servlet specification 2.4.
For example in 2.4 spec, the <taglib> element must be child of the <jsp-config> element, and JetspeedDeploy puts <taglib> directly under <web-app>.
It causes problem under Websphere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Assigned: (JS2-614) Jetspeed Deploy not compliant with
servlet spec 2.4
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-614?page=all ]
Ate Douma reassigned JS2-614:
-----------------------------
Assignee: Ate Douma
> Jetspeed Deploy not compliant with servlet spec 2.4
> ---------------------------------------------------
>
> Key: JS2-614
> URL: http://issues.apache.org/jira/browse/JS2-614
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Project Build
> Affects Versions: 2.1-dev
> Reporter: Nicolas Dutertry
> Assigned To: Ate Douma
>
> I'm using JetspeedDeploy to automatically make my portlet application ready for Jetspeed.
> JetspeedDeploy adds the JetspeedContainerServlet and the portlet taglib in the web.xml. I works fine as long as I use the servlet specification 2.3.
> But JetspeedDeploy is not able to be compliant with the servlet specification 2.4.
> For example in 2.4 spec, the <taglib> element must be child of the <jsp-config> element, and JetspeedDeploy puts <taglib> directly under <web-app>.
> It causes problem under Websphere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Resolved: (JS2-614) Jetspeed Deploy compliant with servlet
spec 2.4
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-614?page=all ]
Ate Douma resolved JS2-614.
---------------------------
Resolution: Fixed
Patch applied
> Jetspeed Deploy compliant with servlet spec 2.4
> -----------------------------------------------
>
> Key: JS2-614
> URL: http://issues.apache.org/jira/browse/JS2-614
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Project Build
> Affects Versions: 2.1-dev
> Reporter: Nicolas Dutertry
> Assigned To: Ate Douma
> Priority: Minor
> Fix For: 2.1, 2.1-dev
>
> Attachments: jetspeed-deploy-patch.zip
>
>
> I'm using JetspeedDeploy to automatically make my portlet application ready for Jetspeed.
> JetspeedDeploy adds the JetspeedContainerServlet and the portlet taglib in the web.xml. I works fine as long as I use the servlet specification 2.3.
> But JetspeedDeploy is not able to be compliant with the servlet specification 2.4.
> For example in 2.4 spec, the <taglib> element must be child of the <jsp-config> element, and JetspeedDeploy puts <taglib> directly under <web-app>.
> It causes problem under Websphere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Reopened: (JS2-614) Jetspeed Deploy compliant with servlet
spec 2.4
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-614?page=all ]
Ate Douma reopened JS2-614:
---------------------------
Patch broke maven-2 build
> Jetspeed Deploy compliant with servlet spec 2.4
> -----------------------------------------------
>
> Key: JS2-614
> URL: http://issues.apache.org/jira/browse/JS2-614
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Project Build
> Affects Versions: 2.1-dev
> Reporter: Nicolas Dutertry
> Assigned To: Ate Douma
> Priority: Minor
> Fix For: 2.1, 2.1-dev
>
> Attachments: jetspeed-deploy-patch.zip
>
>
> I'm using JetspeedDeploy to automatically make my portlet application ready for Jetspeed.
> JetspeedDeploy adds the JetspeedContainerServlet and the portlet taglib in the web.xml. I works fine as long as I use the servlet specification 2.3.
> But JetspeedDeploy is not able to be compliant with the servlet specification 2.4.
> For example in 2.4 spec, the <taglib> element must be child of the <jsp-config> element, and JetspeedDeploy puts <taglib> directly under <web-app>.
> It causes problem under Websphere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-614) Jetspeed Deploy compliant with servlet
spec 2.4
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-614?page=all ]
Ate Douma updated JS2-614:
--------------------------
Summary: Jetspeed Deploy compliant with servlet spec 2.4 (was: Jetspeed Deploy not compliant with servlet spec 2.4)
Issue Type: Improvement (was: Bug)
Fix Version/s: 2.1
2.1-dev
Priority: Minor (was: Major)
I've changed this issue from Bug to Improvement. Portlet spec JSR-168 requires (only) compliance with Servlet spec 2.3, so this issue is not some "specs" violation :)
The patch is great though and I've tested it out with several different web.xml versions and configurations.
Will commit the patch (with a small further enhancement, checking if a portlet.tld already exists in the war file) in a minute or so.
Thanks a lot Nicolas
> Jetspeed Deploy compliant with servlet spec 2.4
> -----------------------------------------------
>
> Key: JS2-614
> URL: http://issues.apache.org/jira/browse/JS2-614
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Project Build
> Affects Versions: 2.1-dev
> Reporter: Nicolas Dutertry
> Assigned To: Ate Douma
> Priority: Minor
> Fix For: 2.1, 2.1-dev
>
> Attachments: jetspeed-deploy-patch.zip
>
>
> I'm using JetspeedDeploy to automatically make my portlet application ready for Jetspeed.
> JetspeedDeploy adds the JetspeedContainerServlet and the portlet taglib in the web.xml. I works fine as long as I use the servlet specification 2.3.
> But JetspeedDeploy is not able to be compliant with the servlet specification 2.4.
> For example in 2.4 spec, the <taglib> element must be child of the <jsp-config> element, and JetspeedDeploy puts <taglib> directly under <web-app>.
> It causes problem under Websphere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-614) Jetspeed Deploy not compliant with
servlet spec 2.4
Posted by "Nicolas Dutertry (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-614?page=all ]
Nicolas Dutertry updated JS2-614:
---------------------------------
Attachment: jetspeed-deploy-patch.zip
Proposal for a solution
> Jetspeed Deploy not compliant with servlet spec 2.4
> ---------------------------------------------------
>
> Key: JS2-614
> URL: http://issues.apache.org/jira/browse/JS2-614
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Project Build
> Affects Versions: 2.1-dev
> Reporter: Nicolas Dutertry
> Assigned To: Ate Douma
> Attachments: jetspeed-deploy-patch.zip
>
>
> I'm using JetspeedDeploy to automatically make my portlet application ready for Jetspeed.
> JetspeedDeploy adds the JetspeedContainerServlet and the portlet taglib in the web.xml. I works fine as long as I use the servlet specification 2.3.
> But JetspeedDeploy is not able to be compliant with the servlet specification 2.4.
> For example in 2.4 spec, the <taglib> element must be child of the <jsp-config> element, and JetspeedDeploy puts <taglib> directly under <web-app>.
> It causes problem under Websphere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Resolved: (JS2-614) Jetspeed Deploy compliant with servlet
spec 2.4
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-614?page=all ]
Ate Douma resolved JS2-614.
---------------------------
Resolution: Fixed
Fixed maven-2 build by adding commons-lang build dependency.
> Jetspeed Deploy compliant with servlet spec 2.4
> -----------------------------------------------
>
> Key: JS2-614
> URL: http://issues.apache.org/jira/browse/JS2-614
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Project Build
> Affects Versions: 2.1-dev
> Reporter: Nicolas Dutertry
> Assigned To: Ate Douma
> Priority: Minor
> Fix For: 2.1, 2.1-dev
>
> Attachments: jetspeed-deploy-patch.zip
>
>
> I'm using JetspeedDeploy to automatically make my portlet application ready for Jetspeed.
> JetspeedDeploy adds the JetspeedContainerServlet and the portlet taglib in the web.xml. I works fine as long as I use the servlet specification 2.3.
> But JetspeedDeploy is not able to be compliant with the servlet specification 2.4.
> For example in 2.4 spec, the <taglib> element must be child of the <jsp-config> element, and JetspeedDeploy puts <taglib> directly under <web-app>.
> It causes problem under Websphere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org