|Actually the RARDeployer registers RARDeployments with ServiceController so |they participate in dependency management also.
right, good |I changed Application and Container so EJB mbeans do this also: do you mind |if I put it in before 3.0 beta? Do you want to wait until we are using |jsr-77 mbeans for dependencies? thanks for asking. I proposed the dependencies for the jsr77 framework and it was met with deafening silence. Either they or we don't get it. So don't wait for anyone since this dependency mechanism generalized to all types of deployments 1- is made possible by the new unified deployers and unified representation of the DeploymentInfo 2- is absolutely necessary if we want to have a standardized way of defining the dependencies and order of creation/starting ACROSS all deployment types with one semantic so go ahead. You say you want the ServiceController to take over the create/start steps. I remember there was another spot where you wanted to introduce the DeployerSupport in the codebase, i think providing super calls that call the ServiceController in create and start, after the deployer specific create and start calls have been done is worthwhile. This is an absolute kick ass piece of code. marcf | |david jencks | |> |> to do what you want you should put the ejb inside the sar, anywhere, and |> that will work. |> |> marcf |> | |> | |> |Dave Smith wrote: |> |> Do we have any docs on this stuff? I'm tring to create a dependancy |> with |> |> a message driven Mbean that will wait until the topic it publishes is |> |> created and also wait until the EJB that it uses is deployed. From a |> |> quick look at the example with the TopicManager it looks like you have |> |> to create a an MBean attribute with type ObjectName that maps to the |> JMX |> |> service you need. If that is the case how would you tie it to an EJB? |> |> |> |> Head spinning in Toronto ... |> |> |> _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
