Issue Type: Bug Created: 2010-01-19T06:52:21.000+0000 Last Updated: 2012-11-06T19:37:08.000+0000 Status: Open Fix version(s): Reporter: Matthias Steinböck (rocksocke) Assignee: Wade Arnold (wadearnold) Tags: - Zend_Amf
Related issues: Attachments:
Sending an array with typed objects, which contain typed objects themselves causes an "Unknows Definition reference" in Zend_Amf_Parse_Amf3_Deserializer (line 304).
Tracing that error back to Zend_Amf_Parse_Amf0_Deserializer i found that the deserializer is created newly everytime readAmf3TypeMarker is called (line 297).
Changing this behaviour back (caching the amf3-parser and using a getter for it) this issue is resolved.
The working Zend_Amf_Parse_Amf0_Deserializer i took was from june 2009 - zendfw 1.8
Posted by Stefan Klug (stefanklug) on 2010-01-21T07:09:43.000+0000
The solution provided above is no valid fix, as the caching of the Amf3 Parser was removed on purpose. See the fix for ZF-6393. If someone (Matthias?) could provide a failing testcase, I can work on a solution.
Posted by Stefan Klug (stefanklug) on 2010-01-21T07:24:32.000+0000
It might be, that this issue boils down to the problem (and fix) mentioned in ZF-8015.
Posted by Matthias Steinböck (rocksocke) on 2010-01-22T12:22:39.000+0000
thanks for your response! i didn't want to post a invalid fix sorry... i didn't find a fix in ZF-8015 though it seems that its the same problem, but i can't say it for sure.
in fact i'm no expert on the amf-protocol. i can post my logs in the next days. i'd really appreciate if you'd find time to check this...
Posted by Adam Lundrigan (adamlundrigan) on 2011-11-08T18:28:41.000+0000
Is this still an issue?
Have you found an issue?
See the Overview section for more details.