[Design the new POJO MicroContainer] - Re: Scoped Kernels
by alesj
"alesj" wrote :
| From previous problem (duplicate 'context') temp fix, I currently have Context's hashCode under WORK level to diff the contexts. What's the appropriate fix?
|
| public ScopeKey getFullScope(KernelControllerContext context)
| {
| ScopeKey scope = ScopeKey.DEFAULT_SCOPE.clone();
| scope.addScope(CommonLevels.INSTANCE, context.getName().toString());
| BeanMetaData beanMetaData = context.getBeanMetaData();
| if (beanMetaData != null)
| {
| String bean = beanMetaData.getBean();
| if (bean != null)
| scope.addScope(CommonLevels.CLASS, bean);
| }
| // todo - some other level
| scope.addScope(CommonLevels.WORK, String.valueOf(context.hashCode()));
| return scope;
| }
|
Otherwise I cannot differentiate between these two beans:
| <bean name="simple" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl">
| <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation>
| <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment1")</annotation>
| <constructor>
| <parameter>deployment1</parameter>
| </constructor>
| </bean>
|
| <bean name="simple" class="org.jboss.test.kernel.deployment.support.SimpleBeanImpl">
| <annotation>@org.jboss.metadata.plugins.scope.ApplicationScope("testApp")</annotation>
| <annotation>@org.jboss.metadata.plugins.scope.DeploymentScope("deployment2")</annotation>
| <constructor>
| <parameter>deployment2</parameter>
| </constructor>
| </bean>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021636#4021636
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021636
18 years, 10 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging 1.2.0 integration with JBoss 5.0.Beta
by ovidiu.feodorov@jboss.com
Messaging 1.2.0.CR1 in the head did not break the build. I have tested the build personally, and everything was compiling just fine. Check out a 23/Feb/07 02:21 AM PST snapshot of the head and try for yourself, if you don't belive me.
AOP 2.0.0.Alpha3 in the head broke the build.
Before checking-in the change in SVN, you should have updated the head, as it was, delete 'thirdparty', and try to build locally, and you'd have seen that it breaks, because Messaging declars compatibility with AOP 1.5.x only.
The next step would have been to post on the Messaging development forum, or to me or Tim personally, we don't mind, or create a Messaging JIRA issue and ask us to validate 1.2.0.CR1 with AOP 2.0.0.Alpha3, by running our testsuites with AOP 2.0.0.Alpha3.
That did not happen, somebody just modified our component-info.xml in the head, as in "oh well, who cares ...".
Anyway, http://jira.jboss.org/jira/browse/JBMESSAGING-892
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021458#4021458
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021458
18 years, 10 months