September 1, 2013 anandraj.
JNDI lookup for a WebSphere application server resource could be tricky due to lots of client jar being required.
Below are few common exceptions you might run into during JNDI lookup from an external java client.
Caused by: java.
, Our continuously growing database currently holds more than 18.
000 classes from over 147.
900 JAR files.
If you think that an important JAR file is missing in our index, please do not hesitate to suggest it NEW for inclusion.
We will try to take your proposal into consideration.
, I think its not a problem with camel ,You added ws.
runtime jar in your classpath that is creating the issue ,if you want to run junit along with ws.
runtime ,you have to setup your context and JVM based on the ibm jdk ,else you can skip the jar for the unit test case, JNDI lookup for a WebSphere application server resource could be tricky due to lots of client jar being required.
Below are few common exceptions you might run #, FAQ Where is the IBM Developer Answers (formerly developerWorks Answers) forum?
The platform was sunset on 30 April 2020.
Much of the content was migrated to the IBM Support forum.
Links to specific forums will automatically redirect to the IBM Support forum.
, Caused by: java.
logger maven jar logger.
class # jar #maker jar #es#maven# jar #.
, 03/08/2010 #,IBM com.
#WebSphere Application Server 7.
0 ,#!!!, Dismiss Join GitHub today.
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.