Ok no worries.
The action=restart param has been dropped and it just makes a request directly
to the portlet which restarts it. The code looks like:
<a href="render.userLayoutRootNode.target.{@ID}.uP"
title="{$TOKEN[@name='PORTLET_RESTART_LONG_LABEL']}" class="up-portlet-control
restart">
This doesn't rely on the portlet timing out and rendering the error portlet,
it's if the remote server's session times out and requests authentication
again, it can get into a weird state which rebooting fixes since Basic LTI
doesn't required credentials. There is a screenshot in the Jira (login boxes).
cheers,
Steve
On 30/08/2011, at 11:52 AM, Eric Dalquist wrote:
> For 4.0 GA its probably too late since I don't have the time to wrangle the
> UI resources into getting me an icon that matches up with the 4.0 theme. My
> other question is that I'll need to go through and look in 3.2 and see just
> what the "action=restart" parameter even does functionally to a portlet.
>
> Note that in 4.0 the error portlet is NOT stateful. You see it once and then
> simply hitting refresh in the browser resubmits the previous request to the
> portlet.
>
> -Eric
>
> On 8/29/11 6:02 PM, Steve Swinsburg wrote:
>> Hi Eric,
>>
>> I'm not sure how much work this is, but would you consider porting
>> https://issues.jasig.org/browse/UP-2934 to uP4?
>>
>> It's off by default but would be very useful for those wanting to use Basic
>> LTI portlets in uPortal as it allows a manual restart of the portlet in case
>> the other end times out.
>>
>> cheers,
>> Steve
>>
>>
>> On 30/08/2011, at 1:41 AM, Eric Dalquist wrote:
>>
>>> If you have any changes or fixes that need to go in please either post here
>>> or jump in IRC and check first. We're a day or two away from the 4.0 GA
>>> release.
>>>
>>> -Eric
>>>
>>
>
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
