On Dec 1, 2006, at 4:20 PM, Aaron Mulder wrote:
So what you get back is ordinarily a proxy to the actual service. If
you get the abstract name for the returned module builder (the kernel
has a call to do that) and then get a fresh proxy to it (from the
proxy manager from the kernel), does it include your new interface?
Yes, creating a fresh proxy includes the new interface, but unfortunately that only gets me passed the class cast, as it throws an exception "No implementation method" when calling a method on the interface. :(
If so, it suggests that the proxies generated for the reference
include only the interfaces that match the reference type.
Thats what I assumed, but if I changed the reference type to the new interface, then for some reason getWebConfigBuilder() returns null, so something was still expecting the referenceType for the builders to be ModuleBuilder.class.
If not, it
may be that the class loader that's provided to create the proxy
doesn't include the added interface (though there used to be a warning
emitted every time this happened).
I'm not sure what could be done to
work around that -- maybe either add the interface to other modules as
needed or contrive to use the right module's class loader to create
I'm having some trouble figuring out why I'm getting a ClassCastException
and would appreciate if someone could shed some light...
In TomcatModuleBuilder I implement an "additional" interface ModuleBuilder2
as well as add..
But then in EARConfigBuilder if I call...
I get a ClassCastException casting it to ModuleBuilder2 during the building
of the configs which I don't understand why. If I inspect the interfaces of
getWebConfigBuilder() it only returns ModuleBuilder and
GeronimoManagedGBean. Why isn't ModuleBuilder2 being listed?
I tried updated the referenceType for WebBuilder in EARConfigBuilder from
ModuleBuilder to ModuleBuilder2, but then in that case getWebConfigBuilder
ends up returning null.
What am I missing? Why can't I add an additional interface to the