portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor" <da...@bluesunrise.com>
Subject RE: Question on Muliple portlet instance behavior
Date Fri, 28 Jun 2002 18:44:25 GMT

I don't like the naming of PersistentPor(t)let.
I think what we are really working with are portlet instances. Why not
call it 'PortletInstance'.
Would also recommend moving PortletInstance interface into
org.apache.jetspeed.portal package.

Then given a portlet, you could get back an instance:

PortletInstance pi = portlet.getInstance();   
String attribute = pi.getAttribute(name);

Do you have any unit tests for the service?
If not, I would be glad to write one. 

So do you want me to take it from here?
I can do this:

1. change interface name and package to
2. clean up the code a bit
3. write the unit tests
4. remove old persistence code
5. modify all existing code to use the new service
6. check it in

This is great. This refactoring has been long overdue. Thanks Scott!


-----Original Message-----
From: Weaver, Scott [mailto:Sweaver@rippe.com] 
Sent: Friday, June 28, 2002 8:45 AM
To: 'Jetspeed Developers List'
Subject: RE: Question on Muliple portlet instance behavior

Hi David, 
I re-designed the persistence mechanism to be more object oriented and
easier to use than my first iteration. 
There is now PersistentPortlet interface and a concrete implementation,
JetspeedPersistentPortlet.  The PersistenceService now only has 3
methods two to retrieve a PersistentPortlet and one to store it.
All operations are performed through the PersistentPortlet as opposed to
the PersistenceService itself, save for retrieval and storage.  This has
allowed me to simplify the methods used to set, get and remove portlet
> -----Original Message----- 
> From: David Sean Taylor [mailto:david@bluesunrise.com] 
> Sent: Thursday, June 27, 2002 6:02 PM 
> To: 'Jetspeed Developers List' 
> Subject: RE: Question on Muliple portlet instance behavior 
> Scott, 
> Had a quick look. 
> Few comments: 
> jData.getProfile();                 -- this will always get you the 
> current profile, good! 
> doc.getEntryById(portlet.getID())   -- great, that will get the
> instance! 
> Looking good, I will review it in more detail tomorrow. 
> Thanks, 
> David 
> -----Original Message----- 
> From: Weaver, Scott [mailto:Sweaver@rippe.com] 
> Sent: Thursday, June 27, 2002 2:31 PM 
> To: 'Jetspeed Developers List' 
> Subject: RE: Question on Muliple portlet instance behavior 
> David, 
> Here is what I finished today.  There is a service interface, an 
> implementation and a fa├žade class to access the service plus an 
> exception. 
> I have tested the get and set and they are working and are aware of 
> individual portlet instances.  I have yet change AbstractPortlet and 
> test it there.  Hopefully, I will get to that tomorrow.  I also still 
> need to add the Apache license to the classes and better
> I will be adding more methods as I get to them/think of them: 
> getPortletAttributeList(),getPortletAttributeNames(), etc. 
> Let me know of another other important functionality I may not have 
> thought of/been aware of. 
> Thanks, 
> Scott 
> -- 
> To unsubscribe, e-mail:   <mailto:jetspeed-dev- 
> unsubscribe@jakarta.apache.org> 
> For additional commands, e-mail: <mailto:jetspeed-dev- 
> help@jakarta.apache.org> 

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

View raw message