Karol Bucek

> Saxon may be the best path forward, but using the JDK Xalan may be a short-term way to avoid the super-stale external version. @headius so the only downside is...

:+1: and just to clarify: `Java::JavaLang::IllegalAccessError` means users that would use Nokogiri with JDK Xalan would likely have to edit their JRUBY/JAVA_OPTS to `--add-ones` for the internals to be accessible...

> Are these illegal accesses from using reflection to dig inside Xalan? From what we've bumped into so far it was not reflection - simply using Xalan's classes (from the...

same as Kristian, looks fine - for a Java library the SLF4J warnings are usually fine. for a Ruby gem not sure - might confuse users. adding a noop impl...

and as usual great work Mike! :+1: thanks for caring about JRuby :sparkling_heart:

@jvshahid @flavorjones do you guys happen to know if BOM removal happens at C-Ruby level or libxml? ... there's some support for BOM skips in JRuby so it might be...

for context, AR-JDBC has been quite under utilized - 3.x/4.x support was pretty much a one man show with all adapters (MySQL, SQLite, Postgre, DB2, Oracle, SQLServer, HSQLDB+H2, Derby) ......

> @rdubya and @iaddict happy to chat more if you guys have the time. @kares are you interested in joining? sorry, not really into chatting more ... was interested before,...

might be an edgy case, you could try "forcing" JRuby's class-loader to be the context-loader during boot. `require 'jruby'; JRuby.set_context_class_loader` if works Warbler could/should? maybe set it for you

quite unfortunate but inevitable with platform specific gems, it's a bit of a hack since how do we force you to have the _-java_ (JRuby) version of the gem installed...