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.
There were a couple instances where a component was implementing more methods than the interface called for, and we had casts. Now we have yet another interface extending the opriginal interface and life is good.
But, the majority of changes were because of the use of life-cycle interfaces like "Contextualizable" to set contexts. With the Fortress proxies we couldn't do that. We have solved that by simply separating the core Fortress context from the Keel context and having a separate interface for that....voila...no more "instanceof Contextualizable".
I agree this is the best approach, and the one we are following. It's good to have built-in Fortress support for this.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.
Thanks.
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
