list unparsed-entity-uri()

bonekrusher · April 21st, 2008, 12:55 PM

Hi,

Using Saxon 9.002 and XSLT 2.0, how can I get the value of the an unparsed-entity-uri() with out knowing the name for the entities in the below example?

Code:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE DRIVERSLICENSE SYSTEM "driverlicense.dtd" [
    <!ENTITY phone SYSTEM "phone.ent">
    <!ENTITY % commonEnties SYSTEM 'c:/temp/common.ent'> 
    %commonEnties;
]>

Thanks,

samjudson · April 23rd, 2008, 07:53 AM

I'm not 100% sure but does this not work:

Code:

<xsl:value-of select="unparsed-entity-uri('phone')" />

/- Sam Judson : Wrox Technical Editor -/

mhkay · April 23rd, 2008, 09:35 AM

Support for unparsed entities and notations in the XDM data model is very limited (not many people seem to use them). In particular, you can't find out what entities have been declared, you can only get the system ID and public ID of an entity whose name you already know.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

bonekrusher · April 23rd, 2008, 10:48 AM

Thanks,

"you can only get the system ID and public ID of an entity whose name you already know." - this is my dilemma.

The XML files uses numerious entity references, but these references are burried in other entity files, which makes for inventoring these files a mess. I need GPS to navigate these files! The best way to describe it is "like a daisy chain". A poor design, which makes reading them horrible.

Maybe you may have some suggestions to do the following:

I wrote an XSLT file (called from a java swing app) that will to output all the base-uri's to temp.xml file. I then read this XML file (using Saxon xpath) and zip those files. This works great except if the entity is not directly called. I am up for any "out-of-the-box" suggestions (if any)

Thanks for the help.

Regards

mhkay · April 23rd, 2008, 12:59 PM

Basically, XSLT doesn't have access to this information. I would write a SAX application in Java to collect notifications of the entity declarations from the XML parser, then write the list of entity names to an XML document, then process this XML document using XSLT.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

bonekrusher · April 23rd, 2008, 02:14 PM

Thanks...Good idea. I will try.

bonekrusher · April 28th, 2008, 10:52 AM

Hi,

Solved! If any one is interested:

Code:

 try {
                // Create an XML parser
                DocumentBuilder builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
                // Install the entity resolver
                builder.setEntityResolver(new MyResolver());
                // Parse the XML file
                org.w3c.dom.Document doc = builder.parse(new File(myXML.xml));

            } catch (SAXException e) {
            // A parsing error occurred; the xml input is not valid
            } catch (ParserConfigurationException e) {
            } catch (IOException e) {
            }

Entity Resolver:

Code:

 public class MyResolver implements EntityResolver {

        public InputSource resolveEntity(String publicId, String systemId) throws FileNotFoundException {
            try {

                URI uri = new URI(systemId);

                System.out.println(systemId);                    

            } catch (URISyntaxException e) {

            }

            return null;
        }
    }