I doubt it would break anything, but unless you're willing to change your
code to work with the new changes, I'd suggest making a plugin instead of
modifying the source, that way you get the complete updated version, but
you still get your specialized parsing.
Marcus
On Friday, May 26, 2017 at 4:56:59 PM UTC-4, chris schiffman wrote:
>
> Hi All,
>
> So i've been happily chugging along with openbd 2.x for about 5 years now,
> and i'm testing out 3.1 with my existing application. Most everything
> seems to be compatible, however, it seems serializejson() was changed that
> has had a pretty big affect on my clients who parse the json responses my
> service provides. The 3.1 version of serializeJson seems to parse empty
> strings and numbers with the word 'null' instead of simply displaying an
> empty container. I think this is the code:
>
> Old:
> if ( var == null || var.getDataType() == cfData.CFSTRINGDATA || var.
> getDataType() == cfData.CFNULLDATA) {
>
>
> /*
> * Encode Strings
> */
> out.append("\"" + encodeString(var.getString()) + "\"");
>
>
> } else if (var.getDataType() == cfData.CFBOOLEANDATA) {
>
> New:
> if ( var == null || var.getDataType() == cfData.CFNULLDATA) {
> out.append( "null" );
>
>
> }else if ( var.getDataType() == cfData.CFSTRINGDATA ){
>
>
> /*
> * Encode Strings
> */
> out.append("\"" + encodeString(var.getString()) + "\"");
>
>
> } else if (var.getDataType() == cfData.CFBOOLEANDATA) {
>
>
> I'm sure we could make the change ourselves and recompile, but i want to
> make sure we won't break anything else. Any thoughts/ideas/workarounds?
>
> Thanks!
>
>
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
---
You received this message because you are subscribed to the Google Groups "Open
BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
