What's the 'migration' for an existing uportal installation to a new
installation?
---- Cris J H
Jen Bourey wrote:
Hi all,
As part of the Portlet Administration Portlet work (UP-2047), Unicon has
been working on a re-implementation of IChannelRegistryStore and the
ChannelRegistryManager. I've been working on replacing the existing
channel and channel type persistence with a more modern JPA/Hibernate
approach, as well as splitting the existing ChannelDefinition and
ChannelType classes into interface/implementation pairs. This work
should allow us to remove some of the legacy database code from uPortal
and move four tables (UP_CHANNEL, UP_CHAN_TYPE, UP_CHANNEL_PARAM, and
UP_CHANNEL_MDATA) from tables.xml to hibernate. I'm hoping that this
work will better position us to make changes to the associated domain
objects and service layer code in preparation for some proposed portlet
approval lifecycle work (email to follow).
To start, I've tried to preserve the existing data tables as much as
possible, and they should continue to have the same table and column
names. However, I've moved the sequences away from the custom uportal
sequence and changed the classname of the channel definition entity. As
a result, committing this patch will require anyone working in the trunk
to re-initialize his or her database. I'd like to commit this work
sometime tomorrow. Does anyone have objections to this work appearing
in trunk tomorrow or have concerns about needing to run an initdb?
- Jen
--
Jen Bourey
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
