David,
While what you've done works, you must be aware that you've actually modified
a Castor auto-generated class:
org.apache.jetspeed.xml.api.portletmarkup.Portlets
and thus you cannot depend anymore on the API regeneation during the build
process, which may be very painful.
To address the current limitation of the PSML implementations, I'm working on
an interface based PSML object model with hand written implementation and
a loading service, just like we have for the Registry.
This should allow you to load PSML data from any source an is much cleaner than
modifying an auto-generated API.
David Halsted wrote:
> Sure. We took a version of CastorPsmlManagerService called
> DatabasePsmlManagerService that is being worked on by a group of people --
> our contact is Atul Dambalkar ([EMAIL PROTECTED]), but there are several
> other authors. The version we have of DatabasesPsmlManagerService isn't
> finished, but looks as though it anticipates that a PSML will be stored as a
> binary chunk, and we have that information already in other spots in a
> database, so it'd be redundant to store it as an XML in the database that
> essentially summarizes information already available elsewhere. Therefore,
> we added unmarshal(Class, Node) (I think -- haven't got the code in front
> of me at the moment) to org.apache.jetspeed.xml.api.portletmarkup.Portlets;
> that calls org.exolab.castor.xml.Unmarshaller.unmarshal(Node) in Castor.
> That let us create a Portlets directly from a DOM instead of using a Reader,
> so we could skip writing and reading a file as an intermediary step.
>
> I can send bits of code to anybody who's interested. If other people are
> interested in doing this, the unmarshal() bit we added to Portlets is pretty
> innocent and might be a candidate for inclusion in the code base.
>
> Best,
>
> Dave Halsted
>
> -----Original Message-----
> From: Dave Carlson [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 31, 2001 12:46 PM
> To: [EMAIL PROTECTED]
> Subject: PSML from DOM Document
>
> I'm especially interested in this point because I've considered using dbXML
> as a native XML database to store psml. dbXML allows me to query the
> database and return a DOM Document, or as SAX stream. This may be a quick
> solution to a scalable storage of psml, without having to map to a
> relational dbms.
>
> A very brief summary of how you accomplished this would be helpful!
>
> Dave
>
>
>>-----Original Message-----
>>From: David Halsted [mailto:[EMAIL PROTECTED]]
>>
>
>>Today, for example, we got Jetspeed to read PSML
>>information from an org.w3c.dom.Document, rather than a file;
>>that's kind of
>>handy.
>>
>>
>
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
