Hi,

Seaside-REST is included in Seaside since version 3.1
ConfigurationOfSeasideREST is outdated; it works with version 3.0

Therefore, load the ���REST��� group from ConfigurationOfSeaside3:

Metacello new
configuration: 'Seaside3';
version: #stable;
load: ���REST'

If you want to experiment with all of Seaside, load everything:

Metacello new
configuration: 'Seaside3';
version: #stable;
load: ���OneClick'

Seaside is also not tested on Pharo5 as it���s still a moving target. 
Use Pharo4 if you want to make sure it works.

regards
Johan

On 25 Nov 2015, at 01:07, Franck Warlouzet <franck.warlouzet@hotmail.fr> wrote:

I was using both ConfigurationOfSeaside3 and ConfigurationOfSeasideRest. Is it the wrong way ?

Franck

> To: pharo-dev@lists.pharo.org
> From: stephan@stack.nl
> Date: Wed, 25 Nov 2015 00:26:05 +0100
> Subject: Re: [Pharo-dev] Seaside REST on Pharo 50
> 
> On 24/11/15 16:43, Franck Warlouzet wrote:
> > We are working on Pharo 50, and we noticed that Seaside-REST is not
> > working anymore.
> 
> How are you loading it?
> 
> (ConfigurationOfSeaside3 project version: #'release3.2') load: 
> #('OneClick' 'REST')
> 
> There could be a configuration problem, or not the right combination of 
> groups.
> 
> To resolve it, compare the package cache from Pharo4 vs Pharo5 after 
> loading.
> 
> Stephan
> 
>