September 2008 - jboss-dev-forums

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by pgier

"kabir.khan(a)jboss.com" wrote : Once the new build is complete, will we need the thirdparty folder? In one way I like it (probably due to old habit), but having things duplicated seems unnecessary. In AS I like the thirdparty folder since it makes it easier to test new versions of thirdparty dependencies locally, but in aop we don't really have that many dependencies. We'll need it for a little while so that the tests scripts can still use it for their classpaths. But eventually I'll update the test scripts to generate their classpaths from the pom and then I think we won't need the thirdparty dir. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178406#4178406 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178406

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by pgier

"kabir.khan(a)jboss.com" wrote : "pgier" wrote : If you run the build from the main build directory you have to pass the parameter like this: | | ./build.sh -Dbuild.maven.opts=-DJROCKIT_HOME=/path/to/jrockit | | | | Otherwise it doesn't get through to the maven build. | I added a build/build-release.sh to avoid having to remember that :-) | I made a couple of improvements now to the jrockit handling so I think you won't need this anymore. You now have a few options. 1. Add a local.properties file to the build directory and ant will pick it up and pass to maven. 2. Call ./build.sh or ant from the build directory and pass -Djrockit.home=/path/to/jrockit 3. Or if you are running "mvn" directly from the root directory or the aop directory you can use something like option 2 mvn install -Djrockit.home=/path/to/jrockit Hopefully this makes things a little easier. I also updated the hudson configs so that they use the local.properties file like before. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178405#4178405 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178405

17 years, 3 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Datasources not parsing jboss.server.data.dir

by adrian＠jboss.org

It also looks like you broke the smoke tests? | Caused by: java.lang.IllegalArgumentException: Wrong value: ${org.jboss.test.jca.xads.SomeProperty} | at org.jboss.test.jca.xads.TestXADataSource.setSomeProperty(TestXADataSource.java:43) | at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:577) | at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:449) | at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:409) | at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:611) | at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:257) | at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:607) | at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:354) | at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381) | at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:409) | at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:854) | at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89) | at org.jboss.test.jca.xads.Test.test(Test.java:46) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178385#4178385 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178385

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM Classloading

by camunda

Hi Bjoern, did you use the proposed solution in your project? I wanted to use it for an own problem with classloading (and I can also commit it back to jbpm after it works correctly) but have the problem, that this is leading to and endless loop, since the classloader is already needed to load the jbpm.cfg.xml in the JbpmConfiguration (InputStream jbpmCfgXmlStream = ClassLoaderUtil.getStream(resource);). Exception StackTrace: | at org.jbpm.util.ClassLoaderUtil.getClassLoader(ClassLoaderUtil.java:50) | at org.jbpm.util.ClassLoaderUtil.getStream(ClassLoaderUtil.java:83) | at org.jbpm.JbpmConfiguration.getInstance(JbpmConfiguration.java:279) | at org.jbpm.JbpmConfiguration.getInstance(JbpmConfiguration.java:257) | at org.jbpm.JbpmConfiguration$Configs.getObjectFactory(JbpmConfiguration.java:418) | at org.jbpm.JbpmConfiguration$Configs.hasObject(JbpmConfiguration.java:426) | at org.jbpm.util.ClassLoaderUtil.getClassLoader(ClassLoaderUtil.java:50) | How did you solve this? Thanks Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178371#4178371 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178371

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

Once the new build is complete, will we need the thirdparty folder? In one way I like it (probably due to old habit), but having things duplicated seems a unnecessary. In AS I like the thirdparty folder since it makes it easier to test new versions of thirdparty dependencies locally, but in aop we don't really have that many dependencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178361#4178361 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178361

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - add

by camunda

Hi. I found a not so nice design detail of the CommandService: The Command.execute throws an Exception, the CommandService.execute not. I think either both or none should add "throws Exception" to the signature. But I think it would not be the best idea to change the signature of the CommandService now, what do you guys think? Maybe this should be addressed in the PVM? Or do you think it is fine like this? Cheers Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178351#4178351 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178351

17 years, 3 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Datasources not parsing jboss.server.data.dir

by adrian＠jboss.org

I guess you missed my post? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178350#4178350 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178350

17 years, 3 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Datasources not parsing jboss.server.data.dir

by alex.loubyansky＠jboss.com

I committed this. But it covers only string-based properties. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178333#4178333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178333

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

"pgier" wrote : If you run the build from the main build directory you have to pass the parameter like this: | ./build.sh -Dbuild.maven.opts=-DJROCKIT_HOME=/path/to/jrockit | | Otherwise it doesn't get through to the maven build. I added a build/build-release.sh to avoid having to remember that :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178317#4178317 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178317

17 years, 3 months

1
0
0 / 0

[Design of the JBoss EJB Container] - Container artifacts should have symmetric lifecycles

by emuckenhuber

I've started to write some basic tests for ejb container lifecycle, based on the cts.tests from the testsuite for: https://jira.jboss.org/jira/browse/JBAS-5332 So basically what i do is: - deploy the cts.jar - run a cts tests - call the serviceController to do a stop/destroy/create/start on the tested bean - run the test a 2nd time - undeploy the cts.jar I do that for the container, then for the cache, the pool. This was actually not working for any container. So i've moved some obvious things around, which should put that in a better shape. Still - after talking to Alexey it seems that it could be a bit more difficult doing the same with CMP. At the moment the persistenceManager is created/stopped/destroyed in the entityContainer itself and started in the EJBModule. And it seems that it's needed to be started in that way. But this makes the bean not usable after restarting just the container - moving this parts into the EJBModule seems to work (at least for the simple testcase). But i still don't know whether this makes sense or not? Most probably we also need to do a bit more testing to make sure that it's really function correctly, but at least those tests exposed some problems. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178316#4178316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178316

17 years, 3 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 2008