You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Randy Watler (JIRA)" <je...@portals.apache.org> on 2005/08/24 23:05:29 UTC
[jira] Created: (JS2-350) Implement Graffito based PageManager for PSML
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
Assigned to: 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-350) Implement Graffito based PageManager for PSML
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-350?page=comments#action_12319921 ]
Randy Watler commented on JS2-350:
----------------------------------
Michael,
Thanks for the comments. A few points:
- I plan on preserving the existing file based system for some time to come.
- We believe that there will be either a file store type for Graffito so that it can be used directly over a local/remote file system or a way to at least import a populated file system directory. If not, I recognoze the need for such a thing as you outlined above... if for no other reason than porting to Graffito!
Randy
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-350) Implement Graffito based PageManager for PSML
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-350?page=all ]
Randy Watler updated JS2-350:
-----------------------------
Fix Version: 2.0-POST
(was: 2.0-FINAL)
> 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-POST
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-350) Implement Graffito based PageManager for
PSML
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma updated JS2-350:
--------------------------
Fix Version/s: (was: 2.1)
Assignee: (was: Randy Watler)
Priority: Minor (was: Major)
Issue Type: Wish (was: New Feature)
Nobody is working on this or has plans for doing so.
Scaling down to a Low Priority Wish and Unknown fix target
> Implement Graffito based PageManager for PSML
> ---------------------------------------------
>
> Key: JS2-350
> URL: https://issues.apache.org/jira/browse/JS2-350
> Project: Jetspeed 2
> Issue Type: Wish
> Components: PSML
> Affects Versions: 2.0-M4, 2.0-FINAL
> Reporter: Randy Watler
> Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-350) Implement Graffito based PageManager for PSML
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ 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
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
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-350) Implement Graffito based PageManager for PSML
Posted by "Randy Watler (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-350?page=comments#action_12359314 ]
Randy Watler commented on JS2-350:
----------------------------------
>From a conversation with DLS:
rwatler: i plan on doing import from Graffito next
rwatler: but i still have to think about that more
DLS: That will be very nice.
DLS: We could have a JSR 170 back portal page framework at one point!
DLS: With graffito in between.
DLS: Opens up all kind of opportunities...
DLS: ...once the new year comes, I want to focus more on the graffito integration as well.
DLS: Imaging being able to drive the page model from a CMS system. Wouldn't that be great?
rwatler: that is the goal
DLS: With a JSR 170 layer in between, you can drive the page structure from most of the CMS out there including commercial as they move towards 170 support.
rwatler: so it is J2 Page Manager <-> JSR 170 <-> CMS (Graffito)?
DLS: Yes, but it could also be J2 Page Manager <-> Graffito<-> JSR 170 <-> CMS
DLS: Basically, Jetspeed relies on Graffito which can expose JSR 170 therefore any CMS that complies with the standard.
> 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-FINAL, 2.0-M4
> Reporter: Randy Watler
> Assignee: Randy Watler
> Fix For: 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-350) Implement Graffito based PageManager for PSML
Posted by "Michael Lipp (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-350?page=all ]
Michael Lipp updated JS2-350:
-----------------------------
Fix Version: (was: 2.0-M4)
> 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-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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org