[jira] Updated: (PLUTO-276) Do not force cross servlet contex when portlet window context path is same as servlet context path

["Daniel Krieg (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/PLUTO-276?page=all ]

Daniel Krieg updated PLUTO-276:
-------------------------------

    Attachment: pluto-1.1.0-crossContextFree.diff

This patch corrects pluto-container components by comparing the portletWindow contextPath with the servletContext contextPath and only if they are different does it issue servletContext.getContext(contextPath).  I have testing this patch on Tomcat 5.5.9 and I have successfully utilized pluto-portal as a 'starter' webapp and have been able to develop and test new portlets with this webapp.  One issue that I encountered for which I am creating another ticket is that the Castor mapping is unable to unmarshall the portlet.xml file unless the root element excludes the namespace attributes as such:
<portlet-app> 
...instead of ...
<portlet-app
    xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd"
    version="1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd
                        http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd">


> Do not force cross servlet contex when portlet window context path is same as servlet context path
> --------------------------------------------------------------------------------------------------
>
>                 Key: PLUTO-276
>                 URL: http://issues.apache.org/jira/browse/PLUTO-276
>             Project: Pluto
>          Issue Type: Improvement
>          Components: portlet container
>    Affects Versions: Current CVS
>            Reporter: Daniel Krieg
>         Attachments: pluto-1.1.0-crossContextFree.diff
>
>
> Several component issue servletContext.getContext(contextPath) thus forcing a 'crossContext' enabled deployment senario and preventing a truly embedded Pluto implementation.

-- 
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