September 2007 - jboss-dev-forums

[Design the new POJO MicroContainer] - Re: More build problems.

by adrian＠jboss.org

I'm going to update the versions to those of beta4 and see where that gets me. https://svn.jboss.org/repos/jbossas/projects/microcontainer/tags/2.0.0.Be... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082199#4082199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082199

18 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - More build problems.

by adrian＠jboss.org

The MC trunk eclipse build is broken. e.g. The eclipse build has been updated to use jboss-test:1.0.4.GA https://svn.jboss.org/repos/jbossas/projects/microcontainer/trunk/contain... anonymous wrote : | | but maven is still using the snapshot https://svn.jboss.org/repos/jbossas/projects/microcontainer/trunk/build/p... anonymous wrote : | <version.org.jboss.test>1.0.4-SNAPSHOT</version.org.jboss.test> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082198#4082198 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082198

18 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: mc release prep

by pgier

I created the pom-jdk14.xml in each of the projects for the jdk14 artifacts. When you build with "mvn -f pom-jdk14.xml" it will build the jdk14 stuff, and you can deploy it as jboss-container-jdk14, jboss-ejb-api-jdk14, etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082197#4082197 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082197

18 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failure on XAResourceRecoveryTest

by clebert.suconic＠jboss.com

The test fails on an assertion... It's rolling back instead of doing a commit. It's like initializing TxControl by hand is making Recovery "to think" that there is another Xid on the storage. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082194#4082194 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082194

18 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: mc release prep

by kabir.khan＠jboss.com

"adrian(a)jboss.org" wrote : "scott.stark(a)jboss.org" wrote : | | Like I said before. The container project (and the classloader project) | | shouldn't be in the MC build. They are only there because the MC was initially | | the major consumer while we developed them. | | If/when this is split out, can we have a separate artifacts from container for metadata etc. for JDK 1.4 like we do for JDK 5? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082192#4082192 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082192

18 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Redesign extended persistence context

by bstansberry＠jboss.com

To document our chat: In 4.2 it works like this: BeanA is the parent of a nested SFSB hierarchy. It holds a ref to the BeanB SBC (and to the XPC). The "one serialized unit" you mention is passivated under BeanA.id. When BeanB is passivated, what gets written to disk under BeanB.id is a ProxiedStatefulBeanContext; a proxy. If the user activates BeanB, the ProxiedStatefulBeanContext is activated and knows how to find BeanA's cache, find the BeanA SBC in that cache, and find the real BeanB SBC inside the BeanA SBC. The ProxiedStatefulBeanContext then delegates all calls to the real BeanB SBC. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082191#4082191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082191

18 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: mc release prep

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | Inside the appserver, the advice should be replaced with one that | (un)registers with the ServiceController. I've created this task: http://jira.jboss.com/jira/browse/JBMICROCONT-206 We should be able to just replace the advice for JBoss5-beta3 but it would be better to have this advice be more extensible instead of repeating code (a task for MC2-RC1). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082176#4082176 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082176

18 years, 7 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Deployer Changes for AOP

by adrian＠jboss.org

I've fixed the bootstrap-repo-beans.xml otherwise the testsuite will crash. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082169#4082169 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082169

18 years, 7 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: Shared session data, JBAS-1909

by ChristopheA

This is an old subject now... Could anybody from the JBoss AS team give us some feed back on session sharing at the ear level and JIRA http://jira.jboss.com/jira/browse/JBAS-2861 ? A month ago or so, the issue was still on JBoss 4.2.2 AS roadmap. Not any more... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082167#4082167 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082167

18 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: mc release prep

by adrian＠jboss.org

"sacha.labourey(a)jboss.com" wrote : "adrian(a)jboss.org" wrote : | | Why did you release 2.0.0.Beta4 without first a snapshot of the latest stuff in jboss-head? | | This will have to wait until RC1 now :-( | | Should we fix those and re-do a new beta ASAP? Actually, I don't think the problem is really in aop-mc-int anyway. The issue is that the default aspect from aop-mc-int registers directly with the MBeanServer. But the thing that gets registered implements ServiceMBeanSupport so it "lazily" registers itself with the ServiceController. This leads to double unregistration. Inside the appserver, the advice should be replaced with one that (un)registers with the ServiceController. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082166#4082166 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082166

18 years, 7 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 September 2007