Hello Tal,
thanks for your report. There was a bug in the Protocol class which
causes the generation of bad responses with the RIAP protocol.
This should work better now. Let us know if it still fails.
Best regards,
Thierry Boileau
> OK, I managed to build it, and some things work but some don't.
>
> My example does work. However, I cannot redirect to riap://application/
> URIs. My understanding is that these are not supported by the server
> dispatcher (I'm not sure why -- could it be something to do with
> handling asynchronous requests?). Thing is, I cannot redirect to RIAP at
> all with the client dispatcher, which as far as I know does support all
> RIAP authorities. For example, the following will hang Restlet:
>
> router.attach("/note/{id}"), new Redirector(component.context,
> "riap://application/note", Redirector.MODE_CLIENT_DISPATCHER));
>
>
>
> On 02/22/2010 09:07 AM, Thierry Boileau wrote:
>
>> Hello Tal,
>>
>> thanks for your report. The fix is available in the svn repository.
>>
>> Best regards,
>> Thierry Boileau
>>
>>
>>
>>> It seems like I cannot use a Redirector to an RIAP URI.
>>>
>>> For example:
>>>
>>> router.attach("/note/{id}"), new Redirector(component.context,
>>> "riap://component/myapp/note", Redirector.MODE_SERVER_DISPATCHER));
>>>
>>> Is this intentional? Can anyone think of a simple workaround?
>>>
>>> The use case is to have a different internal URI space, and a different
>>> one exposed to the world.
>>>
>>> By the way, setting the Redirector in MODE_CLIENT_DISPATCHER in this
>>> case causes a JVM failure...
>>>
>>> -Tal
>>>
>>> ------------------------------------------------------
>>> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2449457
>>>
>>>
>>>
> ------------------------------------------------------
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2450618
>
>
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2453459
