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)
-> + element type must not contain ... (3)
-> + XML to .txt file (7)
-> + Modifying a XSL-FO report (5)
-> + Retrievning multiple values...... (2)
-> + does Stylus Enterprise work wi... (2)
-> + MSSQL to 837P conversion (4)
-> + Generating XML files accesing ... (6)
-> + How to bold text using XSL (6)
-> + Different heading based on pag... (3)
-> + Code folding (2)
-> + Bad param=value pair on comman... (2)
-> + Saving an XML file (2)
-> + stylus adding random non print... (2)
-> + Displaying Base64Binary as Ima... (6)
-> - probleme de representation d'i... (1)
-> + SS 2008 error message not disp... (8)
-> + XQuery external variable conve... (4)
-> + encodings available (3)
-> + stand-alone application file n... (4)
-> + Windows Installer Dialog Box a... (4)
-> + Block search and replace (2)
-> + Problem with validation (3)
-> + ISA12 vs GS08 (5)
-> + Web Service Call failure... an... (11)
-> + Quotes in xpath query (3)
-> - Java Built-in processor no lon... (6)
-> ->Java Built-in processor n...
-> ->Java Built-in processor n...
-> ->Java Built-in processor n...
-> ->Java Built-in processor n...
-> ->Java Built-in processor n...
-> + Dynamic input and output names (8)
-> + Java built-in parser (3)
-> + Contains an invalid path (2)
-> + Wizard XML Schema to XML (2)
-> + XML to EDI (14)
-> + Computer with original install... (2)
-> + using Custom Tool - passing ar... (3)
-> + Non-printable special characte... (3)
-> + Transfer Options (Settings, Pr... (2)
-> + Enterprise Edition, Rel. 3, Bu... (9)
-> + Need help with xsl file and xm... (2)
-> + Upgrading and retaining settin... (4)
-> + saxon9.dll etc. missing (2)
-> - Error on using XQuery File in ... (1)
-> - Strange Dialog Box (1)
-> + Studio Crashes in schema edito... (3)
-> + Xml to XMl Conversion (2)
-> + Unable to create a complex typ... (2)
-> + Error message wen trying run j... (2)
-> - XSLT Mapper question... (1)
-> + Dcument Wizard XSLT Editor Tab... (2)
-> + Beginner Question - XPath with... (2)
-> + Trying to generate .net code w... (2)
-> + duplicate values in variable w... (5)
-> + Java Runtime Environment libra... (4)
-> + programmatically generate XML ... (4)
-> + Help Loading Oracle BI Publish... (4)
-> + [French] xsl <=> report (3)
-> + XML Diff (3)
-> + StylusStudio 2008, saxon saxon... (6)
-> + Msql Table err:FODC0004 Table ... (2)
-> + The evaluation period for Data... (2)
-> + Mysql to XML (2)
-> + Is there a Collapse All nodes ... (2)
-> + flat file conversion with CDAT... (4)
-> + Struzzo.exe eats up %40 CPU ba... (2)
-> + schematron support? (11)
-> + XML Generator did not generate... (2)
-> + Nesting XML files (2)
-> + Web Service Call fails - targe... (5)
-> + getting not valid for content ... (2)
-> - element modem was referenced i... (1)
-> + xerces-c++ xml parser (2)
-> + movie.dtd (2)
-> + HELP! Stylus Studio 2008 Enter... (3)
-> + Xalan problem with xsl:attribu... (2)
-> + Breakpoints being ignored (12)
-> + Need a new key for Stylus Stud... (2)
-> + Global parameters are not reco... (4)
-> + mySQL DB Connection 2 (10)
-> + Using Data Direct xQuery to ag... (4)
-> + stylusXslt command line -- XSL... (15)
-> + XSLT processor using EXSLT fun... (2)
-> + Integrating Omni Mark (2)
-> + EDI Standards to gXML (2)
-> + flat file conversion (3)
-> + EDI to XML: Invalid URI error (3)
-> + Validating and XML Schema (6)
-> + XSD to DDL (MS-SQL/2005) (6)
-> + xml converter cant encode 0x19 (4)
-> + XSD Help Needed (2)
-> + How do you delete a field in a... (2)
-> + Disable page breaks (3)
-> + XSD semantic structure compari... (3)
-> + Studio Crashes On File Open (7)
-> + Which parser is used by Stylus... (2)
-> + How to DIFF XML windows with d... (3)
-> + Automation using Visual Studio (7)
-> + CSV to XML conversion help (2)
-> + XML tree help (3)
-> + java.lang.NullPointerException... (2)
-> + Creating schema from xml - how... (3)
-> + Mismatch between intellisense ... (4)
-> + Using FOP 0.94 in XML Pipeline (2)
-- Previous [1081-1100] [1101-1120] [1121-1140] 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.