[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Indirect dependency names

[adrian@jboss.org]

"alesj" wrote : 
  | Perhaps having a more open BeanMetaDataBuilder is the way to go - meaning you can provide what the actual metadata impls are we gonna use, 
  | 

You mean something like Builder::addInstallCallback(InstallCallback ic);
Where ic can be your own implementation. Ok.

But I don't think that is the issue here is it?

For this case (as I understand it),
the thing that is building the BeanMetaData just needs to do:
builder.addInstallCallback(method, someGeneratedName);

The part I don't understand is why it has to get more complicated?
Why do we need lots of new interfaces or methods when the thing creating
the BeanMetaData is the one that knows what the generated names are?

Like I said above, if you don't know what the generated name is
how are you going to uninstall it when it is no longer required?


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

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