I would be happy with STORING the settings as preferences, but the underlying requirement is to be able to create a dynamic and arbitrary number of portlet instances that will all have different specific settings. For this, the people who manage the content need to be able to change and implement the settings in the content (PSML) and not as a programmatic change (as far as they are concerned anyway). In many larger installations, the people who deploy portlets and the people who manage the content are not going to be the same people with the same duties. That is where this is coming from.
Thanks for all the info. Chris On 6/27/05, Boyce, Keith Garry <[EMAIL PROTECTED]> wrote: > > > Well also you could deploy 1 portlet and a default preference and the > administrator can change the preference for each portlet whereever it's > displayed... You can also write some thing to modify preferences of portlet > automatically... (Haven't figured that one out yet but it's possible) > > > -----Original Message----- > From: James Liao [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 26, 2005 10:29 PM > To: Jetspeed Users List > Subject: Re: Passing parameters to portlet from PSML > > Yes, preferences are standard. I think you can define three portlet entity > in the same porltet.xml, give them different portlet id, different portlet > name and different default preferences value for the same preferences. But > the porlet-class can be same. > Hope it works. > -James Liao > > On 6/27/05, Boyce, Keith Garry <[EMAIL PROTECTED]> wrote: > > > > It has been told to me that the better way to was parameters to portlets > is through portlet preferences.. It is the standard way to do this.. > > Psml is jetspeed specific. Preferences are standard.. > > > > -----Original Message----- > > From: Paul ANDERSON [mailto:[EMAIL PROTECTED] > > Sent: Sunday, June 26, 2005 5:24 AM > > To: Jetspeed Users List > > Subject: RE: Passing parameters to portlet from PSML > > > > I asked this question, and with help from the list, I now use something > like: > > > > Page p = (Page)request.getAttribute("org.apache.jetspeed.Page"); > > String param = ((Node)p).getTitle(new Locale("xx")); > > > > I abuse the psml page title in locale 'xx'. It's dirty and > Jetspeed-specific, but maybe this is enough for you until M4. > > > > Paul > > > > -----Message d'origine----- > > De: Chris Custine [mailto:[EMAIL PROTECTED] Envoyé: 24 June > > 2005 20:49 À: Jetspeed Users List Objet: Re: Passing parameters to > > portlet from PSML > > > > I did find your message on jetspeed-dev. Do you have any code checked in > to support this (current SVN)? I would love to have this available and I > would offer to help test and maybe work on some small parts. I deperately > need this so let me know if I can help. > > > > Chris > > > > > > On 6/24/05, Raphaël Luta <[EMAIL PROTECTED]> wrote: > > > > > > I'm currently working to have PSML-page defined portlet preferences > > > implemented for J2 M4. Check out the jetspeed-dev mailing-list for > > > more information. > > > > > > -- raphael > > > > > > Randy Watler wrote: > > > > Chris, > > > > > > > > One can define properties in the psml page fragments, (see the > > > > castor page-mapping.xml file in > components/page-manager/src/java/META-INF). > > > > Assuming that your portlet code can access the current fragment > > > > and consume them, you should be set. > > > > > > > > I have not actually done this, so YMMV and I am not sure how to > > > > get the properties in the portlet code out of the portlet request. > > > > If you do succeed, please add to the wiki or this list with a reply. > > > > > > > > Thanks, > > > > > > > > Randy > > > > > > > > Chris Custine wrote: > > > > > > > >> This pertains to J2 BTW. > > > >> > > > >> On 6/23/05, Chris Custine <[EMAIL PROTECTED]> wrote: > > > >> > > > >> > > > >>> I remember seeing this question before but I can't find any > > > >>> outcome anywhere. I have a portlet that I want to parameterize > > > >>> so that I can use it in several places but have slight > > > >>> customizations for each instance. So for example, lets say I > > > >>> want the same weather portlet 3 times on a page but each one has > > > >>> a different city. I don't want this to be a per user preference, > > > >>> I want the admin to be able to specify the parameter in PSML so > > > >>> that the users all get the same thing. Is there (or will there > > > >>> be) a way to pass a parameter from the PSML so that the fragments > get the cities passed to them (and or all users). > > > >>> I hope this question makes sense, if not I can elaborate. > > > >>> > > > >>> Thanks, > > > >>> Chris > > > >>> > > > > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > This message is a PRIVATE communication. > > If you are not the intended recipient, please do not read, copy, or > > use it, and do not disclose it to others. Please notify the sender of > > the delivery error by replying to this message, and then delete it > > from your system. Thank you. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > This message is a PRIVATE communication. > If you are not the intended recipient, please do not read, copy, > or use it, and do not disclose it to others. Please notify the > sender of the delivery error by replying to this message, and then > delete it from your system. Thank you. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
