[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: What is going on with aliases?

[alesj]

"adrian at jboss.org" wrote : 
  | None of this makes any sense to me. I don't remember you discussing
  | any of these changes?
  | 
  | The order of the aliases cannot matter and you can't have an alias more than once.
  | So why a List when a Set describes exactly what is required.
  | 
I agree, I'll put the Set back.
Though I'll need a list, but I don't.

"adrian at jboss.org" wrote : 
  | Also what does it mean for a deployment rather than a bean to have an alias?
  | Is this a Spring thing?
  | 
Yup, this was originally taken from Spring.
But I think they have a full implementation - the one mentioned on the JIRA. Which I think we initially don't need .

"adrian at jboss.org" wrote : 
  | As far as I can tell, your DeploymentAliasMetaDataDeployer is just going to fail
  | when a deployment has more than one bean in it.
  | You will try to apply the alias names to all the beans in the deployment.
  | Only one of the beans can have an alias. It must be unique!
  | 
  | Also, the component deployer was not intended for this kind of thing.
  | 
  | The idea of a component is to represent a part of a deployment,
  | e.g. a single ejb in an ejb jar or single bean in a -beans.xml
  | soon I will be using the components to assign scopes for the MetaDataRepository
  | where instance=component-name 
  | This kind of hack is just going to confuse things. 
  | There should be only one scope not a scope for every alias.
  | 
I don't understand this.
How else do you think to deploy this, if not as a component?
Or is this not relevant anymore due to next posts?

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

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