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]
