[jboss-dev-forums] [Deployers on JBoss (Deployers/JBoss)] - Re: JSR88 updated with a StreamingTarget implementation

[scott.stark@jboss.org]

Yes, that is the simple add a deployment sequence.

We don't care about how the service is packaged for this scenario. Something has to care about the packaging in terms of how admin changes are applied to the deployment repository, but there are a lot of details to flesh out. The issue is that, for a given deployment:

- there has to be a management interface representation that allows a tool to perform changes without the jboss server running
- there has to be a mapping from the management interface properties to the deployment metadata the admin changes apply to, and/or a mapping to the runtime component properties the changes apply to. There can be a management property that only applies to the deployment metadata and requires a restart, applies to only a runtime mc component property, or applies to both. The change has to be a delta of some form in the deployment repository. How this is stored and the override applied depends on the management interface to deployment metadata/component property mapping. The RARDeployer port certainly affects the mapping, but should not affect the managment interface.

I'm working on a profile service overview/state of being description to put out tonight as background for the parties to use as a basis for what we want to do with a managment aspect.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992122#3992122

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992122