Sorry for the late response, I unsubscribed from my previous email/job, and looks like I missed a few days (or more) of jetspeed-user questions...
I think the problem is that when you clone a portlet - it doesn't get written to the portlet.xml deployment descriptor. So when you redeploy, you will wipe out any portlets in an application which are not defined in the portlet.xml. I know, not a desirable effect, but that's how it works. I am thinking maybe we should create a JIRA issue / bug report on this, its really more of a bug than a new feature Its kind of a pain to have to create new portlet entries in your XML file. It would be nice if you could export out a PA from the database to a descriptor. We have been wanting that feature for a long time. On Fri, Sep 10, 2010 at 6:39 AM, <[email protected]> wrote: > I have need to occassionally move a jetspeed instance from one server to > another. tarring up the directory structure seems simple enough and seems > to work fine. I also have used the jetspeed 2.2.1 installer functions to > export and import data from/to mysql, as well as, mysqldump and simply > moving the database directory structure. All of this seems to work fine > at first, but for one exception. My jetspeed has many cloned portlets and > although everything else moves and works great on the new server, the > cloned portlets never seem to make it. They are in the import/export or > the mysqldump or the directory structure, but they disappear after the > first invocation of the jetspeed server after moving. How can I move an > instance of jetspeed and ensure the complete configuration comes across? > Actually, they do come across, I can see them in portlet_definitions > table, but after I fire up jetspeed, they disappear. > This communication and any attachments are confidential, protected by > Communications Privacy Act 18 USCS § 2510, solely for the use of the > intended recipient, and may contain legally privileged material. If you > are not the intended recipient, please return or destroy it immediately. > Thank you. -- David --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
