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)
-> - More flexible generated Java c... (1)
-> + Generic Schemas for representi... (2)
-> + Stylus Studio Professional rep... (2)
-> + XML XML Help (2)
-> + xsd help (2)
-> + XML data element friendly name... (2)
-> + HTML Tidy adapter is missing? (3)
-> + New Guy Here... (2)
-> + How to combine two similar fil... (2)
-> + Berkeley XML DB (4)
-> + What is the context node in th... (3)
-> + Multi element List (4)
-> + Cannot preview XSL transformat... (9)
-> + Why is this variable not showi... (7)
-> + Customising Schema Prefix (3)
-> + Please help!! XML AND XSL Tra... (6)
-> + XML to Excel in Home Edition (2)
-> + how to copy elements from an x... (2)
-> + Setting Saxon parameters in pi... (2)
-> + Trying to move SS license (3)
-> + Does SS PRO Support CSS (2)
-> + Selected values are not showin... (3)
-> + Copy Xpath To Clipboard Option... (2)
-> + Upgrading to SS 2006 3 - Activ... (3)
-> + XSL Efficiency tips (4)
-> - Report page Size and table hea... (1)
-> + Endless loop with xquery (8)
-> - Xpress XML (1)
-> + Extracting XML data into SQL s... (2)
-> + Crashes when I save (2)
-> + XSL cannot save: I/O error...b... (8)
-> + Diagram view has disappeared f... (5)
-> + Convert from http://www.w3.org... (2)
-> + Round-trip Converting; CSV-XML... (2)
-> + XSL error function call PHP (8)
-> + WYSIWYG XSLT Designer (5)
-> + generate xhtml+css from xml re... (2)
-> + generate xhtml+css from xml re... (3)
-> + generate xhtml+css from xml re... (2)
-> - Help using xsd xs:redefine nee... (1)
-> + Data loss opening External sch... (2)
-> + Install Apache FOP Plugin with... (8)
-> + Generating a Publisher Canvas ... (2)
-> + Stylus Studio comment block no... (3)
-> + Report Designer Screen Repaint... (5)
-> + validating on values (5)
-> + reuse of xslt (2)
-> + The evaluation period for the ... (2)
-> + export to documentation (3)
-> + Validating XML files using sev... (2)
-> + Missing 'Command' Tab in Custo... (3)
-> + Do I have to download new vers... (6)
-> + Can SS validate tags used in a... (5)
-> + validating schemas (2)
-> + Off-Topic Question - Looking f... (4)
-> + cannot see anything in mapper ... (2)
-> + Validating XSD schema sets (7)
-> + Standard Validation Engines (3)
-> + Style Sheet amendment to inclu... (2)
-> + Documentation - prevent import... (3)
-> + Debugging breakpoints with Sax... (17)
-> + Conversion (3)
-> + New and I am sure this is an e... (7)
-> + Saxon 8 with multiple xml inpu... (3)
-> + Compilation error (5)
-> + webservice call failing - pls ... (3)
-> + C# from Java Binding Classes (3)
-> + Java binding class generation (5)
-> + Validation of deeply-nested sc... (5)
-> + How to make Drag and drop in X... (2)
-> + Malformed XPATH expression par... (5)
-> + Toolbars and missing options (4)
-> + Converting Text File (2)
-> + Java Heap Issue (2)
-> + Formatting SOAP messages (6)
-> + Attribute Entity Expansion on ... (2)
-> + Text File to xml conversion wi... (9)
-> + Different XPath results when u... (7)
-> + Where is my XSLT mapper module (3)
-> + Where is my XSLT WYSIWYG Edito... (2)
-> + Regarding Stylus support of IA... (2)
-> + Debugging Problem with Enterpr... (5)
-> + various report designer prob;e... (12)
-> - will it EVER get fixed ?? Stru... (1)
-> - Migrate from wysiwyg xslt edit... (1)
-> + Entity Resolver in UI? (4)
-> + Visual Studio and Stylus Studi... (2)
-> + how to get rid of parameter in... (8)
-> + XQuery file (2)
-> + 505 error calling a WS from SS... (2)
-> + Configure Subversion with Styl... (2)
-> + XSLT Mapping of xsi:nil and xs... (2)
-> + Printing values in a table or ... (2)
-> + query on using stylus API for ... (12)
-> + WSDL retruns no response (2)
-> + SS XSL Processor Bug: Count() (6)
-> + Stylus Studio crashes after re... (2)
-> + Custom Converter in IBM JVM is... (10)
-> + Malformed XPATH epressions on ... (4)
-> - XML Report table borders when ... (1)
-- Previous [1501-1520] [1521-1540] [1541-1560] 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.