portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Updated: (JS2-614) Jetspeed Deploy compliant with servlet spec 2.4
Date Thu, 23 Nov 2006 13:13:02 GMT
     [ 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


Mime
View raw message