[jboss-dev-forums] [Design of POJO Server] - Re: DataSource/ServiceXSLDeployer processing issue

[scott.stark@jboss.org]

"adrian at jboss.org" wrote : COMPONENTS
  | 
  | This is very much a prototype. When I wrote this it was just to get something
  | working and express the idea. Like I said before, this needs revisiting and
  | doing properly.
  | 
  | But what I will say is that components are an implementation detail.
  | The profile service should not be interested in the components directly,
  | it is not going to touch their attachments.
  | 
  | The components that get constructed from a particular metadata model
  | can change from release to release.
  | 
  | The only part the profile service needs to know about these is the
  | context names. i.e. what are the MBean/POJO names
  | so it can map missing dependencies back to the original deployment
  | that caused them.

There is a notion of components in the profile service since the management interface wants to be able to query by functional detail rather than structural. A service deployment has mbeans which have managed objects. How this maps back onto the DeploymentUnit attachments depends on the ModelObjectBuilder. I don't see why it could not map to a component DeploymentUnit if desired.


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

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