I am building a Maven Project in Eclipse and getting an exception while deploying the application on Weblogic 11G.
Stacktrace:
WSSERVLET13: JAX-WS context listener destroyed
2013-01-02 01:23:08.229 PM <id 14> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> [INFO] com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized : WSSERVLET12: JAX-WS context listener initializing
2013-01-02 01:23:08.233 PM <id 14> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> [SEVERE] com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized : WSSERVLET11: failed to parse runtime descriptor: java.lang.Error: Unresolved compilation problems:
The import test.company.TestClass cannot be resolved
Solution :
The issue is related to Eclipse workspace. If you are building the Maven Project from the within Eclipse. The classpath settings into local workspace might cause this issue. Clean up your workspace by resetting class paths, Java home, Maven path etc.
To check if its a workspace issue try building your Maven project from command prompt and deploy. I was able to successfully deploy my application after building it from command prompt.
Stacktrace:
WSSERVLET13: JAX-WS context listener destroyed
2013-01-02 01:23:08.229 PM <id 14> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> [INFO] com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized : WSSERVLET12: JAX-WS context listener initializing
2013-01-02 01:23:08.233 PM <id 14> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> [SEVERE] com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized : WSSERVLET11: failed to parse runtime descriptor: java.lang.Error: Unresolved compilation problems:
The import test.company.TestClass cannot be resolved
Solution :
The issue is related to Eclipse workspace. If you are building the Maven Project from the within Eclipse. The classpath settings into local workspace might cause this issue. Clean up your workspace by resetting class paths, Java home, Maven path etc.
To check if its a workspace issue try building your Maven project from command prompt and deploy. I was able to successfully deploy my application after building it from command prompt.
No comments:
Post a Comment