blob: 2aa4b596701cabba02092a1352c71f73ebb18a49 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">
<!-- /*******************************************************************************
* Copyright (c) 2000, 2005 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Eclipse Public License v1.0
* which accompanies this distribution, and is available at
* Contributors:
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
<title>Limitations of XML Editor</title>
<body id="rlimitations_slushXML"><a name="rlimitations_slushXML"><!-- --></a>
<h1 class="topictitle1">Limitations of XML Editor</h1>
<div><p>This section describes known product aspect limitations and workarounds.</p><div class="skipspace" id="rlimitations_slushXML__unresolv_URI"><a name="rlimitations_slushXML__unresolv_URI"><!-- --></a><p>The
behavior of the XML parser when encountering an unresolvable URI (for example,
in a DOCTYPE declaration) is to report a fatal IO error and stop any further
processing. An unresolved URI is seen neither as a syntactic nor a semantic
error and as such, the parser does not attempt to handle it. Essentially,
the document remains unchecked. This is a known problem.</p>