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)
-> + Conerting Excel to XML (5)
-> + count the number of 1 appearin... (10)
-> + Import validation errors (2)
-> + Custom Validation Saxon (4)
-> + How Can i Check if else condit... (2)
-> + Stylus Studio 2009 Ent still b... (2)
-> + cannot download SS2009 (2)
-> + Use of import-schema wants sch... (4)
-> + Replacement Install Media/Bits (3)
-> + XML to Flat File (5)
-> + Select one of multiple attribu... (13)
-> + Web Service - SOAP Error (3)
-> + I find a BUG in stylus studio ... (8)
-> + Text to XML conversion issue (2)
-> + Fixed width flat files (3)
-> + Stylus Studio Crashes when val... (3)
-> + XSL Changes doesn't reflect in... (2)
-> + Custom Conversion Definition T... (6)
-> + Support for UK EDI Tradacoms ... (2)
-> + How to find and remove all ins... (2)
-> + XML to cobol Sequential file (2)
-> + Pipe delimited flat file conve... (2)
-> + Cannot Function Block > DataDi... (3)
-> + License Authentication failed (2)
-> + Flat File Conversion (3)
-> + Struzzo.exe sing 50% of CPU (2)
-> + Saxon9 Transformation error ha... (2)
-> + com.ddtek.xquery3.XQQueryExcep... (10)
-> + XML attribute name (2)
-> + JAVA and XML (2)
-> + DB Connection Error (3)
-> + Dicstionaty Librarys for other... (2)
-> + Passing parameters (3)
-> + Xmlconverter does not work (2)
-> + non-printing characters in Fil... (3)
-> + Including row nos while conve... (5)
-> + Getting Evaluation Copy except... (2)
-> + SS 2008 R2 Bug? (4)
-> + Java Heap Space (2)
-> + generate report from .xsl file... (3)
-> + Can't encode 0x4 in text (3)
-> + Recognize Japanese Characters (2)
-> + converting .xsl to xml using c... (2)
-> - Uninstall doesn't clean up reg... (1)
-> + CDISC (5)
-> - creating database from XML sch... (1)
-> + error: side-by-side configurat... (3)
-> - How to convert pdf into rdf fo... (1)
-> + Apache FOP (5)
-> + XPath Query Editor 'Buggy' (3)
-> - Feature request (1)
-> + XML Convertors (2)
-> + XMLConverters version 3.2.0.0 ... (2)
-> + JVM/stylus studio abort on sav... (3)
-> + using oasis catalog in pipelin... (6)
-> + Another whitespace issue with ... (2)
-> + saxon 9.1.0.2 (2)
-> + xslt change namespace (4)
-> - xslt change namespace (1)
-> + HL7 Conversion (3)
-> + mixed content mapping (2)
-> + HL7 to XML to HL7 (5)
-> + newest version of Saxon SA? (3)
-> + ORM / ORU Seqments (7)
-> + XSLT is causing Java.lang OutO... (3)
-> + Create POJOs from EDI (4)
-> - Embedded message (1)
-> + How to create Documentation fo... (2)
-> + xslt transformation (2)
-> - remove BOM (1)
-> + Changing data as it goes into... (5)
-> + How to (graphically) map one X... (2)
-> + Stylus Studio 2008 Release 2 -... (2)
-> + keyboard shortcuts to switch b... (2)
-> + Help with getting Output XML f... (8)
-> + Document created from schema (2)
-> + XSD Validation error (2)
-> + Set the value of an attribute ... (2)
-> + Saving as XML, Source Data Typ... (2)
-> + Own templates in file/new (4)
-> + Does Stylus Studio support the... (2)
-> - How to transform XML file to T... (1)
-> + Extract XML file from a HTML s... (2)
-> + Crashing, high cpu usage, larg... (6)
-> + Creating an xml document based... (2)
-> + Problem with restriction (2)
-> + EDI Invalid date time error (2)
-> + How to Compose a Web Service C... (5)
-> + Java Complie errors with XML C... (2)
-> + Creating xml file from CSV uss... (4)
-> + XML Converters (6)
-> + schema validation (15)
-> - 9/30 Customer Showcase Webinar... (1)
-> + ETL (2)
-> + xsd:sequence question (3)
-> + contains an invalid path (5)
-> - Custom converter to map flat f... (1)
-> + validating a 4.01 transitional... (2)
-> + Cannot Use Stylus Studio On Mu... (5)
-> + Missing DB to XML option (2)
-- Previous [901-920] [921-940] [941-960] 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.