Igor & Gary, thanks for the
suggestions. However, I don't believe this is an Xalan bug. This same test fails
with Saxon7, which leads me to believe that I'm running into a restriction with
the underlying Java API's on which these processors use. Or it simply user
error, based on not understanding what I have to do to make this
work.
Igor, I will follow-up with the use
of CVS (If I can figure out how to use it). I will also fill out a bugzilla
report as soon as I'm sure it's a bug. It really won't be possible to work up a
test case for you. You will need a web service of some type that supports
Basic Authentication and will serve you any xml doc. The XSLT is very
easy.
<?xml version="1.0"
encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
<xsl:template match="/">
<xsl:variable name="httplink" select="'http://username:[EMAIL PROTECTED]/anydirectory/filename.xml'"/>
<xsl:variable name="test" select="document($httplink)"/>
<xsl:copy-of select="$test"/>
</xsl:template>
</xsl:stylesheet>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
<xsl:template match="/">
<xsl:variable name="httplink" select="'http://username:[EMAIL PROTECTED]/anydirectory/filename.xml'"/>
<xsl:variable name="test" select="document($httplink)"/>
<xsl:copy-of select="$test"/>
</xsl:template>
</xsl:stylesheet>
Gary,
on a TCP/IP trace. I assume you mean capturing the http protocol exchange
between the XMLServer and the XSLT Transform Engine. If you know of app to
capture this, Yahoo! I was ready to take this step a week ago, and would like to
see what's happening myself. Do you know of a free or shareware app to capture
data on a port?
Joe
-----Original Message-----
Joe --
If Igor's suggestion touse the latest CVS doesn't work, I recommend getting a TCP/IP trace from your machine so we can see exactly what's going on.Gary----------------------------Yes, we had some problems with URI resolver in 2.5.1.Could you try the latest CVS?
Could you open defect in http://nagoya.apache.org/bugzilla/
if it wouldn't fix your problem. (It could be really easier for us if you could attach a reproducible test-case).Igor Hersht
---------------------------
XSLT DevelopmentI've been beating my head against the wall trying to find an answer to this problem, or even a place to ask about it. You all win, sorry for the burden.I'm using Oracle's http interface to pull in XML from our relational tables. Xalan is the XSLT processor we're using 2.5.1, and the following fails:<xsl:variable name="sampleurl" select="'http://username:[EMAIL PROTECTED]:8002/anydirectory'"/><xsl:variable name="test" select="document($sampleurl)"/>We end up receiving a HTTP 401 error. This kind of makes since, it's an authentication error and also part of the process of authenticating Basic Authentication. However, I shouldn't see the error and I should be authenticated.Best I can figure it's a URI resolver issue. Anyone know how to get around this or make it work?FTP works fine in a document(), xsl:Import, or xsl:Include, But HTTP doesn't want to function.Thanks for any help, I hope to return the favor.
