Berin,
1) Add an attribute to the root config element in the .xconf which identifies the type of config we want such as "proxy-type".
2) proxy-type="none" uses a NoopWrapperObjectFactory (one that does nothing)
There have been many discussions about this in the past for people to find out about the pros/cons of proxies/wrappers. So leaving that discussion alone, I have another different but related question. We (at Keel) have been modifying our code-base to adapt to proxies, the primary interest being able to stay current with Fortress and the next-gen container. The question I have is that if we (or others) start using the "none" option here, what is the impact from the future-proof POV? In other words, what features (using your crystal ball) might we be loosing out on if we do not work well with proxies?
As long as you stick with well behaved contracts, nothing. I.e. as long as you only access your component that is looked up with the work interface and never recast it to another interface/class you will be fine. You will run into problems as soon as you start doing that.
If you need to squeeze every last bit of performance from your application, I suggest developing with proxies enabled and then doing performance testing with them disabled.
-- "You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, The Swiss hold the America's Cup, France is accusing the US of arrogance, and Germany doesn't want to go to war. And the 3 most powerful men in America are named 'Bush', 'Dick', and 'Colon' (sic)".
-----Chris Rock
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
