Hi, We are currently using seaside, magritte, reef etc to do a project at school. We also have to do a mobile app (written in Java :(), so we are doing a REST service to access the database from the mobile app. We are working on Pharo 50, and we noticed that Seaside-REST is not working anymore. For simple get, it is ok, for example : test <get> ^ 'foo' but if you want to have a complete path like that : test: aValue <get> <path: '/foo?value={aValue}'> ^ 'foo' You get a DNU RBVariableNode>>key during the route creating (Same on pharo 40 is working). Any idea why ? In the meantime, we are using Teapot, it seems to be working on Pharo 50. Btw, I cannot subscribe to seaside mailing list (I never get the confirmation mail), so if someone could forward this email on seaside mailing list, it would be nice. Franck
On 24 Nov 2015, at 12:43, Franck Warlouzet <franck.warlouzet@hotmail.fr> wrote:
Hi,
We are currently using seaside, magritte, reef etc to do a project at school. We also have to do a mobile app (written in Java :(), so we are doing a REST service to access the database from the mobile app.
We are working on Pharo 50, and we noticed that Seaside-REST is not working anymore. For simple get, it is ok, for example :
test <get> ^ 'foo'
but if you want to have a complete path like that :
test: aValue <get> <path: '/foo?value={aValue}'> ^ 'foo'
You get a DNU RBVariableNode>>key during the route creating (Same on pharo 40 is working).
Any idea why ?
Can you provide an image where this happens? (just knowing what to load would take some effort elseâ¦) Marcus
I don't have such an image anymore :( I guess Seaside and Seaside-Rest are enough (latest for both of them). Franck From: marcus.denker@inria.fr Date: Tue, 24 Nov 2015 13:45:14 -0300 To: pharo-dev@lists.pharo.org Subject: Re: [Pharo-dev] Seaside REST on Pharo 50 On 24 Nov 2015, at 12:43, Franck Warlouzet <franck.warlouzet@hotmail.fr> wrote:Hi, We are currently using seaside, magritte, reef etc to do a project at school. We also have to do a mobile app (written in Java :(), so we are doing a REST service to access the database from the mobile app. We are working on Pharo 50, and we noticed that Seaside-REST is not working anymore. For simple get, it is ok, for example : test <get> ^ 'foo' but if you want to have a complete path like that : test: aValue <get> <path: '/foo?value={aValue}'> ^ 'foo' You get a DNU RBVariableNode>>key during the route creating (Same on pharo 40 is working). Any idea why ? Can you provide an image where this happens? (just knowing what to load would take some effort elseâ¦) Marcus
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
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
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 <mailto:pharo-dev@lists.pharo.org> From: stephan@stack.nl <mailto: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
Ok I will do that, thanks. Franck From: johan@inceptive.be Date: Wed, 25 Nov 2015 07:46:09 +0100 To: pharo-dev@lists.pharo.org Subject: Re: [Pharo-dev] Seaside REST on Pharo 50 CC: seaside@lists.squeakfoundation.org Hi, Seaside-REST is included in Seaside since version 3.1ConfigurationOfSeasideREST 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. regardsJohan 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
participants (4)
-
Franck Warlouzet -
Johan Brichau -
Marcus Denker -
Stephan Eggermont