Neeme Praks wrote:
>
> > -----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,
You can use Schema and just a subset of dublic core. Only the subset
should be generated.
> 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?
not sure here... it doesnt' support them perfectly but I am not sure
what you mean.
> 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?
As far as abastraction here is how I see it:
DOM/SAX <-> JDOM <-> Castor
Castor is higher than JDOM because it uses data typing. Also, I don't
want to add another library just for this.
It would be nice if the RSSPortlet used JDOM though.
Kevin
--
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]
