aspose file tools*
The moose likes Beginning Java and the fly likes Cannot be resolved to a type Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Beginning Java
Bookmark "Cannot be resolved to a type" Watch "Cannot be resolved to a type" New topic
Author

Cannot be resolved to a type

Miran Cvenkel
Ranch Hand

Joined: Nov 23, 2010
Posts: 149
I copyed 'everything' to new machine, so all looks good.

When I type at design:


everything gets suggested as expected, so all conneted OK.
Not using Import here, is obviously irelevant.

At run time:
foo.foo1.foo2 cannot be resolved to a type (same thing in same manner on existing peaces of code that used to work OK).


Thanks for tips.


Searchable nature photo gallery: http://agrozoo.net/jsp/Galery.jsp?l2=en
Henry Wong
author
Sheriff

Joined: Sep 28, 2004
Posts: 18990
    
  40

Miran Cvenkel wrote:At run time:
foo.foo1.foo2 cannot be resolved to a type (same thing in same manner on existing peaces of code that used to work OK).


If it compiles okay, but doesn't run okay, I would look to see what the CLASSPATH differences are.

BTW, no idea what you mean by "suggested as expected" and "connected okay".

Henry


Books: Java Threads, 3rd Edition, Jini in a Nutshell, and Java Gems (contributor)
Miran Cvenkel
Ranch Hand

Joined: Nov 23, 2010
Posts: 149
Thanks.

Ahh cr.., I gave up on net beans 7.0.1 & bundled apache tomcat 7.0 (where they invented new roles, from which I manged to implement only manager-script, all the rest did not work whatewer I did), and reverted to previous verions of NB and AT.

The net has a lot of statements that NB & AT 7.0 does not work ok together.

All OK now.
 
 
subject: Cannot be resolved to a type