Something strange has just happened. I did a new pull, redeployed the portal v4.0.9 and the portlet is working as expected! Not sure why, might have been me all along :) Thanks anyways!
P.S: Did confirm though that there are adequate tests that exercise mocked portlet preferences. -Misagh > -----Original Message----- > From: bounce-26522675-57692...@lists.wisc.edu [mailto:bounce-26522675- > 57692...@lists.wisc.edu] On Behalf Of Eric Dalquist > Sent: Tuesday, January 01, 2013 1:38 PM > To: uportal-dev@lists.ja-sig.org > Subject: Re: [uportal-dev] 4.0.9 Release Plans > > Interesting. Can you describe the actual request/prefs interaction flow > in more detail? A cursory test using the Jasig Test Portlet seems to > show the correct behavior. Perhaps you could add a test case to that > portlet to try and reproduce the problem then we'll have a continuing > way to verify the functionality. > > -Eric > > > On 12/31/12 11:58 AM, Misagh Moayyed wrote: > > Eric, > > I haven't actually been able to track this issue down at the portal > level > > to open a JIRA, but I have stumbled upon a rather strange an issue > with > > portlet preferences. Cross posted to @portlet-dev, the problem I have > run > > into is that portlet preferences do not seem to return the stored > values > > on subsequent calls on the portlet request object. Specifically, the > email > > preview portlet is one that I have been able to duplicate this issue > > running against the latest master. When the portlet saves the > > configuration, I see that all proper calls are made and values stored > and > > yet, on subsequent calls when the portlet actually goes to retrieve > the > > values, they are returned as null. I think the problem is at the > portal > > level somewhere as the portlet doesn't really do anything weird > enough to > > make me suspect something, but nevertheless, I haven't been able to > step > > through the code just yet. > > > > To provide a little bit of context, the one preference value I have > been > > having trouble is the authenticationServiceKey, which gets properly > set to > > portletPreferences and yet comes back as null when the portlet goes > to > > retrieve the account configuration set. Drew had suggested that this > may > > be to a previous bug recently fixed that mixed up the handling of > readonly > > preference values, but I have pull that change and am running the > latest > > portal master. Something else must be interfering with the > preferences > > object. > > > > I think I'll try and see if I can duplicate the issue with a simple > > HelloWorld portlet first before stepping through the portal. My plan > is to > > save a couple of values into the preferences in the EDIT mode and > retrieve > > them in the VIEW mode. I'll post back shortly, but in the meanwhile, > if > > the dev team do get a chance to review this, it'd great help. > > > > Regards, > > > > -Misagh > > > > > >> -----Original Message----- > >> From: bounce-26511269-57692...@lists.wisc.edu [mailto:bounce- > 26511269- > >> 57692...@lists.wisc.edu] On Behalf Of Eric Dalquist > >> Sent: Sunday, December 30, 2012 3:54 PM > >> To: uportal-dev@lists.ja-sig.org > >> Subject: [uportal-dev] 4.0.9 Release Plans > >> > >> I'm planning on cutting 4.0.9 on the 3rd. Get your changes in or let > me > >> know if there is a sore issue you'd like looked at before then! > >> > >> -Eric > > > -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
