Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It works with ear file we build with Maven. Using Gradle, I have an EAR (MyEnterpriseApp) file with a WAR (Myweb) and set of jar files in the root folder. When we deploy it is fine no problem. When the applicatin starts it throws a compound class loader for a class (com.test.mypackage.MyClass) that is available in the one of the jars. We are using Websphere 6.1 on windows.
Any suggestions.
I figured it out my self, using deploy and earlib together will cause this problem.
Now I am using only deploy with runtime dependencies in war gradle file. For now it solved the problem. If any of you have better idea than this, always welcome.