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 ji...@apache.org on 2004/06/04 04:36:53 UTC

[jira] Created: (JS2-68) PortalCache needs to be updated when a portlet app is undeployed

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-68

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-68
    Summary: PortalCache needs to be updated when a portlet app is undeployed
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Jetspeed 2
   Versions:
             2.0-dev/cvs
             2.0-a1

   Assignee: 
   Reporter: Scott T Weaver

    Created: Thu, 3 Jun 2004 7:36 PM
    Updated: Thu, 3 Jun 2004 7:36 PM

Description:
The PortletCache needs to have a removeAll(PortletApplicationDefinition) method added so that when a portlet app is hot undeployed that all of its associated portlet definitions are removed from the cache.

This is required because the cached Portlet is holding onto an instance of the ServletContext.  When servlet application that ServletContext belongs to is undeployed by tomcat, the ServletContext becomes invalid causing multiple issues including:

1. Redployed servlet classes seemed to be cached within the invalid SC, and do not allow for the new sevlet class(es) to be loaded.

2. SC.getRequestDispatcher() returns a null object causing all kind of headaches.   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

[jira] Updated: (JS2-68) PortalCache needs to be updated when a portlet app is undeployed

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Scott T Weaver (mailto:weaver@apache.org)
       Date: Thu, 3 Jun 2004 7:36 PM
    Changes:
             assignee changed to Scott T Weaver
             Version changed to 2.0-dev/cvs
             Version changed to 2.0-a1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/JS2-68?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-68

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-68
    Summary: PortalCache needs to be updated when a portlet app is undeployed
       Type: Bug

     Status: Open
   Priority: Major

    Project: Jetspeed 2
   Versions:
             2.0-dev/cvs
             2.0-a1

   Assignee: Scott T Weaver
   Reporter: Scott T Weaver

    Created: Thu, 3 Jun 2004 7:36 PM
    Updated: Thu, 3 Jun 2004 7:36 PM

Description:
The PortletCache needs to have a removeAll(PortletApplicationDefinition) method added so that when a portlet app is hot undeployed that all of its associated portlet definitions are removed from the cache.

This is required because the cached Portlet is holding onto an instance of the ServletContext.  When servlet application that ServletContext belongs to is undeployed by tomcat, the ServletContext becomes invalid causing multiple issues including:

1. Redployed servlet classes seemed to be cached within the invalid SC, and do not allow for the new sevlet class(es) to be loaded.

2. SC.getRequestDispatcher() returns a null object causing all kind of headaches.   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

[jira] Closed: (JS2-68) PortalCache needs to be updated when a portlet app is undeployed

Posted by ji...@apache.org.
Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-68

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-68
    Summary: PortalCache needs to be updated when a portlet app is undeployed
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Jetspeed 2
   Fix Fors:
             2.0-dev/cvs
             2.0-a1
   Versions:
             2.0-dev/cvs
             2.0-a1

   Assignee: Scott T Weaver
   Reporter: Scott T Weaver

    Created: Thu, 3 Jun 2004 7:36 PM
    Updated: Thu, 3 Jun 2004 7:40 PM

Description:
The PortletCache needs to have a removeAll(PortletApplicationDefinition) method added so that when a portlet app is hot undeployed that all of its associated portlet definitions are removed from the cache.

This is required because the cached Portlet is holding onto an instance of the ServletContext.  When servlet application that ServletContext belongs to is undeployed by tomcat, the ServletContext becomes invalid causing multiple issues including:

1. Re-deployed servlet classes seemed to be cached within the invalid SC, and do not allow for the new sevlet class(es) to be loaded.

2. SC.getRequestDispatcher() returns a null object causing all kind of headaches.   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

[jira] Updated: (JS2-68) PortalCache needs to be updated when a portlet app is undeployed

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Scott T Weaver (mailto:weaver@apache.org)
       Date: Thu, 3 Jun 2004 7:37 PM
    Changes:
             description changed from The PortletCache needs to have a removeAll(PortletApplicationDefinition) method added so that when a portlet app is hot undeployed that all of its associated portlet definitions are removed from the cache.

This is required because the cached Portlet is holding onto an instance of the ServletContext.  When servlet application that ServletContext belongs to is undeployed by tomcat, the ServletContext becomes invalid causing multiple issues including:

1. Redployed servlet classes seemed to be cached within the invalid SC, and do not allow for the new sevlet class(es) to be loaded.

2. SC.getRequestDispatcher() returns a null object causing all kind of headaches.    to The PortletCache needs to have a removeAll(PortletApplicationDefinition) method added so that when a portlet app is hot undeployed that all of its associated portlet definitions are removed from the cache.

This is required because the cached Portlet is holding onto an instance of the ServletContext.  When servlet application that ServletContext belongs to is undeployed by tomcat, the ServletContext becomes invalid causing multiple issues including:

1. Re-deployed servlet classes seemed to be cached within the invalid SC, and do not allow for the new sevlet class(es) to be loaded.

2. SC.getRequestDispatcher() returns a null object causing all kind of headaches.   
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/JS2-68?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-68

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-68
    Summary: PortalCache needs to be updated when a portlet app is undeployed
       Type: Bug

     Status: Open
   Priority: Major

    Project: Jetspeed 2
   Versions:
             2.0-dev/cvs
             2.0-a1

   Assignee: Scott T Weaver
   Reporter: Scott T Weaver

    Created: Thu, 3 Jun 2004 7:36 PM
    Updated: Thu, 3 Jun 2004 7:37 PM

Description:
The PortletCache needs to have a removeAll(PortletApplicationDefinition) method added so that when a portlet app is hot undeployed that all of its associated portlet definitions are removed from the cache.

This is required because the cached Portlet is holding onto an instance of the ServletContext.  When servlet application that ServletContext belongs to is undeployed by tomcat, the ServletContext becomes invalid causing multiple issues including:

1. Re-deployed servlet classes seemed to be cached within the invalid SC, and do not allow for the new sevlet class(es) to be loaded.

2. SC.getRequestDispatcher() returns a null object causing all kind of headaches.   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org