Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Cannot be resolved to a type

 
Miran Cvenkel
Ranch Hand
Posts: 196
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.

 
Henry Wong
author
Marshal
Pie
Posts: 20892
75
C++ Chrome Eclipse IDE Firefox Browser Java jQuery Linux VI Editor Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Miran Cvenkel
Ranch Hand
Posts: 196
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic