org.jboss.deployers.spi.deployer.managed
Interface ManagedObjectCreator

All Known Implementing Classes:

AbstractParsingDeployerWithOutput

public interface ManagedObjectCreator

ManagedObjectCreator. TODO JBMICROCONT-181 Critique Rather having the contexts create the managed objects directly they should provide the underlying metadata, e.g. the Fields + other information from which we can create the managed object. This is important because it is likely that multiple builders/deployers will play populate an object, e.g. (possibly?) - the parsing deployer will describe the properties/metadata - there maybe transformation, augmentation by some other deployers - the component deployers will want to link their component metadata back into the parent by reference, e.g. an mbean as part of sar/-service.xml - the real deployer will describe any runtime support, e.g. managed operations and statistics

Version:

$Revision: 1.1 $

Author:

Adrian Brock

Method Summary

void	build(org.jboss.deployers.structure.spi.DeploymentUnit unit, Map<String,org.jboss.managed.api.ManagedObject> managedObjects) Build managed objects for this deployment context

Method Detail

build

void build(org.jboss.deployers.structure.spi.DeploymentUnit unit,
           Map<String,org.jboss.managed.api.ManagedObject> managedObjects)
           throws org.jboss.deployers.spi.DeploymentException

Build managed objects for this deployment context

Parameters:

unit - the deployment unit

managedObjects - the managed objects

Throws:

org.jboss.deployers.spi.DeploymentException