Hello Randy,
I admit that I know little about Graffito; I just looked at the Web site
and got a first impression. I'd just like to state one concern (and
maybe this turns out to be no issue at all). "Storing PSML in Graffito"
and the management portlets mentioned on the web page arise in my mind
the picture of a managed environment that may turn out to be "closed" to
batch setup.
I'm using Jetspeed2 as a framework for an application, i.e. I bundle it
with several portlets, EJBs etc. to get a ready to run EAR. The
possibility to change the portal at runtime is nice, but of minor
importance. For this kind of usage, it is very important that I can
build a runnable Jetspeed configuration automatically from my sources.
Currently, it is no problem to maintain the PSML files and copy them in
the proper directory before bundling Jetspeed. Things would be much more
difficult if e.g. the PSML would be stored in a database. Of course,
storing it in a database has advantages for changing the portal at
run-time....
So if configuration should no longer be possible my maintaining the
pages "manually" in an editor and copying them in the right place, then
there should at least be support for some kind of "setup directory".
This directory would be scanned on startup and the data integrated in
the Graffito database. I could put my page sources there, bundle, and my
pages would be available after application startup.
Sorry for the noise if everybody else knows that this is no problem at
all. And as you said that your component should be optional, leaving it
out of my configuration may be a way, too. It is just that I know that
many people think of a portal as something that is configured over time
by an administrator and saved by making database backups, whereas I need
the possibility to create a valid portal configuration from sources;
hence my concern.
Regards,
Michael
Randy Watler wrote:
> Graffito Dev Team,
>
> For those that do not recognize me, I am a committer on the J2 portal team.
>
> Although I have been threatening to do this for some time, I am finally
> getting started on the integration of Graffito into J2 as a PageManager
> component. The intent is to store the PSML that currently resides in the
> file system in Graffito as XML documents. We will also want to leverage
> many of Graffito's features in the J2 implementation, including security
> and modification notification/timestamps.
>
> There are new patches to the J2 svn HEAD version related to Connection
> management, (see JS2-326), that should allow us to update the J2
> deployment past the M3 support currently in place.
>
> My personal goal is to commit this optional component into J2 for M4.
>
> Of course, many thanks for developing, managing, and promoting Graffito.
>
> Randy Watler
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
