[jboss-dev-forums] [Design of POJO Server] - Re: Moving forward with the profile service mgmt api

[scott.stark@jboss.org]

"adrian at jboss.org" wrote : 
  | The initial construction of DeploymentContexts from the profile
  | is a problem for the profile service (with or without predetermined attachments).
  | 
  | Of course the managed object will provide a method to
  | turn a managed object into its wrapped attachment (metadata object)
  | for serialization by the profile service.
  | 
  | The piece that is missing outside the profile service
  | will be an extension to the deployers api where there will be two links:
  | 
  | 1) You are a "parsing deployer", tell me what your managed object looks like.
  | i.e. construct a managed object for this attachment you created.
  | 
  | 2) You want to support runtime updates (not just redeployment), 
  | then the server side support of the managed object needs a link to the 
  | "real deployer' for the attachment.
  | 

For 1), I am relying on a new MainDeployer.process(CLASSLOADER_DEPLOYER) to only process deployments using deployers below a given level/order.

For 2), this gets back to the ManagedObject to metadata mapping. A given ManagedProperty can apply to both an attachment metadata property and a kernel bean property.


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

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