XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1169)
- Stylus Studio Technical Forum (14438)
-> - Auto EDI File Translation (1)
-> + Need help parsing EDI and crea... (2)
-> + Bug in generating Xml from Dtd (7)
-> + Stylus Studio 15, install erro... (4)
-> + How to create UML from XSD (2)
-> + Java configuration (4)
-> + embedding/starting X15 dircet ... (2)
-> + Stylus X15 R2 environment crip... (5)
-> + Output Method TEXT does not wo... (6)
-> + CONV loses its format on re-op... (5)
-> - Trouble Converting 846 EDI Fil... (1)
-> + XML Catalog support - DITA (2)
-> + non-persistent VDI, App-V Lice... (2)
-> + Can we READ XLS file and Conve... (8)
-> + Mapping XML to XML (3)
-> + SS X15 - Getting Error with 45... (2)
-> + Optimal for DB to XML? (2)
-> + Issues exporting SQL Server ->... (2)
-> + need additinal field in XML (2)
-> + blinking (3)
-- Previous [61-80] [81-100] [101-120] Next
+ Website Feedback (244)
+ XSLT Help and Discussion (7593)
+ XQuery Help and Discussion (1941)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (363)
+ Stylus Studio Announcements (113)
Topic  
Postnext
HereGear HereGearSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: HereGear HereGear
Date: 02 May 2014 10:59 AM
It appears that my StylusStudio install has died - after it threw an error yesterday, it will now not run known good xsl 2.0 transforms. It was a JVM error of some sort, I didn't catch it.

The app seems to launch OK, but won't run any XSL.

It will run the xsl, show output in the console, then will state "processing complete in 28.5 seconds" in that annoying/flashing info bar, then at the bottom it just shows the green progress bar and "processing..." and it never seems to finish/stops responding altogether.

I've tried it w/several known good xsl files - these same XSL files work fine in XMLSpy.

I'm forced to revert to XMLSpy right now as this product appears to be completely inoperative. Is there some type of corruption in a file or cache that can happen to Stylus Studio?

Config:
-Windows7 running on a VM
-Build info for all components seems to be 1910n
-1.6.0_45 Java HotSpot(TM) Client VM Sun Microsystems Inc.
debug mode port:8000

Postnext
Ivan PedruzziSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: Ivan Pedruzzi
Date: 02 May 2014 11:15 AM
Hi Eric,

Can we setup a GoToMeeting session so I can investigate the problem.

Let me know what time works best for you at stylussupport@ivitechnologies.com

Ivan Pedruzzi
Stylus Studio Team

Postnext
HereGear HereGearSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: HereGear HereGear
Date: 02 May 2014 11:18 AM
UPDATE: this is a bug in StylusStudio X15 that I just found related to my original post:

The app's console output defaults to tree-based view of data after a given query runs. After an initial launch of StylusStudio, there is no way that I can find to choose "text" as the output in the console. So if you're processing a large file THE FIRST TIME AFTER YOU STARTUP STYLUSSTUDIO, it will default to tree-based console out view - and run out of memory/locking the app I guess. My physical machine didn't run out of memory - StylusStudio appears to have - or just choked on that much data..

So - the workaround if you're processing a large file:
1. Start StylusStudio
2. Process a SMALL file first
3. After SS completes, only then can you see the options for console output
4. Choose text output
5. Reset the scenario/input for the larger file
6. Run it - it takes seconds vs. who-knows-how-long (I think it's a tree-based view bug, personally).

Now - I'm hoping I can find a "reviews" thread - if not, I've got some issues w/SS that need to be addressed ASAP.

Postnext
Ivan PedruzziSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: Ivan Pedruzzi
Date: 02 May 2014 11:34 AM
I don't see the behavior you are describing.

The Preview window features a vertical toolbar which allows to switch between the different viewers (Tree, Text, IE).

If the transformation's output is large, Stylus Studio should prompt a warning before switching to the IE view which is the less scalable.

The tree view can handle very large files. We have customers processing hundreds of MB without problems. How big is the output you are generating?

May be there is something peculiar in your configuration.


Ivan Pedruzzi
Stylus Studio Team

Postnext
HereGear HereGearSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: HereGear HereGear
Date: 05 May 2014 01:29 PM
A picture is worth 1000 words: attached is an image of a screenshot showing the output console at 2 different points in time:

1. The first time you fire up SS, it plainly shows no option to control how the output console formats the data

2. AFTER THE FIRST TIME DATA IS RUN via an xsl transform, you can now see the output console format options - and BTW: the default it tree...and, as I've stated in 2 other posts - that's another bug: tree-based output console for large data returns locks up SS. I ran it on a Friday, left it running on the weekend, came back on a Monday...still thinking, thinking.

ALSO: I've returned results of over 500k lines in the output console and I have yet to see SS warn me about "large data sets" as you stated previously.

Please fix these issues.

Postnext
HereGear HereGearSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: HereGear HereGear
Date: 05 May 2014 01:32 PM
Edit: there's also a bug in this forum - it didn't let me upload the image even after I checked the box to upload the image - trying again.


ImageSStudioConsoleOutOptionsBug.jpg

Postnext
Ivan PedruzziSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: Ivan Pedruzzi
Date: 05 May 2014 01:53 PM

The Output window and the Preview window are two separate entities.

The preview window is activated as soon an editor requires to render some output. The Preview window has an associated a tab for each scenario is configured in the scenario manager.

The default is the tree viewer because most likely Stylus Studio detected the output to be XML. If you click on the "Preview Text" button, the text viewer will be used on the following runs.

The Output windows captures what normally is sent the standard output.
Look under the View menu for the list of docking windows available.

This is a very well established UI metaphor.

The number of lines does not say much about the output size. How big is the file generated in Mb?
Is the output encoding Unicode?

You can setup the output URL in the scenario dialog which will force to create a file on this disk on each run.

The warning is triggered only when switching to the IE preview.

Ivan Pedruzzi
Stylus Studio Team

Postnext
HereGear HereGearSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: HereGear HereGear
Date: 05 May 2014 02:08 PM
>
>The Output window and the
>Preview window are two
>separate entities.

OK, then I guess its the Preview Window that has the bug whereby on the first "run" there's no way to choose between Preview Modes...

>
>The preview window is
>activated as soon an editor
>requires to render some
>output. The Preview window has
>an associated a tab for each
>scenario is configured in the
>scenario manager.
>
>The default is the tree viewer
>because most likely Stylus
>Studio detected the output to
>be XML. If you click on the
>"Preview Text" button, the
>text viewer will be used on
>the following runs.

The output was non-XML - it was JSON (thus it probably never could figure out what to put in the tree - thus the bug whereby it never stops thinking after running the XSL in Tree Preview Mode.

>
>The Output windows captures
>what normally is sent the
>standard output.
>Look under the View menu for
>the list of docking windows
>available.

My Bad: I was calling the Preview Window the Output Window.

>
>This is a very well
>established UI metaphor.
>
>The number of lines does not
>say much about the output
>size. How big is the file
>generated in Mb?
>Is the output encoding
>Unicode?

File generated is about 10mb.

It's just old-school ASCII text (i.e. JSON-compliant)


>
>You can setup the output URL
>in the scenario dialog which
>will force to create a file on
>this disk on each run.
>

Yes, you can create a file output in the scenario but guess what - even if you do that, it still runs a Preview. It would be MUCH better to have an option that never runs a preview and, instead, runs the file - then notifies me when the file processing is done. Why? Because preview takes a while - why wait for a GUI process when you can just wait for a file process?


>The warning is triggered only
>when switching to the IE
>preview.

I still think you have several bugs here.

>
>Ivan Pedruzzi
>Stylus Studio Team

Postnext
Ivan PedruzziSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: Ivan Pedruzzi
Date: 05 May 2014 03:16 PM
Originally Posted: 05 May 2014 03:13 PM
I did a quick experiment transforming 21 MB XML into 9 MB text output. Source are attached here, on my machine takes 5 seconds on Java 1.7, the Tree viewer renders the result immediately as single text node which is remarkable.

May be something is peculiar in your transformation.


Running on Java 1.8 takes 4 seconds.

Running without populating the the Preview window provides no value.
You can ask Stylus Studio to generate the Java code (XSLT -> Generate Code -> Generate Java Code ) for this purpose.


Hope this help
Ivan Pedruzzi
Stylus Studio Team


Imagetest(2).PNG


DocumentTEMP(1).ZIP

Postnext
HereGear HereGearSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: HereGear HereGear
Date: 05 May 2014 08:17 PM
OK - I finally figured out what is going on here:

Assigning the Output URL in a scenario to a file is somehow tied to the Preview Window's memory consumption. When I deleted the code that SS generates into the XSL file - i.e. the code that defines the scenario metadata - then ran it without setting that file-based URL output - SS tried to dump 464k lines of txt output to the Preview Window, which locked up the app.

I went back and setup the scenario as I originally had it - i.e. the output to a file and, voila - worky worky.

Now - Altova does this automagically without meta info in the file and by running some type of algorithm beforehand and, if it senses the output will be big, it'll turn off "autosense" in the output window (maybe it senses that the output won't necessarily be XML).

So, in conclusion, I think there's some fixes that should be affected:
-The biggee: Preview, plain-and-simple: insure that the output options are visible and configurable upon first startup of SS. This is a must-have - it's a big, bad, bug.

-Preview can lock up the app if you don't have a file set for the output for txt-based XSL conversion (and know that many developers are doing lots of txt-based XSL > JSON conversions these days - know it, love it, learn it, please respond accordingly within your application's logic sooner rather than later)

-Preview vs. Output: bad idea. Lose Preview, just use one output window. Too confusing.

-Get the app to try and sense what the output is going to be and - if it can't definitively sense that it'll be XML, AND the scenario has no output file configured - pop up a warning, fairly straightforward.

I just bought this tool - I would like a fix for this stuff soon so that it's in my upgrade contract. Don't look at my feedback as a negative: take it as a positive, you just got a high-paid developer to effectively debug a nasty problem with your app that I'm sure others have been frustrated with as well. (I should get paid!)

Last little rant I'm going to make (maybe): please modify the app so that I can run java from any location without having to update windows itself. I should be able to pop into SS, go to a config screen, change java's location, run it - and 5 seconds later do the same thing without leaving SS. Go look at Eclipse: it's the standard.

Thanks.

Posttop
HereGear HereGearSubject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: HereGear HereGear
Date: 05 May 2014 08:23 PM
Oh - and to be fair:

I was running a complex XSL from a + 10MB source file AND I was doing lookups inside a 4-level-deep for..each loop AGAINST 2 10MB EXTERNAL DOCS!

And it was burning through this w/Saxon9 in < 70 seconds.

So, Kudos for Stylus Studio performance - awesome.

Just fix the lil' things! It's in every developer's best interest to have a solid XSL and XQuery product offering that's non-monopolistic (i.e. someone besides Altova).

Thanks.

   
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.