Member Avatar for manojd

fellow developers...i am new to web development...I am developing a simple web application using Oracle for Weblogic Workshop with Weblogic 10Gr3 server.

However my deployment server is weblogic 7.1. When i deploy and run the app, i get the following error

Parsing of JSP File '/index.jsp' failed
/index.jsp(6): class 'xxx.xxx.xxxx' could not be loaded
probably occurred due to an error in /index.jsp line 6:
<jsp:useBean id="xxxx" scope="session" class="xxx.xxx.xxxx"/>

appreciate quick response...

  • 2 Contributors
  • 3 Replies
  • 326 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by Thirusha

Dani AI

Generated

Short expert note adding practical checks and fixes for the JSP load error reported by and the suggestions from .

The JSP compiler is failing because the bean class referenced by the page cannot be loaded by the server at compile time. Common root causes (besides simple missing files) are: wrong package-to-directory layout, case mismatches on a case-sensitive OS, the class being packaged in the wrong place inside the WAR, or the classfile being compiled for a newer Java than the WebLogic JVM can run. Start by confirming four things in order.

Quick, actionable checks:

  • Verify the class appears in the WAR with the correct package path (for example, com/example/YourBean.class lives under WEB-INF/classes/com/example/). You can inspect the WAR with:

    jar tf yourapp.war | grep WEB-INF/classes

  • Confirm the server JVM version and the classfile version. On the server run java -version. To inspect the classfile major version run from your build or exploded WAR root:

    javap -verbose -classpath WEB-INF/classes fully.qualified.ClassName | grep "major"

    Major version reference (common values): 48 => Java 1.4, 49 => 1.5, 50 => 1.6, 51 => 1.7, 52 => 1.8.

  • Check the bean itself: it should be in a package (not the default package), the package declaration must match the folder structure, and it needs a public no-arg constructor if the JSP creates it with useBean.

Fixes to apply

  • If the classfile major version is newer than the server JVM, recompile targeting the older JDK (or rebuild the WAR using your build tool settings). For javac you can use -source and -target and provide the older rt.jar on -bootclasspath to avoid accidental newer-API usage. Alternatively, build with the same JDK version that the WebLogic 7.1 instance uses or retarget the project to that runtime in your IDE/build tool.

  • If the class is packaged incorrectly, move it to the correct WEB-INF/classes/... path or package it into a JAR under WEB-INF/lib.

Last checks: scan the WebLogic server logs for the full ClassNotFound/NoClassDefFound stack trace to see whether the problem is "not found" or "unsupported major.minor version", and prefer rebuilding the WAR against the target runtime rather than trying to run binaries compiled for a newer Java on an older container.

Recommended Answers

All 3 Replies

Member Avatar for Thirusha

check that your class is in the WEB-INF/classes folder.

Edited by Thirusha because: n/a
Member Avatar for manojd

It is in the folder WEB-INF\classes..
I am doubting that this a problem caused because i am building the app for Weblogic 10GR3 and deploying in weblogic 7...is there somethign i need to take care while deploying to old version?

Member Avatar for Thirusha

I think that is the problem then. what jdk are u using? I think if u use the same version then is should work, but for example if you are using a higher jdk on weblogic 10 it is definitely not going to work in weblogic 7

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.