Thanks. Alexandre also replied on the ticket so I'll revert and see if I can find a better solution.
Thanks guys -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Dec 8, 2020 at 11:21 AM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Yes - there's a bug with parsing Japanese characters with Xalan. It also > looks like its not maintained any more. > > I was under the impression that the Transformer functionality was part of > the JDK, so I'm curious as to what is missing. I'll have a look at that > failing test. Looks like we're missing org.apache.xpath - looks like this > is a little messy. > > Jon > > On Tue, Dec 8, 2020 at 9:58 AM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> > wrote: > > > Hi, > > > > Been looking at the JSTL failures > > > > > http://ec2-54-173-218-40.compute-1.amazonaws.com:17171/tests?path=com.sun.ts.tests.jstl&build=1607347669779&status=FAILED > > > > I realized that Xalan is missing from our distribution. > > Looks like it's been removed about a year ago. > > > > > > > https://github.com/apache/tomee/commit/5f1b57af1b4f11638c8c9540fcc83feb618980a4 > > > > Does anyone have any clue on why? > > Obviously we won't pass the transform TCK without an XSLT Processor like > > Xalan. Adding it back solved most of the issues. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > >
