Step to reproduce:

- Create a java project
- Create a uml project and associate it to the java project
- Create a class diagram
- Add class to the diagram and name it 'Outer'
- Go to the source code of the class
- Add inner 'Inner' class to the 'Outer' class
  -----------------------------------------------------------
  public class Outer {
    
    class Inner {
        
        double add(double a, double b){
            return a + b;
        }
        
    }
    
  }
  -----------------------------------------------------------

- Go to the body of the 'Inner' class and press <Ctrl+Shift+4>

  'Outer' class is selected under UML model tree instead of
  'Outer|Inner' class.

Evaluation:
The way it works is that DataObject cookie from activated node is retrieved to
determine its associated UML project, and then the tree is searched to locate
the model element based on the selected source node package hirachy and name.
The data object is available regardless of the document open status, user can
select the source node (even package node) from java project tree and locate its
model element. This feature does not and should not go with the granularity at
the editor cursor level, it is consistent with NB 'Select in Project' behavior.
Please re-evaluate and provide your feedbacks, thanks.

Evaluation (Entry 2):
'Select in Model' and 'Select in Project' search for different node types.

'Select in Project' looks for source file node.
and 'Select in Model' should look for class element node.

let's try the following example:
source file test.java with the following java code (without public classes):
-------------------------------
class MyTest {
}

class HisTest {
}
-------------------------------
Result:
'Select in Project' will correctly find test.java source node.
'Select in Model' will find nothing!
May be It should look from which class source declaration it was invoked?
And use Public class only if it was invoked outside any class?

Evaluation (Entry 3):
I probably missed something, but I tried the case, 'Select in Model' does find
something, it selects the outer class element node as stated in original
description. The reason is that we can only detect the data object associated
with the activated node, in this case, editor, the data object is the outer
class source file and search from there. Once user gets to the outer class
element node, it should be easy to expand and find the inner class node.

I'm not sure if we should go extra miles to locate the element at the cursor
point, data object approach works generically, even when editor is not open.
User can select a java node on java project tree and locate its corresponding
model element, but again at outer class level.