|
From: Andy D. <an...@ma...> - 2004-11-05 16:20:11
|
I wonder if one could device a way to separate it enough so that it could be paired with different already-existing BeanFactorys? For example, some people are experimenting with configuration formats other than XML... it would be cool if this tool could work for those alternate formats (such as a database based Spring config or a Groovy based Spring config)... Let the alternate config implementations create their internal representation of the config and then use this internal representation as the basis for all beandocs. I'm not very familiar to the internal workings of the BeanFactory or ApplicationContext, so I'm not sure if this is braindead easy or pipe dream impossible? - Andy On Friday 05 November 2004 06:37 am, Daniel Potter wrote: > 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 |