"ramses" wrote : @ 1) | JBoss can load the native library. The SubDeployerSupport.class uses the method System.load with the full qualified filename (e.g: /home/rameder/jboss/server/sx/tmp/native/libopenFTjni.so) of the native library, therefore no java.library.path has to be set. | | I can see this in the loggings (no exception during first deployment). | | When the native method is invoked an | UnsatisfiedLinkError with the method name is thrown. | | I can reproduce this behaviour in a small test example without JBoss. | see http://forum.java.sun.com/thread.jspa?messageID=3366590 | | Therfore my allegation, that the class which invokes the native method, and the native library has to be loaded by the same classloader. | | I have tested with your propsal (start JBoss with java.library.path) also, but with the same result |
I do not write code to implementation details, that just makes for nonportable code across jvms. The spec says any classloader scoping is not used for loading, which makes sense since you can't scope dlls bound in the runtime. In anycase, the fact that the deployer framework loads the library is wrong, so the problem is mute. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871911#3871911 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871911 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
