uPortal developers,
Do you suppose that DLM saveUserLayout()
http://goo.gl/kRxyqz
ought to be invalidating the layout cache so that the saved layout is
read back from the layout store on next access?
I suspect yes.
I think I'm seeing goofiness where user changes to received DLM
fragments (as in, deleting them from the personal layout) take immediate
effect and persist to the database, but *don't* reflect on logout and
log-back-in without Tomcat restart. I suspect this is because the
in-user-session cached copy is being properly updated and the changes
are being persisted to the database, but they're not being pushed into
that cache. I hope simply invalidating the cache on save is going to be
a reasonable solution (rather than heroically injecting just the right
new data into the cache without round-tripping from the layout store).
I hope to have a cogent explanation and a pull request today. But hey,
if you already know I'm going in the wrong direction on this, do a
fellow a solid and let me know? :)
Credit due to Tim Levett for the insight that the ghost in the machine
I'm seeing might be due to this particular cache.
Andrew
--
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
