Hello Tomáš,

First:
      The behavior is fixed in build #615. Problem methods would
      remove from the tree as the problem is fixed and refresh action
      taken. Note it wouldn't appear again if problem reintroduced
      until inspection is re-run.

Second:
        Yes, code inspection supports EJB. The behavior is as follows:
        ejb classes are automatically added as entry points. EJB
        interface methods are automatically added only if
        corresponding checkbox is marked in code
        inspection/Unreachable code options panel that appears upon
        inspection startup. If you see your EJB class reported as
        unused that might be a IDEA bug. What icon appears for your
        class in inspection tree view? If it is usual class icon (C
        under round blue background) you most probably haven't
        configured your project properties or ejb descriptor. In other
        case you see special ejb class icon we might need a project
        configuration and ejb descriptor in order to reproduce the
        problem on site.

Third:
      The actual behavior is exactly you're asking for! Inspect Code
      action is avaliable for project/directory/file under all IDEA's
      navigation tools (Project, Commander, EJB view).

-- 
Best regards,
Maxim Shafirov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"

TL> Yes, it is much better now. 

TL> But I also found a few buggies there:
TL> *****************************************************
TL> First:
TL>         I did code inspection
TL>         It found a "Type cast is redundant" problem in one class
TL>         I modified the source code to remove it
TL>         The inspector showed:
TL>                 "Warning Source file(s) has been changed. Press refresh to
TL> synchronize inspection results"
TL>         but when I press refresh, nothing happens
TL> *****************************************************
TL> Second:
TL>         Does the code inspection understand EJB's?
TL>         If the answer is Yes, than there is a problem:
TL>         In "Unreachable code" it shows, that my Bean is never instantiated,
TL> although it is an EJB in which case it is understandable that no calls on
TL> constructors are  done....
TL> *****************************************************
TL> Third:
TL>         When I launch the code inspection, it always takes only the current
TL> class (the one in the focused editor). To code inspect more files, I have to
TL> close all editors and then the code inspect inspects the whole project....
TL>         I would like it better, if it took the focused object (even the one
TL> selected in project view - e.g. package, class, set of classes)
TL> *****************************************************


TL> Tomas Langer



TL> _______________________________________________
TL> Eap-list mailing list
TL> [EMAIL PROTECTED]
TL> http://www.intellij.com/mailman/listinfo/eap-list


_______________________________________________
Eap-list mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-list

Reply via email to