You can find jboss client jar of Jboss-6-1.0.Final from directory: jboss-6.1.0.Final\client You should add jbossall-client.jar in your client application classpath, in its MANIFEST.MF points to all required jars, you need to place following jars together: jbossall-client.jar jboss-annotations-api_1.1_spec.jar jboss-aop-client.jar jboss-appclient.jar jboss-aspect-jdk50-client.jar jboss-classpool.jar jboss-classpool-jbosscl.jar jboss-classpool-scoped.jar jboss-client.jar jboss-common-core.jar jboss-connector-api_1.5_spec.jar jboss-deployers-client.jar jboss-deployers-client-spi.jar jboss-deployers-core.jar jboss-deployers-core-spi.jar jboss-deployers-vfs.jar jboss-deployers-vfs-spi.jar jboss-deployment.jar jboss-ejb3-async-impl.jar jboss-ejb3-async-spi.jar… Read More


Working with Weblogic 8.1, it’s fine just to put jar of weblogic-8.1.jar into your classpath, your client application will find weblogic server easily but with Weblogic 9+ (in my case, Weblogic 10.3), it’s not the case if you don’t know. You may get similar errors as: java.lang.NoClassDefFoundError: weblogic/utils/NestedException or java.lang.NoClassDefFoundError: weblogic/descriptor/DescriptorBean or java.lang.NoClassDefFoundError: weblogic/utils/classloaders/GenericClassLoader So… Read More