[Seaside] Re: [Seaside-dev] GRPharoUtf8CodecStream does not understand object:

[Johan Brichau]

Hi Sabine,

I'm passing this message to the seaside mailinglist, as I believe it's a question of general interest.

This is not a difference between Pharo 2 and 3, but between Seaside3.0 and Seaside3.1
Philippe has done a great job describing the differences here: https://code.google.com/p/seaside/wiki/Seaside310Changelog
The way json is rendered is mentioned there.

#jsonOn:  now takes a rendered as an argument.
I think you should rather use the #asJson method to convert an object to Json.

Without taking a look at JQGrid, I would guess this is a problem in JQGrid.

regards
Johan

On 24 Jan 2014, at 12:02, Sabine Knöfel <sabine.knoefel at gmail.com> wrote:

> Hi,
> 
> I think there is a bug in Seaside.
> I run into this when using JQGrid.
> 
> Code in Pharo3:
> 
> Dictionary>>jsonOn: aRenderer
> 	aRenderer object: [
> 		self keysAndValuesDo: [ :key :value |
> 			aRenderer key: key value: value ] ]
> 	
> aRenderer is iOf GRPharoUtf8CodecStream
> GRPharoUtf8CodecStream does not understand object:
> 
> You can reproduce it also when running JQGrid example.
> Have a look in the Network response in the internet browser where you will
> see a 500 internal server error with "MessageNotUnderstood:
> GRPharoUtf8CodecStream>>object:
> Your request could not be completed. An exception occurred."
> 
> or implement 
> 
> GRPharoUtf8CodecStream>>object: anObject
> self halt.
> 
> In Pharo2, it was implemented like this:
> Dictionary>>jsonOn: aStream
> 	JSJsonStream encodeDictionary: self on: aStream
> 
> 
> 
> Sabine
> 
> 
> 
> --
> View this message in context: http://forum.world.st/GRPharoUtf8CodecStream-does-not-understand-object-tp4738990.html
> Sent from the Seaside Development mailing list archive at Nabble.com.
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev