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

[scott.stark@jboss.org]

"adrian at jboss.org" wrote : This seems to be getting very confused?
  | 
  | ATTACHMENTS
  | 
  | The original design was the following:
  | 
  | You have two types of attachment:
  | 1) Transient - these are created by the parsing deployers from the raw xml
  | inside the deployments
  | 2) Predetermined - these are what the profile service (or some other invoker of the
  | deployers) passes in to override what is in the deployment.
  | 
  | The Predetermined attachments are a sort of alt-dd but done programmatically.
  | 
  | I can see an argument for having a third type of attachment which is internal state
  | related to the deployment but it is stuff that we don't want the profile service/management
  | layer to override. It will always be constructed at runtime.
  | 
  | However, this can also be trivially dealt with by the ManagedObjectBuilder
  | NOT creating a ManagedObject for that attachment type.

I don't see the confusion as, other than the new third form of attachment, this is how I have described the attachments usage is it not? The notion of the third attachment being classified separately was really only to control what attachments have some serialization requirement.


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

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