February 2007 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Scoped Kernels

by bkeh12

Hi,kabir if try this | <property name="pointcut"> | execution(* $instanceof{org.jboss.test.kernel.deployment.support.SimpleObjectWithBean}->*(..)) | </property> | Why ast get "\n" ? isn't property metadata "execution(* $instanceof{org.jboss.test.kernel.deployment.support.SimpleObjectWithBean}->*(..))" ? thank View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022416#4022416 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022416

18 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Automatic Scoped Kernels - A good idea

by adrian＠jboss.org

Given Ales's latest issue/hack, I'm beginning to wonder whether the automatic construction of scoped kernels is really such a good idea. For ease of use it probably is, but making it work is requiring too many hacks and I have a feeling that Ales is doing it wrong anyway or has at least misunderstood part of it (Given some of the problems he is reporting). The alternate approach would be to move the scoping of kernels to the deployers. i.e. The MC can support scoped kernels but you have to use an api to configure them. The deployment chain would then look something like: 1) Parsing as now (for POJOs - BeanDeployer) 2) ClassLoading deployer (as now or replaced with OSGi style) 3) Component Deployer (for POJOs KernelDeploymentDeployer) 4) Scoping Deployer (NEW looks at BeanMetaData and creates ScopedKernel) 5) Real Deployer (as now BeanMetaDataDeployer - but deploys into ScopedKernel) This gives a cleaner api and probably makes it easier to override scoping rules. The downside is that you don't get scoping out of the box, you either have to use the deployers or write your own scoping config code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022413#4022413 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022413

18 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped Kernels

by alesj

"adrian(a)jboss.org" wrote : | In fact, what is really required to fix this problem is something we discussed a while ago | where the bean is given a UID (unique identifier) to store its internal state. This means adding getUniqueName() on BeanMetaData? Where all should it be applied? I think we mentioned this with aliases and inner un-named beans. Any other place? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022412#4022412 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022412

18 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JCA AOP-MC Integration

by kabir.khan＠jboss.com

Weston, can you please provide some code that reproduces the problem for me to look at? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022411#4022411 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022411

18 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging 1.2.0 integration with JBoss 5.0.Beta

by kabir.khan＠jboss.com

Hmmm, yes I replied late at night and hadn't thought through what I was saying :-) I updated build-thirdparty.xml to "your" version and the build works. But the snapshot of AOP in trunk is a snapshot from the 2.0 branch. Why this works I am not sure. Maybe snapshots aren't checked properly for compatibility? In any case for future reference, head always uses AOP 2.0.0 releases/snapshots View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022410#4022410 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022410

18 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped Kernels

by adrian＠jboss.org

We really need to split off some of this discussion into other topics. I already forked this discussion once because it was becoming too entangled (see the original post on this thread). Let's try to keep the discussions focused on one issue and use links if there is some relation to other issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022409#4022409 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022409

18 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped Kernels

by adrian＠jboss.org

"alesj" wrote : "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> | | That looks like a very dirty hack to me. I'm beginning to think that if we are going to add one hack (pretending mutating the name to avoid clashes) because of another hack (moving the controller) then we are on the wrong track. In fact, what is really required to fix this problem is something we discussed a while ago where the bean is given a UID (unique identifier) to store its internal state. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022406#4022406 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022406

18 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped Kernels

by kabir.khan＠jboss.com

Workaround for | [ScopedKernelController] Error installing to Start: name=InterceptedBinding state=Create | org.jboss.aop.pointcut.ast.TokenMgrError: Lexical error at line 1, column 1. Encountered: "\n" (10), after : "" | is | <property name="pointcut">execution(* $instanceof{org.jboss.test.kernel.deployment.support.SimpleObjectWithBean}->*(..))</property> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022402#4022402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022402

18 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : I don't understand this? | If you are talking about multiple processors of the ConnectionFactory metadata then that framework already exists in the new deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022401#4022401 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022401

18 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by adrian＠jboss.org

I don't understand this? The correct approach is xml -> metadata model metadata model -> components (jmx/pojo) why does the parsing need to be aspectized? Evolution of the metadata model is an OOP issue not an AOP issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022398#4022398 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022398

18 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2007