OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsrp] Action redirects to self


My understanding is that redirect URLs must be absolute URLs and thus 
cannot be action or render URLs.

Having not absolute URLs would lead into the discussion of portlet 
addressability in my view, which was moved to V 3.0.


Stefan


Mike Caffyn wrote:
> Subbu,
> 
> That is my understanding of the redirect URL as well.
> 
> Mike, I'm not exactly sure what you are trying to accomplish with this. 
> For example a performBlockingInteraction returns different types of 
> rewritten wsrp urls.
> 
> wsrp render url:
> This would be very similar to the normal action of most portals after a 
> performBlockingInteraction.
> 
> wsrp action url:
> This would cause another performBlockingInteraction on the particular 
> portlet. This would have to be carefully used since it could result in a 
> loop. But in theory it could be used to do performBlockingInteraction, 
> performBlockingInteraction and then a render.
> 
> wsrp resource url:
> This would just use the portal as a proxy to obtain the resource. But 
> the user probably has left the portal now.
> 
> Mike is this correct assumption in how the redirect would work with wsrp 
> rewritten urls?
> 
> Mike
> ----- Original Message ----- From: "Subbu Allamaraju" <subbu@bea.com>
> To: "Michael Freedman" <michael.freedman@oracle.com>
> Cc: "wsrp" <wsrp@lists.oasis-open.org>
> Sent: Tuesday, December 06, 2005 6:27 PM
> Subject: Re: [wsrp] Action redirects to self
> 
> 
>> Your question made me think about another issue. I don't think there 
>> is a requirement for consumers to rewrite redirect URLs before 
>> redirecting.
>>
>> Subbu
>>
>> Michael Freedman wrote:
>>
>>> I believe we talked about this but don't recall the outcome.  Is it
>>> valid for a performBlocking Interaction to return a properly encoded
>>> action url [i.e. either a templated url or a consumer rewrite token 
>>> string] as the redirect url if/when the portlet's action wants the
>>> action result to be a redirect back to itself via the current page?  If
>>> its valid (in 2.0), was it in 1.0?  Did anyone implement/support this?
>>>     -Mike-
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this mail list, you must leave the OASIS TC that
>>> generates this mail.  You may a link to this group and all your TCs 
>>> in OASIS
>>> at:
>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  You may a link to this group and all your TCs in 
>> OASIS
>> at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]