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

[Design of JBoss jBPM] - Re: releasing 3.2.Beta1

by tom.baeyens＠jboss.com

i have updated the file definition so that a null value is returned if the file doesn't exist. most part of the webapp is updated for this. but the view should be redirected to the process instance view instead of the task instance view in case a process is started without a start task. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997357#3997357 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997357

17 years, 12 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Update AOPTestDelegate to better integrate into eclipse

by kabir.khan＠jboss.com

The initialization of the AOPSetup/TestDelegate results from the testcase setUp() method. Once that is called the class has already been loaded: | Thread [main] (Suspended (breakpoint at line 39 in AOPTestDelegate)) | AOPTestDelegate.<init>(Class) line: 39 | AOPTestWithSetup.getDelegate(Class) line: 51 | NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] | NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39 | DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 | Method.invoke(Object, Object...) line: 585 | AbstractTestDelegate.getDelegate(Class) line: 70 | AbstractTestSetup.setUp() line: 62 | AOPArrayTestCase(AbstractTestCaseWithSetup).setUp() line: 90 | AOPArrayTestCase(TestCase).runBare() line: 125 | TestResult$1.protect() line: 106 | TestResult.runProtected(Test, Protectable) line: 124 | TestResult.run(TestCase) line: 109 | AOPArrayTestCase(TestCase).run(TestResult) line: 118 | TestSuite.runTest(Test, TestResult) line: 208 | TestSuite.run(TestResult) line: 203 | TestSuite.runTest(Test, TestResult) line: 208 | TestSuite.run(TestResult) line: 203 | JUnit3TestReference.run(TestExecution) line: 128 | TestExecution.run(ITestReference[]) line: 38 | RemoteTestRunner.runTests(String[], String, TestExecution) line: 460 | RemoteTestRunner.runTests(TestExecution) line: 673 | RemoteTestRunner.run() line: 386 | RemoteTestRunner.main(String[]) line: 196 | The classloader uses whatever -aop.xml info has been deployed in AOP to determine if the class should be woven, in other words having this deployed by the Setup/Delegate is too late. 2 possible solutions: 1) Refactor all existing xxxTestCase classes to xxxTestCaseDelegate and create new xxxTestCase classes delegating to the xxxTestCaseDelegate 2) Create a new javaagent that delegates to the exisiting transformer. This transformer should be able to leverage the existing transformer for it's work and deploy use the info about the testcase to 1) is a pain, and 2) while conceptually straight-forward is complicated by the fact that there doesn't seem to be a way to tell which test is being run. One option though could be to have my classloader dig into the junit stack, and weave the org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main() method so this information is available in a system property somewhere. Eclipse seems to load that class for each test run. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997352#3997352 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997352

17 years, 12 months

1
0
0 / 0

[Design of Security on JBoss] - SecurityDeployer needs to be more selective about what is pr

by scott.stark＠jboss.org

Starting the all configuration is producing a duplicate mbean problem as mentioned here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997313#3997313 The SecurityDeployer needs to be looking for some security related metadata to trigger its behavior. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997344#3997344 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997344

17 years, 12 months

1
0
0 / 0

[Design of JBoss Web Services] - New jboss version info attributes

by dimitris＠jboss.org

Just saw 4 new attributed added to jboss.system:type=ServerConfig mbean (I'm posting here 'cause Thomas added them) SpecificationTitle (JBoss) ImplementationTitle (JBoss [Trinity]) and ImplementationVersion (4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200701021921)) are either obvious or exist already in a jboss.system:type=Server mbean: Version (4.2.0CR1(build: CVSTag=JBoss_4_2_0_CR1 date=200701021921)) VersionName (Trinity) The only useful addition seems to be the SpecificationVersion (4.2.0.CR1) which again looks more appropriate to appear in jboss.system:type=Server mbean as, e.g., VersionNumber, VersionId, or similar. Are those new attributes used somewhere? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997343#3997343 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997343

17 years, 12 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Update AOPTestDelegate to better integrate into eclipse

by scott.stark＠jboss.org

Its not clear why the aop processing cannot be done before the test classes are loaded by expanding the AOPTestWithSetup/AOPTestDelegate. It should just require an aop aware class loader be installed at the proper level in the test harness. I assume this is what the javaagent is doing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997342#3997342 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997342

17 years, 12 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SecurityContext

by scott.stark＠jboss.org

This has to be part of the client proxy interceptor stack. Today there is only the SecurityInterceptor that accesses the SecurityAssociation. The interceptor stack associated with a proxy needs to include whatever security aspects are needed based on the security metadata. One way would be to include several different security interceptors in the proper order so that the aggregate security context of the call is correct. Some interceptors may do nothing if there already is a security context associated with the call while others may augment it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997339#3997339 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997339

17 years, 12 months

1
0
0 / 0

[Design of POJO Server] - Re: Problem deploying a -beans.xml in a SAR

by scott.stark＠jboss.org

This is a problem with the beans created by the SecurityDeployer. It is not being selective enough about what contexts its processing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997332#3997332 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997332

17 years, 12 months

1
0
0 / 0

[Design of JBossCache] - Re: Serialization Compatibility Tests

by ryan.campbell＠jboss.com

Manik, Where should we document this test case? A readme in the src/etc folder? Somewhere else? Thanks, Ryan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997331#3997331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997331

17 years, 12 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Code Coverage in JBoss AS Test Suite

by ryan.campbell＠jboss.com

Oops, you are right, sorry. Will delete the bad postings. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997330#3997330 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997330

17 years, 12 months

1
0
0 / 0

[Design of JBoss ESB] - Re: JMS Provider(s) Design - JBossMQ/JBossMessaging/ActiveMQ

by jeffdelong

I removed xml-apis-1.3.02.jar and xercesImpl-2.7.1 from the jbossesb.sar and the second exception appears to have gone away. There are versions of these jars in jboss-4.0.5/lib/endorsed (xalan.jar is in lib and the sar as ell). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997328#3997328 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997328

17 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007