You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Lou Amodeo (JIRA)" <tu...@ws.apache.org> on 2007/01/11 21:19:27 UTC
[jira] Created: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
NPE caused by null Constructor Definition when using componentType side file
-----------------------------------------------------------------------------
Key: TUSCANY-1045
URL: https://issues.apache.org/jira/browse/TUSCANY-1045
Project: Tuscany
Issue Type: Bug
Components: Java SCA Integration Tests
Reporter: Lou Amodeo
r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
// setup constructor injection
ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
d(JavaComponentBuilder.java:120)
at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
d(JavaComponentBuilder.java:53)
at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
stryImpl.java:106)
at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
ld(CompositeBuilder.java:56)
at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
stryImpl.java:106)
at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
:142)
at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
a:97)
at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
(AbstractRuntime.java:148)
at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
avenEmbeddedRuntime.java:135)
at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
tartMojo.java:296)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7 seconds
[INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
[INFO] Final Memory: 6M/30M
[INFO] ------------------------------------------------------------------------
C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
Component Type file:
<?xml version="1.0" encoding="ASCII"?>
<componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
<service name="CallBackCTypeService">
<interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
</service>
</componentType>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Resolved: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Sebastien Delfino resolved TUSCANY-1045.
---------------------------------------------
Resolution: Fixed
Fixed in revision r496640
> NPE caused by null Constructor Definition when using componentType side file
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1045
> URL: https://issues.apache.org/jira/browse/TUSCANY-1045
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Affects Versions: Java-SCA-M3
> Reporter: Lou Amodeo
> Assigned To: Luciano Resende
> Fix For: Java-SCA-M3
>
> Attachments: test-CallBackCType.zip
>
>
> r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
> // setup constructor injection
> ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
> java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
> [INFO] [tuscany-itest:start {execution: start}]
> [INFO] Starting Tuscany...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:120)
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:53)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
> ld(CompositeBuilder.java:56)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
> :142)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
> a:97)
> at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
> (AbstractRuntime.java:148)
> at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
> avenEmbeddedRuntime.java:135)
> at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
> tartMojo.java:296)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
> [INFO] Final Memory: 6M/30M
> [INFO] ------------------------------------------------------------------------
> C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
> Component Type file:
> <?xml version="1.0" encoding="ASCII"?>
> <componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
> <service name="CallBackCTypeService">
> <interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
> callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
> </service>
> </componentType>
>
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
Posted by "Lou Amodeo (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465436 ]
Lou Amodeo commented on TUSCANY-1045:
-------------------------------------
I am seeing that -967 is fixed. The fix for that is to copy the componentType file to the resources directory. The rev I have 496640 does have this modification to the test case packaging.
> NPE caused by null Constructor Definition when using componentType side file
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1045
> URL: https://issues.apache.org/jira/browse/TUSCANY-1045
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Affects Versions: Java-M3
> Reporter: Lou Amodeo
> Assigned To: Luciano Resende
> Fix For: Java-M3
>
> Attachments: test-CallBackCType.zip
>
>
> r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
> // setup constructor injection
> ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
> java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
> [INFO] [tuscany-itest:start {execution: start}]
> [INFO] Starting Tuscany...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:120)
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:53)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
> ld(CompositeBuilder.java:56)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
> :142)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
> a:97)
> at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
> (AbstractRuntime.java:148)
> at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
> avenEmbeddedRuntime.java:135)
> at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
> tartMojo.java:296)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
> [INFO] Final Memory: 6M/30M
> [INFO] ------------------------------------------------------------------------
> C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
> Component Type file:
> <?xml version="1.0" encoding="ASCII"?>
> <componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
> <service name="CallBackCTypeService">
> <interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
> callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
> </service>
> </componentType>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
Posted by "Luciano Resende (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luciano Resende updated TUSCANY-1045:
-------------------------------------
Fix Version/s: Java-M3
Affects Version/s: Java-M3
> NPE caused by null Constructor Definition when using componentType side file
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1045
> URL: https://issues.apache.org/jira/browse/TUSCANY-1045
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Affects Versions: Java-M3
> Reporter: Lou Amodeo
> Assigned To: Luciano Resende
> Fix For: Java-M3
>
> Attachments: test-CallBackCType.zip
>
>
> r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
> // setup constructor injection
> ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
> java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
> [INFO] [tuscany-itest:start {execution: start}]
> [INFO] Starting Tuscany...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:120)
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:53)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
> ld(CompositeBuilder.java:56)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
> :142)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
> a:97)
> at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
> (AbstractRuntime.java:148)
> at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
> avenEmbeddedRuntime.java:135)
> at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
> tartMojo.java:296)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
> [INFO] Final Memory: 6M/30M
> [INFO] ------------------------------------------------------------------------
> C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
> Component Type file:
> <?xml version="1.0" encoding="ASCII"?>
> <componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
> <service name="CallBackCTypeService">
> <interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
> callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
> </service>
> </componentType>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Assigned: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
Posted by "Luciano Resende (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luciano Resende reassigned TUSCANY-1045:
----------------------------------------
Assignee: Luciano Resende
> NPE caused by null Constructor Definition when using componentType side file
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1045
> URL: https://issues.apache.org/jira/browse/TUSCANY-1045
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Reporter: Lou Amodeo
> Assigned To: Luciano Resende
> Attachments: test-CallBackCType.zip
>
>
> r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
> // setup constructor injection
> ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
> java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
> [INFO] [tuscany-itest:start {execution: start}]
> [INFO] Starting Tuscany...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:120)
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:53)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
> ld(CompositeBuilder.java:56)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
> :142)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
> a:97)
> at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
> (AbstractRuntime.java:148)
> at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
> avenEmbeddedRuntime.java:135)
> at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
> tartMojo.java:296)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
> [INFO] Final Memory: 6M/30M
> [INFO] ------------------------------------------------------------------------
> C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
> Component Type file:
> <?xml version="1.0" encoding="ASCII"?>
> <componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
> <service name="CallBackCTypeService">
> <interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
> callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
> </service>
> </componentType>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
Posted by "Luciano Resende (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465351 ]
Luciano Resende commented on TUSCANY-1045:
------------------------------------------
Note that the all Tuscany extensions have the same behavior where the ComponentTypeLoader make the introspection and sideFile paths exclusive
> NPE caused by null Constructor Definition when using componentType side file
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1045
> URL: https://issues.apache.org/jira/browse/TUSCANY-1045
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Affects Versions: Java-M3
> Reporter: Lou Amodeo
> Assigned To: Luciano Resende
> Fix For: Java-M3
>
> Attachments: test-CallBackCType.zip
>
>
> r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
> // setup constructor injection
> ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
> java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
> [INFO] [tuscany-itest:start {execution: start}]
> [INFO] Starting Tuscany...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:120)
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:53)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
> ld(CompositeBuilder.java:56)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
> :142)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
> a:97)
> at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
> (AbstractRuntime.java:148)
> at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
> avenEmbeddedRuntime.java:135)
> at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
> tartMojo.java:296)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
> [INFO] Final Memory: 6M/30M
> [INFO] ------------------------------------------------------------------------
> C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
> Component Type file:
> <?xml version="1.0" encoding="ASCII"?>
> <componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
> <service name="CallBackCTypeService">
> <interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
> callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
> </service>
> </componentType>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464305 ]
Raymond Feng commented on TUSCANY-1045:
---------------------------------------
Here's the what's in the SCA spec about how the componentType should be loaded:
"The component type is calculated in two steps where the second step adds to the information found in the first step. Step one is introspecting the implementation (if possible), including the inspection of implementation annotations (if available). Step two covers the cases where introspection of the implementation is not possible or where it does not provide complete information and it involves looking for an SCA component type file. Component type information found in the component type file must be compatible with the equivalent information found from inspection of the implementation. The component type file can specify partial information, with the remainder being derived from the implementation. "
But the code in the JavaComponentTypeLoader make the two path exclusive:
public void load(CompositeComponent parent,
JavaImplementation implementation,
DeploymentContext deploymentContext) throws LoaderException {
Class<?> implClass = implementation.getImplementationClass();
URL resource = implClass.getResource(JavaIntrospectionHelper.getBaseName(implClass) + ".componentType");
PojoComponentType componentType;
if (resource == null) {
componentType = loadByIntrospection(parent, implementation, deploymentContext);
} else {
componentType = loadFromSidefile(parent, resource, deploymentContext);
}
implementation.setComponentType(componentType);
}
We need to merge the results from componentType file into the introspection step.
> NPE caused by null Constructor Definition when using componentType side file
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1045
> URL: https://issues.apache.org/jira/browse/TUSCANY-1045
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Reporter: Lou Amodeo
> Attachments: test-CallBackCType.zip
>
>
> r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
> // setup constructor injection
> ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
> java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
> [INFO] [tuscany-itest:start {execution: start}]
> [INFO] Starting Tuscany...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:120)
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:53)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
> ld(CompositeBuilder.java:56)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
> :142)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
> a:97)
> at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
> (AbstractRuntime.java:148)
> at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
> avenEmbeddedRuntime.java:135)
> at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
> tartMojo.java:296)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
> [INFO] Final Memory: 6M/30M
> [INFO] ------------------------------------------------------------------------
> C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
> Component Type file:
> <?xml version="1.0" encoding="ASCII"?>
> <componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
> <service name="CallBackCTypeService">
> <interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
> callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
> </service>
> </componentType>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
Posted by "Luciano Resende (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465341 ]
Luciano Resende commented on TUSCANY-1045:
------------------------------------------
Possible fix available, but then I start getting the issue described in http://issues.apache.org/jira/browse/TUSCANY-967, wasn't that fixed already ?
> NPE caused by null Constructor Definition when using componentType side file
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1045
> URL: https://issues.apache.org/jira/browse/TUSCANY-1045
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Affects Versions: Java-M3
> Reporter: Lou Amodeo
> Assigned To: Luciano Resende
> Fix For: Java-M3
>
> Attachments: test-CallBackCType.zip
>
>
> r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
> // setup constructor injection
> ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
> java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
> [INFO] [tuscany-itest:start {execution: start}]
> [INFO] Starting Tuscany...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:120)
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:53)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
> ld(CompositeBuilder.java:56)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
> :142)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
> a:97)
> at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
> (AbstractRuntime.java:148)
> at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
> avenEmbeddedRuntime.java:135)
> at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
> tartMojo.java:296)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
> [INFO] Final Memory: 6M/30M
> [INFO] ------------------------------------------------------------------------
> C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
> Component Type file:
> <?xml version="1.0" encoding="ASCII"?>
> <componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
> <service name="CallBackCTypeService">
> <interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
> callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
> </service>
> </componentType>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1045) NPE caused by null Constructor
Definition when using componentType side file
Posted by "Lou Amodeo (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lou Amodeo updated TUSCANY-1045:
--------------------------------
Attachment: test-CallBackCType.zip
> NPE caused by null Constructor Definition when using componentType side file
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1045
> URL: https://issues.apache.org/jira/browse/TUSCANY-1045
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Integration Tests
> Reporter: Lou Amodeo
> Attachments: test-CallBackCType.zip
>
>
> r494421. The test-CallBackCType test is failing with a NPE. This test case previously worked when using the workaround for Tuscany-967. It is using a componentType side file to specify a callback interface shown below. Problem appears that ctodDef is null.
> // setup constructor injection
> ConstructorDefinition<?> ctorDef = componentType.getConstructorDefinition();
> java:120 Constructor<?> constr = ctorDef.getConstructor(); Constructor Definition is null.
> [INFO] [tuscany-itest:start {execution: start}]
> [INFO] Starting Tuscany...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:120)
> at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.buil
> d(JavaComponentBuilder.java:53)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.implementation.composite.CompositeBuilder.bui
> ld(CompositeBuilder.java:56)
> at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegi
> stryImpl.java:106)
> at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java
> :142)
> at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav
> a:97)
> at org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScdl
> (AbstractRuntime.java:148)
> at org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(M
> avenEmbeddedRuntime.java:135)
> at org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(TuscanyS
> tartMojo.java:296)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:64)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:615)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Thu Jan 11 13:14:43 EST 2007
> [INFO] Final Memory: 6M/30M
> [INFO] ------------------------------------------------------------------------
> C:\Tuscany\LousTestCases\testing\sca\itest\test-CallBackCType>
> Component Type file:
> <?xml version="1.0" encoding="ASCII"?>
> <componentType xmlns="http://www.osoa.org/xmlns/sca/1.0" >
> <service name="CallBackCTypeService">
> <interface.java interface="org.apache.tuscany.sca.test.CallBackCTypeService"
> callbackInterface="org.apache.tuscany.sca.test.CallBackCTypeCallBack"/>
> </service>
> </componentType>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org