Neeme Praks wrote:
<snip>
> 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>
This should be fine... just use the properties on Entries.
> 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>
attribute please. We are using attributes on entries already.
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
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]
