[emuckenhuber]

Actually the HQ1.jpg (which is the simplest diagram) describes best what needs to be done

Leaving ProfileService aside for now. The only things which matters for the deployers integration are the ParsingDeployer and the RealDeployer.

The most important part about this is that you don't have any control about the metadata (e.g. JMSConfiguration). When the RealDeployer gets a JMSConfiguration metadata it has to deploy it.

There a couple of ways to actually install/register things in MC, so that it's visible for dependency resolution. So that should not be a real issue.

[clebert.suconic]

So, that's the agreement we have so far:

- We keep on the current track... Fix the testsuite and merge trunk/AS6

- Emmanuel will reuse the deployers I wrote to deploy queues and will make tweaks to the MOs he wrote initially. (The tweak also include putting them at the right place. I'm not the expert here but it seems to me it should be created on the real deployer where the JMSConfiguration is given as an input).

- We will keep the current view Andy has created, but we will talk to JON guys how to make it better, since it has basically what we think it should be added to the main console.

- I will not commit my changes on making every destination available to @depends. If the user is using the HornetQ's API directly that means it's doing it for a reason. I think a serious messaging user will be dealing with HornetQ's API directly and those users will usually need more performance (probably even turning off management). So anything done at HQ's level will be a performance burden.

- We will keep supporting @depends for users deploying stuff through the application server.

*** Speak now or forever hold your peace! ***