How does SErviceDeployer register with MC

[bill.burke]

Hoping that somebody will answer before I spend the next hour or so figuring it out myself...

But...

I need to be able to set up a dependency between an EJBContainer and a datasource deployed. Currently ds.xml creates a set of MBeans (the old shit), just wondering how these MBeans are registered with the MC so that I can create a dependency on them.

Thanks

[bill.burke]

More importantly I need to know how to create a AbstractDemandMetaData to create the dependency.

[bill.burke]

it converts ON to a canonical string.

[weston.price]

Bill wanted me to note that it was my bad advice (thinking that the ObjectName of the deployment was maintained versus a string) that caused him such heartache.....

[anil.saldhana]

Bill wanted me to note that it was my bad advice (thinking that the ObjectName of the deployment was maintained versus a string) that caused him such heartache.....

Please follow http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96686
for something Bill told me that caused me headache.

[starksm64]

So what was the answer to the datasource question? I'm using a datasource deployment as the poc for the next phase of the deployment update that introduces the profile service and managed object change sets. How a change set for a "datasource" management view relates back to the datasource metadata objects as understood by the jca deployers is a mapping I need to understand.

[weston.price]

I would have to look at what you are doing to better answer that question. The mapping you talk about might not exist currently and this would be something I would have to do.

Can you give me a particular example of how the profile service works, capabilities etc?

[bill.burke]

We're going to quickly run smack into the problem where references to services like datasources are expressed in terms of JNDI names and the referencing component is being deployed before these referenced services.

What I do now is VERY VERY hacky. I take the JNDI name of the datasource and construct an Kernel name from it.

We talked before about requiring services that register in JNDI to also create a generic JndiBinding bean. Another thought I had, what about integrating/federating JNDI with the Kernel Registry?

ANyways, this should be a topic for a different thread.

[starksm64]

I'm working on an overview of the profile service and the expected usecases of management views mapping to deployment metadata/component properties. I'm working to get something out tonight as we want to start talking about the managment aspects of jboss5 and their intersection with the mc/vdf as part of the post cts call on Fridays.

[weston.price]

Cool. I will review. I should be able to address your questions regarding profile/JCA when I see the doc.