Re: [Springframework-developer] beandoc tool

[Daniel P. <po...@ci...>]

How difficult would it be to write a BeanFactory that simply recorded
what it WOULD do to load all of its beans if it were a REAL BeanFactory,
but not actually do it? (tracking autowired dependencies,
advices/interceptors applied, etc).  This 'mock' factory could expose
this information in whatever fashion is most convenient for a tool like
Darren's to produce the desired graphs and documentation.

Daniel

On Fri, Nov 05, 2004 at 10:48:33AM +0000, Rod Johnson wrote:
> 
> >>I really like the approach 
> >>you've taken with this (sort of a combination of SpringViz and
> >>JavaDoc).  A few weeks ago, someone suggested the idea of actually
> >>loading the application context or bean factory and generating the graph
> >>and documentation from that.  It seems like this would be the only way
> >>to support autowired configurations, but obviously poses problems b/c
> >>you don't want to actually instantiate/lookup all the beans.
> 
> This will also allow you to get at AOP advice. You can cast any proxy to 
> Advised and walk the advice chain, unless the config explicitly sets the 
> "opaque" flag to disable that (for example, for security reasons).
> 
> The problem is if you require a JNDI environment etc to load the context.
> 
> I think this tool is important. Thanks, Darren!
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer