Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Commented: (XERCESJ-1204) Can not set XMLEntityResolver for LSParser

Commented: (XERCESJ-1204) Can not set XMLEntityResolver for LSParser

2006-11-16       - By Dick Deneer (JIRA)
Reply:     1     2     3  

   [ http://issues.apache.org/jira/browse/XERCESJ-1204?page=comments#action
_12450458 ]
           
Dick Deneer commented on XERCESJ-1204:
--------------------------------------

On 20/Oct/06 I commented:
================================================
Strange enough it is called when you first do a revalidation with :
- you have set config.setParameter("schema-type",
"http://www.w3.org/2001/XMLSchema");
and then switch back to
- config.setParameter("schema-type",
"http://www.w3.org/TR/REC-xml");
=================================================

This comment can be ignored; it was caused by my program where I reread the xml
into a Dom.
The Dom revalidation itself will never call getExternalSubset.
But personally this is not a problem for me.
You van use the set  schema-location, and then the resolveEntity method will be
called, with in the systemId the given location.




> Can not set XMLEntityResolver for LSParser
> ------------------------------------------
>
>                 Key: XERCESJ-1204
>                 URL: http://issues.apache.org/jira/browse/XERCESJ-1204
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: DOM (Level 3 Core)
>    Affects Versions: 2.8.1
>            Reporter: Dick Deneer
>         Assigned To: Michael Glavassevich
>            Priority: Minor
>         Attachments: DOMConfigurationImpl.java, DOMConfigurationImpl.java,
DOMParserImpl.java, DOMParserImpl.java, XMLParser.java
>
>
> Using the DOM level 3 api to create a DOM using :
>         DOMImplementationRegistry registry =
>                 DOMImplementationRegistry.newInstance();
>         DOMImplementationLS domImpl = (DOMImplementationLS)
>                 registry.getDOMImplementation("LS 3.0");
>         LSParser parser = domImpl
>                 .createLSParser(DOMImplementationLS.MODE_SYNCHRONOUS,
>                                 XMLConstants.W3C_XML_SCHEMA_NS_URI);
>       org.w3c.dom.DOMConfiguration config = parser.getDomConfig();
>       config.setParameter("resource-resolver", resolver);  //where  resolver
is an LSResolver
>         Document doc = parser.parseURI(sourceURI);
> The LSResolver  has the resolveResoure method:
> public LSInput resolveResource(String type, String namespaceURI,
> String publicId, String systemId, String baseURI)
> My problem is that I need much more information about the resource
> than what is passed to this method.
> For instance I can not distinguish a DTD grammar from an
> XMLEntityDescription because from the "type" parameter passed.
> I want to use the XMLEntityResolver but trying:
> config.setParameter(
>           "http://apache.org/xml/properties/internal/entity-resolver",
myXMLEntityResolver)
> gives an org.w3c.dom.DOMException: FEATURE_NOT_FOUND: The parameter http:/
/apache.org/xml/properties/internal/entity-resolver is not recognized.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http:/
/issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
For additional commands, e-mail: j-dev-help@(protected)