Just for informational purposes...
I control all of the xml files in question, as the largest xml file is a
configuration file containing several XSL transformations. I was able to
work around this problem because I had already coded in all of the files
the full pathname to the imported files. The only thing I did in the end
was to hard code setting the base uri to the top of our configuration
directory. I could have set it anywhere, but that seemed a logical choice.
Thanks,
Anthony Zawacki
410-571-7161
[EMAIL PROTECTED]
Anthony
Zawacki/Baltimore/Cont To: [EMAIL PROTECTED]
r/[EMAIL PROTECTED] cc:
Subject: Upgrade 1.4-1.6 Problem:
Could not determine base pathname of the file
09/04/2003 03:37 PM
Please respond to
xalan-dev
Hello,
I am upgrading our software from Xalan 1.4 to Xalan 1.6 (Xerces 2.1 to
Xerces 2.3) on AIX 5.2 using the xlC_r compiler. I have run into a
problem. We are currently still using the Deprecated DOM portion of
Xerces. We are scheduled to upgrade to stop using the deprecated DOM in a
couple of months. However, there is a desire to pick up the bug fixes to
Xerces 2.1, so I was attempting to upgrade the appropriate code to Xalan
1.6.
I've only had three types of changes:
o Both projects now support namespaces, so I have generously used
XALAN_CPP_NAMESPACE_QUALIFIER and the Xerces equivalent.
o I'm now using FormatterToDeprecatedXercesDOM to do the transformation
rather than using a parser liaison to map the xerces document.
o The XMLFormatter constructor now requires the version as well as the
encoding.
I've changed everything that I see as potential problems. However, when I
run my application, it compiles six stylesheets, but the seventh fails. I
believe that I am running into the problem described in:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18464
My simple test program prints out 'Could not determine base pathname of the
file' as the result of getLastError() on the XalanTransformer.
I've read the solution in the bugzilla report, but I cannot find anything
similar in the deprecated API.
Any suggestions of what I can do to fix this short of upgrading to the new
API? That will have to wait for a couple of months yet.
I've attached several files that I've cobbled together that will
demonstrate the problem.
For me, the command line to compile the tmp.C is:
xlC_r -I/home/gerald/xerces-c-src_2_3_0/include/xercesc
-I/home/gerald/xerces-c-src_2_3_0/include/ -qalias=noansi
-I/home/gerald/xml-xalan/c/src/ -I/home/gerald/xml-xalan/c/src/xalanc -g
-qrtti=dyna -qlanglvl=newexcp -qinfo=dcl:eff:ini:rea:ret:uni -bh:5 -brtl
-L/home/gerald/xerces-c-src_2_3_0/lib -lxerces-c23.0
-L/home/gerald/xml-xalan/c/lib -lxalan-c16.0 tmp.C
Then run a.out with tmp.xml tmp.xsl and tmp2.xsl all in the same directory.
It prints the error message.
Running 'Xalan tmp.xml tmp.xsl' in the same place is successful.
(See attached file: tmp.C)
(See attached file: tmp.xml)
(See attached file: tmp.xsl)
(See attached file: tmp2.xsl)
Thanks,
Anthony Zawacki
410-571-7161
[EMAIL PROTECTED]
#### tmp.C has been removed from this note on September 12, 2003 by Anthony
Zawacki
#### tmp.xml has been removed from this note on September 12, 2003 by
Anthony Zawacki
#### tmp.xsl has been removed from this note on September 12, 2003 by
Anthony Zawacki
#### tmp2.xsl has been removed from this note on September 12, 2003 by
Anthony Zawacki
