logger cannot resolve

Thread view:

abhirai - 15 Feb 2006 06:39 GMT

hi..here is my problem ..
i just toggle between the classes of my project by pressing F3 and
when i come today i got these errors at every page which i go through
...

Logger cannot be resolved or is not a field
ActionError cannot be resolved or is not a type
ActionForm cannot be resolved or is not a valid superclass
ActionMapping cannot be resolved (or is not a valid type) for the
parameter mapping of the method Reset...

please help me ..i am very new in this field...

Reply to this Message

Rhino - 15 Feb 2006 14:14 GMT

> hi..here is my problem ..
> i just toggle between the classes of my project by pressing F3 and
[quoted text clipped - 8 lines]
>
> please help me ..i am very new in this field...

Those messages appear to be coming from your compiler; compiler messages
represent problems in your source code. It sounds like you are using an IDE
of some kind to write your code and it is doing the compiling for you; that
is common in IDEs today.

It's very hard to help you without more information. If you post some source
code - please, DON'T post a _large_ program - with the messages that you are
getting for that source code and tell us which IDE (name and version) you
are using, perhaps someone can help you.

I suspect that you simply have to do some imports to make the standard Java
classes visible to your compiler but that is just a guess. Without knowing
what IDE you are using, no one can tell you how to do an import in your IDE.

--
Rhino

Reply to this Message

Roedy Green - 15 Feb 2006 14:29 GMT

On Wed, 15 Feb 2006 09:14:18 -0500, "Rhino"
<no.offline.contact.please@nospam.com> wrote, quoted or indirectly
quoted someone who said :

>> Logger cannot be resolved or is not a field
>> ActionError cannot be resolved or is not a type
>> ActionForm cannot be resolved or is not a valid superclass
>> ActionMapping cannot be resolved (or is not a valid type) for the
>> parameter mapping of the method Reset..

export the code and compile with Jikes or Javac. You might get better
quality error messages .Eclipse's are hopeless.

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.

Reply to this Message

Rhino - 16 Feb 2006 14:22 GMT

> On Wed, 15 Feb 2006 09:14:18 -0500, "Rhino"
> <no.offline.contact.please@nospam.com> wrote, quoted or indirectly
[quoted text clipped - 8 lines]
> export the code and compile with Jikes or Javac. You might get better
> quality error messages .Eclipse's are hopeless.

He didn't say he is using Eclipse; he doesn't mention the name of an IDE at
all. I just inferred that he is using one because he talks about compiling
by pressing F3; if he were using the command line, he wouldn't compile by
pressing F3.

As for Eclipse's compile messages, I'm not sure why you are so negative
about them. I've been using Eclipse happily for a few years now and find
their messages quite good. Once in a while you get a slightly cryptic one
but no compiler is perfect. I used Jikes briefly a long time ago and have
also used javac but I didn't find either of them dramatically better than
Eclipse. Just my two cents worth, of course, other people's mileage may
vary....

--
Rhino

Reply to this Message

Oliver Wong - 16 Feb 2006 16:06 GMT

> if he were using the command line, he wouldn't compile by pressing F3.

You'd be surprise by some of the expectations people may have about a
computer's desired behaviour.

- Oliver

Reply to this Message

Roedy Green - 17 Feb 2006 05:02 GMT

On Thu, 16 Feb 2006 09:22:16 -0500, "Rhino"
<no.offline.contact.please@nospam.com> wrote, quoted or indirectly
quoted someone who said :

>As for Eclipse's compile messages, I'm not sure why you are so negative
>about them. I've been using Eclipse happily for a few years now and find
>their messages quite good.

put in this way. Jikes has the best, then Javac with Eclipse next.
Almost never to I understand the Eclipse error message, BUT I do
understand where it is pointing and that the error just appeared, so
it must have something to do with recent keystrokes.

Eclipse goes insane if you unbalance () or {} with an avalanche of
meaningless and distracting error messages. Further it refuses to
reformat to help find the error until you have corrected it.

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.

Reply to this Message

logger cannot resolve

Free Magazines