You do not need to worry about transactions when accessing portlet preferences. But if you update the preferences in processAction() method, make sure your call PortletPreferences.sator().
well, i'm using JSF portlets with the portlet bridge. i don't cnage the properties from the default jsr 168 methods. does that make any change?
so there is no requirement to configure in jboss-portlet.xml:
<transaction> <trans-attribute>Required</trans-attribute> </transaction>
The preferences are handled entirely by the portlet container - it handles any required transactions to save updated property values.
You need the trans-attribute only if your portlet does its own database work.
(also, earlier I meant PortletPreferences.store(), one of these days I will either learn how to type or how to spell...)
OK, so freferences is clear.
what about window properties?
do i need a transaction to read/write portlet window properties?