XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » saxon 8.9 include path resolution error in 2007 R2 Enterprise
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Maximum recursion depth exceed... (3)
-> + How do I develop the server si... (2)
-> + XSD Reuse (2)
-> + what happened to my preview re... (3)
-> + How do I use the Custom XML Co... (4)
-> + WYSIWYG missing in release 2 o... (2)
-> + space between elements (3)
-> + Oracle XML Gateway output CONV... (6)
-> + Someone please help me install... (5)
-> + XML Schema (XSD) to COBOL Data... (2)
-> + Can't compile Java (9)
-> + Trouble using the UDDI Browser (5)
-> + JVM Problem when installing Ar... (2)
-> + Stylus Studio Enterprise 8r2 d... (2)
-> - xml report headers (1)
-> + ddtek:sql-delete and ddtek:sql... (4)
-> + Validation blocked (4)
-> + List from XMl to be displayed ... (2)
-> + reports - changing data source (5)
-> + Disable HTML tags in Sense:X (8)
-> + .NETCompiledTransform Paramete... (3)
-> + Why Is The Saxon Processor So ... (13)
-> + Still can not get "integrated ... (15)
-> + quick xml gen from xsd (2)
-> - new to sylus, issue with if va... (1)
-> + Question about using Data Dire... (5)
-> + Why is the DB to XML Data Sour... (2)
-> + Relational db => XML pipeline (2)
-> + connection to oracle 10g (8)
-> + xsl:function misdemeanor (3)
-> + Records Extraction from XML (2)
-> + line break variable destroyed (2)
-> + Restricting on an extended typ... (5)
-> + folding all xml elements at on... (2)
-> + help converting a text file to... (5)
-> + Java Functions (5)
-> + XML Schema - extend then restr... (6)
-> + Converting SGML to XML in pipe... (2)
-> + Unattended install? (3)
-> + what are the differences betwe... (2)
-> + cannot install (2)
-> + Missing Parameters within Web ... (3)
-> + XSLT processors not creating o... (8)
-> - How to format a seperate colum... (1)
-> + Finnish language characters (3)
-> + x12 schemas (10)
-> + Howto search multiple XML file... (3)
-> + Chameleon Schema? (2)
-> + Problems generating pdf (9)
-> + Cannot install Stylus Studio R... (19)
-> + source xml of a report (3)
-> + File I/O Error when encounter ... (3)
-> + substitution groups in xslt ma... (4)
-> + Delete rows in a MS SQL Server... (7)
-> - Attaching DB2 Database in File... (1)
-> + Can't debug xsl examples with ... (14)
-> + Best way to transform existing... (2)
-> + Exception in generated java co... (3)
-> + Java API for converting EDI X1... (2)
-> + XPath Query Editor slow perfor... (7)
-> + mapper schema problem (5)
-> + cursor issue in stylus studio ... (2)
-> + how to generate xslt code for ... (4)
-> + Web Service (12)
-> + Additional rule (2)
-> + Help needed: XMLSchema and unp... (9)
-> + Module settings for external X... (3)
-> + Finding Errors in the XML File (6)
-> + CSV 2 XML (2)
-> + Automatic Namespace when using... (2)
-> + Can't find 'Associate XML Sche... (3)
-> + Calling Stylus Studio API from... (2)
-> + EDI TO XML using the Stylus St... (4)
-> + MarkLogic Integration (4)
-> + (null)0:0 (3)
-> + Recent Windows Patch for MSXML... (3)
-> + Show XML from Schema (2)
-> + xml publisher - report to xslt... (4)
-> + EDI TO XML using the Stylus St... (3)
-> + Unable to Generate XML file fr... (6)
-> + DB to XML in Enterprise Suite (2)
-> + pdf to xml (2)
-> - Open External Schema - button ... (1)
-> - Unable to Generate XML from xC... (1)
-> + Unable to Generate XML from xC... (2)
-> + pre-proc processing in xml (2)
-> + FATAL ERROR: Expected comment ... (2)
-> + How to split window (3)
-> + XML Transformation Architectur... (2)
-> + only one record get run in an ... (2)
-> + xbrl schema file (2)
-> + Compare of 2 xml files (2)
-> + config control (4)
-> + create copy link in mapper (5)
-> + SGML DTD (3)
-> + command line access to your xs... (4)
-> + XML Schema: Attribute Choice (2)
-> + Upload file w/ topic (6)
-> - Can't View Properties (1)
-> + Can't View Properties (5)
-- Previous [1381-1400] [1401-1420] [1421-1440] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Kurt WaldSubject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: Kurt Wald
Date: 16 May 2007 12:43 PM
Originally Posted: 16 May 2007 10:22 AM
Hi,

the mechanism for the resolution of relative paths in xsl:include statements seems to be broken (at least) for the Saxon 8.9 processor implementation in Stylus Studio 2007 R2 Enterprise (see patherr.jpg). Using a native Saxon 8.9B as custom processor works ok.

Kurt Wald


Imagepatherr.jpg
Postnext
Goetz HellerSubject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: Goetz Heller
Date: 17 May 2007 06:25 PM
Hi Kurt, it appears that a kind of HTML escaping with URLs needs to be undone, but that this does not work - maybe the stylus developers forgot this point on their agenda. If you replace the character sequence %7E with a simple ~ (tilde) and copy the path to the explorer navigation field, then press ENTER, the explorer will go to to this directory immediately. The tilde sign is used frequently in converting file names to 8.3 compatible names, which stems from the (not so) good old DOS days. The problem is that I can't fix this bug.
For me it is quite frustrating that I have to revert to the previous version of stylus studio, since the correct working of path resolution is essential for my development.

I hope they will remedy the situation quickly.

Kind regards,

Goetz
Postnext
Goetz HellerSubject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: Goetz Heller
Date: 17 May 2007 07:08 PM
Hi Kurt,
while scanning other threads in this forum I found a hint which solves the problem: In the Scenario Properties dialog, uncheck "Use Stylus Studio URI Resolver".

Kind regards,

Goetz
Postnext
Goetz HellerSubject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: Goetz Heller
Date: 17 May 2007 07:56 PM
Hi Kurt,
the solution I proposed generates new problems: all transformations now run without error messages, but the resulting files are stored in the Stylus bin directory instead of the project directory. When I load the project into the old version of Stylus Studio, everything is fine - it works as before, and the unchecked check boxes apparently have no effect.

Kind regards,

Goetz
Postnext
(Deleted User) Subject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: (Deleted User)
Date: 18 May 2007 03:44 AM
Hi,
we are investigating the problem, and what we have found is that the behavior only occurs when using a JVM 1.6 (it looks that it doesn't handle properly short path names); using a JVM 1.5 doesn't trigger the error.
Goetz, could you tell us about the files in the 'bin' directory? Would it be possible for you to send us a testcase (even privately, to the e-mail stylus-field-report@progress.com)?

Thanks,
Alberto
Postnext
Goetz HellerSubject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: Goetz Heller
Date: 18 May 2007 04:36 AM
Hi Alberto,

it's o.k. Please be patient: The documents I'm working on are highly confidential; so let me prepare a test case for you. I hope to have enough time this weekend.

kind regards,

Goetz
Postnext
Kurt WaldSubject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: Kurt Wald
Date: 18 May 2007 06:19 AM
Originally Posted: 18 May 2007 06:11 AM
Hi Alberto,

thanks for the information, which leads me to another question. Why has the option of specifying a runtime library/JDK home directory under Java Virtual Machine options been replaced by a dropdown only showing installed JRE's/JDK's. I use a number of java environments not installed on but copied to the machine. Could you consider to make the former options available again (perhaps as an alternative to dropdown selection)?

One remark concerning output to the Stylus Studio bin directory. I remember, that using an xsl:result-document href without path information also placed the output in the Stylus Studio bin directory in previous versions.

Kurt
Postnext
(Deleted User) Subject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: (Deleted User)
Date: 21 May 2007 02:18 PM
Hi Kurt,
the rationale behind using a combo box was that having two different pieces of informations (location of the runtime library and jre executable) ended up being set to the wrong (or mismatched) values.
You could work around this by directly editing the registry keys used by Stylus Studio (HKEY_CURRENT_USER\Software\Stylus Studio\2007 XML Enterprise Suite Release 2\Runtime Settings), or you could create the proper registry settings used to advertise the available JVMs (HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment, just create a subkey named after the version, with a JavaHome and a RuntimeLib string values).

Hope this helps,
Alberto
Postnext
Kurt WaldSubject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: Kurt Wald
Date: 03 Jun 2007 10:46 AM
Hi Alberto,

2007 R1 does not produce the relative path resolution error with a Java 1.6 JRE.

Kurt
Posttop
Johan De SmedtSubject: saxon 8.9 include path resolution error in 2007 R2 Enterprise
Author: Johan De Smedt
Date: 16 Sep 2007 05:13 AM
Hi,

Did any sollution in stylus 2007 R2 turn up for this issue?

Thanks, Jo
   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.