On 6/11/07, Anthony Israel-Davis <[EMAIL PROTECTED]> wrote:
I had turned global autowiring off because I just read on the Mach-II group that there can be a substantial performance hit, so I'll just do it on a case by case basis.
Not sure what the deal is here, since the autowiring only happens one time (at app startup)? What is the "performance hit" being discussed here? It still seems like one should be able to define a base class and
inherit from it with properties intact, but there may be something I'm just not "getting" about the Coldspring paradigm.
You can define a base class and inherit from it. Public getters and setters for properties in a base class are autowired when you create a subclass (assuming you pass the subclass the appropriate properties in the XML). This seems to be the part that is confusing people. If you set this up correctly it absolutely does work. For now, I think autowiring will work in those cases where I'm using
inheritance and I'll explicitly define my mock objects in my unit test xml. Thanks for the link. It validated my confusion and pointed me in the direction of a workaround.
I commented again on Doug's blog to explain his error more completely. Hope this helps, Brian
