sparklemotion/nokogiri

Explore replacements for Xalan-J

Open

#1829 opened on Dec 3, 2018

View on GitHub
 (13 comments) (0 reactions) (0 assignees)Ruby (5,615 stars) (806 forks)batch import
help wantedplatform/jruby

Description

See #1760 for more context.

The JRuby implementation of Nokogiri uses Xalan-J for XSLT support, but this thread reveals that development (and likely support) has stalled on that project.

A potential replacement, noted in the thread linked above, is Saxon. There may be other potential replacements as well.

The outcome intended for this issue is to do some exploration of replacing Xalan-J:

  • is there a replacement that will functionally support what Xalan-J supports today?
  • how difficult will a transition be?

Tagging @jvshahid and @kares for visibility

Contributor guide

Tech stack
java
Domain
tooling
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaXSLTNokogiri internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the viability of replacing Xalan J with Saxon (or other alternatives) for XSLT support in Nokogiri. Review the discussion in issue #1760 and the linked Apache Xalan dev mailing list thread. Assess compatibility of Saxon with current Nokogiri XSLT functionality and estimate effort required for migration. Consider any existing PRs or forks that may have attempted this.