Re: [jruby-dev] Casting to different types in JRuby

2012-10-18 Thread Carl Bourne
Charles, Indeed it seems to be an issue with JRuby 1.7 RC2 and maybe the included BC libraries. If switch back to JRuby 1.6 I get the expected result. org.bouncycastle.pkcs.PKCS10CertificationRequest@206b4e2 Is there an easy way to exclude the included BC libraries? Regards, Carl On 18

Re: [jruby-dev] Casting to different types in JRuby

2012-10-18 Thread Carl Bourne
Thanks Kristian, Unfortunately I will need to use the SSL support! Any other work arounds be greatly appreciated. Regards, Carl On 18 Oct 2012, at 09:52, kristian m.krist...@web.de wrote: when I used jruby-core maven artifact and replaced the bouncy-castle artifact the built in SSL support

Re: [jruby-dev] Casting to different types in JRuby

2012-10-18 Thread kristian
jruby NEEDS the slightly older version of BC and you need jruby's SSL support, so the last possibility for you is to use that very same version of BC as jruby ! I am sure jruby will support other versions of BC in one of its coming releases ;) actually it would be nice to have IMO. - Kristian

Re: [jruby-dev] Casting to different types in JRuby

2012-10-18 Thread Carl Bourne
Thanks Kristian, What's the best way to replace the BC .jar provided with JRuby with the same version as provided by BC? Can I just download and reference the older version in my JRuby script, or do I need to remove the version that comes with JRuby and replace it? Carl On 18 Oct 2012, at

Re: [jruby-dev] Casting to different types in JRuby

2012-10-18 Thread kristian
JRUBY uses org.bouncycastle:bcmail-jdk15on:jar:1.46 org.bouncycastle:bcprov-jdk15on:jar:1.46 for testing you can just prepend them to your bootclassloader - something like jruby -J-Xbootclasspath/p:bcmail-jdk15on.jar:bcprov-jdk15on.jar but doing so with BC version 1.47 did not work for me (the

Re: [jruby-dev] Casting to different types in JRuby

2012-10-18 Thread Carl Bourne
Thanks Kristian All a little messy I guess - Hopefully this incompatibility will be fixed soon. Thanks for your advice! On 18 Oct 2012, at 11:06, kristian m.krist...@web.de wrote: jruby NEEDS the slightly older version of BC and you need jruby's SSL support, so the last possibility for you

[jruby-dev] Namespace conflict

2012-10-18 Thread Carl Bourne
Hi there, I think I've hit another JRuby namespace confict. e.g. kstore = KeyStore.getInstance(JKS) kstore.load(FileInputStream.new(example.jks), password.toCharArray) NameError: no method 'load' for arguments (java.io.FileInputStream) on Java::JavaSecurity::KeyStore I tried using

Re: [jruby-dev] Namespace conflict

2012-10-18 Thread Carl Bourne
Well to sort of answer my own question here, this works in JRuby 1.7 RC2 but not in 1.6.8. kstore.load(FileInputStream.new(example.jks), String.new(password).toCharArray) Problem is the BC libs don't so I'm sort of stuck between a rock and a hard place ;-) On 18 Oct 2012, at 14:35, Carl

Re: [jruby-dev] Casting to different types in JRuby

2012-10-18 Thread Charles Oliver Nutter
On Thu, Oct 18, 2012 at 6:54 AM, kristian m.krist...@web.de wrote: JRUBY uses org.bouncycastle:bcmail-jdk15on:jar:1.46 org.bouncycastle:bcprov-jdk15on:jar:1.46 for testing you can just prepend them to your bootclassloader - something like jruby

Re: [jruby-dev] Namespace conflict

2012-10-18 Thread Charles Oliver Nutter
Yeah sorry for the troubles here. Hopefully for JRuby 1.7.1 we can get our SSL stuff updated to current BC.. On Thu, Oct 18, 2012 at 9:32 AM, Carl Bourne carl.bou...@me.com wrote: Well to sort of answer my own question here, this works in JRuby 1.7 RC2 but not in 1.6.8.