[Seaside-dev] Re: Rest in Seaside3.1

[Johan Brichau]

ah... if I change the method to:

all
	<get>
	<path: ''>

Then it gets matched...
We should update the documentation... what was the rationally for changing that ;-)

Let me see if I can solve my original matching troubles.

cheers
Johan


On 15 Apr 2014, at 16:01, Johan Brichau <johan at inceptive.be> wrote:

> Hi Philippe,
> 
> I'm having issues with the REST implementation in Seaside 3.1
> Routes are not getting matched.
> 
> I eventually narrowed the issue down by creating a WARestfulFilter with a simple method:
> 
> all
> 	<get>
> 
> 	^''
> 
> This should catch all incoming GET calls, right?
> 
> The problem is that the method WARouteBuilder>>initializeOn: is setting the path instvar to the selector of the method. 
> However, the WARouteBuilder>>create method dispatches on the value of path to create a WASimpleRoute when it's nil.
> This does not happen.
> 
> If I change the WARouteBuilder>>initializeOn: method to set the path to nil (like its done in Seaside 3.0), I'm getting it to work.
> 
> However, it seems the change was intentionally introduced in the following commit:
> 
> Name: Seaside-REST-Core-pmm.48
> Author: pmm
> Time: 24 August 2012, 4:22:37 pm
> UUID: 7c575e6c-04b6-4a29-b0d8-f59f8cae63af
> Ancestors: Seaside-REST-Core-pmm.47
> 
> - <path: > defaults to method name
> 
> 
> However, I don't grasp why it was done as it was the sole change in the package?
> 
> I hope you can remember something ;-)
> 
> cheers
> Johan