Note that you normally should throw the read-only Exc when calling the
set methods and not and the end in the store in order to be compliant
with the JSR 168 spec. It is in the spirit of the spec that you can get
this exc if the current user does not have sufficient rights to do this
(i.e. that the preference is read-only for this request).
Stefan
Elliot Metsger wrote:
Chuck,
If the user doesn't have permission to store(), you could treat the
preference as read-only and throw a ReadOnlyException (PLT.14.1)
Of course, ReadOnly is different semantics than permission denied.
Elliot
Charles Severance wrote:
David,
I just completed building a preferences store for Sakai. I only came
up with a little, tiny thing.. It might be more of a design thing
but...
In the JSR-168 PortletPreferences - there is this method:
public void store()
throws java.io.IOException,
ValidatorException
And in the
./pluto-container/src/main/java/org/apache/pluto/spi/optional/PortletPreferencesService.java
There is this method:
public void store(PortletWindow portletWindow,
PortletRequest request,
InternalPortletPreference[] preferences)
throws PortletContainerException;
But what do I do if in the code in the implementation of
PortletPreferencesService I decide that for this user I do not want
to store these preferences. For example, if the current user does
not have enough privileges for this particular portlet window. not
knowing how to tell the container to throw said IOException, I just
punt and do not do the store and return sheepishly with no thrown
error :)
In the grand scheme of things - this is not like rocket science of
life/death - but thought I would bring it up.
If you want to cut 1.1.1 or at least put up a release candidate - it
is pretty quick for me to pound on it in a few hours and give some
feedback. I can even grab a tag and compile it myself.
/Chuck
On Mar 3, 2007, at 8:11 PM, David H. DeWolf wrote:
I plan to cut a 1.1.1 release sometime in the next few days. We are
down to one issue - related to documentation - and the website can
be updated any time, so I don't consider it a blocker. I'd like to
get 1.1.1 out because it has two bug fixes which will allow
execution in WebLogic 8.1 (thread local bug, and el param tag bug).
There are also several other bug fixes and a couple of enhancements.
Please chime in if there's anything else you want to squeeze in.
David
