On Oct 8, 2004, at 8:50 AM, Marcus Crafter wrote:
In Avalon though, the container runs the constructor and lifecycle of
the component, so opening the call hierarchy of any lifecycle method
always points you to the container utils code, and the call hierarchy
of
the constructor always points to no-where (cos' its all done via
reflection).
Essentially I'd like to be able to say - show me all the places where
this component has been "looked up" in client code so you can see where
it's been used - I guess in reality its just an enhanced (or limited,
depending on perspective :) ) search.
Will a 'Find Usages' on the interface not work? Thats what I do in IDEA.
-pete
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache Excalibur Project -- URL: http://excalibur.apache.org/
