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

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by bill.burke＠jboss.com

Adrian, I'm not grokking here... I was thinking more of: | <deploymen> | <scope name="application"> | <bean name="Foo"/> | <scope name="session"> | <bean name="bar/> | </scope> | </scope | </deployment> | | Kernel app= kernel.createScope("Application"); | Kernel session = app.createScope("session"); | Or something like that. I hope you get the idea. All scoped beans would just be described and their metadata deployed into a new kernel when the scope is created. Child scopes would not be created, but instead registered with the parent scope. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008925#4008925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008925

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Web console changes - IMPORTANT

by david.lloyd＠jboss.com

I verified that the above form (the second one) with ui:component instead of ui:fragment does work. Also I removed the comment (which was mainly for the benefit of you, the reader). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008924#4008924 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008924

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Precedence level

by adrian＠jboss.org

The problem with this is that it works fine for Seam or Spring where you are only dealing with a single application with a fixed set of deployments. The MC has to deal with hotdeployment where beans can be added at anytime. e.g. suppose we define a jboss-jca group so you can depend upon all of jca being deployed, but then you add a new rar to the jboss-jca group? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008923#4008923 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008923

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Class dependencies

by scott.stark＠jboss.org

Somewhat, but then how is this reflected in the profile and exposed via management interfaces? Its hard to deal with something that does not exist. There would have to be some unresolved bean notion that does not fail a deployment when its validated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008922#4008922 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008922

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

The other piece is linking in the AOP domain concept into the scope. i.e. so you can do the same thing with aspect definitions. e.g. Being able to define advices for jdbc objects that only apply when the jdbc object is used inside JCA. User's jdbc objects would be unadvised. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008921#4008921 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008921

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: JBoss configuration build

by david.lloyd＠jboss.com

"tom.baeyens(a)jboss.com" wrote : maybe it is the parent directory of ${jboss.home} that needs to exist. it's in the parent directory that the jboss zip file is unzipped. | | does the ant script itself give a clue ? In this case, the parent does exist. Looking in depth I think this is the problem: <target name="clean.jboss.install" description="deletes the current jboss installation at ${jboss.home}"> | <delete dir="${jboss.home}" /> | </target> The problems here are: * The will fail on error * This task is executed by default - perhaps it is better to fail if the directory exists rather than delete it automatically, and let the user manually delete or rename the directory if it does exist View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008920#4008920 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008920

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Support for Bean Scripting Framework (BSF)

by estaub

Ronald van Kuijk (mis)posted "isn't there a JSR for pluggable scripting?" on another thread (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008880). Oops - yes, there is - JSR-223 (https://scripting.dev.java.net/). I didn't realize it was so far advanced. I'll use it if possible. (Thanks, Ronald!) -Ed Staub View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008915#4008915 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008915

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : "bill.burke(a)jboss.com" wrote : | | Although there it is more related to scoped factory references | | | | The advantages of using factories is that you get late binding of injections | during the "create()" not when you define the beans in the kernel. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008914#4008914 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008914

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

"bill.burke(a)jboss.com" wrote : | In MC land, this would translate to describing each bean deployed to a particular scope and this meta cloned to a new kernel that finally installs the beans. | The same feature has also been requested by jbpm. Although there it is more related to scoped factory references that pass under the wire. And there are multiple runtime scopes e.g. a process is long running but can have subtasks that override the process with different factories. The basic code would then look something like: | // Get the current metadata | MetaData metaData = MetaDataStack.peek(); | | // Get the controller | KernelController controller = metaData.getMetaData(Kernel.class).getController(); | | // Get the factories and create the objects | SomeFactory factory1 = controller.getInstance("SomeFactory").getTarget(); | MyObject1 object = factory1.create(); | AnotherFactory factory2 = controller.getInstance("AnotherFactory").getTarget(); | MyObject2 object = factory2.create(); | Incidently, it would look much nicer if the scope included a MetaDataLoader that just delegated to the local kernel, i.e. it did the wiring above inside the MetaDataLoader. | // Get the current metadata | MetaData metaData = MetaDataStack.peek(); | | // Get the factories and create the objects | SomeFactory factory1 = metaData.getMetaData(SomeFactory.class); | MyObject1 object = factory1.create(); | AnotherFactory factory1 = metaData.getMetaData(AnotherFactory.class); | MyObject2 object = factory2.create(); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008912#4008912 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008912

17 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: JBoss configuration build

by tom.baeyens＠jboss.com

maybe it is the parent directory of ${jboss.home} that needs to exist. it's in the parent directory that the jboss zip file is unzipped. does the ant script itself give a clue ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008911#4008911 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008911

17 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007