is there any white space in deploy directory somehow involved (just to make
sure) ?

@mkristian no. I had noticed the other similar tickets involving white space and double checked my path before opening this ticket. The entire deployment path is /opt/installs/jboss/jboss-as-7.1.1.Final/standalone/testapp.war

I was able to deploy by adding to openssl & bouncy castle to the Gemfile:

gem 'jruby-openssl'
gem 'bouncy-castle-java'

I was under the impression that this was not required for the newest versions of jRuby and Rails 4.x - but that is what fixed it.

well, let's call it a workaround but jruby-1.7.x has both those gems as default gems so the problem is somewhere else. for me this is related to #1119 and it looks like jars from gems can load their vendored jar files but jruby itself can not load those jars - which are jars inside jars. so let's keep it open.

@mkristian, so some change between 1.7.9 and 1.7.10 removed the bouncy-castle-java gem from the default gems. I see the bouncy-castle-java.gemspec in lib/ruby/gems/shared/specifications/default but there is no gem in the ib/ruby/gems/shared/gems directory so now warbler explodes with the following:

https://gist.github.com/atambo/8527800

@mkristian, @jkutner: It looks like with jruby 1.7.10 warbler will fail to include bouncy-castle-java in the war file because bouncy-castle-java is no longer included as a default gem and is instead just a file in the stdlib directory:

https://github.com/jruby/warbler/blob/3c52f33948bb150b8b166639b200e78791fcbc97/lib/warbler/jar.rb#L133

that is kind of desired. there are currently 8 default gems in jruby-1.7.10
as you could see
lib/ruby/gems/shared/specifications/default
but the actual gem is part of jruby itself, i.e. you find it under
lib/ruby/shared/ along some other default gems.

I agree that a war file build with warbler highly depends on the jruby
version you use when building the war. but on the other hand I guess
bundler should add or not add the gem depending on the given set of default
gems.

any ways not including the gem in the war file should be not a problem -
the problem is still that the webapp-classloader/jruby-classloader needs to
be able to load those embedded jars from jruby itself.

what happens if you $ bundle update with jruby-1.7.10 ? why does bundler
anyways take care of bouncy-castle-java - is it part of your Gemfile ?

Ya we had jruby-openssl in our gemfile and bouncy-castle-java was a dependency of jruby-openssl. We are able to workaround this issue by removing jruby-openssl from the gemfile and then moving the krypt, jopenssl, and bouncycastle jars into the WEB-INF/lib directory of our war file. So I agree all these problems would go away if we could get the embedded jars to load in websphere.

Update for jRuby 1.7.11 - my previous workaround of adding:

gem 'jruby-openssl'
gem 'bouncy-castle-java'

no longer works. Warbler complains:

warning: skipping bouncy-castle-java (/path/to/jruby-1.7.11/lib/ruby/gems/shared/gems/bouncy-castle-java-1.5.0147 does not exist)

and of course since warbler doesn't find it, jBoss complains:

--- Backtrace
Bundler::GemNotFound: Could not find bouncy-castle-java-1.5.0147 in any of the sources
   materialize at /opt/installs/jboss/jboss-as-7.1.1.Final/standalone/tmp/vfs/temp3c38813284f63234/pricing_management.war-501a0871d7ebdf1c/WEB-INF/gems/gems/bundler-1.5.3/lib/bundler/spec_set.rb:92

I just merge a patch from @mkristian that may fix this:
jruby/warbler#241

@lightswitch05
try to add WEB-INF/init.rb to your war file with
require 'bcpkix-jdk15on-1.47.jar'
require 'bcprov-jdk15on-1.47.jar'

and let me know if that helps. I needed to add this for most servlet containers when I worked on https://github.com/mkristian/war-pack. will be not needed for the next jruby 1.7.12.

is this still an issue with JRuby >= 1.7.16 (+ jruby-openssl 0.9.6) or can we close this one ?