I would like to add one more point: the current markup of user PSML
files is really confusing: we have three different ways of passing
information to the portlet:
skins:
<skin>
<property name="selected-color" value="#BEBEFF"/>
<property name="background-color" value="FFFFFF"/>
</skin>
parameters:
<parameter name="name" value="mmail"/>
and metadata/metainfo:
<metainfo>
<title>M.Mail</title>
</metainfo>
Could someone more knowledgeable explain the main differences between
these? And how are they used by portlets, controls anbd controllers?
Kevin, Rapha�l, Jeff?
Neeme
> -----Original Message-----
> From: Neeme Praks
> Sent: Thursday, July 20, 2000 4:28 PM
> To: JetSpeed
> Subject: RE: more customization features
>
>
> coming back to one old issue...
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]
> > Sent: Sunday, June 11, 2000 9:21 PM
>
> [snip]
>
> > > ok, this is fine when you don't want to check the markup in
> > the registry
> > > against a DTD or XML Schema. However, when you want to enforce the
> > > schema, then there is no easy way for Jetspeed users to add
> > new metadata
> > > used in controllers.
> >
> > use a namespace. The issue is currently with the castor code
> > which doesn't handle well namespaces.
>
> Well, I added a couple of my own metadata parameters... as they depend
> on the schema, it is a really big hassle: you have to re-generate the
> api with Castor then add the wrapper methods to util.MetaData and then
> finally you get access to it from portletconfig. A real pain. And I
> don't see how namespaces would solve this, you would still have to
> generate the api with Castor, right?
>
> So, I'm still suggesting to use something like
> <portletset>
> <metadata>
> <property name="foo" value="bar"/>
> </metadata>
> </portletset>
>
> And then allow to access this in a similar manner as in
> ParameterParser
> (in Turbine):
> portlet.getPortletConfig().getMetaData().getString("foo")
>
> This way you wouldn't need to generate the api again-and-again.
>
> Also we discussed adding name parameter to portletset and portlet
> markup, where should it go? In attributes or in elements?:
> <portletset name="foo">
> </portletset>
> or
> <portletset>
> <name>foo</name>
> </portletset>
>
> Neeme
>
> (I also saw some locale stuff in metadata classes... what is
> the purpose
> of this, how is it supposed to be used?)
>
>
> --
> --------------------------------------------------------------
> 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]
>
>
--
--------------------------------------------------------------
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]
