Hello All, I just began work on the portlet version of the calendar since using turbine screens was -1'ed. Plus, i was running into some problems anyway :(... Anyway, what is everyones thoughts on associating actions with portlets. Should we Option 1. Should we create a PortletWithAction that has an Action property subclass. Option 2. Should we add an Action property directly onto the portlet. Option 3. Should we let the programmer execute any actions he wishes inside the init() method Option 4. Use the normal turbine action mechanism OPTION 1 My feelings on this are definitely -1. I dont think we should sub-class Portlet. This could get ugly over time as we think of more special cases... Which leads to option 2. Adding a getAction, setAction method onto the Portlet Interface and having the action automatically executed. OPTION 2 Option 2 seems viable, but would require some changes to the Portlet execution mechanism that I dont yet fully understand. Basically, we would have to modify the portlet execution method to execute the action before calling the init() method. I also dont know what would be the best way to specify the Action before calling the init() method. Where would this happen. OPTION 3 Option 3 is the simplest method, but I am not sure how elegant leaving that up to the programmer is. Here I will liken the init method to the turbine buildScreen method. They are both respsonible for creating the content. With that being said turbine has separated the act of performing a non-UI task into an Action and a UI task into screens, navigations, etc. This buys turbine a lot of power in dealing with non-UI tasks vs UI-tasks. The Action class basically consists of one publicly accessible method doPerform. IMHO, we can and should encourage programmers using Jetspeed API to use Actions to abstract out non-UI work... OPTION 4 Use the normal turbine action mechanism to specify an action. I am not sure this is even viable for a couple of reasons. I am not sure how to specify more than one action on a screen. As you know we can have many portlets to a page. First off using the Turbine action mechanism even if we can have more than one action per screen, there is no way to distinguish which action is for which portlet which I think would be important. Anyway, I like Option 2, but am going to forge ahead with the first cut of the calendar using Option 3. Just thinking out loud. I need some guidance here as tying the calendar objects to a portlet will be my first real foray into Kevin and Rafael's world. Thanke Jeff Prickett [EMAIL PROTECTED] -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
