[ http://issues.apache.org/jira/browse/JS2-383?page=comments#action_12332854 ]
Michael Lipp commented on JS2-383: ---------------------------------- >From your comment, I'm not sure: are you going to implement this or do you >think the issue needs further discussion? I have another example (besides the >RSS example that I consider pretty convincing ;-)). I have written a portlet that can be used in two modes: If you have limited space, you use it both as browser and as detail viewer (i.e. display switches when you select a detail). If you have more space on your page, you can use one instance as a browser and another instance as the "connected" detail viewer (i.e. the portlet has a "mode" preference that determines its behaviour). If configuring the portlet in the page description (as browser or as detail viewer) is considered "evil" I cannot layout the browser/detail viewer combination, I can just layout two unconfigured generic instances and can let the user wonder (and describe the issue in the manual; and hope the user reads the manual -- obviously not a real world scenario). Of course, as a work-around, I could describe three portlets types instead of one in portlet.xml. They'd all be similar except for the name and the preferences. While this might be feasable for a mode preference with three possible values, this really becomes ridiculous if there are more values or preferences (e.g. the URL preference of the RSS portlet has an almost unlimited number of possible values). It it is also hardly feasable if I get a pre-packaged portlet.xml and have to patch the portlet.xml for every new version in order to define the required portlet instances as portlet types. The bottom line is: the page description is about laying out portlet instances. But in general, a portlet instance is not a portlet type, it is a portlet type plus some initial configuration information, and that's why we need the possibility to specify this information when laying out portlets. > Configuring portlet in PSML > --------------------------- > > Key: JS2-383 > URL: http://issues.apache.org/jira/browse/JS2-383 > Project: Jetspeed 2 > Type: New Feature > Components: PSML > Reporter: Michael Lipp > Assignee: Randy Watler > > It should be possible to provide preferences for the initial instantiation of > portlets in PSML. These preferences customize the portlet by overriding (or > adding to) the default preferences defined in the portlet.xml. > Example: If I want to have an introductory page displaying e.g. the three > most important RSS feeds, then the selection of the RSS stream is related to > layout, because I want a layout displaying e.g. "Company news", "Department > news" and "Team issues". Binding an RSS portlet to a particular feed makes it > a specific item that I want to put at a specific place. I don't want to > layout three generic RSS feeds, I want to layout company, department and team > news. > As I want to layout portlet instances, it is not sufficient to be able to > layout portlet types. Configuring the instances within PSML would be > convenient and intuitive. It would also be acceptable if I could configure > the instances in some other configuration file. But only laying out three > generic RSS portlets and handing the task to bind the feeds to the end user > is not feasable. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
