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 bu...@apache.org on 2002/10/16 17:04:39 UTC

DO NOT REPLY [Bug 13696] New: - Cache trouble when using references to an abstract portlet in XREG

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13696>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13696

Cache trouble when using references to an abstract portlet in XREG

           Summary: Cache trouble when using references to an abstract
                    portlet in XREG
           Product: Jetspeed
           Version: 1.4b1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Cache
        AssignedTo: jetspeed-dev@jakarta.apache.org
        ReportedBy: apernoud@sopragroup.com


Cache handle is buggy when you create an XREG that has an "abstract" type for a 
portlet and two others portlets (or more) that are references to this abstract 
entry, and that doesn't have any parameters of their own.

If cache is enable, adding both portlets on a pane has side effects (none 
showing, both minimizing...).

Raphael Luta said (on j-users) :

What you describe may be a bug in portlet cache left other from the days
when portlet did not have any unique ID and the cache was using the parameter 
list/values to identify the instances...

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>