Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


[xsl] Writing out to and reading back from an XML file

From: Chris Loschen <closchen@------------------>
To:
Date: 8/1/2004 6:08:00 PM
Hi again all,



I posted this the other day, but made the mistake of burying the question 
down inside an email on

another subject. Of course, it's also a summer weekend... Nevertheless, I 
still can't figure out a

usable workaround, and I'd appreciate any insights anyone might have.



Here's the situation: I have a very large file which I need to parse piece 
by piece, so I'm looping through

<BillHeader> and <Bill> (many times) and finally <BillTrailer> elements. In 
each case, the XSLT is run

on a single <BillHeader>, <Bill>, or <BillTrailer> rather than on the 
entire XML document, which could be

several hundred megabytes. So far, so good, but as it turns out, the 
<BillTrailer> output needs to replicate

most of what's in the <BillHeader> output. The solution I'm trying to use 
is to write out the <BillHeader>

normally, but also to an XML document which can then get called back in 
when we get to the <BillTrailer>.



The file is getting written out more or less as expected, and has the good 
data, but then the later process

can't find the file again. The cause appears to be that my filesystem has 
spaces in the names (d--n that

Windows!) so the file isn't getting written out to c:\Documents and 
Settings\ etc. but to c:\Documents%20and%20Settings

etc. -- I have a complete tree built up on my C drive with all of the 
spaces replaced with %20s. Then the

later process looks in the current directory and the file isn't there.



I've tried to get the URI of the current directory as a string so I could 
then replace the spaces with %20s and

use that as the base URI of the document() function, but wasn't able to 
make that work -- here's the

code I tried:



<xsl:variable name="header"><!-- not working -->

        <!--<xsl:variable name="base">

                <xsl:variable name="uri">

                        <xsl:value-of select="document('')/invoice"/>

                </xsl:variable>

                <xsl:call-template name="translate-space">

                        <xsl:with-param name="base" 
select="string(namespace::$uri)"/>

                </xsl:call-template>

        </xsl:variable>

        <xsl:variable name="file">

                <xsl:value-of select="concat($base,'/BillHeader.xml')"/>

        </xsl:variable>

        <xsl:value-of select="document($file)"/>-->

</xsl:variable>



<xsl:template name="translate-space">

        <xsl:param name="base"/>

        <xsl:choose>

                <xsl:when test="contains($base,' ')">

                        <xsl:call-template name="translate-space">

                                <xsl:with-param name="base" 
select="concat(substring-before($base,' '),'%20',substring-after($base,' '))"/>

                        </xsl:call-template>

                </xsl:when>

                <xsl:otherwise>

                        <xsl:value-of select="$base"/>

                </xsl:otherwise>

        </xsl:choose>

</xsl:template>



I was getting ClassCast exceptions, probably (I'm not sure) from the place 
where I try to cast the namespace as a string

and then it still couldn't find the document. I also tried setting up a 
shortcut to the other file from the current directory but

that didn't work either -- the file still wasn't found.



So, I think I understand what's happening, but I don't have a way around it 
-- any suggestions out there? Thanks!




Yours,



Chris Loschen
closchen@xxxxxxxxxxxxxxxxxx
781-718-3017 (cell)


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent