|
Hi
Matt,
I am having the same problem and I am just wondering hjave
you found a solution. At the moment I am setting the SystemId of my xslSource to
be the location of the parent file but the system still seems to be unable to
find the imported stylesheet (even though it is looking in the correct
location!)
thanks,
Paul.
Hi,
We've recently switched over
some of our XSL transformation at work from our home-grown XSL parser to
Xalan, but we're stuck using an old version because it appears that the new
version looks for relative paths from the user.dir directory (I think), which
causes most includes to choke and not be able to find the file it is looking
for. Is there a fix for this either in the stylesheet side or the Java
side? I just built the latest nightly and it still seems to be this
way. We'd really like to move to Xalan, but this is one thing is holding
us back from adopting it. Please reply to this address, as I am not
subscribed to the list.
Thanks in
advance,
Matt
"If you mess with something for long enough it
will break."
- Schmidt's law of
engineering
|
