Edit report at http://bugs.php.net/bug.php?id=30106&edit=1

 ID:                 30106
 Comment by:         dpholden at gmail dot com
 Reported by:        phpcoder at gmx dot at
 Summary:            SOAP cannot not parse 'ref' element. Causes Uncaught
                     SoapFault exception.
 Status:             Closed
 Type:               Bug
 Package:            SOAP related
 Operating System:   Windows XP
 PHP Version:        5CVS-2004-09-16 (dev)
 Assigned To:        dmitry
 Block user comment: N
 Private report:     N

 New Comment:

It appears that it has not been fixed?



http://bugs.php.net/bug.php?id=53293


Previous Comments:
------------------------------------------------------------------------
[2005-03-22 11:22:41] dmi...@php.net

Fixed in CVS HEAD and PHP_5_0.



Now you can pass/receive XML Schema and <any> element as strings those
contain XML.



------------------------------------------------------------------------
[2005-03-08 14:11:13] h at designplastik dot com

I'm getting this error to on Gentoo with PHP 5.03. Please fix this :)

------------------------------------------------------------------------
[2005-01-11 01:11:19] jfxberns at hotmail dot com

Not to be a nag--but is this bug being worked on or just ignored?  I
just need to know what kind of priority it has or expected timeframe for
resolution so I can make decisions for project planning.  I realize that
this is maintained by contributors--but it helps everybody if we at
least know what is happening....

------------------------------------------------------------------------
[2004-12-18 22:02:37] jfxberns at hotmail dot com

Is there any status on this bug?  I see it has been assigned for a quite
a while.  I just would like to know if there is a solution on the
horizon in the near-term.

------------------------------------------------------------------------
[2004-10-13 20:39:04] jfxberns at hotmail dot com

I am having this problem and I am also having problems with PEAR::SOAP
on 5.0.2...



I can't wait for a fix--I am dead in the water!  



Is there an earlier version of 5.0.x (I am using 5.0.2) that does not
have this issue--or do I have to roll all the way back to PHP 4.3.x?

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    http://bugs.php.net/bug.php?id=30106


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=30106&edit=1

Reply via email to