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 » XSLT Help and Discussion » Behaviour difference between built-in and XalanJ
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
- XSLT Help and Discussion (7625)
-> + Use of before and after string (3) Sticky Topic
-> - How do I substitute element ty... (1)
-> + How does one add working days ... (4)
-> - Help, I have existing XLT and... (1)
-> + Need help on XSLT issue - (2)
-> + EDI to XML Conversion (7)
-> - XML To JSON Conversion using X... (1)
-> + Formatting Paragraphs to same ... (2)
-> - Grouping of records (1)
-> + Problems with xsd 1.1 (4)
-> + XML to HL7 mapping (3)
-> + XSLT 3 and Iterate (2)
-> + XSL-FO to PDF preview (3)
-> + java.lang.RuntimeException: Er... (2)
-> + Create Acroforms with Stylus X... (2)
-> + How to change XSLT parameter s... (3)
-> + how to change format of the da... (2)
-> + Search "Next 8 Results " doesn... (2)
-> - Support for Git (1)
-> + newbee (8)
-- [1-20] [21-40] [41-60] Next
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Steve TrythallSubject: Behaviour difference between built-in and XalanJ
Author: Steve Trythall
Date: 25 Feb 2005 11:32 AM

I have discovered a difference in behaviour between the built-in processor and XalanJ.
I am trying to open a second document from an http URI, eg

<xsl:variable name="emp" select="document('http://scott:tiger@localhost:8080/oradb/SCOTT/EMP')"/>

This works OK with the built-in processor but the variable is empty if I change the scenario and
use Xalan. Any ideas why this should be the case and suggested workarounds?

Thanks

Steve

Postnext
Tony LavinioSubject: Behaviour difference between built-in and XalanJ
Author: Tony Lavinio
Date: 01 Mar 2005 03:41 PM
Could you try with one of the other Java engines - say Saxon 6 or 8?
This could help us to determine whether the problem is specific to the
Java version or to Xalan-J itself.
Postnext
Steve TrythallSubject: Behaviour difference between built-in and XalanJ
Author: Steve Trythall
Date: 01 Mar 2005 04:11 PM

Yes it also fails with both versions of Saxon (but works a real
treat with the built in processor!).

Is the built-in processor not a Java implementation?
Postnext
Tony LavinioSubject: Behaviour difference between built-in and XalanJ
Author: Tony Lavinio
Date: 02 Mar 2005 12:39 PM
The built-in processor is our own C++ implementation specially
instrumented for advanced debugging.
Posttop
Tony LavinioSubject: Behaviour difference between built-in and XalanJ
Author: Tony Lavinio
Date: 02 Mar 2005 12:46 PM
Originally Posted: 02 Mar 2005 12:47 PM
Since we've established that it is most likely a JDK problem and not
a problem specific to Xalan-J or either of the Saxons, there are a
couple of alternatives.

1. If you are on JDK 1.4, you might try upgrading to 1.5. If that works,
please let us know!

2. You could write a custom URI resolver for Xalan-J that would connect
and authenticate.

You might be able to get some help on the Xalan-J mailing list at
xml.apache.org
   
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.