From: Ian Pushee [mailto:[EMAIL PROTECTED]
Subject: Initial Setup: The type java.lang.Object cannot be resolved.
I am running a debian install of tomcat5.5, using
java-gcj-compat-dev (a free jdk replacement).
Which is why you're having problems. Get rid of both of the above, and
use
Ian Pushee wrote:
Any help or suggestions would be greatly appreciated.
Use a proper JVM?
Sounds like yours is knackered.
There's another free JDK from a company called Bun, or something.
Sounds like that anyway.
;o)
p
Thanks,
-Ian
the following error:
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
The type java.lang.Object cannot be resolved. It is indirectly referenced from
required .class files
org.apache.jasper.compiler.DefaultErrorHandler.javacError
From: Ian Pushee [mailto:[EMAIL PROTECTED]
I am running a debian install of tomcat5.5, using
java-gcj-compat-dev (a free jdk replacement).
Oh, dear. Get a real JDK (the Sun one is fine), and a real Tomcat from
http://tomcat.apache.org (the tarball is fine). GNU java is a nice toy, but we
Hi,
Do you really need sudo here? Perhaps that's creating some issues.
doesn't seem so. I get exactly the same error in my home directory.
What happens if you try to compile a simple Hello World program,
without anything specified for -cp? (Try it with and without sudo to
see if that makes
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: Re: java.lang.Object cannot be resolved
No, simple javac Hello.java doesn't work. Only if I set $CLASSPATH
to /usr/lib/jdk/jre/lib/rt.jar or with the -cp-option.
Then your JDK installation is broken. Where is javac being executed
Hi,
On Feb 13, 2006, at 5:56 PM, Caldarale, Charles R wrote:
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: Re: java.lang.Object cannot be resolved
No, simple javac Hello.java doesn't work. Only if I set $CLASSPATH
to /usr/lib/jdk/jre/lib/rt.jar or with the -cp-option.
Then your
linux distributions insist on installing bearly
usable java versions ?
On 13/02/06, Sebastian Funk [EMAIL PROTECTED] wrote:
Hi,
On Feb 13, 2006, at 5:56 PM, Caldarale, Charles R wrote:
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: Re: java.lang.Object cannot be resolved
] wrote:
Hi,
On Feb 13, 2006, at 5:56 PM, Caldarale, Charles R wrote:
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: Re: java.lang.Object cannot be resolved
No, simple javac Hello.java doesn't work. Only if I set $CLASSPATH
to /usr/lib/jdk/jre/lib/rt.jar or with the -cp
]
To: Tomcat Users List users@tomcat.apache.org
Sent: Sunday, February 12, 2006 6:04 AM
Subject: Re: java.lang.Object cannot be resolved
Hi Martin,
I reinstalled JDK as well as JRE and both didn't change neither
$CLASSPATH nor $JAVA_HOME.
I set $JAVA_HOME to /usr/lib/jdk, it's a link to /usr/lib
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: Re: java.lang.Object cannot be resolved
I set $JAVA_HOME to /usr/lib/jdk, it's a link to /usr/lib/jdk1.5.0_05.
JAVA_HOME has no effect on compilations; the Tomcat startup scripts use
it to find the installed JRE/JDK, but the standard
java.lang.Object cannot be resolved. It is indirectly
referenced from required .class files
the same source code worked fine for weeks. I don't use any IDE's
like Eclipse.
Greetings,
Sebastian Funk
-
To unsubscribe, e-mail
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: java.lang.Object cannot be resolved
import java.lang.Object;
The type java.lang.Object cannot be resolved. It is indirectly
referenced from required .class files
Don't know why you're suddenly getting
On Feb 11, 2006, at 6:30 PM, Caldarale, Charles R wrote:
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: java.lang.Object cannot be resolved
import java.lang.Object;
The type java.lang.Object cannot be resolved. It is indirectly
referenced from required .class
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: Re: java.lang.Object cannot be resolved
The type java.lang.Object cannot be resolved. It is indirectly
referenced from required .class files
This would imply that javac (or whatever compiler is being used) cannot
find rt.jar
On 2/11/06, Sebastian Funk [EMAIL PROTECTED] wrote:
On Feb 11, 2006, at 6:30 PM, Caldarale, Charles R wrote:
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: java.lang.Object cannot be resolved
import java.lang.Object;
The type java.lang.Object cannot
be resolved
import java.lang.Object;
The type java.lang.Object cannot be resolved. It is indirectly
referenced from required .class files
Don't know why you're suddenly getting this message, but there's no
reason to import java.lang.Object (or anything else from java.lang
Lets start with the easy stuff is
$JAVA_HOME\lib\rt.jar on your $CLASSPATH ???
Martin-
- Original Message -
From: David Smith [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 11, 2006 1:56 PM
Subject: Re: java.lang.Object cannot be resolved
-
- Original Message - From: David Smith [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 11, 2006 1:56 PM
Subject: Re: java.lang.Object cannot be resolved
Looks like the kind of weirdness that makes me think the JVM has
become unstable. Have you
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Subject: Re: java.lang.Object cannot be resolved
Lets start with the easy stuff is
$JAVA_HOME\lib\rt.jar on your $CLASSPATH ???
The rt.jar should NOT be on CLASSPATH. CLASSPATH refers to the location
of application classes, not ones provided
From: Sebastian Funk [mailto:[EMAIL PROTECTED]
Subject: Re: java.lang.Object cannot be resolved
I never set $CLASSPATH, but when I call rt.jar via javac -cp .../
rt.jar Servlet.java, it works fine. Should I set $CLASSPATH or is
that enough?
No, you don't want to put rt.jar on the -cp
Sent: Saturday, February 11, 2006 4:05 PM
Subject: Re: java.lang.Object cannot be resolved
Hi,
I never set $CLASSPATH, but when I call rt.jar via javac -cp .../ rt.jar
Servlet.java, it works fine. Should I set $CLASSPATH or is that enough?
On Feb 11, 2006, at 9:49 PM, Martin Gainty wrote:
Lets
22 matches
Mail list logo
