Okay, after relentless hair pulling, I figured out what's going on. AMF-PHP overwrites the default error handler. So, what's happening is wen Zend_Loader::isReadable() is called, the fopen() check failes (because obviously the file doesn't exist). However, AMFPHP overwrites the default PHP Error handlers. So, instead of being supressed by the @ like it's suppose to, AMFPHP catches the "Failed to open" error and throws an exception out.
Well, one more reason why @ is bad! Philip On Tue, Apr 22, 2008 at 1:32 PM, Philip G <[EMAIL PROTECTED]> wrote: > > Okay, this error I completely do not get. Here's the circumstances. When I > build a basic PHP script that runs like normal, everything works fine. > However, the moment I switch to AMF-PHP for flash remoting, > Zend_Validate_EmailAddress returns the following error: > ----------------- > fopen(Zend/Validate/Hostname/Com.php) [function.fopen]: failed to open > stream: No such file or directory > --------------- > > Looking within that directory, it's pretty obvious there isn't a prefix > file for every possible domain prefix. So, what's causing this and why is it > even being triggered? > > It only happens within AMF-PHP flash remoting. I'm trying to determin why > it does /not/ trigger when I call the class directly using a test script so > that I can figure out why it /is/ triggering during flash remoting. > > This is really boggling me. It's the exact same code, absolutely no > difference. Same include path, same class, same method being called, same > parameters passed in, etc. It's really throwing me for a loop. > > Any suggestions? ideas? > > -- > Philip > [EMAIL PROTECTED] > http://www.gpcentre.net/ -- Philip [EMAIL PROTECTED] http://www.gpcentre.net/
