Portlet changing a default definition preference results in the definition level being updated instead of entity level

Description

If a portlet has a default portlet preference set as a definition level preference and the portlet then modifies that preference via user-interaction the modified preference is not saved at the entity level like it should be. It is actually saved as an update to the definition level preference. This has the affect of all users sharing a single preference for that published instance of the portlet.

Environment

None

Activity

Show:
Eric Dalquist
September 2, 2009, 7:10 PM

Fixed in trunk and 3.0-patches, resolved by creating copies of preference objects before returning them to the portlet.

Fixed

Assignee

Eric Dalquist

Reporter

Eric Dalquist

Labels

None

Estimated End Date

None

Fix versions

Affects versions

Priority

Major