- This topic has 7 replies, 3 voices, and was last updated 16 years, 6 months ago by
Riyad Kalla.
-
AuthorPosts
-
moloMemberMy simple index.jsp created within a MyEclipse project wont compile when I bring it up after starting Weblogic 9.2 MP3 inside MyEclipse 6.5. It compiles fine if I start weblogic outside of MyEclipse
I get this warning on startup
<Oct 27, 2008 9:43:39 AM EDT> <Warning> <HTTP> <BEA-101296> <Unable to load the default compiler class “com.sun.tools.javac.Main”. Using the default javac compiler to compile JSPs.>Here is the error I get
Oct 27, 2008 9:46:21 AM EDT> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@17d812b – appName: ‘_appsdir_CAS1_dir’, name: ‘CAS1’, context-path: ‘/CAS1’] Root cause of ServletException.
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /index.jsp
index.jsp:1:1: The superclass specified could not be resolved.
<%@ page language=”java” import=”java.util.*” pageEncoding=”ISO-8859-1″%>
^———————————————————————–^
Loyal WaterMemberWere you able to start the server without issue before deploying the application? Can you create a new project and check if you are able to reproduce this issue.
moloMemberI am not having trouble starting the server.
I am also able to deploy the applicationI am having trouble when I try and bring up the jsp page in my browser and the server tries to compile it.
I suspect that somehow the server is using a different library when I startup directly from within my weblogic domain versus when I startup the server from within myeclipse.
I have reproduced this error with a new project.
Loyal WaterMemberWhat JDK version are you using with Weblogic? You should try upgrading the JDK. I hope that solves the issue.
moloMemberI am using JDK150_12, I do not think that is the issue.
The issue is starting weblogic server from within MyEclipse somehow changes the libraries used by the weblogic Server to compile jsp’s when they are first brought up in the browser for the deployerd application.
Riyad KallaMembermolo,
Have you set the connector up to launch *specifically* with the JDK (not JRE) that is installed under the BEA home directory for WebLogic 9.2? The fact that it cannot find the default compiler (which comes from tools.jar, which comes from any JDK install) makes me thing you might have it accidentally launching with MyEclipse’s JRE and not the JDK that BEA ships with WebLogic.
Is that possible? Can you double check that under Window > Prefs > MyEclipse > App Servers > WebLogic > WebLogic 9.x > JDK, and make sure that it’s not just a JDK but the one that is installed under the BEA home dir?
moloMemberThat worked
Thank you so much Riyad
Riyad KallaMemberAwesome, glad to hear it.
-
AuthorPosts