One problem showing up in the mdb tests is that since we don't order deployments using
packaging depth (Russian doll thing), tests that include jms destinations in the
deployment are failing because the mdb container is not specifying a dependency on the jms
destination. Since the actual jmx name/kernel name of the component that supplies the
destination is arbitrary, one way to address this would be for the mdb container to
declare a dependency on the supplier of the jndi name for the destination.
Alternatively, and more correctly, we need the jms destination injected into the
container. The issue with this is that we need a policy plugin for resolving the source of
the destination provider. There could be a JndiLookupProvider, or jms specific providers
that map the destination name onto the mc component name/property to inject.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032425#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...