You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Ignacio Silva-Lepe <is...@verizon.net> on 2006/07/20 18:06:07 UTC
Async Java Target Invoker
I have an initial pass at a replacement for one-way async support using a target invoker rather than an interceptor. I have been able to test it in chianti and ported it to the latest trunk. For some reason having to do with SCA SPI test failures, I can't successfully build the man trunk yet so I haven't yet verified the target invoker there. In any case, in the interest of having something go into the trunk sooner rather than later, here's the patch.
Notice that the target invoker should be using a monitor to flag an error during invoke on a separate thread. However, trying to use a monitor I get the build error (in chianti) below. So, I have commented out use of a monitor for now.
Running localwire.LocalWireTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.511 sec <<< FA
ILURE!
testMessage(localwire.LocalWireTestCase) Time elapsed: 0.501 sec <<< ERROR!
org.apache.tuscany.spi.builder.BuilderConfigException: No builder registered for
implementation [org.apache.tuscany.core.implementation.java.JavaImplementation]
Context stack trace: [TargetComponent]
at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
stryImpl.java:93)
at org.apache.tuscany.core.implementation.system.builder.SystemComposite
Builder.build(SystemCompositeBuilder.java:97)
at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
stryImpl.java:99)
at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
:125)
at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
a:91)
at org.apache.tuscany.core.launcher.Launcher.bootApplication(Launcher.ja
va:195)
at org.apache.tuscany.test.SCATestCase.setUp(SCATestCase.java:40)
at junit.framework.TestCase.runBare(TestCase.java:125)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.jav
a:210)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes
tSet(AbstractDirectoryTestSuite.java:135)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab
stractDirectoryTestSuite.java:122)
at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(Su
refireBooter.java:225)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j
ava:747)
Results :
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
Re: Async Java Target Invoker
Posted by Jim Marino <ji...@gmail.com>.
Hi Ignacio,
The test case issue is due to assertions getting
On Jul 20, 2006, at 9:06 AM, Ignacio Silva-Lepe wrote:
> I have an initial pass at a replacement for one-way async support
> using a target invoker rather than an interceptor. I have been able
> to test it in chianti and ported it to the latest trunk. For some
> reason having to do with SCA SPI test failures, I can't
> successfully build the man trunk yet so I haven't yet verified the
> target invoker there. In any case, in the interest of having
> something go into the trunk sooner rather than later, here's the
> patch.
> Notice that the target invoker should be using a monitor to flag an
> error during invoke on a separate thread. However, trying to use a
> monitor I get the build error (in chianti) below. So, I have
> commented out use of a monitor for now.
>
> Running localwire.LocalWireTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.511 sec <<< FA
> ILURE!
> testMessage(localwire.LocalWireTestCase) Time elapsed: 0.501 sec
> <<< ERROR!
> org.apache.tuscany.spi.builder.BuilderConfigException: No builder
> registered for
> implementation
> [org.apache.tuscany.core.implementation.java.JavaImplementation]
>
> Context stack trace: [TargetComponent]
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build
> (BuilderRegi
> stryImpl.java:93)
> at
> org.apache.tuscany.core.implementation.system.builder.SystemComposite
> Builder.build(SystemCompositeBuilder.java:97)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build
> (BuilderRegi
> stryImpl.java:99)
> at org.apache.tuscany.core.deployer.DeployerImpl.build
> (DeployerImpl.java
> :125)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy
> (DeployerImpl.jav
> a:91)
> at org.apache.tuscany.core.launcher.Launcher.bootApplication
> (Launcher.ja
> va:195)
> at org.apache.tuscany.test.SCATestCase.setUp
> (SCATestCase.java:40)
> at junit.framework.TestCase.runBare(TestCase.java:125)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:
> 124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute
> (JUnitTestSet.jav
> a:210)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes
> tSet(AbstractDirectoryTestSuite.java:135)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab
> stractDirectoryTestSuite.java:122)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(Su
> refireBooter.java:225)
> at org.apache.maven.surefire.booter.SurefireBooter.main
> (SurefireBooter.j
> ava:747)
>
>
> Results :
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> <AsyncJavaTargetInvokerPatch.txt>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Async Java Target Invoker
Posted by Jim Marino <jm...@myromatours.com>.
Hi Ignacio,
The test case failure is due to the assertion problem that was
outlined in another threead (just change MAVEN_OPTS to have -ea).
I'll submit the patch as soon as I clear out another checkin I have
on my machine and will take a look at the monitor problem as well.
Thanks,
Jim
On Jul 20, 2006, at 9:06 AM, Ignacio Silva-Lepe wrote:
> I have an initial pass at a replacement for one-way async support
> using a target invoker rather than an interceptor. I have been able
> to test it in chianti and ported it to the latest trunk. For some
> reason having to do with SCA SPI test failures, I can't
> successfully build the man trunk yet so I haven't yet verified the
> target invoker there. In any case, in the interest of having
> something go into the trunk sooner rather than later, here's the
> patch.
> Notice that the target invoker should be using a monitor to flag an
> error during invoke on a separate thread. However, trying to use a
> monitor I get the build error (in chianti) below. So, I have
> commented out use of a monitor for now.
>
> Running localwire.LocalWireTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.511 sec <<< FA
> ILURE!
> testMessage(localwire.LocalWireTestCase) Time elapsed: 0.501 sec
> <<< ERROR!
> org.apache.tuscany.spi.builder.BuilderConfigException: No builder
> registered for
> implementation
> [org.apache.tuscany.core.implementation.java.JavaImplementation]
>
> Context stack trace: [TargetComponent]
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build
> (BuilderRegi
> stryImpl.java:93)
> at
> org.apache.tuscany.core.implementation.system.builder.SystemComposite
> Builder.build(SystemCompositeBuilder.java:97)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build
> (BuilderRegi
> stryImpl.java:99)
> at org.apache.tuscany.core.deployer.DeployerImpl.build
> (DeployerImpl.java
> :125)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy
> (DeployerImpl.jav
> a:91)
> at org.apache.tuscany.core.launcher.Launcher.bootApplication
> (Launcher.ja
> va:195)
> at org.apache.tuscany.test.SCATestCase.setUp
> (SCATestCase.java:40)
> at junit.framework.TestCase.runBare(TestCase.java:125)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:
> 124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute
> (JUnitTestSet.jav
> a:210)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes
> tSet(AbstractDirectoryTestSuite.java:135)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab
> stractDirectoryTestSuite.java:122)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(Su
> refireBooter.java:225)
> at org.apache.maven.surefire.booter.SurefireBooter.main
> (SurefireBooter.j
> ava:747)
>
>
> Results :
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> <AsyncJavaTargetInvokerPatch.txt>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org