Please see results after calling these two XSL files separately.
http://68.32.61.40/ccbn/test_usingListXSL.cfm
http://68.32.61.40/ccbn/test_usingTextXSL.cfm
I kind of question the wisdom of getting all these XSL files from a remote site, and constantly checking if they would work with CF and make changes if not, just for the project I intend to do. Or because of no better alternatives?
Again, I appreciate it.
Don
>The document had a bunch of errors like this:
>
>Window::transform:
>javax.xml.transform.TransformerConfigurationException:
>javax.xml.transform.TransformerException:
>javax.xml.transform.TransformerException: Non-whitespace text is not
>allowed in this position in the stylesheet!
>
>They could have been added in the email, but I don't think so. They seem
>to occur around <xsl:choose>'s. Its probably on the xslt generation end
>if they are using a legacy system to create the xslt file. Either they
>are using a wack editor, or the process they use to generate the xslt is
>sticking in non-printable control characters.
>
>Most any white space (aside from tab, newline, return, space) will cause
>these errors and they are hard to spot because it looks just like white
>space. If you have a hex editor handy, you can spot them a bit easier.
>
>After I removed the bad whitespace chars it ran fine. Try running the
>xsl file against that fake xml file I sent in the last post. (That why
>you know any errors are in the xslt)
>
>
>
>--
>Vale,
>Rob
>
>Luxuria immodica insaniam creat.
>Sanam formam viatae conservate!
>
>http://www.rohanclan.com
>http://treebeard.sourceforge.net
>http://ashpool.sourceforge.net
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
