Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 299
  • Last Modified:

ClassCastException: oracle.ojc.compiler.AutoBoxingExpression JDeveloper 10.3

I'm getting an odd exception using JDeveloper 10.3 compiling with JDK 1.5.

ClassCastException: oracle.ojc.compiler.AutoBoxingExpression

Anybody run across this before?
I'm mostly an Eclipse guy, so is there something with JDev or the internal OC4J server I'm missing? I haven't started the server.
0
MehtaJasmin
Asked:
MehtaJasmin
  • 5
  • 3
1 Solution
 
krakatoaCommented:
Probably to do with Generics. These days you need to tell the compiler what sort of objects are involved.

Previously : Vector v = new Vector();

with generics:

Vector<String> v = new Vector<String>();

etc.
0
 
CEHJCommented:
0
 
MehtaJasminAuthor Commented:
Sure, that makes sense, but the class that's throwing the exception is in the oracle libraries. Maybe my .jars are out of date.

I'll credit for correct response if that's what it turns out to be. Thanks.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
MehtaJasminAuthor Commented:
Here's the full error message:

java.lang.ClassCastException: oracle.ojc.compiler.AutoBoxingExpression
      at oracle.ojc.compiler.ClassFileWriter.createClassFile(ClassFileWriter.java:1224)
      at oracle.ojc.compiler.RawClassSymbol.generateClass(Symbol.java:7217)
      at oracle.ojc.compiler.Parser.resolveMethodBodies(Parser.java:8397)
      at oracle.ojc.compiler.Parser.parse(Parser.java:7823)
      at oracle.ojc.compiler.Compiler.main_internal(Compiler.java:978)
      at oracle.ojc.compiler.Compiler.main(Compiler.java:745)
      at oracle.jdeveloper.compiler.Ojc.translate(Ojc.java:1486)
      at oracle.jdeveloper.compiler.UnifiedBuildSystem$CompileThread.buildGraph(UnifiedBuildSystem.java:300)
      at oracle.jdeveloper.compiler.UnifiedBuildSystem$CompileThread.buildProjectFiles(UnifiedBuildSystem.java:515)
      at oracle.jdeveloper.compiler.UnifiedBuildSystem$CompileThread.buildProject(UnifiedBuildSystem.java:608)
      at oracle.jdeveloper.compiler.UnifiedBuildSystem$CompileThread.buildAll(UnifiedBuildSystem.java:665)
      at oracle.jdeveloper.compiler.UnifiedBuildSystem$CompileThread.run(UnifiedBuildSystem.java:893)
0
 
CEHJCommented:
Sure, that makes sense, but the class that's throwing the exception is in the oracle libraries.
Yes, but it's important to see it anyway. Unfortunately the authors of the code have not seen fit to show the problematic source (of course i'm assuming the error IS caused by a problem in compiling the source) so it makes it difficult to correct.

What i would do in this case is start updating stuff. You should in any case be using a 1.7 compiler (even if you compile to target 1.5). Also update the JDeveloper version if possible.

If that doesn't cure it, let us know
0
 
MehtaJasminAuthor Commented:
I've requested that this question be deleted for the following reason:

Problem was solved along with my other question by the credited solution on that thread.
0
 
CEHJCommented:
Before you close this, please state the solution here that explains how to get JDeveloper working correctly. It should not be necessary to use a different compiler
0
 
MehtaJasminAuthor Commented:
When I selected "use javac" in the JDeveloper compiler properties, both errors (this and the class format error in my other thread) resolved. The reason for two threads was that the class format error was discovered before db connection was established, so I hadn't tried to run at that point.
0
 
MehtaJasminAuthor Commented:
The answer from another thread also corrected this. It was credited and graded A there.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now