Part of the post 2.6 plan I think will include this change. Switching to a more sane DAO for the layout store perhaps even using hibernate to leverage the great CLOB (and in some cases XML object) support databases have now would likely improve performance as well as clarity.
-Eric Mark Boyd wrote: > Having a chunk of XML would be nice and would certainly remove a chunk > of confusing code from the layout stores. And with all of the > standards that have matured since the beginings of uPortal there > really is a lot that we could leverage in such an initiative. > > Mark > > On 8/6/07, *Susan Bramhall* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Another approach would be to change the layout manager (or ??) to > remove > the channel from the layout as it builds it instead of > substituting the > "channel not found error". We talked about doing this but decided > against it. > Susan > > Andrew Petro wrote: > > Philip, > > > > It might be best to write some Java code to actuate the layout > > management API to load each user's layout, change it as you desire, > > and save it again. This would make a very nice addition to the > > channel manager -- perhaps a button to "Remove this channel from all > > user layouts". > > > > Andrew > > > > PS: I'm becoming increasingly convinced that the approach in the > > sandbox uPortal code of storing layout fragments as really wide > > database columns containing the layout XML instead of representing > > each node as a database row is a very good idea -- it's > probably just > > as performant if not more performant for real uses, and it's a whole > > lot simpler to understand and code against. I suspect that if > layout > > storage were implemented this way, you'd be done with this > > remove-a-channel-from-everyone's-layout task already. > > > >> I'm looking for a way to purge a channel from both the channel > >> registry and all layouts it is contained in. > >> > >> Deleting a channel in ChannelManager gives 'Channel not found' > errors > >> in any layouts that already had the channel. Deleting the record > >> directly from the LAYOUT_STRUCT table seems to completely ruin > that > >> users layout. (I've done deluser on myself a few times now.) > >> > >> Are there multiple tables that would need to be changed in order to > >> not destroy the layout? > >> > >> Thanks > >> Phil > >> > >> > >> ps. Sorry, if there is some simple solution to this, and I'm > >> completely over thinking the problem! > >> > >> > > > > > > -- > It's no use trying to be clever--we are all clever here; just try > to be kind--a little kind. > -- F.J. Foakes Jackson > > > -- > You are currently subscribed to [email protected] > <mailto:[email protected]> as: > [EMAIL PROTECTED] <mailto:[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
smime.p7s
Description: S/MIME Cryptographic Signature
