On Sat, Aug 14, 2010 at 8:11 AM, kentyler <[email protected]>wrote:
> I think it was having "resolveurl" set to "true"... that caused the > "http://127.0.0.1"; to be interpolated into the text... which then > broke the desearlize json... because its quotes where not escaped > > when i set "resolveurl" to false the deserializejson seems to work > fine > Interesting--do you need to use resolveurl in this case or is that optional for you? I'm not sure what the expected behavior would really be here, but it does seem that resolveurl shouldn't throw off the JSON serialization. Can you do me a favor and file a ticket for this here? http://code.google.com/p/openbluedragon/issues/entry That way it's on our radar to take a look. Thanks. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
