Re: Strange error - Solved

Ok, just incase anyone else runs into something funky like this here is what was wrong. My API call was named GetMessages. I had then built a new internal method named getMessage and apparently when PEAR::SOAP tried to access GetMessages it was instead accessing getMessages. I don't know if this is a PEAR::SOAP issue or if it's a PHP issue but that is what the problem was. Renaming getMessages to something else fixed the problem. Rob "Rob Booth" <rbooth@indyme.com> wrote in message news:20030709180405.3221.qmail@pb1.pair.com... > I have a server that had a method that was working but now isn't. I didn't > make any changes to this method and it is almost exactly like another method > (one returns 1 object, the bad one returns a list of those objects). For > some reason I get back a text/html response instead of the text/xml data > that I'm expecting. I've gone so far as to remove all of the code any only > return an int in this method but I still get the text/html response. I've > even removed the method entirely hoping to get a method doesn't exist error > but I still get the text/html response. I've set trace and looked at the > wire (see below) but it doesn't tell me anthing. Has anyone ran into > anything like this or have any suggestions of what else I can try to solve > the error? > > Thanks, > Rob > > INCOMING > > HTTP/1.1 200 OK > Date: Wed, 09 Jul 2003 18:00:49 GMT > Server: Apache/1.3.27 (Unix) PHP/4.2.3 > X-Powered-By: PHP/4.2.3 > Connection: close > Content-Type: text/html > > > > >