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

[Design the new POJO MicroContainer] - Re: anonymous beans

by scott.stark＠jboss.org

I would make the name anon#n, but yes, that seems about all that is required to add this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038688#4038688 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038688

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Barriers inhibiting tight JBPM integration

by bill.burke＠jboss.com

Here's what I can think of that are barriers to tight JBPM integration. * JBPM Designer doesn't support pluggable action/node types (JBPM core does through node.types.xml). I know nothing about eclipse or how hard this would be. * JBPM nodes/actions don't support lifecycle. We need start/stop for both nodes and actions. This may be solvable by MCizing/beanitizing the JBPM object model and rewriting the JBPM XML parser so that it creates MC bean metadata. * Different Message interfaces. ESB has org.jboss.soa.esb.Message. JBPM has Token. Both have different ways at getting at metadata and conversational data. I think we can solve this problem with pluggable node/action types that JBPM core provides (so long as the designer supports it) as well as using Seam bijection. If all our ESB actions are written in terms of Seam bijection, then maybe we can plug/play with JBPM. The end goal of all of this is to be able to blur ESB, JBPM, and Web flow so that ESB actions and glue can be used anywhere within a business process or webflow. Vice versa too. ESB can embed workflow within its definitions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038686#4038686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038686

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Lookup a particular ManagedComponent in a ManagementView

by bytor99999

Should or will there be a method in ManagementView to get a single ManagedComponent by name. Just like the | protected ManagedComponent getManagedComponent(ManagementView mgtView, | ComponentType type, String name) | throws Exception | | | | | in the ProfileServiceUnitTestCase? | | | | Thanks | | | | Mark View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038676#4038676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038676

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - anonymous beans

by bill.burke＠jboss.com

I finding that I don't always need to specify a bean name attribute. In fact, in these scenarios, its quite annoying. It would be cool if the name attribute was optional. How hard would it be to add this? Just generate a random name in the default initialization of BeanMetaData and let the container override it if somebody has specified it? And change the schema too? thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038665#4038665 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038665

19 years, 1 month

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Woven class compatibility

by kabir.khan＠jboss.com

Code woven with 1.5.4.GA and run with 1.5.5.GA has the following failures * Introductions handled by interceptors (same as when woven with 1.5.2.GA and 1.5.3.GA) The caller pointcuts failing when woven with 1.5.2.GA pass when woven with 1.5.3.GA. The corner cases for inherited fields failing with 1.5.2.GA and 1.5.3.GA pass when woven with 1.5.4.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038637#4038637 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038637

19 years, 1 month

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Woven class compatibility

by kabir.khan＠jboss.com

Code woven with 1.5.3.GA and run with 1.5.5.GA has the following failures * Introductions handled by interceptors (same as when woven with 1.5.2.GA) * Some corner cases for inherited fields (same as when woven with 1.5.2.GA) The caller pointcuts failing when woven with 1.5.2.GA pass when woven with 1.5.3.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038635#4038635 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038635

19 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Maven project naming conventions

by pgier

Looking at the snapshots repository, I can imagine the root jboss folder http://snapshots.jboss.org/maven2/jboss getting large very quickly. Possibly to the point where it is difficult to navigate. Would it be beneficial to change the naming conventions to group smaller projects together similar to their structure in svn? For example, instead of the current flat structure common could be grouped like this within the jboss directory: | /common | /common/jboss-common-core | /common/jboss-common-logging-jdk | /common/jboss-common-logging-log4j | /common/jboss-common-logging-spi | /common/jboss-common-xb | This way the actual artifact names would still be unique as long as we keep the path in the artifact name. The javaee project could have a structure like this: | /javaee/jboss-javaee-ejb-api | /javaee/jboss-javaee-jacc-api | /javaee/jboss-javaee-jad-api | etc... | This structure would map a little better to our svn structure, and I think it would be a little easier to navigate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038634#4038634 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038634

19 years, 1 month

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Woven class compatibility

by kabir.khan＠jboss.com

I have tested the AOP 1.5.5.GA tests against classes woven with 1.5.2.GA, and it is MOSTLY compatible. Areas of failure are: * Introductions handled by interceptors * MethodByConstructor pointcuts * ConstructorByConstructor pointcuts * Some corner cases for inherited fields - these tests did not exist in 1.5.2.GA, so this was functionality added later View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038631#4038631 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038631

19 years, 1 month

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Woven class compatibility

by kabir.khan＠jboss.com

"next AOP 2.0 release will be **completely incompatible** with the woven code from the previous releases." => next AOP 2.0 ALPHA release will be **completely incompatible** with the woven code from the previous ALPHA releases. Once we have a AOP 2.0.0.CR we will add the backwards compatibility tests to the 2.0.0 branch View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038619#4038619 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038619

19 years, 1 month

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Woven class compatibility

by kabir.khan＠jboss.com

I am in the process of optimizing the AOP 2.0 weaving model, and now is as good time as any to point out that the woven code in the next AOP 2.0 release will be **completely incompatible** with the woven code from the previous releases. Note that this only applies to the new AOP 2.0 weaving (generated advisor), and not to the 1.5.x woven code unless you used the following when aopc'ing with AOP 1.5.x: | <aopc ...> | ... | <sysproperty key="jboss.aop.instrumentor" value="org.jboss.aop.instrument.GeneratedAdvisorInstrumentor"/> | </aopc> | The default weaving mode for 1.5.x is ClassicInstrumentor and the default for 2.0 is GeneratedAdvisorInstrumentor. 1.5.5 woven with the default ClassicInstrumentor remains runnable on AOP 2.0 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038617#4038617 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038617

19 years, 1 month

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 April 2007