Re: Comments on Pages

----- Original Message -----
From: "Anthony Eden" <[email protected]>
To: "'jpublish-developer'" <[email protected]>
Sent: Monday, October 21, 2002 9:46 AM
Subject: RE: [JPublish-developer] Comments on Pages


>
>
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On
> > Behalf Of Derick Fernando
> > Sent: Thursday, October 17, 2002 9:53 PM
> > To: 'jpublish-developer'
> > Subject: [JPublish-developer] Comments on Pages
> >
> >
> > Hello,
> >
> > I'd like to throw some ideas, questions in the air about
> > JPublish pages and they way it handles them. I like the way
> > things are set up, Pages can be in one XML file or individual
> > xml files, all in all pages are awesome.
> >
> > What are opinions on creating a dynamic page "repository"?
>
> Well, as you point out in your next message this is already possible
> within JPublish Professional, and that is due to the
> getPageConfigurationWriter() method in the PageManager interface (which
> will be made even easier with the putPage() method once it is
> implemented in all of the PageManager implementation classes).
>
> The DBPageManager is still in the works though, and I am still trying to
> figure out how it should be done.  I don't really want to store the XML
> document in a single field in the database, rather I would like to
> convert the XML document into a more relational format, but that may not
> be possible considering a.) pages supported an unlimited number of
> name/value properties and b.) page actions can have arbitrary XML
> configurations.  Suggestions on this issue are welcome.
>

Hmm, You could create a table that holds the properties as foreign keys (an
id telling it which jpublish.xml it belongs to). With something like Torque
you don't really need to worry about getting and setting those properties or
managing ID's, so it might make it fairly simple. Just my 2 cents :).

Derick



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future of 
Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
http://www.sun.com/javavote