Issue Type: Task Created: 2008-01-03T02:30:17.000+0000 Last Updated: 2008-02-26T14:47:43.000+0000 Status: Resolved Fix version(s): - 1.0.4 (26/Feb/08)
Reporter: Trevor Johns (tjohns) Assignee: Trevor Johns (tjohns) Tags: - Zend_Gdata
Related issues: Attachments:
There are a handful of Zend_Gdata classes which do not lazy-load exceptions before throwing them. These should be corrected and stricken from the list of offending classes at:
Posted by Trevor Johns (tjohns) on 2008-01-03T02:33:25.000+0000
Currently waiting on clarification of policy for Exception subclasses, since these also show up on the list of classes to be fixed.
Posted by Trevor Johns (tjohns) on 2008-01-03T03:10:16.000+0000
Okay, as I expected, Exception subclasses are exempt. That leaves about 5 classes that need to be fixed.
Posted by Trevor Johns (tjohns) on 2008-01-14T09:40:02.000+0000
Patch committed to trunk as r7429.
Posted by Ryan Boyd (rboyd) on 2008-01-22T16:02:58.000+0000
Committed some changes in r7575 to lazy load exception clasess that were throwing exceptions as they weren't loaded prior to instantiation :)
Posted by Trevor Johns (tjohns) on 2008-01-23T06:32:01.000+0000
Ryan, I think those were the exceptions that needed to be updated to resolve ZF-1752. I've had a patch sitting around to do that for a while (it's a simple change), but I've been hesitant to commit it without updating the unit tests.
Posted by Ryan Boyd (rboyd) on 2008-01-23T10:35:12.000+0000
Yep-- sorry, didn't see that bug. This was causing exceptions when running the sample app. While unit tests would be nice, my priority in this case was making the sample app work :) I resolved the issue, but left it assigned to you so you can attach unit tests if/when you get a chance. If you'd prefer to re-open it in the meantime, that'd be fine too.
We should have a status of 'resolved in trunk, but still needs unit test'
Have you found an issue?
See the Overview section for more details.