I tried to research and look thoroughly on that exception, I thought it was really an exception on my code but, I tried to removed the mvn bundle plugin config on my pom.xml and put my two classes that invokes the function in reading I/O in Amazon S3 and it worked like a charm, so I don't think it's an exception to the could or to the AmazonS3Client initialization, I think it a jar conflict between something and the amazonaws,
And here is one more thing that I tried, With Maven Bundle Plugin commenting out the // AmazonS3Client s3CLient new AmazonS3Client(); and call my function hello(String) inside provider.jar it worked perfect, so my config from my war to my external jar is working without the AmazonS3 But if I removed the Maven Bundle Plugin on my pom.xml and test reading I/O in S3 inside my HelloWorld servlet it is working perfect as well. Do you still think its an application issue? Thanks -- View this message in context: http://karaf.922171.n3.nabble.com/deploying-a-war-with-dependencies-in-bundled-jars-tp4037488p4037762.html Sent from the Karaf - User mailing list archive at Nabble.com.
