portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randy Watler (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-350) Implement Graffito based PageManager for PSML
Date Wed, 24 Aug 2005 21:16:08 GMT
    [ http://issues.apache.org/jira/browse/JS2-350?page=comments#action_12319913 ] 

Randy Watler commented on JS2-350:

From: Michael.Lipp@danet.de

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

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.



> Implement Graffito based PageManager for PSML
> ---------------------------------------------
>          Key: JS2-350
>          URL: http://issues.apache.org/jira/browse/JS2-350
>      Project: Jetspeed 2
>         Type: New Feature
>   Components: PSML
>     Versions: 2.0-M4, 2.0-FINAL
>     Reporter: Randy Watler
>     Assignee: Randy Watler
>      Fix For: 2.0-M4, 2.0-FINAL

> Integrating a CMS in J2 for PSML as a PageManager has long been sought to provide a PSML
repository solution for clustered deployments. Graffito is the obvious technical component
choice since it is part of the portals project!
> This project is fairly open ended at the moment, but should include at least a PageManager
implementaion that uses Graffito and the integration of the Graffito browser and editor portlets.
> I have opened this issue to serve as a way to collect comments and requirements as the
project progresses.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message