Caution: The documentation you are viewing is
for an older version of Zend Framework.
You can find the documentation of the current version at docs.zendframework.com
Advanced Usage of Zend_Json - Zend_Json
When encoding PHP objects as JSON, all public properties of that object will be encoded in a JSON object.
JSON does not allow object references, so care should be taken not to encode objects with recursive references. If you have issues with recursion, Zend_Json::encode() and Zend_Json_Encoder::encode() allow an optional second parameter to check for recursion; if an object is serialized twice, an exception will be thrown.
By default, Zend_Json will decode JSON objects as associative arrays. However, if you desire an object returned, you can specify this:
Any objects thus decoded are returned as
with properties corresponding to the key/value pairs in the JSON
The recommendation of Zend Framework is that the individual developer should decide how to decode JSON objects. If an object of a specified type should be created, it can be created in the developer code and populated with the values decoded using Zend_Json.
If you are encoding PHP objects by default the encoding mechanism can only access public properties of these objects. When a method toJson() is implemented on an object to encode, Zend_Json calls this method and expects the object to return a JSON representation of its internal state.
Zend_Json has two different modes depending if ext/json is enabled in your PHP installation or not. If ext/json is installed by default json_encode() and json_decode() functions are used for encoding and decoding JSON. If ext/json is not installed a Zend Framework implementation in PHP code is used for en-/decoding. This is considerably slower than using the PHP extension, but behaves exactly the same.
Still sometimes you might want to use the internal encoder/decoder even if you have ext/json installed. You can achieve this by calling:
object. It implements the value object pattern and is immutable. You can set the
to pass the option
'enableJsonExprFinder' = true into the
encode function. If enabled the expression support works for all nested
expressions in large object structures. A usage example would look like: