[jboss-dev-forums] [Design of POJO Server] - Re: Depends on @JMX mbean name

[adrian@jboss.org]

"anil.saldhana at jboss.com" wrote : 
  | I spent 30 mins of my time yesterday in tracing the log wondering why my xxx-beans.xml was not getting processed. How can we help users with this? Maybe some warning message hinting at xxx-jboss-beans.xml?
  | 

This really falls under the "missing deployer" category.
But I think this is broken because we are generating some default metadata
regardless of whether other deployers actually process the deployment.

AbstractDeployment has

  |    public Object addAttachment(String name, Object attachment)
  |    {
  |       DeploymentContext deploymentContext = getDeploymentContext();
  |       deploymentContext.deployed();
  |       return deploymentContext.getTransientAttachments().addAttachment(name, attachment);
  |    }
  | 

So when the classloader deployers adds attachments, e.g. create
a default ClassLoadingMetaData for this top level deployment,
it is treated as deployed.
The same goes for the classpath deployer.

I think to fix this, we need a new method that says the attachment we are
adding should not be considered as flagging the deployment as really processed/deployed.

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

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