September 2008 - jboss-dev-forums

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by jaikiran

Andrew, I'm done with the changes including the review comments. I am planning to summarize the exact changes and even upload the new patch to the JIRA in my next post. Brian, As discussed in this thread, "bstansberry(a)jboss.com" wrote : | | If you refresh your ejb3 checkout, you'll find that there is a new ejb3 module added -- proxy-clustered. The classes in this module are mostly extensions of the ones in proxy that add the behavior necessary for cluster-aware proxies. | | Since these classes are extensions, there's a fair amount of overriding of protected methods, including some methods you're probably changing (e.g. JndiSessionRegistrarBase.createJndiReferenceBindingSet(...)). So, you're patch will need to include changes to proxy-clustered as well. AIUI, you're mostly working on passing an InvokableContext param instead of a bunch of details. The changes to proxy-clustered needed to handle that should be simple and pretty obvious. i have taken care of the necessary changes to the classes in proxy-clustered module. However, i see that the pom of proxy-clustered has a dependency on 0.1.2 version of proxy module: | <dependency> | <groupId>org.jboss.ejb3</groupId> | <artifactId>jboss-ejb3-proxy</artifactId> | <version>0.1.2</version> | </dependency> Is there any specific reason for this dependency? For integrating the changes in the proxy module with the proxy-clustered module, i would have to use a higher version of ejb3-proxy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177800#4177800 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177800

17 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Internal Evaluation - JBoss ESB more or less useless

by mark.little＠jboss.com

Just to re-enforce what Kev has said, if there are any issues then the best way of finding out what is going on (problems with our stuff, problems with yours) is to post specific requests to the forums and go into as much detail as you can. I wouldn't confuse the postings by putting a lot of information into each posting: forum posts are cheap, so if you have N separate problems to discuss then post N separate entries. If it turns out there are issues, then either you or we can raise JIRAs to get them fixed: that's in the best interests of the entire community, after all. Obviously buying a support contract gets you more dedicated help and better/quicker responses, but the forums are here for a reason too. Use them. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177779#4177779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177779

17 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Annoyance when running unit tests in eclipse

by timfox

Ok. so I worked out where logs from running tests in eclipse goes - it uses the main log4g config from src/config so the logs go in trunk/logs. This is all back to front and upside down. We should have: 1 main log4j config file which lives in src/config this is used for server logging, not for tests. 1 log4j config file in tests/config - this is used for tests and nothing else. "Tests" include: a) Tests run in eclipse b) Tests run using runtest on the command line c) Tests run using ant from command line (normal test suite) For consistency test log4j output should go to tests/logs, not tests/output/logs or tests/build/logs or anywhere else. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177777#4177777 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177777

17 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Annoyance when running unit tests in eclipse

by timfox

Seems like this whole test logging thing is a complete mess.. Needs a cleanup. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177776#4177776 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177776

17 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Annoyance when running unit tests in eclipse

by timfox

"ataylor" wrote : Ok, Ive fixed it. tests/config was ahead of src/config in the classpath. When i added the log4j file to tests/config it was picked up first. Ive switched these around. | | But these are tests. Surely they should be using log4j.xml from tests/config *not* src/config!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177775#4177775 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177775

17 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Annoyance when running unit tests in eclipse

by timfox

I'm confused. I seem to have one log file in tests/output/logs, another one in tests/build/logs neither of which are the output of the unit tests when run in eclipse. Can't we just have one config and one log file for eclipse. Also, I thought we got rid of the convention of using output dirs, and use build everywhere?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177774#4177774 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177774

17 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Internal Evaluation - JBoss ESB more or less useless

by Kevin.Conner＠jboss.com

In that case it would be a better approach if you provided us with some decent (for that read constructive) feedback. We have no idea what you have been trying to do nor what issues you may have identified. It could be a simple misunderstanding, misconfiguration or indeed a bug on our part. We are not perfect, nor do we claim to be, but we do try our best to help when people have issues. Having said that, this is a forum and is supported on a 'best effort' basis. This will sometimes mean that our responses are tardy as our efforts may be directed elsewhere. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177773#4177773 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177773

17 years, 6 months

1
0
0 / 0

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

by pgier

Here is a summary of the changes to the aop build so far. The aop module is now built with maven, so running "mvn install" from the aop module directory will run this part of the build. Running the tests can still be done with "ant -f build-tests-jdk50.xml tests" after the maven build is run. It looks like ant is compiling the tests twice, is this intentional? The combined aop build can be run from the build directory can still be run using build.sh or build.bat. To compile the JRockit stuff you have to pass JROCKIT_HOME to maven. This can be done in the aop directory using mvn install -DJROCKIT_HOME=/path/to/jrockit or from the main build directory ./build.sh -Dbuild.maven.opts=-DJROCKIT_HOME=/path/to/jrockit I'm planning to move the asintegration and aspects modules to maven on Monday. That will allow the entire build (except for the testsuite) to be run from the root directory using "mvn install". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177760#4177760 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177760

17 years, 6 months

1
0
0 / 0

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

by pgier

While working on this, I came up with a few questions about how the AOP build is supposed to work. First, should the artifactId be "jboss-aop" or "jboss-aop-jdk50"? Currently, we have two different artifactIds representing the same artifact, so I would like to combine them into one. Since we don't have other artifacts with the jdk version in the id, I would prefer just "jboss-aop". I am a little confused by the setup of building the jrockit-pluggable-instrumentor.jar. In the ant build, there are three files included in this jar: JDK14Transformer.class JDK14TransformerManager.class JRockitPluggableClassPreProcessor.class All three of these files are also included in the jboss-aop-jdk50.jar file. Do these files need to be in both places? Can I move these files out into the new pluggable-instrumentor module? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177759#4177759 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177759

17 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - jbpm-3.3.0.CR1

by thomas.diesler＠jboss.com

Dear Folks, I am pleased to announce that we have just released jbpm-3.3.0.CR1. This release was mainly about productization issues like * SVN source repository * Maven build system * Automated Hudson QA * IzPack based Installer * Defined set of target containers * Defined set of target databases * Bug fixes Prove that we actually did it is here in our Hudson Matrix http://jbpm.dyndns.org:8280/hudson/job/jBPM-Matrix More detailed Release Notes are here https://jira.jboss.org/jira/secure/ReleaseNote.jspa?projectId=10052&style... Finally I'd like to thank everybody who helped to make this release happen. cheers -thomas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177737#4177737 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177737

17 years, 6 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