From: <ad...@jb...> - 2005-05-23 15:36:19
|
"bil...@jb..." wrote : "ad...@jb..." wrote : It can also be used to support other models, e.g. where Bill is dragging his heels | | deploying AOP metadata as BeanMetaData and instead using the POJO MC | | as a ServiceLocator. | | | Please expand what you want explicitly and what exactly is missing instead of just insulting me. | I am not insulting you, at least that was not my intension. I'm sorry if you interpreted it that way. I am actually agreeing with you. If you want to take it incrementally and use the dependencies as a ServiceLocator we should support that as a first class notion. You shouldn't have to do unnatural things to make this work. The "Dragging Heels" comment refers to originally we agreed that the aspect factories would be deployed as beans through the kernel, but this isn't what you are doing now. Somewhere down the road, the aspect manager will support DI and be integrated with the full dependency model. In the meantime we need the ability to query dependencies and use the service locator pattern. To fully clarify before you misinterpet :-). By the "aspect manager will support DI", I mean the aspect metadata will be injected into the aspect manager as the aspect's dependencies are satisfied. Currently the aspect is placed in the aspect manager's "holding area" where anybody could activate "by reference" before the dependencies are satisfied. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878761#3878761 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878761 |