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 » document() fails in home edition -- does this really require Enterprise Ed.?
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Specifying EDI Delimiters (2)
-> + Defining 'connection string' f... (9)
-> + Help Programatically Convertin... (2)
-> + Using adapter URL in pipeline. (7)
-> + How to enable EDI functionalit... (2)
-> + Unable to open file with '%2F'... (2)
-> + How to create a dependency gra... (2)
-> + If block (2)
-> + Mapping multiple files within ... (7)
-> + StylusStudio vs Altova vs BizT... (4)
-> + Command line execution (7)
-> + CSS and Styling in X15 (2)
-> + Ignores debug breakpoints in X... (5)
-> + Cursor dissapearing in Text vi... (5)
-> + compile error xquery java styl... (3)
-> + Stylus Studio Setup: Applicati... (10)
-> + Stylus StudioX15 Crashing whe... (4)
-> + Upgrade Stylus 14 to 15 (2)
-> + ACE Broker Download v2.5 (2)
-> + Help creating custom convertor (7)
-> + Problem saving Documentation (5)
-> + Registry keys for Stylus x15 (8)
-> + How to add a value when conver... (10)
-> + Stylus Studio Pro & Ent X15r1 ... (2)
-> + You need to install Java 2 SDK... (4)
-> - How to disable automatic and m... (1)
-> + Does Stylus Studio / DataDirec... (4)
-> + Stylus Studio fails with 'The ... (12)
-> + Struzzo.exe side by side confi... (7)
-> + unable to use converter (5)
-> + How to enable XSD 1.1 for Saxo... (3)
-> + XSD v.1.1 validation and Xerce... (8)
-> + FATAL ERROR: unsupported XML v... (2)
-> + Java Runtime Environment boot ... (2)
-> + Associate XML with Schema (3)
-> + JVM not found in stylus studio... (2)
-> + Change newline to Linux (on Wi... (4)
-> + Indent XML Tags only partially... (2)
-> + dealing with invalid character... (2)
-> + Unable to call Webservice thro... (2)
-> + XML to CSV Video create csv te... (5)
-> + Try to test this product, (2)
-> + How to migrate license? (3)
-> - kepp your settings on X15 upda... (1)
-> + No Topic (2)
-> + XSD validation scalability iss... (2)
-> + Installing documentation in ai... (4)
-> + Stylus Studio is currently una... (2)
-> + Change from SS Pro 2011 to SS ... (2)
-> + Problem with pipeline function... (2)
-> + Min and Max Occurs for Choices... (2)
-> + XSLT without Preview window ou... (3)
-> + How to achieve this transforma... (2)
-> + Licence Authentication Failed (2)
-> - using Oracle V2 for validation... (1)
-> + Steps needed to execute standa... (2)
-> + xsi:noNamespaceSchemaLocation ... (8)
-> + Using Saxon 9.4 and integrated... (4)
-> + "net XML Parser (5)
-> + How to undo in Stylus Studio X... (2)
-> + .RENAME section not loaded cor... (3)
-> + Stylus StudioŽ X14 Release 2 X... (2)
-> + The JVM initialization failed ... (2)
-> + XML schema to XML does not wor... (4)
-> + missing ExtraLines (3)
-> + EDI validation tool (2)
-> + Registering Custom Tool from c... (5)
-> + Setting Default XML Validation... (2)
-> + Project Directory in Custom Do... (3)
-> + Problem with Saxon 9.4.0.4 AVT... (5)
-> + XML To HL7 (3)
-> + Siblings not repeating when mi... (7)
-> + Nesting of records from fixed ... (5)
-> + Licensing (3)
-> + CSV set up to support predefin... (10)
-> + Scripting conversion (2)
-> + Edi/Euritmo automatic conversi... (4)
-> + Have new stylesheet automatica... (3)
-> + Text file to CSV to xml (9)
-> + EDIFACT to XML (4)
-> + About Stylus Studio... dialog ... (5)
-> + Set Stylus as default editor f... (3)
-> + CSV to XML (11)
-> + Indent XML tags no longer work... (9)
-> + XSL code completion moe like o... (3)
-> + xsl:fo - unable to use any fon... (5)
-> + Bug when calling a ms script f... (13)
-> - url schema (1)
-> + Quickbooks invoice to XML (4)
-> + X14 locks up, Unresponsive (4)
-> + Fields missing from middle of ... (2)
-> + Cannot install trial (2)
-> + Text File with Page breaks - H... (8)
-> + Complex transactional CSV mapp... (2)
-> + XML Report (2)
-> - Create an XML feed for videos (1)
-> + word doc (2)
-> + Saving to a UNC path (7)
-> + sharing violation (3)
-> + Convert XML to XML (6)
-- Previous [181-200] [201-220] [221-240] 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
Shane McRobertsSubject: document() fails in home edition -- does this really require Enterprise Ed.?
Author: Shane McRoberts
Date: 25 Sep 2005 11:29 PM
I have a very simple stylesheet that attempts to open an XML file using the following (I'm using Saxon to get XSLT 2.0 functionality):

<xsl:variable name="site" select="document('atomicpug.net.xml')"/>

I get the following error:

java.lang.RuntimeException:
This feature is only available in the Stylus Studio Enterprise Edition
You are not licensed to use the StylusFileFactory API.

I'm using a fairly straightforward technique from Dmitry Kirsanov's book "XSLT 2.0 web development" to build a 6-page personal website and I'm surprised this requires EE. Does it really?

Postnext
Tony LavinioSubject: document() fails in home edition -- does this really require Enterprise Ed.?
Author: Tony Lavinio
Date: 26 Sep 2005 04:43 PM
Could you post or email to stylus-field-report (at) stylusstudio.com
your XSL and XML file? Then we could determine why it thinks EE is
needed. AFAIK, you should be able to use Saxon with Home Edition, but
it might be the document() function that has the trouble.
Postnext
Tony LavinioSubject: document() fails in home edition -- does this really require Enterprise Ed.?
Author: Tony Lavinio
Date: 26 Sep 2005 05:00 PM
Go to the scenario page, and see if the "Use Stylus Studio URI resolver"
box is checked. If it is, that is the problem. The Stylus Studio URI
resolver is only available with Enterprise, and can only be enabled by
an Enterprise edition (or an older Professional edition, from before we
had a separate Enterprise edition).

If that XSL document was created by another version, and then loaded
into a Home version, the flag will still be set. Try changing the
engine type from Saxon to Built-in and then back. If that doesn't
disable it, create a new scenario, copy the options, and then delete
the troubled scenario.
Postnext
Shane McRobertsSubject: document() fails in home edition -- does this really require Enterprise Ed.?
Author: Shane McRoberts
Date: 26 Sep 2005 10:34 PM
That setting was, in fact, set. I have never had anything but home (and only for a few days) and had just switched to Saxon to get the XSLT 2.0 support. Weird thing is that checkbox is disabled so there was no way to clear it. I rebooted for unrelated reasonse, and it cleared itself. Now all is fine. I'm looking forward to native Stylus support for 2.0--the Saxon error messages are nearly useless (they tell you where the problem is but seldom what it is).

Postnext
Tony LavinioSubject: document() fails in home edition -- does this really require Enterprise Ed.?
Author: Tony Lavinio
Date: 27 Sep 2005 01:07 AM
Saxon does report errors; to see them, use View|Output Window.

In the next release of Stylus Studio, we've made them more prominent
so that this isn't necessary.
Postnext
Shane McRobertsSubject: document() fails in home edition -- does this really require Enterprise Ed.?
Author: Shane McRoberts
Date: 28 Sep 2005 12:36 AM
I've confirmed that this bug repros.

1. Create a new xsl stylesheet in Home edition.
2. Change version= to "2.0".
3. Run it. You will be prompted to use Saxon instead of built-in because the built-in processor doesn't support 2.0.
4. Accept the switch to Saxon. You will immediately get an error in the Output window saying the Enterprise edition is required
5. Open the scenario and go to the Processor tab. You'll see that the URI resolver checkbox is checked but disabled (grayed).

The only way I've found to clear this is to reboot.

PS> Yes, I know the Saxon processor outputs error messages. I have found the built-in processor's error messages much more useful.
Posttop
Tony LavinioSubject: document() fails in home edition -- does this really require Enterprise Ed.?
Author: Tony Lavinio
Date: 28 Sep 2005 04:19 PM
Okay, here's the problem. If we automatically switch you from 1.0 to
2.0 mode, we don't touch the 'Use Stylus resolver' setting. It doesn't
matter how it is set for the internal processor, but it does matter for
Saxon. We should be forcing it off if you are using a version of Stylus
Studio that doesn't support using our resolver, but instead we're just
leaving it at the default value.
It has been fixed for the next patch release and also the next full
release of Stylus Studio.
In the meantime, you can open any affected XSL files with notepad or
some other simple editor, and in the meta-information at the end of the
file, change
useresolver="yes"
to
useresolver="no"
and the XSL file will become usable without having to restart anything.
   
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.