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 » Java Built-in processor no longer working since upgrade to Enterprise 2008 R2
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Varying Length Multiple Record... (2)
-> + Flat Flie to xml - validation (2)
-> + File Association (2)
-> + Generate XSL to transform from... (2)
-> + Installation Problem (3)
-> + compile error with generated j... (4)
-> + Help with Result of "Create Sc... (2)
-> + Region start position (line ve... (3)
-> + XSLT Mapper calling wrong temp... (3)
-> + Convert XSL to XSL:FO (5)
-> + Problem after downloading the ... (2)
-> + Moving node up / down (4)
-> + License transfer problem (2)
-> + Long element names in EDIFACT ... (4)
-> + Convert XML Schema to DB Table... (2)
-> + Connecting to DB2/400 through ... (2)
-> - Uninstall doesn't work (1)
-> + Pound (#) symbols appear inste... (3)
-> + Multiple file regions - dynami... (3)
-> + Cannot start Stylus studio pro... (2)
-> + XQuery missing Data when run (3)
-> + I need Help with a symple type... (2)
-> + Error while opening XML file f... (4)
-> + xquery variable substitution (2)
-> + Tab delemited Flat file to XML (17)
-> + Error on XSchema validation: "... (3)
-> + How to delete a file from a pr... (3)
-> + Generate Java Binding Classes (2)
-> + stylusstudio2008 suddenly stop... (2)
-> + Please Help (2)
-> - Looking in one tag to get the ... (1)
-> + Entity 'nbsp' was not found (2)
-> + Create 1 xml file for each lin... (4)
-> + SchemaLocation attribute (3)
-> + page break (4)
-> + name attribute of wsdl:fault e... (3)
-> + Cannot use my custom converter (3)
-> + java.lang.ClassNotFoundExcepti... (16)
-> + Witch product to buy (2)
-> + Trial version giving errors (2)
-> + Building and Integrating modul... (2)
-> + How to deploy pipeline (4)
-> + Is it possible to create xml f... (4)
-> + XML - CSV - XML Help! (2)
-> - xml file with many xsl style s... (1)
-> + Crash when using XML with DOCT... (2)
-> + Calling .Net classes from XSL ... (6)
-> + datadirect coverter result dif... (4)
-> + .net ConverterFactory().Create... (2)
-> + Dynamically created xsl used i... (4)
-> + Help with XSD attributes (3)
-> + Duplicated XML tag name in XML... (2)
-> + XML Publisher Repeater Bug wit... (4)
-> + HTML / FO selection (2)
-> + Command line interface to gene... (2)
-> + Provider org.apache.xerces.jax... (3)
-> + Problems with xsl:variable (2)
-> + any way to stop auto declarati... (2)
-> + Holding information in memory (9)
-> + Error whenever we try to read ... (4)
-> + Evaluation Versio Stylus Studi... (3)
-> + Convert linefeed-separated tex... (2)
-> + Transferring Stylus Studio fro... (3)
-> + Activation working on only one... (4)
-> + Populating Database from XML (2)
-> + Inserting Annotation (3)
-> + Project Window (2)
-> + DTD to Schema conversion gener... (2)
-> - Can't add multiple faults to a... (1)
-> + Soap fault name element (2)
-> + xml files supported outside of... (2)
-> + how to allow null values for d... (2)
-> + xml report query (5)
-> + Stylus Studio automatically ad... (3)
-> + Can we can stylus studio autom... (2)
-> + is it possible to insert into ... (3)
-> + Java Heap Space error (4)
-> + custom validation engines (3)
-> + W3C schema for enumerated taxo... (3)
-> + Using Stylus to generate elect... (2)
-> + WSDL editor and drop downs in ... (2)
-> + XSLT Mapper "forgetting" setti... (2)
-> + StylusStudio Crash: Error: Get... (7)
-> + Error in installation (2)
-> + Applying constraints & naming ... (5)
-> + Windows Installer prevents ins... (5)
-> + XML Schema to XML producing in... (8)
-> + calling javascript function in... (2)
-> + Repairin .xml file (2)
-> + HIgh CPU on a laptop after hib... (2)
-> - conditional rendering in XSL.. (1)
-> + Way to replace codes by labels... (4)
-> + Strange 'invisible' characters (4)
-> + syntax (2)
-> + Problem using mySQL (2)
-> + accessing Javascript variable ... (2)
-> + problem when openning files (2)
-> + Free Form Text (2)
-> + Cant open the database (4)
-> + Problem using MS Access (4)
-- Previous [1021-1040] [1041-1060] [1061-1080] 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
Michel DuronSubject: Java Built-in processor no longer working since upgrade to Enterprise 2008 R2
Author: Michel Duron
Date: 23 May 2008 03:49 PM
We have been developing XSLT transforms with Stylus Studio for almost 2 years now and have always used the built-in java processor because our code needs calls to java date fucntions.

However, the R2 upgrade means the same sourcesafe forms and XML samples that used to work no longer work.

We have build 1147c.

Do i need to downgrade?

The following code used to work:

XML (fragment):
<EntitlementTimeLicenseModelAttributes>
<Attribute>
<Name>LANGUAGE</Name>
<Value>en</Value>
</Attribute>
</EntitlementTimeLicenseModelAttributes>

XSL FRAGMENT:

<xsl:for-each select="EntitlementTimeLicenseModelAttributes/Attribute/Value[preceding-sibling::Name='LANGUAGE']">
<item>
<date>9999</date>
<lang>
<xsl:value-of select="."/>
</lang>
</item>
</xsl:for-each>

WHERE the result would be:
<item>
<date>9999</date>
<lang>
en
</lang>
</item>

Since 2008R2, we have the following instead:
<item>
<date>9999</date>
<lang>
LANGUAGE
en

</lang>
</item>

and, doing a copy-of instead of the value-of:
<item>
<date>9999</date>
<lang>
<Attribute>
<Name>LANGUAGE</Name>
<Value>en</Value>
</Attribute>
</lang>
</item>

Basically, the context instead in the for-each loop is totally wrong now...
Postnext
Michel DuronSubject: Java Built-in processor no longer working since upgrade to Enterprise 2008 R2
Author: Michel Duron
Date: 23 May 2008 03:56 PM
One more thing...

I checked the standard built-in parser (by removing all the java dependencies), and the code works perfectly in that case.

So, this is really a critical regression bug with Stylus Studio when using the java built-in processor.
Postnext
(Deleted User) Subject: Java Built-in processor no longer working since upgrade to Enterprise 2008 R2
Author: (Deleted User)
Date: 26 May 2008 08:58 AM
Hi Michel,
Stylus should not be involved in the generation of the output of the Java built-in XSLT engine, so the difference could be in the Java engine itself. By chance, did the new installation of Stylus Studio pick a different JRE, maybe embedding a different version of Xalan-J? (you can see the JRE version in the About box dialog)

Alberto
Postnext
Michel DuronSubject: Java Built-in processor no longer working since upgrade to Enterprise 2008 R2
Author: Michel Duron
Date: 26 May 2008 12:05 PM
Hello Alberto,

Indeed, after checking the JDK used for the built-in Java, it had switched to 1.5 instead of 1.4.2. I changed it back and all is working again.

So, you are saying then that the axis context problem is on the Sun side and not Stylus Studio IDE? I will look on the sun forum.

Thank you again,

Michel
Postnext
(Deleted User) Subject: Java Built-in processor no longer working since upgrade to Enterprise 2008 R2
Author: (Deleted User)
Date: 26 May 2008 12:29 PM
Hi Michel,
when Stylus Studio runs an XSLT processor different from the "Built-in" (i.e. the Java built-in, Saxon, MSXML) it simply installs hooks to intercept the generation of the output in order to provide debugging and backmapping. So, a difference in the serialization format could be a bug of ours, but a change like having a different node as the context of a xsl:for-each is too deep in the engine to be caused by Stylus Studio, and almost certainly is a bug in the engine itself.

BTW, which 1.5 version were you running? Was it the latest Update 15?

Alberto
Posttop
Michel DuronSubject: Java Built-in processor no longer working since upgrade to Enterprise 2008 R2
Author: Michel Duron
Date: 26 May 2008 02:36 PM
Thank you Alberto for the clarification.

For 1.5, it picked up 1.5.0_03.

I checked with update 15 of 1.5 (the current one) has the same problem plus additional ones elsewhere.

And 1.6.0_03 and 1.6.0_06 also do not work, with results consistent with 1.5.0_15, i.e. the node context within the for-each look is erroneously one level above where it should be. Go figure...

Right now, our production environment uses 1.4.2 so this is not a problem as of yet.

Anyhow, I was able to resolve the problem finally with 1.6 (probably would work with 1.5 as well) by using the java "Endorsed Standards Override Mechanism" and copying the latest Xalan and Xerces jars (from xml.apache.org) in the "C:\Program Files\Java\jre1.6.0_06\lib\endorsed" folder. After that, everything is good.

Thanks again for the help.

Michel
   
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.