Using libxml_use_internal_errors() may suppress errors but Exception still requires decent handling. I used following code snippet.
<?php
libxml_use_internal_errors(true);
try{
$xmlToObject = new SimpleXMLElement($notSoWellFormedXML);
} catch (Exception $e){
echo 'Please try again later...';
exit();
}
?>
SimpleXMLElement::__construct
(PHP 5 >= 5.0.1)
SimpleXMLElement::__construct — Creates a new SimpleXMLElement object
Description
$data
[, int $options = 0
[, bool $data_is_url = false
[, string $ns = ""
[, bool $is_prefix = false
]]]] )Creates a new SimpleXMLElement object.
Parameters
-
data -
A well-formed XML string or the path or URL to an XML document if
data_is_urlisTRUE. -
options -
Optionally used to specify additional Libxml parameters.
-
data_is_url -
By default,
data_is_urlisFALSE. UseTRUEto specify thatdatais a path or URL to an XML document instead of string data. -
ns -
Namespace prefix or URI.
-
is_prefix -
TRUEifnsis a prefix,FALSEif it's a URI; defaults toFALSE.
Return Values
Returns a SimpleXMLElement object representing
data.
Errors/Exceptions
Produces an E_WARNING error message for each error
found in the XML data and additionally throws an Exception if the XML data
could not be parsed.
Use libxml_use_internal_errors() to suppress all XML errors, and libxml_get_errors() to iterate over them afterwards.
Examples
Note:
Listed examples may include example.php, which refers to the XML string found in the first example of the basic usage guide.
Example #1 Create a SimpleXMLElement object
<?php
include 'example.php';
$sxe = new SimpleXMLElement($xmlstr);
echo $sxe->movie[0]->title;
?>
The above example will output:
PHP: Behind the Parser
Example #2 Create a SimpleXMLElement object from a URL
<?php
$sxe = new SimpleXMLElement('http://example.org/document.xml', NULL, TRUE);
echo $sxe->asXML();
?>
Changelog
| Version | Description |
|---|---|
| 5.2.0 | Added the ns and is_prefix parameters. |
| 5.1.2 | Added the options and data_is_url parameters. |
See Also
- Basic SimpleXML usage
- simplexml_load_string() - Interprets a string of XML into an object
- simplexml_load_file() - Interprets an XML file into an object
- Dealing with XML errors
- libxml_use_internal_errors() - Disable libxml errors and allow user to fetch error information as needed
As I was filling out a bug report, I realized why (speculation here) the constructor is final: so that functions like simplexml_load_file and simplexml_load_string can work. I imagine the PHP-ized code looks something like
<?php
function simplexml_load_file($filename, $class_name = "SimpleXMLElement", $options = 0, $ns = "", $is_prefix = false) {
return new $class_name($filename, $options, true, $ns, $is_prefix);
}
?>
If we were to use a different $class_name and change the constructor's definition these functions wouldn't work.
There's no easy, sensible solution that keeps simplexml_load_file and simplexml_load_string.
This class is extendable, but it's too bad that its constructor cannot be overriden (PHP says it's a final method). Thus the class should be wrapped using the delegation principle rather that extended.
SimpleXML does not correctly parse SOAP XML results if the result comes back with colons ‘:’ in a tag, like <soap:Envelope>. Why? Because SimpleXML treats the colon character ‘:’ as an XML namespace, and places the entire contents of the SOAP XML result inside a namespace within the SimpleXML object. There is no real way to correct this using SimpleXML, but we can alter the raw XML result a little before we send it to SimpleXML to parse.
All we have to do is use the preg_replace function to get rid of the colons in the SOAP response tags BEFORE you hand it off to SimpleXML, like so:
<?php
// SimpleXML seems to have problems with the colon ":" in the <xxx:yyy> response tags, so take them out
$xmlString = preg_replace("/(<\/?)(\w+):([^>]*>)/", "$1$2$3", $response);
?>
