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

[Sabine Knöfel]

Hi Phillippe,

how do I get a stack trace?
"Fuel out Stack" in the Debugger?

jsonOn: is sent in this context:

JQGrid>>processSearchCallback
 |searchRequest searchResponse|
searchRequest := JQGridSearchRequest parseFromWARequest: self
requestContext request using: jqGridColumns.
 searchResponse := searchCallback value: searchRequest value:
jqGridColumns.
searchResponse jqGridColumns: jqGridColumns.
 self requestContext respond: [:response|
response
doNotCache;
 contentType: (WAMimeType applicationJson
charset: self requestContext handler charSet).
searchResponse jsonOn: response stream].
 regards
Sabine



On Sat, Jan 25, 2014 at 4:34 PM, Philippe Marschall [via Smalltalk] <
ml-node+s1294792n4739300h95 at n4.nabble.com> wrote:

> On Fri, Jan 24, 2014 at 12:02 PM, Sabine Knöfel
> <[hidden email] <http://user/SendEmail.jtp?type=node&node=4739300&i=0>>
> 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:
>
> The argument to #jsonOn: should be a WAJsonCanvas and not a
> GRPharoUtf8CodecStream in Seaside 3.1. Do you have a stack trace?
>
> > 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
>
> That was Seaside 3.0. JSON support in Seaside 3.1 is "new". It's no
> longer based on JavaScript (JSON isn't actually a JavaScript subset).
> It now has a canvas much like the HTML and XML support. This allowed
> us to fix many corner case bugs.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=4739300&i=1>
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://forum.world.st/GRPharoUtf8CodecStream-does-not-understand-object-tp4738990p4739300.html
>  To start a new topic under Seaside Development, email
> ml-node+s1294792n1294793h78 at n4.nabble.com
> To unsubscribe from GRPharoUtf8CodecStream does not understand object:, click
> here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4738990&code=c2FiaW5lLmtub2VmZWxAZ21haWwuY29tfDQ3Mzg5OTB8MTA0OTM5MTYx>
> .
> NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://forum.world.st/GRPharoUtf8CodecStream-does-not-understand-object-tp4738990p4739476.html
Sent from the Seaside Development mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20140126/58b6d0ab/attachment.htm