Use of 1.6.0-alpha.6 in WildFly

[oliviercailloux]

The doc in README indicates that in an OSGi environment, the Factory create method accepting a class loader has to be used. But it is deprecated in 1.6.0-alpha.6.

Also, the README gives instructions about adding asciidoctor as a module to WildFly, but does not explain why this is useful (or necessary?).

Indeed I managed to make it load by adding it as a module and using Asciidoctor.Factory.create(Arrays.asList("META-INF/jruby.home/lib/ruby"), "gems/asciidoctor-1.5.6.1/lib"). (I tried to find the right paths to use by looking in the jruby-complete-9.1.12.0.jar and asciidoctorj-1.6.0-alpha.6.jar. But I don’t really understand what I’m doing…)

I would much prefer to get rid of the Wildfly module as it makes deployment more complex. Is this module really necessary? (Indeed I could not create an asciidoc instance before following the instructions about the module, but it is highly likely that I overlooked something.) I use other libraries with no problem and no need to include them as modules: the libraries are included in the war.

If it is necessary to do so in Wildfly, can someone tell me briefly why or point to some relevant documentation? It makes me wonder whether the application will work on other Java EE servers. (I tried Glassfish, it works with no special configuration and a simple Factory.create(), but I don’t know about other servers, and besides, I would like to ensure that my application is correct considering the specs, not just see that it works by trial and error.)

I am willing to propose a patch to improve the README once I understand the whole process…

[robertpanzer]

This is due to Wildly implementing an own ClassLoader that enforces many properties. One thing for example is that Crypto providers can only be loaded from a Module, not from a Deployment. (And I think JRuby even fails on this one iirc, because it tries to register an own crypto provider but I might be wrong) For details please check the documentation of Wildfly for details.

It's hard to speak for other application servers, because they all do sth with class loading, but servers like TomEE or WAS shouldn't have these problems.

[oliviercailloux]

The latest WildFly developer guide has a chapter about modules. But it doesn’t say anything related to our point, AFAICS. On the contrary, it indicates that if a resource is not found as a system dependency or in a module, it will be loaded from the local resources. The administrator guide is not helpful either. And searching for “wildfly modules cryptographic providers” or similar queries does not seem to yield recent related doc.

More specifically, my questions are:

• do I need to, and if so, why, set up asciidoctor as a WildFly module (and depend on it), rather than simply including it as a library in my WAR as with other dependencies of mine?
• do I need to, and if so, why, include jruby-complete as one of the dependencies in the module, whereas jruby-complete is not required when using asciidoctorj in Glassfish or in Java SE?
• how can I create an asciidoctor instance programmatically without using APIs marked deprecated in 1.6.0-alpha?

If anyone can provide hints or pointers, I’d be most interested.