Project

Profile

Help

Bug #1966

ClassNotFoundException: net.sf.saxon.lib.StAXHandler

Added by Michael Kay over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
JAXP Java API
Sprint/Milestone:
-
Start date:
2013-12-23
Due date:
% Done:

100%

Spent time:
-
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Found in version:
9.5
Fixed in version:
9.5.1.4

Description

See message on saxon-help list today.

Iniitial investigation:

The reference to a separate JAR file for StAX in the 9.4 change history appears spurious. It seems the strategy was probably changed before release, and the change list was not corrected to match.

What the code is actually trying to do is to dynamically load the code module that references StAXResult, so that no failure occurs if StAXResult is not on the classpath. But it is loading it by the wrong name, specifically net.sf.saxon.lib.StAXHandler rather than net.sf.saxon.lib.StAXResultHandlerImpl.

There's a surprising absence of tests in this area...

History

#1 Updated by Michael Kay over 2 years ago

  • Status changed from New to Resolved

I have committed and tested a patch on the 9.5 and 9.6 branches. (module SerializerFactory).

As a workaround, StaxResult appears to work correctly when using the s9api interface rather than JAXP.

#2 Updated by O'Neil Delpratt over 2 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in version set to 9.5.1.4

Bug fix applied in Saxon maintenance release 9.5.1.4

Also available in: Atom PDF