You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by "Dr. Michael Lipp" <Mi...@danet.de> on 2006/06/28 15:24:32 UTC
How to preserve pages
Hi,
is there a "best practice" how to preserve the pages between
deployments? If I re-deploy Jetspeed because of e.g. some update,
everything falls back to the page directory in the WAR.
Regards,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: How to preserve pages
Posted by Maurizio Pedraglio <pe...@ngi.it>.
Hi,
I don't know if this is a best practice but it works in my case (I store
pages & folder out of tomcat directory)
Under {tomcat_home}\webapps\jetspeed\WEB-INF\assembly you can find a
file named page-manager.xml. You shuld edit pages location there, having
them not modified during deployment task.
Hope this helps you.
Hi,
Maurizio
Dr. Michael Lipp wrote:
> Hi,
>
> is there a "best practice" how to preserve the pages between
> deployments? If I re-deploy Jetspeed because of e.g. some update,
> everything falls back to the page directory in the WAR.
>
> Regards,
>
> Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: How to preserve pages
Posted by David Sean Taylor <da...@bluesunrise.com>.
Dr. Michael Lipp wrote:
> Hi,
>
> is there a "best practice" how to preserve the pages between
> deployments? If I re-deploy Jetspeed because of e.g. some update,
> everything falls back to the page directory in the WAR.
>
Recommend using the Maven-1 plugin (j2:genapp) and just overwrite the
Spring configuration for the page manager, overriding the location of
the pages to some place secure on your file system, outside of the web
application. I usually just create a directory structure like:
myPortalProject
applications
myPortletApp
...
src
webapp
WEB-INF
assembly
<<put custom Spring config here >>
Our Maven-2 build supports custom portals as well, and IMO, is a
preferred solution for new projects
For larger installations, I recommend using the Database Page Manager
We support both import and export from/to the db page manager
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org