Hi Dustin,

could you send us a reproductible test case?

 >I'm trying to track down the method(s) that look for the annotated POST
 >methods in the Resource in case they're not coming back properly.
you can have a look at the ServerResource class and the 
org.restlet.engine.resource.AnnotationUtils class, especially the 
methods that rely on the "cache" attribute such as "getAnnotations".

 > Are there some set conditions for POST methods? (i.e. Cannot return 
anything, no arguments, etc.).
Well, nothing special.
The tunnel service filters methods according to a query parameter 
(called "method" by default). This may be the cause of your problems.

Best regards,
Thierry Boileau

> Hi Thierry,
>
> I'm using the 2.0M6 version, and this issue is still happening. I have 
> an Apache 2.2.x proxy in front of my Tomcat Container.
>
> I'm trying to track down the method(s) that look for the annotated POST 
> methods in the Resource in case they're not coming back properly. Are 
> there some set conditions for POST methods? (i.e. Cannot return 
> anything, no arguments, etc.).
>
> Thanks, very much!
> Dustin
>
>
>
> Thierry Boileau wrote:
>   
>> Hi Dustin,
>>
>> something is not clear for me. When you send a post request to your 
>> resource, is your "post" method called or not?
>> If not, there is a problem. Otherwise, as said Stephan, a redirection 
>> makes your browser makes automatically an additional GET request the new 
>> location.
>>
>> Best regards,
>> Thierry Boileau
>>
>>   
>>     
>>> Hi Dustin,
>>>
>>> 303 (see other) says, that the result is at the given location, and you 
>>> have to get it with GET. So the behaviour is right.
>>> Use 301 (Moved Permanently) or 307 (Temporary redirect).
>>> See http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection
>>>
>>> best regards
>>>    Stephan
>>>
>>> Dustin N. Jenkins schrieb:
>>>   
>>>     
>>>       
>>>> I'm using Java 6, Tomcat 6.0.20, RESTlet 2.0M5 on a Linux platform.
>>>>
>>>> After my business operations in my POST call, I simply call 
>>>> redirectSeeOther().  When I make POST calls to the Resource now, the log 
>>>> records it as a POST call, but my @Get method is being called instead.  
>>>> Does the redirectSeeOther() get cached somewhere or something?  Normally 
>>>> I'd see a POST followed by a GET in the log.  Is this a bug in the 
>>>> current 2.0 tree?  The snapshot is doing the same thing.
>>>>
>>>> I've used wget and browser clients just to test this.
>>>>
>>>> Thanks,
>>>> Dustin
>>>>
>>>>     
>>>>       
>>>>         
>>> ------------------------------------------------------
>>> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2420195
>>>
>>>
>>>     
>>>       
>> ------------------------------------------------------
>> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2420445
>>
>>     
>
> ------------------------------------------------------
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2430998
>
>

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2431067

Reply via email to