|
From: Darren D. <da...@da...> - 2004-11-05 02:24:55
|
On Friday 05 November 2004 00:53, Daniel Potter wrote: > Will it handle autowired bean factories? not right now, some of the really basic stuff isn't finished yet ;) > I really like the approach=20 > 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. exactly. Some of which may depend on container resources and so on. At th= e=20 moment the tool has no dependencies on anything other than a couple of=20 libs. > I played=20 > with this a bit and wrote a custom BeanFactory or ApplicationContext > (can't remember which) that simply skipped bean creation. I thought I'd > just be able to then query for all the bean definitions and use them to > generate the documentation, including dependency links. Unfortunately, > it turns out that autowired dependencies aren't stored in the collection > of bean definitions (the definitions just reflect what was in the > configuration files). I stopped there and decided to wait for someone > else to figure it out. ;) Perhaps all that is needed is a custom > BeanFactory that maintains these details and updates its bean > definitions to reflect autowired dependencies as it's loaded? > > Thoughts? depends how many are really using autowiring heavily - may look at it in th= e=20 future but there's lots of other stuff to do first. =2D-=20 Darren Davison Public Key: #DD356B0D |