Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » What does this Message Mean?
What does this Message Mean? [message #203969] Wed, 18 May 2005 02:31 Go to next message
Eclipse UserFriend
Originally posted by: rbronson1976.yahoo.com

While debugging I'm getting this message in the Eclipse status bar:

"Current text selection does not resolve to a Java element"

This happens when I have the carrot over a type (like, for example,
java.lang.String) and I press the F3 key to open the declaration. What
should happen is the source code for java.lang.String should open.

This problem only seems to happen when I am debugging with the source
code of Tomcat and even then, it doesn't seem to happen with every
class.

Does anyone know what the message means???
Re: What does this Message Mean? [message #204014 is a reply to message #203969] Wed, 18 May 2005 08:39 Go to previous messageGo to next message
Eclipse UserFriend
> "Current text selection does not resolve to a Java element"
> (..)
> Does anyone know what the message means???

it means that for some reason it thinks that whatever you selected is
not a name of a class/interface/field/method/temp/etc

if that happens for String, that would most likely be a bug. look in
bugzilla and in the log
/adam
Re: What does this Message Mean? [message #204035 is a reply to message #204014] Wed, 18 May 2005 09:45 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: rbronson1976.yahoo.com

"Adam Kiezun" <akiezun@mit.edu> wrote in message
news:d6fd3r$l18$2@news.eclipse.org...
>> "Current text selection does not resolve to a Java element"
>> (..)
>> Does anyone know what the message means???
>
> it means that for some reason it thinks that whatever you selected is
> not a name of a class/interface/field/method/temp/etc



Yes, obviously. You are just re-phrasing what the error message says. I
understand the literal meaning of the words as well as you.

I was hoping someone could describe the underlying reason (rather than,
"for some reason") as to why Eclipse would throw up such a message.
Re: What does this Message Mean? [message #204044 is a reply to message #204035] Wed, 18 May 2005 09:51 Go to previous messageGo to next message
Eclipse UserFriend
Tony LaPaso wrote:
> "Adam Kiezun" <akiezun@mit.edu> wrote in message
> news:d6fd3r$l18$2@news.eclipse.org...
>
>>>"Current text selection does not resolve to a Java element"
>>>(..)
>>>Does anyone know what the message means???
>>
>>it means that for some reason it thinks that whatever you selected is
>>not a name of a class/interface/field/method/temp/etc
>
>
>
>
> Yes, obviously. You are just re-phrasing what the error message says. I
> understand the literal meaning of the words as well as you.
>
> I was hoping someone could describe the underlying reason (rather than,
> "for some reason") as to why Eclipse would throw up such a message.

a bug.
That sounds like a likely explanation. if it were a different type, then
maybe a classpath is bogus, but if it's String, then it very likely a bug.

hth
/adam

ps, [OT]. also, this sounds sort of suspicious "This happens when I have
the carrot over a type ...". Those kinds of things happen when you put a
carrot when it does not belong. LOL
Re: What does this Message Mean? [message #205033 is a reply to message #204044] Fri, 27 May 2005 04:26 Go to previous message
Eclipse UserFriend
I think this may caused by the independent classloader used by Tomcat,
which is always the nightmare for J2EE/Web App developers.:)

Adam Kiezun wrote:
> Tony LaPaso wrote:
>
>> "Adam Kiezun" <akiezun@mit.edu> wrote in message
>> news:d6fd3r$l18$2@news.eclipse.org...
>>
>>>> "Current text selection does not resolve to a Java element"
>>>> (..)
>>>> Does anyone know what the message means???
>>>
>>>
>>> it means that for some reason it thinks that whatever you selected is
>>> not a name of a class/interface/field/method/temp/etc
>>
>>
>>
>>
>>
>> Yes, obviously. You are just re-phrasing what the error message says.
>> I understand the literal meaning of the words as well as you.
>>
>> I was hoping someone could describe the underlying reason (rather
>> than, "for some reason") as to why Eclipse would throw up such a message.
>
>
> a bug.
> That sounds like a likely explanation. if it were a different type, then
> maybe a classpath is bogus, but if it's String, then it very likely a bug.
>
> hth
> /adam
>
> ps, [OT]. also, this sounds sort of suspicious "This happens when I have
> the carrot over a type ...". Those kinds of things happen when you put a
> carrot when it does not belong. LOL
Previous Topic:field and variable completion
Next Topic:On passing the project's classpath to external tools.
Goto Forum:
  


Current Time: Thu May 15 13:22:14 EDT 2025

Powered by FUDForum. Page generated in 0.04379 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top