September 2007 - jboss-dev-forums

[Design of JBoss Build System] - Re: Cannot release javaee project

by wolfc

I got a subcomponent jboss-ejb3-cache which is dependent on jboss-ejb-api 3.0.0. Either I'm going to depend on jboss-javaee (bummer) or we need the individuals. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082003#4082003 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082003

18 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Cannot release javaee project

by scott.stark＠jboss.org

The release process for the javaee project is not working, so only the aggregate jboss-javaee.jar at version 5.0.0.Beta3 is valid in terms of its version. I probably should just delete all of the individual javaee artifacts until javaee is at GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081952#4081952 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081952

18 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Cannot release javaee project

by wolfc

Some issues: SNAPSHOTS in: - jboss-ejb-api/pom.xml - jboss-jacc-api/pom.xml jboss-jaspi-api is a PR, not 1.0 final. Do we include it as a tech preview? Or supported? If tech preview, then I don't think we should put it in the agregator, because we might want to change it soon after release. Currently that'll change the jboss-javaee artifact and thus a new version would be required (and thus new integration). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081948#4081948 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081948

18 years, 7 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Deployer order solely based on inputs/outputs now?

by wolfc

http://jira.jboss.com/jira/browse/EJBTHREE-811 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081944#4081944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081944

18 years, 7 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Deployer order solely based on inputs/outputs now?

by wolfc

Yes, and I want each deployer to use a clean SPI. So no use of InjectionContainer which is too bloated. But one created in projects/integration based on the org.jboss.ejb3.javaee interfaces. After the describe phase each JavaEEComponent should be able to answer the questions in the interface. (I don't like the createObjectName methods. Maybe getComponent(name) on JavaEEModule level and getModule(name) on JavaEEApplication. If we add generics we could even specify what kind of components are in the module. Hmm EE 6 clash, getComponent(name, type).) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081943#4081943 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081943

18 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: KernelRegistryPlugins and dependencies

by wolfc

For option 2 we could use javax.naming.event. But what's the advantage compared to the current JNDIKernelRegistryPlugin? I don't like the threads in option 3. How about something like EjbLinkDemandMetaData (RemoteJNDIDemandMetaData)? It can do a lookup remotely when resolving is needed. Do we ever have a dependency on a remote JNDI? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081942#4081942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081942

18 years, 7 months

1
0
0 / 0

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

by clebert.suconic＠jboss.com

I need some help understanding this... XAResourceRecoveryTest::testRecoveryOnSend will aways fail if running after XARecoveryTest::testMockCoordinatorRecoveryWithJBossTSXids. After some investigation, XAResourceRecoveryTest would fail by simply initializing TxControl by calling any method (such as TxControl.isEnabled()). http://anonsvn.jboss.org/repos/messaging/trunk/tests/src/org/jboss/test/m... This is because testMockCoordinatorRecoveryWithJBossTSXids is instantiating com.arjuna.ats.jta.xa.XidImple, and that is initializing TxControl which is starting a ObjectStore. Later on testRecoveryOnSend, the test would get a message "Told not to rollback {0}" on logs. I still don't know what's the reason but any help is welcome. I was considering to comment the Mock Test out until we find a way to use the XidImple directly. Clebert View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081936#4081936 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081936

18 years, 7 months

1
0
0 / 0

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

by scott.stark＠jboss.org

The basic mc 2.0.0.Beta4 is released and is now used by jboss5. The aggregate assembly seems broken so I don't know if we are putting out a standalone release as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081925#4081925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081925

18 years, 7 months

1
0
0 / 0

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

by scott.stark＠jboss.org

The aop 2.0.0.alpha6 and mc 2.0.0.Beta4 release are ready, but there is a temp AspectDeployer that is broken. I assume this is due to the class loading being in flux. I have commented out the JBossScopedClassLoaderHelper usage. | [javac] Compiling 43 source files to /home/svn/JBossHead/jboss-head/system/output/classes | /home/svn/JBossHead/jboss-head/system/src/main/org/jboss/aop/deployers/temp/AspectDeployer.java:36: package org.jboss.aop.deployment does not exist | import org.jboss.aop.deployment.JBossScopedClassLoaderHelper; | ^ | /home/svn/JBossHead/jboss-head/system/src/main/org/jboss/aop/deployers/temp/AspectDeployer.java:39: warning: [deprecation] org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer in org.jboss.deployers.vfs.spi.deployer has been deprecated | import org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer; | ^ | /home/svn/JBossHead/jboss-head/system/src/main/org/jboss/aop/deployers/temp/AspectDeployer.java:56: warning: [deprecation] org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer in org.jboss.deployers.vfs.spi.deployer has been deprecated | public class AspectDeployer extends AbstractVFSRealDeployer | ^ | /home/svn/JBossHead/jboss-head/system/src/main/org/jboss/aop/deployers/temp/AspectDeployer.java:368: cannot find symbol | symbol : variable JBossScopedClassLoaderHelper | location: class org.jboss.aop.deployers.temp.AspectDeployer | if (JBossScopedClassLoaderHelper.isScopedClassLoader(unit.getClassLoader())) | ^ | 2 errors | 2 warnings | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081921#4081921 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081921

18 years, 7 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Deployer order solely based on inputs/outputs now?

by bill.burke＠jboss.com

The only thing about this is that there would need to be a JavaEEDescribeDeployer that would need to work with EJBs, Servlets and any other EE component that uses EE XML/annotation component references. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081906#4081906 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081906

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