> -----Original Message-----
> From: Rapha�l Luta [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 24, 2000 11:14 AM
[snip]
>
> Yes, certainly. The <skin> is defined for a given *element*
> not a global property
> Children a elements inherit these settings and may override them.
> Using a property based system in this case require defining a
> CSS-like element
> selector and process it server-side...
>
> > > Could someone more knowledgeable explain the main
> differences between
> > > these? And how are they used by portlets, controls anbd
> controllers?
> > <snip>
> >
> > I see your point on the <metainfo><title> stuff. Although
> I think this
> > is cleaner than:
> >
> > jetspeed.title
> >
>
> Actually I don't like the <metainfo><title> stuff, I think
> this should really be
> handled by the Dublin Core schema, as in:
>
> <portlets xmlns="http://java.apache.org/jetspeed/xsd/psml/1.0/"
> xmlns:dc="http://purl.org/dc/elements/1.0/">
>
> <dc:title>myTitle</dc:title>
> <dc:description>myDescription</dc:description>
> <dc:language>EN</dc:language>
>
> <!-- ... -->
> </portlets>
>
> This would allow PSML to focus on its core task: describing
> portlet sets layout while
> still keeping readability, schema validation, etc...
well, it looks good in theory... however, with the current
implementation of our XML access using Castor, one would still need to
regenerate the classes if one would like to access a new element...
Or if we would generate the Castor classes for entire dublin core, then
maybe that would be sufficient... but then there is still the issue of
namespace support in Castor... as I understood, it doesn't support
namespaces yet?
It would be more flexible, if we would use something like JDOM for
accessing XML? Is there any reason for using Castor, besides the
simplicity of that approach?
Neeme
--
--------------------------------------------------------------
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]
