Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / May 2006

Tip: Looking for answers? Try searching our database.

issue with XSLT 'trax' processor (Ant) ...

Thread view: 
bravegag - 08 May 2006 18:03 GMT
Hi all,

I developed a transformation process that works beautifully
when tested using MS Internet Explorer i.e. adding the
<?xml-stylesheet type="text/xsl" href="../xslt/xmldiffs.xsl"?>
on top of the source XML and opening it using MS Internet
Explorer.

The problem is that testing it under the ultimate actual process
from Ant using the most up to date XSL processor "trax" then
my process does not work.

Does not work means:

1-. The trax processor inserts tons of spacing all over i.e. &nbsp;
    even when my input XML documents are generated in compact
    format.

2-. The differences highlightings are not evidenced even when I made
    sure that it was not ignoring input files e.g. css or additional
    input XML.

Which is the closest Java XSL processor implementation to MS Internet
Explorer? worst case I will just upload my XML to the WebServer instead
of try getting the HTML doing the transformation myself but it is not
a beautiful solution i.e. it would consume client side resources
running from the client MS IE, would execute n times instead of
once in the server.

My AnT target looks like this:

<!-- Generate difference report -->
<target name = "difference_report"
description = "Generate differences report between consolidated master
and consolidated ldap snapshots" >

 <!-- Generate XML of differences as report input -->
 <xml_diff_generator desc="MASTER-vs-LDAP"
      destfile="${report.dir}/${difference.report.xml}"
      ctrlfile="${master.dir}/${master.export.all}"
      testfile="${export.dir}/${ldap.export.all}"
      failonerror = "true" />

 <!-- Generate final HTML diff report of the two XML -->
 <xslt basedir="${xslt.dir}"
     destdir="${report.dir}"
     extension=".html"
     in="${master.dir}/${master.export.all}"
     processor="trax"
     out="${report.dir}/${difference.report.html}"
     style="${xslt.dir}/${difference.report.style}"
     force="true" />
       
 <echo message = "Completed successfully" />
</target>       

TIA,
Me
Joseph Kesselman - 08 May 2006 18:22 GMT
Hard to answer without seeing the stylesheet and a sample document.
Could be a bug in the particular processor being found by TrAX (Sun's
Java ships with a badly outdated version of Apache Xalan); could be a
bug in the Microsoft processor.

Signature

Joe Kesselman / Beware the fury of a patient man. -- John Dryden

bravegag - 09 May 2006 12:41 GMT
Hi Joseph,

Thanks for your interest to help.

I solved the issue by updating the xalan binaries to the
latest version 2.7 I had the 2.5. Now it works ok pretty
much like Internet Explorer except for a couple of extra
line breaks I am still hunting down.

Thanks,

Regards,
Me


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.