Folks,
Please, Can you use the
xsl:import tag within an XSLT which is packed into a jar/war/ear file? Especially one with a relative path? as in:
<xsl:import href="../../include/xsl/smis-reporting-common.xsl" />
We've just rejigged our deployment: to deploy an single ear file (per server), as apposed to jars + wars + stuff + parts + bits + things + components + resources + odds + ends + sundry files... which should be much cleaner, "tighter", with less opportunity for "deployment issues"... which have plagued us a bit in the past.
Except: I've just discovered this "XSL import "bug"" (in system-test thank goodness)...
An error occured while generating pdf Report: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException:
java.io.FileNotFoundException: /home/smisxcpt/domains/smis/SMIS_SERVER/.wlnotdelete/nrm-smis-application/nrm-smis-smartmap.war!/pndb/xsl/smis-placenames-detail-report.xsl (No such file or directory)
"Aha" I thought "I know what'd cause that: The XSL is now a resource, as apposed to a real file-system file"... So in I go and swap it over to getResourceAsStream(...), only to be faced with:
An error occured while generating pdf Report: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException: Had IO Exception with stylesheet file: ../../include/xsl/smis-reporting-a4portrait-template.xsl
So
smis-placenames-detail-report.xsl imports
smis-reporting-common.xsl with the command:
<xsl:import href="../../include/xsl/smis-reporting-common.xsl" />
... And I haven't got a clue!!! Other than "Hacking Around It" by writing a little deployer utility which extracts *.xsl from jar/war/ear files back onto the local file system. Yuck! Fooey! Shazbutt!
Please has anyone faced & solved this problem before?
Any brilliant ideas on "stuff to try next"?
I've got nothin'
Cheers all. Keith.
PS: We're running Weblogic 8.1 on Solaris 10 on a Sparc sun-fire v490.
Edited by: corlettk on 29/09/2008 18:03 - Ooops!