I have a working solution.
In order for others to make use of it, I stripped it down to a basic
portlet (removing the Spring Portlet MVC layer)
Hate to put source in emails, the formatting goes to hell
So I attached an example to the JIRA issue I created for this one
https://issues.apache.org/jira/browse/JS2-672
Note that a new API was added to the PreferencesProvider interface:
/**
* Create a property on the given node.
* @param node the node to have a property added to it
* @param name the name of the property to add to the node
* @param value the value of the property to add to the node
* @return the newly created property
* @since 2.1.1
*/
Property createProperty(Node node, String name, Object value);
The reason I did this is that I didn't like that you were forced to
access the PropertyImpl class
which is not a part of the Jetspeed API. Additionally, by doing this,
you may have caused
the storage error since the object may have come from a different
class loader
You will need the backing implementation, the prefs component as well
as the jetspeed-api jar
I uploaded the latest jars here:
http://www.bluesunrise.com/maven/org.apache.portals.jetspeed-2/jars/
jetspeed-api-2.2-dev.jar
http://www.bluesunrise.com/maven/org.apache.portals.jetspeed-2/jars/
jetspeed-prefs-2.2-dev.jar
so your pom.xml will need to specifically reference these when you
build your portlet app
which will require deleting them from your local repo and dl'ing over
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
