September 2007 - jboss-dev-forums

[Design of JBoss jBPM] - expression or execute

by pete.muir＠jboss.org

Hi If you are using Seam with JBPM you end up with different syntax for executing actions uising EL: Seam's pages.xml <page> | <action execute="#{foo.bar}" /> | </page> Seam's components.xml <event> | <action execute="#{foo.bar}" /> | </event> (actually currently its components.xml <event> | <action expression="#{foo.bar}" /> | </event> but we are planning to deprecate this) .jpdl.xml <action expression="#{foo.bar}"/> We (Seam dev) feel that execute is a better word as expression is what it is, whilst execute is what it does. In particular you can use expressions inside other attributes (e.g. condition="#{foo.isBar}" or actor-id="#{foo.actor}"). But I also think consistency is very important, so we am hoping that we can get execute as an alias to expression available in JPDL (best would be to deprecate expression I think). What do you guys think? A possibility? http://jira.jboss.com/jira/browse/JBSEAM-1775 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080849#4080849 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080849

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation processing

by alesj

Regarding MetaData.getScopeMetaData() I have this next drawback. :-) Looks like introduction of MetaDataContext into MetaDataRetrievalToMetaDataBridge doesn't really fit: | public MetaData getScopeMetaData(ScopeKey scopeKey) | { | if (retrieval instanceof MetaDataContext) | { | MetaDataContext context = (MetaDataContext)retrieval; | ... | } | return null; | } | Perhaps having a new MetaDataContextToMetaDataBridge would do the trick, but this, at a quick glance, looks like a big propagation through the metadata stuff ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080847#4080847 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080847

17 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Graphical Cut/Copy/Paste in GPD

by koen.aers＠jboss.com

Hi Matthew, I did not do any work on this yet. Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080844#4080844 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080844

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation processing

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : | | and add an isEmpty() to the MetaData api. | | | What would mean that MetaData.isEmpty() == true? | | This? | | | public boolean isEmpty() | | { | | MetaDatasItem items = retrieval.retrieveMetaData(); | | return items == null || items.getMetaDatas() == null || items.getMetaDatas().length == 0; | | } | | Yes, but I think you should propogate the isEmpty() through the api such that it can be done in a more efficient manner where possible. i.e. no need to construct the metadata array from the annotations and plain metadata just to see if there are any. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080842#4080842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080842

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation processing

by alesj

"adrian(a)jboss.org" wrote : | and add an isEmpty() to the MetaData api. | What would mean that MetaData.isEmpty() == true? This? | public boolean isEmpty() | { | MetaDatasItem items = retrieval.retrieveMetaData(); | return items == null || items.getMetaDatas() == null || items.getMetaDatas().length == 0; | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080840#4080840 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080840

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Post-install supply change

by wolfc

I've hit a snag while spotting some regression because of http://jira.jboss.com/jira/browse/EJBTHREE-1042. If a container looks itself up using JNDI it should not register a dependency. To check this I need to iterate bindings before install (after processMetaData). But because of http://jira.jboss.com/jira/browse/EJBTHREE-942 metadata is only complete after create()->initializeClassContainer(), e.g. post-install. This is a no-go on MC, metadata must be complete pre-install. To make things more interesting: in general we allow metadata additions from ejb3-interceptors-aop.xml, so it should be processed after descriptor handler, but before any metadata is used. This nags EJB3InterceptorsFactory which needs the metadata to establish an interceptor chain. So either we don't allow metadata additions in interceptor-aop (not an option) or we don't use metadata during interceptors-aop setup (ehr...). Suggestions? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080831#4080831 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080831

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation processing

by adrian＠jboss.org

"alesj" wrote : | What's the difference between local and non-local retrievers (from MetaDataContext): | | | /** | | * Get the retrievals | | * | | * @return the retrievals | | */ | | List<MetaDataRetrieval> getRetrievals(); | | | | /** | | * Get the local retrievals | | * | | * @return the local retrievals | | */ | | List<MetaDataRetrieval> getLocalRetrievals(); | | | | A MetaDataContext is made of local retrievals and a parent context. | retrievals = local + parent retrievals. | | anonymous wrote : | | Any quick tips on how MetaData.hasInstanceMetaData() should look like? | | Should it still use MetaDataContext as current impl in AOPConstructorJoinpoint does? | | Just move the AOP alogrithm into the MetaData/bridge. | i.e. see whether the backing MetaDataContext has an INSTANCE scope | and whether that scope has local annotations or metadata. | | A more complete api would be to allow | MetaData.getScopeMetaData(ScopeKey) | which would produce a MetaData backed by the local retrievals of that scope | and add an isEmpty() to the MetaData api. | | The hasInstanceMetaData() could then be implemented as: | | | MetaData instance = getScopedMetaData(instanceScope); | | return instance.isEmpty(); | | | making it redundant. | | But that might be a bit more complicated to implement with the caching, etc.? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080801#4080801 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080801

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: mc eclipse project has ant 1.7.0 build path problems

by adrian＠jboss.org

I've got both in my repository. My guess is the 1.7.0 ant dependency has recently been removed due to the suppression of other dependencies? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080794#4080794 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080794

17 years, 7 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP asintegration WITHOUT the integration :-)

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : | I am thinking of the following line: | bPolicy.setDelegates(createDelegates(supportPolicy)); | | This says the classloader "b" imports the classloader "support". i.e. all the exported classes from "support" are visible to "b". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080789#4080789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080789

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation processing

by alesj

"alesj" wrote : | "adrian(a)jboss.org" wrote : | | Also the BasicBeanAdapter and related classes need fixing such that they use the MetaData not the MetaDataRetrieval. | | | | The same is true of its usage in the Scoping. | | | MetaData has all the required functionality - as MetaDataRetrieval? | | Scoping as in PreInstall stuff that we did? | Yup, it was easy to move annotations handling to plain MetaData lookup. :-) I also (re)moved the part in PreInstallAction where MetaDataRetrieval was referenced from KernelMetaDataRepository. But I guess this code cannot be changed to use plain MetaData since I _need_ to build the whole MetaDataRetrieval for the scope - similar to how we do it for ControllerContext's MetaData (hidden in BasicKernelMetaDataRepository). | // find scoped controller | MutableMetaDataRepository mmdr = repository.getMetaDataRepository(); | MetaDataRetrieval mdr = mmdr.getMetaDataRetrieval(scopeKey); | if (mdr == null) | { | mdr = new MemoryMetaDataLoader(scopeKey); | mmdr.addMetaDataRetrieval(mdr); | } | MetaDataItem<ScopedKernelController> controllerItem = mdr.retrieveMetaData(ScopedKernelController.class); | ScopedKernelController scopedController; | if (controllerItem != null) | { | scopedController = controllerItem.getValue(); | } | else | { | AbstractController parentController = null; | ScopeKey parentKey = scopeKey.getParent(); | while (parentController == null && parentKey != null) | { | MetaDataRetrieval pmdr = mmdr.getMetaDataRetrieval(parentKey); | if (pmdr != null) | { | MetaDataItem<ScopedKernelController> pci = pmdr.retrieveMetaData(ScopedKernelController.class); | if (pci != null) | { | parentController = pci.getValue(); | } | } | parentKey = parentKey.getParent(); | } | if (parentController == null) | { | if (controller instanceof AbstractController == false) | throw new IllegalArgumentException("Underlying controller not AbstractController instance!"); | parentController = (AbstractController) controller; | } | scopedController = new ScopedKernelController(controller.getKernel(), parentController); | ((MutableMetaData)mdr).addMetaData(scopedController, ScopedKernelController.class); | } | scopedController.addControllerContext(context); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080779#4080779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080779

17 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums September 2007