-
1. Re: Proxy Tasks for Delegation
alrubinger May 13, 2008 2:34 AM (in response to alrubinger)4) Add tests to ProxyFactoryRegistryUnitTestCaseBase that check to ensure that:
* ProxyFactory.start() is called upon ProxyFactoryRegistry.registerProxyFactory()
* ProxyFactory.stop() is called upon ProxyFactoryRegistry.deregisterProxyFactory()
S,
ALR -
2. Re: Proxy Tasks for Delegation
alrubinger May 13, 2008 2:39 AM (in response to alrubinger)5) Set up a code coverage M2 Plugin (Where is this being done already?)
S,
ALR -
3. Re: Proxy Tasks for Delegation
wolfc May 13, 2008 6:48 AM (in response to alrubinger)I've added a name server in beans.xml, so the JNDI test is runnable.
I still don't see the need for any registries. We got enough of those lying around (kernel registry and JNDI itself). Likewise start and stop semantics are then handled by MC. -
4. Re: Proxy Tasks for Delegation
wolfc May 13, 2008 10:02 AM (in response to alrubinger)I've committed test/proxy/session to illustrate the current JNDI problems. Note that the test is not yet complete.
It also outlines the scope of the proxy component. -
5. Re: Proxy Tasks for Delegation
alrubinger May 13, 2008 2:14 PM (in response to alrubinger)"wolfc" wrote:
I still don't see the need for any registries. We got enough of those lying around (kernel registry and JNDI itself). Likewise start and stop semantics are then handled by MC.
Both MC and JNDI are specific to the current JVM; abstracting the Registry allows for resources to be defined by key locally only, and maintained elsewhere. This allows us to provide custom load-balancing by distributing EJB lookups, proxy creation, and invocation among different physical machines or clusters.
The Registry itself is an MC Bean; one objective of this component is to leverage MC wherever possible.
S,
ALR -
6. Re: Proxy Tasks for Delegation
alrubinger May 13, 2008 4:44 PM (in response to alrubinger)"ALRubinger" wrote:
4) Add tests to ProxyFactoryRegistryUnitTestCaseBase that check to ensure that:
* ProxyFactory.start() is called upon ProxyFactoryRegistry.registerProxyFactory()
* ProxyFactory.stop() is called upon ProxyFactoryRegistry.deregisterProxyFactory()
Revision 73366.
S,
ALR -
7. Re: Proxy Tasks for Delegation
alrubinger May 18, 2008 2:37 AM (in response to alrubinger)Some more for my wishlist:
* Unit Tests for org.jboss.ejb3.proxy.lang.SerializableMethod - hashCode and equals.
* Unit Tests for org.jboss.ejb3.proxy.handler.ProxyInvocationHandlerBase - construct a Proxy using this InvocationHandler and call "handleInvocationDirectly", checking for proper handling of equals, hashCode, and toString - these should be handled directly by the InvocationHandler. Anything else should throw NotEligibleForDirectInvocationException.
S,
ALR -
8. Re: Proxy Tasks for Delegation
alrubinger May 26, 2008 2:41 AM (in response to alrubinger)"wolfc" wrote:
I still don't see the need for any registries. We got enough of those lying around (kernel registry and JNDI itself). Likewise start and stop semantics are then handled by MC.
I've removed the notion of the ProxyFactoryRegistry, this is now handled by MC via the EJB3 Registrar Facade.
S,
ALR