Issue 25595 - XHTML XSLT (master document) filter should work with various XSLT processors
Summary: XHTML XSLT (master document) filter should work with various XSLT processors
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: xml
Classification: Code
Component: external filters (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: svante.schubert
QA Contact: issues@xml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-17 10:55 UTC by svante.schubert
Modified: 2008-01-17 18:18 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description svante.schubert 2004-02-17 10:55:35 UTC 
Currently the XHTML XSLT filter is only able to use the XT processor of James
Clark to transform master documents (e.g. SDK documentation). This happens due
to large node-set arguments between Java and the XSLT Processor during the
work-around of "#102311# - Internal Office links are no valid URI's ". 

As JDK1.5 changes the default parser (from Crimson to Xalan) and the package
structure of the exisiting XSLT processor (adding a 'com.sun' before the
'org.apache...'), it is worth to test this during the JDK's early beta phase and
report internally potential obstacles.
Comment 1 svante.schubert 2004-07-05 17:25:23 UTC 
This concerns only the usage of the XHTML filter with Master Documents.
Postponed due to work on Excel filter.
Comment 2 svante.schubert 2008-01-17 18:18:08 UTC 
Closed as Master Document Functionality was removed..