Jeff, > Is KeelContextualizable in 1.0? The NSC is working > off of 1.0, so if at all possible, I need to make it > backward compatible. >
I don't believe it is. This stemmed primarily from one issue, which was that Fortress-1.0 (used after Keel-1.0), went to the use of proxies. When proxying components, Fortress deliberately takes out access to life-cycle interfaces/methods. Therefore, you can no longer check for (instanceof) or cast to Contextualizable in Keel-2.0. An additional thing we did was to make the KeelConext writable. Avalon contexts are nestable, and we use that to store the container context in the Keel context. I guess to be compatible with both Keel 1.0 you can simply call getContext() like Santanu suggested. In 2.0, to maintain backwards compatibility, we return getKeelContext() from within getContext(). I think this should work. Shash http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
