[jira] Updated: (PLUTO-75) Pluto unkind on WebSphere Application Developer (WSAD)

[pl...@jakarta.apache.org]

The following issue has been updated:

    Updater: David DeWolf (mailto:ddewolf@apache.org)
       Date: Tue, 19 Oct 2004 6:11 AM
    Comment:
Moving to Portal Driver category.
    Changes:
             priority changed from Major to Minor
             Component changed to portal driver
             Component changed from general
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/PLUTO-75?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/PLUTO-75

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: PLUTO-75
    Summary: Pluto unkind on WebSphere Application Developer (WSAD)
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Pluto
 Components: 
             portal driver

   Assignee: 
   Reporter: BIll Birch

    Created: Mon, 18 Oct 2004 4:21 AM
    Updated: Tue, 19 Oct 2004 6:11 AM
Environment: WSAD 5.1.2
Windows 2000

Description:
class PortletDefinitionRegistryServiceFileImpl assumes a tomcat style directory structure such as

  pluto/WEB-INF/..

WSAD likes to deploy projects with a structure such as :

  pluto/WebContent/WEB-INF/..

pluto searches through all the directories looking for "portlet.xml" and "web.xml". When it finds one it assumes it's a portlet app. Unfortunately it assumes the app name is "WebContent". This string gets into the PortletApplicationDefinition in many places including the portlet ids e.g. "WebContent.TestPortlet2". This in turn means that none of the objects can be found in the PortletApplicationDefinitionList when needed. 

PortletApplicationDefinitionListImpl.get(ObjectID objectId) returns null (instead of chucking an exception). The null pointer returned fails higher up the stack.

Also, you have to set the WebSphere "Shared Session Context" tickbox in the EAR deployment descriptor as an equivalent to tomcat's crossContext=true

Also, for some reason the PortletDefinitionRegistryServiceFileImpl cannot see all the webapps under WSAD, maybe contextroot is one level too low? I had to copy the portlet.xml into the pluto project from testsuite.










---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira