Thanks. I guess I was just surprised and didn't find any documentation to explain what was going on. I tried finding the code that created the proxy and put it into the ServiceManager. What interface does the Proxy implement? Could you give me a pointer to some docs or classes to look at? Thanks!
David
Marcus Crafter wrote:
Hi David, IIRC ECM returns proxies to components, rather than the actual component instances themselves. This lets it do things like automatically handle deprecated or missing methods (like the Serviceable/Composable situation).Is there actually a problem that you're noticing, or were you just surprised to notice this ? :) The proxy should wrap the instantiated component and its invocation handler should orward all calls to the original instance implicitly. Is this happening? Cheers, Marcus On Fri, Aug 01, 2003 at 12:10:17PM -0400, David Kavanagh wrote:I tried the dev list already... any ideas? I'm getting my GenericTaskManager stuff running under 2.1rc1 and ran across a snag. I thought 2.1 was switching over to the whole Serviceable interface. So, I make this action I wrote implement Serviceable and ask the ServiceManager for a component that is defined in the cocoon.xconf file (the GenericTaskManager) and I get some class back called "$Proxy2"! So, that is an inner class with no package! I look around the code and it looks like the ExcaliburComponentManger is still being used which deals just with Components. Should I even try asking the ServiceManager for components defined in the cocoon.xconf file? David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
