[jira] Assigned: (TUSCANY-1791) binding-notification-* samples don't work
[
https://issues.apache.org/jira/browse/TUSCANY-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe reassigned TUSCANY-1791:
---
Assignee: Ignacio Silva-Lepe
binding-notification-* samples don't work
-
Key: TUSCANY-1791
URL: https://issues.apache.org/jira/browse/TUSCANY-1791
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects Versions: Java-SCA-1.0
Environment: Windows XP
Reporter: Simon Nash
Assignee: Ignacio Silva-Lepe
Fix For: Java-SCA-1.0.1
I tried to run the binding-notification-* samples from the 1.0 rc3a binary
distro by following the README instructions. I always get a failure on the
second application that starts. I tried various different combinations of
which application to start first and which to start second and the failure
was consistent. For example, if I start the consumer first on port 8083 and
then the producer second on port 8084, I see the following exception from the
producer:
H:\tuscany-1.0-rc3a\tuscany-sca-1.0-incubating\samples\binding-notification-producerjava
-Dnotification.httpPort=8084 -cp
target\sample-binding-notification-producer-1.0-incubating.jar;%TUSCANY_SCA_MANIFEST_JAR%
notification.producer.TrafficAdvisoryServer
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.
exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]:
[1,0]
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:610)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:95)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:51)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl.newProducer(NotificationTypeManagerImpl.java:150)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.deployProducer(NotificationReferenceBindingProvider.java:170)
at
org.apache.tuscany.sca.binding.notification.NotificationBindingProviderFactory.referenceProviderStarted(NotificationBindingProviderFactory.java:186)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.start(NotificationReferenceBindingProvider.java:159)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:456)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:186)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69)
at
notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServer.java:31)
Caused by:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col
{unknown-source}]: [1,0]
at
org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:65)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:607)
... 11 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at
[row,col {unknown-source}]: [1,0]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661)
at
com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:60)
... 12 more
org.osoa.sca.ServiceRuntimeException: java.lang.RuntimeException:
java.lang.RuntimeException:
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col
{unknown-source}]: [1,0]
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69)
at
notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServer.java:31)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
[jira] Resolved: (TUSCANY-1791) binding-notification-* samples don't work
[
https://issues.apache.org/jira/browse/TUSCANY-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe resolved TUSCANY-1791.
-
Resolution: Fixed
I have verified that the binding notification samples run without the
unexpected EOF failure
binding-notification-* samples don't work
-
Key: TUSCANY-1791
URL: https://issues.apache.org/jira/browse/TUSCANY-1791
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects Versions: Java-SCA-1.0
Environment: Windows XP
Reporter: Simon Nash
Assignee: Ignacio Silva-Lepe
Fix For: Java-SCA-1.0.1
I tried to run the binding-notification-* samples from the 1.0 rc3a binary
distro by following the README instructions. I always get a failure on the
second application that starts. I tried various different combinations of
which application to start first and which to start second and the failure
was consistent. For example, if I start the consumer first on port 8083 and
then the producer second on port 8084, I see the following exception from the
producer:
H:\tuscany-1.0-rc3a\tuscany-sca-1.0-incubating\samples\binding-notification-producerjava
-Dnotification.httpPort=8084 -cp
target\sample-binding-notification-producer-1.0-incubating.jar;%TUSCANY_SCA_MANIFEST_JAR%
notification.producer.TrafficAdvisoryServer
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.
exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]:
[1,0]
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:610)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:95)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:51)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl.newProducer(NotificationTypeManagerImpl.java:150)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.deployProducer(NotificationReferenceBindingProvider.java:170)
at
org.apache.tuscany.sca.binding.notification.NotificationBindingProviderFactory.referenceProviderStarted(NotificationBindingProviderFactory.java:186)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.start(NotificationReferenceBindingProvider.java:159)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:456)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:186)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69)
at
notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServer.java:31)
Caused by:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col
{unknown-source}]: [1,0]
at
org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:65)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:607)
... 11 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at
[row,col {unknown-source}]: [1,0]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661)
at
com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:60)
... 12 more
org.osoa.sca.ServiceRuntimeException: java.lang.RuntimeException:
java.lang.RuntimeException:
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col
{unknown-source}]: [1,0]
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69)
at
notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServer.java:31)
Caused by:
[jira] Resolved: (TUSCANY-1603) Notification samples don't have ant scripts
[ https://issues.apache.org/jira/browse/TUSCANY-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe resolved TUSCANY-1603. - Resolution: Fixed Fix Version/s: (was: Java-SCA-Next) Java-SCA-1.0.1 The ant scripts are now included in the 1.0.1 release Notification samples don't have ant scripts --- Key: TUSCANY-1603 URL: https://issues.apache.org/jira/browse/TUSCANY-1603 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-0.99 Environment: Windows XP Reporter: Simon Nash Assignee: Ignacio Silva-Lepe Priority: Minor Fix For: Java-SCA-1.0.1 In the 0.99 binary distro, the following samples don't have ant scripts: binding-notification-broker binding-notification-consumer binding-notification-producer implementation-notification -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-1603) Notification samples don't have ant scripts
[ https://issues.apache.org/jira/browse/TUSCANY-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe reassigned TUSCANY-1603: --- Assignee: Ignacio Silva-Lepe Notification samples don't have ant scripts --- Key: TUSCANY-1603 URL: https://issues.apache.org/jira/browse/TUSCANY-1603 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-0.99 Environment: Windows XP Reporter: Simon Nash Assignee: Ignacio Silva-Lepe Priority: Minor Fix For: Java-SCA-1.0.1 In the 0.99 binary distro, the following samples don't have ant scripts: binding-notification-broker binding-notification-consumer binding-notification-producer implementation-notification -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-1799) ant script needed for implementation-notification sample
[ https://issues.apache.org/jira/browse/TUSCANY-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe reassigned TUSCANY-1799: --- Assignee: Ignacio Silva-Lepe ant script needed for implementation-notification sample Key: TUSCANY-1799 URL: https://issues.apache.org/jira/browse/TUSCANY-1799 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.0 Environment: All Reporter: Simon Nash Assignee: Ignacio Silva-Lepe Priority: Minor Fix For: Java-SCA-1.0.1 The implementation-notification sample doesn't have an ant scipt. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-1799) ant script needed for implementation-notification sample
[ https://issues.apache.org/jira/browse/TUSCANY-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe updated TUSCANY-1799: Fix Version/s: (was: Java-SCA-Next) Java-SCA-1.0.1 ant script needed for implementation-notification sample Key: TUSCANY-1799 URL: https://issues.apache.org/jira/browse/TUSCANY-1799 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.0 Environment: All Reporter: Simon Nash Assignee: Ignacio Silva-Lepe Priority: Minor Fix For: Java-SCA-1.0.1 The implementation-notification sample doesn't have an ant scipt. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-1799) ant script needed for implementation-notification sample
[ https://issues.apache.org/jira/browse/TUSCANY-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe resolved TUSCANY-1799. - Resolution: Fixed The ant scripts are now included in the 1.0.1 release ant script needed for implementation-notification sample Key: TUSCANY-1799 URL: https://issues.apache.org/jira/browse/TUSCANY-1799 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.0 Environment: All Reporter: Simon Nash Assignee: Ignacio Silva-Lepe Priority: Minor Fix For: Java-SCA-1.0.1 The implementation-notification sample doesn't have an ant scipt. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1791) binding-notification-* samples don't work
[
https://issues.apache.org/jira/browse/TUSCANY-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529647
]
Ignacio Silva-Lepe commented on TUSCANY-1791:
-
I have double checked with the latest trunk that using a distro built from it
the notification binding producer and consumer samples work.
Also, looking at the trace of a run of the consumer sample in RC3a, it's odd
that the runtime starts a Tomcat Servlet Engine, whereas the trunk distro does
not, not to mention a number of servlet warnings that occur in RC3a but not on
the trunk:
C:\Devt\RC3a\binary\tuscany-sca-1.0-incubating\samples\binding-notification-cons
umerjava -Dnotification.httpPort=8083 -cp target\sample-binding-notification-c
onsumer-1.0-incubating.jar;%TUSCANY_SCA_MANIFEST_JAR% notification.consumer.Tra
fficAdvisoryServer
Sep 22, 2007 8:13:40 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.10
Sep 22, 2007 8:13:40 AM org.apache.catalina.startup.ContextConfig defaultWebConf
ig
INFO: No default web.xml
Sep 22, 2007 8:13:40 AM org.apache.catalina.startup.DigesterFactory register
WARNING: Could not get url for /javax/servlet/jsp/resources/jsp_2_0.xsd
Sep 22, 2007 8:13:40 AM org.apache.catalina.startup.DigesterFactory register
WARNING: Could not get url for /javax/servlet/jsp/resources/web-jsptaglibrary_1_
1.dtd
Sep 22, 2007 8:13:40 AM org.apache.catalina.startup.DigesterFactory register
WARNING: Could not get url for /javax/servlet/jsp/resources/web-jsptaglibrary_1_
2.dtd
Sep 22, 2007 8:13:40 AM org.apache.catalina.startup.DigesterFactory register
WARNING: Could not get url for /javax/servlet/jsp/resources/web-jsptaglibrary_2_
0.xsd
Sep 22, 2007 8:13:40 AM org.apache.catalina.startup.DigesterFactory register
WARNING: Could not get url for /javax/servlet/resources/j2ee_web_services_1_1.xs
d
Sep 22, 2007 8:13:41 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8083
Sep 22, 2007 8:13:41 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8083
Sep 22, 2007 8:13:41 AM org.apache.tuscany.sca.http.tomcat.TomcatServer addServl
etMapping
INFO: Added Servlet mapping: http://localhost:8083/ntm/trafficAdvisory
Sep 22, 2007 8:13:41 AM org.apache.tuscany.sca.http.tomcat.TomcatServer addServl
etMapping
INFO: Added Servlet mapping: http://localhost:8083/consumer/trafficAdvisory
TrafficAdvisoryServer, hit return to end
Any ideas?
binding-notification-* samples don't work
-
Key: TUSCANY-1791
URL: https://issues.apache.org/jira/browse/TUSCANY-1791
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects Versions: Java-SCA-1.0
Environment: Windows XP
Reporter: Simon Nash
Fix For: Java-SCA-1.0.1
I tried to run the binding-notification-* samples from the 1.0 rc3a binary
distro by following the README instructions. I always get a failure on the
second application that starts. I tried various different combinations of
which application to start first and which to start second and the failure
was consistent. For example, if I start the consumer first on port 8083 and
then the producer second on port 8084, I see the following exception from the
producer:
H:\tuscany-1.0-rc3a\tuscany-sca-1.0-incubating\samples\binding-notification-producerjava
-Dnotification.httpPort=8084 -cp
target\sample-binding-notification-producer-1.0-incubating.jar;%TUSCANY_SCA_MANIFEST_JAR%
notification.producer.TrafficAdvisoryServer
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.
exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]:
[1,0]
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:610)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:95)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:51)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl.newProducer(NotificationTypeManagerImpl.java:150)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.deployProducer(NotificationReferenceBindingProvider.java:170)
at
org.apache.tuscany.sca.binding.notification.NotificationBindingProviderFactory.referenceProviderStarted(NotificationBindingProviderFactory.java:186)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.start(NotificationReferenceBindingProvider.java:159)
at
[jira] Commented: (TUSCANY-1791) binding-notification-* samples don't work
[
https://issues.apache.org/jira/browse/TUSCANY-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529657
]
Ignacio Silva-Lepe commented on TUSCANY-1791:
-
Interestingly, if I replace tuscany-sca-all-1.0-incubating.jar from the trunk
distro and into RC3a, then the samples run.
Looking into the jars, I notice that the org/apache/tuscany/sca/http/tomcat
classes appear much earlier in the tuscany-sca-all-1.0-incubating.jar for the
trunk distro than in that for RC3a. This could explain why the Tomcat Servlet
Engine is being run instead of the Jetty Servlet Engine, which is what the
notification binding needs.
binding-notification-* samples don't work
-
Key: TUSCANY-1791
URL: https://issues.apache.org/jira/browse/TUSCANY-1791
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects Versions: Java-SCA-1.0
Environment: Windows XP
Reporter: Simon Nash
Fix For: Java-SCA-1.0.1
I tried to run the binding-notification-* samples from the 1.0 rc3a binary
distro by following the README instructions. I always get a failure on the
second application that starts. I tried various different combinations of
which application to start first and which to start second and the failure
was consistent. For example, if I start the consumer first on port 8083 and
then the producer second on port 8084, I see the following exception from the
producer:
H:\tuscany-1.0-rc3a\tuscany-sca-1.0-incubating\samples\binding-notification-producerjava
-Dnotification.httpPort=8084 -cp
target\sample-binding-notification-producer-1.0-incubating.jar;%TUSCANY_SCA_MANIFEST_JAR%
notification.producer.TrafficAdvisoryServer
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.
exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]:
[1,0]
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:610)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:95)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:51)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl.newProducer(NotificationTypeManagerImpl.java:150)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.deployProducer(NotificationReferenceBindingProvider.java:170)
at
org.apache.tuscany.sca.binding.notification.NotificationBindingProviderFactory.referenceProviderStarted(NotificationBindingProviderFactory.java:186)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.start(NotificationReferenceBindingProvider.java:159)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:456)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:186)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69)
at
notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServer.java:31)
Caused by:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col
{unknown-source}]: [1,0]
at
org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:65)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:607)
... 11 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at
[row,col {unknown-source}]: [1,0]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661)
at
com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:60)
... 12 more
org.osoa.sca.ServiceRuntimeException: java.lang.RuntimeException:
java.lang.RuntimeException:
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col
[jira] Commented: (TUSCANY-1799) ant script needed for implementation-notification sample
[ https://issues.apache.org/jira/browse/TUSCANY-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529664 ] Ignacio Silva-Lepe commented on TUSCANY-1799: - The implementation-notification sample, along with the binding-notification-* samples have ant scripts in the trunk, they just did not make it into the 1.0 release. ant script needed for implementation-notification sample Key: TUSCANY-1799 URL: https://issues.apache.org/jira/browse/TUSCANY-1799 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.0 Environment: All Reporter: Simon Nash Priority: Minor Fix For: Java-SCA-Next The implementation-notification sample doesn't have an ant scipt. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1791) binding-notification-* samples don't work
[
https://issues.apache.org/jira/browse/TUSCANY-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529584
]
Ignacio Silva-Lepe commented on TUSCANY-1791:
-
This is odd. This code has been working for a while now. And testing in the
trunk works as well. I was a bit suspicious of the changes that were made to
the encoders and decoders as part of the reorg to make the module activation
lazy. But then, I have tested after the merge from the branch and it works.
But I do get Simon's error as well.
binding-notification-* samples don't work
-
Key: TUSCANY-1791
URL: https://issues.apache.org/jira/browse/TUSCANY-1791
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects Versions: Java-SCA-1.0
Environment: Windows XP
Reporter: Simon Nash
Fix For: Java-SCA-1.0.1
I tried to run the binding-notification-* samples from the 1.0 rc3a binary
distro by following the README instructions. I always get a failure on the
second application that starts. I tried various different combinations of
which application to start first and which to start second and the failure
was consistent. For example, if I start the consumer first on port 8083 and
then the producer second on port 8084, I see the following exception from the
producer:
H:\tuscany-1.0-rc3a\tuscany-sca-1.0-incubating\samples\binding-notification-producerjava
-Dnotification.httpPort=8084 -cp
target\sample-binding-notification-producer-1.0-incubating.jar;%TUSCANY_SCA_MANIFEST_JAR%
notification.producer.TrafficAdvisoryServer
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.
exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]:
[1,0]
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:610)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:95)
at
org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:51)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl.newProducer(NotificationTypeManagerImpl.java:150)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.deployProducer(NotificationReferenceBindingProvider.java:170)
at
org.apache.tuscany.sca.binding.notification.NotificationBindingProviderFactory.referenceProviderStarted(NotificationBindingProviderFactory.java:186)
at
org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.start(NotificationReferenceBindingProvider.java:159)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:456)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:186)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
at
org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69)
at
notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServer.java:31)
Caused by:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col
{unknown-source}]: [1,0]
at
org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:65)
at
org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:607)
... 11 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at
[row,col {unknown-source}]: [1,0]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661)
at
com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:60)
... 12 more
org.osoa.sca.ServiceRuntimeException: java.lang.RuntimeException:
java.lang.RuntimeException:
org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException:
org.apache.tuscany.sca.binding.notification.encoding.EncodingException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col
{unknown-source}]: [1,0]
at
[jira] Commented: (TUSCANY-1620) Exception running the binding-notification-producer sample
[ https://issues.apache.org/jira/browse/TUSCANY-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523249 ] Ignacio Silva-Lepe commented on TUSCANY-1620: - I misspoke above about where the databinding interceptor is not being added. The trace above shows the invocation chain between the notification component and the composite reference. In particular, it shows the notification component invoker calling the notification reference binding invoker directly with no databinding interceptor in between. This is indeed correct, as both ends have the same databinding. However, where a databinding interceptor _should_ be added is in the invocation chain between the traffic advisory producer and the notification component. Doing a little bit of debugging, I have a break point in DataBindingRuntimeWireProcessor.process, and in line 116 I can see that the target contract (a WSDLInterfaceContractImpl) has a single OperationImpl in its list of operations, which is ok, but this operation has a dataBinding value of null. This means that isTransformationRequired eventually returns null and no databinding interceptor is added. I am not sure what has changed in the last week or so to make this happen, as I am assuming that the OperationImpl's databinding value was not null before, since the sample was working. Any ideas? Exception running the binding-notification-producer sample -- Key: TUSCANY-1620 URL: https://issues.apache.org/jira/browse/TUSCANY-1620 Project: Tuscany Issue Type: Bug Components: Java SCA Data Binding Runtime, Java SCA Samples Affects Versions: Java-SCA-0.99, Java-SCA-1.0 Environment: WIndows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.99, Java-SCA-1.0 I am getting the following exception trying to run the binding-notification- producer sample and trying to send a message to a binding-notification- consumer. The NotificaitonReferenceBindingInvoker is expecting an OMElement that should be coming from the notification component via the corresponding databinding. But I don't see a databinding interceptor between the RuntimeSCABindingInvoker and the NotificationReference- BindingInvoker, the way you see it in the databinding-echo trace of TUSCANY-1582. Any ideas as to why the databinding interceptor is not being added to the invocation chain? java.lang.RuntimeException: payload not OMElement at org.apache.tuscany.sca.binding.notification.NotificationReferenceBind ingInvoker.getWriteableFromPayload(NotificationReferenceBindingInvoker.java:115) at org.apache.tuscany.sca.binding.notification.NotificationReferenceBind ingInvoker.invoke(NotificationReferenceBindingInvoker.java:81) at org.apache.tuscany.sca.implementation.notification.NotificationCompon entInvoker.invoke(NotificationComponentInvoker.java:81) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingInvoker.invo ke(RuntimeSCABindingInvoker.java:48) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke (JD KInvocationHandler.java:236) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:93) at $Proxy8.trafficNotification(Unknown Source) at notification.producer.TrafficAdvisoryProducer.produceTrafficNotificat ion(TrafficAdvisoryProducer.java:34) 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.tuscany.sca.implementation.java.invocation.JavaImplementat ionInvoker.invoke(JavaImplementationInvoker.java:91) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingInvoker.invo ke(RuntimeSCABindingInvoker.java:48) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke (JD KInvocationHandler.java:236) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:93) at $Proxy7.produceTrafficNotification(Unknown Source) at notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServe r.java:45) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-1620) Exception running the binding-notification-producer sample
[ https://issues.apache.org/jira/browse/TUSCANY-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe resolved TUSCANY-1620. - Resolution: Fixed With Raymond's advice, the NotificationImplementationProvider now sets the databinding in the interface contract, rather than relying on the deprecated scdl databinding extension. See r570563. This takes care of the subject of this issue and so it can be resolved. Exception running the binding-notification-producer sample -- Key: TUSCANY-1620 URL: https://issues.apache.org/jira/browse/TUSCANY-1620 Project: Tuscany Issue Type: Bug Components: Java SCA Data Binding Runtime, Java SCA Samples Affects Versions: Java-SCA-0.99, Java-SCA-1.0 Environment: WIndows XP Reporter: Ignacio Silva-Lepe Assignee: Raymond Feng Fix For: Java-SCA-0.99, Java-SCA-1.0 I am getting the following exception trying to run the binding-notification- producer sample and trying to send a message to a binding-notification- consumer. The NotificaitonReferenceBindingInvoker is expecting an OMElement that should be coming from the notification component via the corresponding databinding. But I don't see a databinding interceptor between the RuntimeSCABindingInvoker and the NotificationReference- BindingInvoker, the way you see it in the databinding-echo trace of TUSCANY-1582. Any ideas as to why the databinding interceptor is not being added to the invocation chain? java.lang.RuntimeException: payload not OMElement at org.apache.tuscany.sca.binding.notification.NotificationReferenceBind ingInvoker.getWriteableFromPayload(NotificationReferenceBindingInvoker.java:115) at org.apache.tuscany.sca.binding.notification.NotificationReferenceBind ingInvoker.invoke(NotificationReferenceBindingInvoker.java:81) at org.apache.tuscany.sca.implementation.notification.NotificationCompon entInvoker.invoke(NotificationComponentInvoker.java:81) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingInvoker.invo ke(RuntimeSCABindingInvoker.java:48) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke (JD KInvocationHandler.java:236) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:93) at $Proxy8.trafficNotification(Unknown Source) at notification.producer.TrafficAdvisoryProducer.produceTrafficNotificat ion(TrafficAdvisoryProducer.java:34) 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.tuscany.sca.implementation.java.invocation.JavaImplementat ionInvoker.invoke(JavaImplementationInvoker.java:91) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingInvoker.invo ke(RuntimeSCABindingInvoker.java:48) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke (JD KInvocationHandler.java:236) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:93) at $Proxy7.produceTrafficNotification(Unknown Source) at notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServe r.java:45) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1620) Exception running the binding-notification-producer sample
Exception running the binding-notification-producer sample -- Key: TUSCANY-1620 URL: https://issues.apache.org/jira/browse/TUSCANY-1620 Project: Tuscany Issue Type: Bug Components: Java SCA Data Binding Runtime, Java SCA Samples Affects Versions: Java-SCA-0.99, Java-SCA-1.0 Environment: WIndows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.99, Java-SCA-1.0 I am getting the following exception trying to run the binding-notification- producer sample and trying to send a message to a binding-notification- consumer. The NotificaitonReferenceBindingInvoker is expecting an OMElement that should be coming from the notification component via the corresponding databinding. But I don't see a databinding interceptor between the RuntimeSCABindingInvoker and the NotificationReference- BindingInvoker, the way you see it in the databinding-echo trace of TUSCANY-1582. Any ideas as to why the databinding interceptor is not being added to the invocation chain? java.lang.RuntimeException: payload not OMElement at org.apache.tuscany.sca.binding.notification.NotificationReferenceBind ingInvoker.getWriteableFromPayload(NotificationReferenceBindingInvoker.java:115) at org.apache.tuscany.sca.binding.notification.NotificationReferenceBind ingInvoker.invoke(NotificationReferenceBindingInvoker.java:81) at org.apache.tuscany.sca.implementation.notification.NotificationCompon entInvoker.invoke(NotificationComponentInvoker.java:81) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingInvoker.invo ke(RuntimeSCABindingInvoker.java:48) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke (JD KInvocationHandler.java:236) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:93) at $Proxy8.trafficNotification(Unknown Source) at notification.producer.TrafficAdvisoryProducer.produceTrafficNotificat ion(TrafficAdvisoryProducer.java:34) 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.tuscany.sca.implementation.java.invocation.JavaImplementat ionInvoker.invoke(JavaImplementationInvoker.java:91) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingInvoker.invo ke(RuntimeSCABindingInvoker.java:48) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke (JD KInvocationHandler.java:236) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:93) at $Proxy7.produceTrafficNotification(Unknown Source) at notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServe r.java:45) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1299) NPE after NoClassDefFoundError in trunk distro for o.a.t.s.databinding.sdo.SDODataBinding
NPE after NoClassDefFoundError in trunk distro for o.a.t.s.databinding.sdo.SDODataBinding - Key: TUSCANY-1299 URL: https://issues.apache.org/jira/browse/TUSCANY-1299 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-Next After a full update and mvn clean; mvn of trunk, and mvn clean; mvn in sca/distribution, I unzip the binary distro and try: C:\Devt\NotificationComponents\samples\brokerjava -Dnotification.httpPort=8080 -cp target\tuscany-notification-broker-sample-1.0-incubating-SNAPSHOT.jar;..\.. \local\target\tuscany-notification-local-1.0-incubating-SNAPSHOT.jar;..\..\bindi ng\target\tuscany-notification-binding-1.0-incubating-SNAPSHOT.jar;\Documents an d Settings\Administrator\.m2\repository\stax\stax\1.1.1-dev\stax-1.1.1-dev.jar;\ Devt\tuscany-sca-distr\tuscany-sca-1.0-incubating-SNAPSHOT\lib\tuscany-sca-manif est.jar org.apache.tuscany.sca.notification.broker.TrafficAdvisoryServer java.lang.NoClassDefFoundError: commonj/sdo/DataObject at org.apache.tuscany.sca.databinding.sdo.SDODataBinding.clinit(SDODat aBinding.java:46) at org.apache.tuscany.sca.databinding.sdo.module.SDODataBindingModuleAct ivator.start(SDODataBindingModuleActivator.java:57) at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.startMod ules(ReallySmallRuntime.java:161) at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.start(Re allySmallRuntime.java:110) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(Def aultSCADomain.java:86) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCAD omain.java:229) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain. java:68) at org.apache.tuscany.sca.notification.broker.TrafficAdvisoryServer.main (TrafficAdvisoryServer.java:35) Looking in tuscany-sca-1.0-incubating-SNAPSHOT/lib I find sdo-api-r2.1-1.0-incubating-20070520.134246-1.jar, but the manifest has a reference to sdo-api-r2.1-1.0-incubating-SNAPSHOT.jar. So after copying that expected jar from my local repo, I then see: C:\Devt\NotificationComponents\samples\brokerjava -Dnotification.httpPort=8080 -cp target\tuscany-notification-broker-sample-1.0-incubating-SNAPSHOT.jar;..\.. \local\target\tuscany-notification-local-1.0-incubating-SNAPSHOT.jar;..\..\bindi ng\target\tuscany-notification-binding-1.0-incubating-SNAPSHOT.jar;\Documents an d Settings\Administrator\.m2\repository\stax\stax\1.1.1-dev\stax-1.1.1-dev.jar;\ Devt\tuscany-sca-distr\tuscany-sca-1.0-incubating-SNAPSHOT\lib\tuscany-sca-manif est.jar org.apache.tuscany.sca.notification.broker.TrafficAdvisoryServer *** Activating notification binding module, localBaseUrl [http://spyder.watson.i bm.com:8080] *** Activating local notification module *** binding ntm [http://localhost:8080/ntm], notificationType [trafficAdvisory] *** binding ntm [http://localhost:8080/ntm], notificationType [trafficAdvisory] org.osoa.sca.ServiceRuntimeException: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCAD omain.java:263) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain. java:68) at org.apache.tuscany.sca.notification.broker.TrafficAdvisoryServer.main (TrafficAdvisoryServer.java:35) Caused by: java.lang.NullPointerException at commonj.sdo.impl.HelperProvider.getDefaultContext(HelperProvider.java :379) at org.apache.tuscany.sca.databinding.sdo.SDODataBinding.introspect(SDOD ataBinding.java:66) at org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.i ntrospectType(DefaultDataBindingExtensionPoint.java:84) at org.apache.tuscany.core.databinding.processor.DataBindingJavaInterfac eProcessor.processInterface(DataBindingJavaInterfaceProcessor.java:115) at org.apache.tuscany.core.databinding.processor.DataBindingJavaInterfac eProcessor.visitInterface(DataBindingJavaInterfaceProcessor.java:55) at org.apache.tuscany.sca.interfacedef.java.introspect.ExtensibleJavaInt erfaceIntrospector.introspect(ExtensibleJavaInterfaceIntrospector.java:83) at org.apache.tuscany.sca.implementation.java.introspect.impl.ReferenceP rocessor.createReference(ReferenceProcessor.java:160) at org.apache.tuscany.sca.implementation.java.introspect.impl.ReferenceP rocessor.visitField(ReferenceProcessor.java:93) at org.apache.tuscany.sca.implementation.java.introspect.ExtensibleJavaC lassIntrospector.introspect(ExtensibleJavaClassIntrospector.java:99) at org.apache.tuscany.sca.implementation.java.xml.JavaImplementationProc essor.resolve(JavaImplementationProcessor.java:119) at
[jira] Reopened: (TUSCANY-1260) NPE when component reference has target composite with custom implementation
[ https://issues.apache.org/jira/browse/TUSCANY-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe reopened TUSCANY-1260: - Sorry to insist on this, but after removing the test case issues mentioned the main problem persists (1) the package renaming that requires renaming the ModuleActivator was not a factor initially, but it has been addressed (2) there is now only one componentType file visible (the one in local was part of the test and thus not in the jar, and the duplicate one in remote-producer was removed) NPE when component reference has target composite with custom implementation Key: TUSCANY-1260 URL: https://issues.apache.org/jira/browse/TUSCANY-1260 Project: Tuscany Issue Type: Bug Components: Java SCA Model Affects Versions: Java-SCA-0.90 Environment: Windows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.90 A NPE occurs in DefaultCompositeActivator.createWires() when component reference has target composite with custom implementation. This used to work before the last refactor. Running org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCase *** binding ntm [null], notificationType [trafficAdvisory] NotificationImplementationLoader.resolve, tmpUri [TrafficAdvisoryNotificatio n.componentType], ctUri [file:/C:/Devt/NotificationComponents/samples/remote-pro ducer/target/test-classes/TrafficAdvisoryNotification.componentType] Composite assembly problem: No implementation for component: TrafficAdvisoryProd ucer Composite assembly problem: Reference not found for component reference: Traffic AdvisoryProducer/destination createWires, component [TrafficAdvisoryProducer], reference [destination], b inding [EMAIL PROTECTED] org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.core.runtime.ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:197) at org.apache.tuscany.host.embedded.SCADomain.newInstance(SCADomain.java :73) at org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCas e.setUp(TrafficAdvisoryTestCase.java:40) at junit.framework.TestCase.runBare(TestCase.java:132) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) getInterfaceContract *** interfaceContract [null] *** provider not null, bindingContract [null] getInterfaceContract, interfaceContract [null] *** bindingContract [null] *** bindingContract.getInterface() [null] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 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:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:818) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.core.runtime .ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:136) at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:186) ... 20 more Caused by: org.apache.tuscany.core.runtime.ActivationException: java.lang.NullPo interException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:587) at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:134) ... 21 more Caused by: java.lang.NullPointerException at
[jira] Resolved: (TUSCANY-1260) NPE when component reference has target composite with custom implementation
[ https://issues.apache.org/jira/browse/TUSCANY-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe resolved TUSCANY-1260. - Resolution: Fixed Ok, so the real issue is a dependency on tuscany-implementation-java-runtime. The pom being used to build the sample was missing this dependency and so the implementation.java for the missing component was not being created. Perhaps there can be a more apparent way to warn about this? NPE when component reference has target composite with custom implementation Key: TUSCANY-1260 URL: https://issues.apache.org/jira/browse/TUSCANY-1260 Project: Tuscany Issue Type: Bug Components: Java SCA Model Affects Versions: Java-SCA-0.90 Environment: Windows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.90 A NPE occurs in DefaultCompositeActivator.createWires() when component reference has target composite with custom implementation. This used to work before the last refactor. Running org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCase *** binding ntm [null], notificationType [trafficAdvisory] NotificationImplementationLoader.resolve, tmpUri [TrafficAdvisoryNotificatio n.componentType], ctUri [file:/C:/Devt/NotificationComponents/samples/remote-pro ducer/target/test-classes/TrafficAdvisoryNotification.componentType] Composite assembly problem: No implementation for component: TrafficAdvisoryProd ucer Composite assembly problem: Reference not found for component reference: Traffic AdvisoryProducer/destination createWires, component [TrafficAdvisoryProducer], reference [destination], b inding [EMAIL PROTECTED] org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.core.runtime.ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:197) at org.apache.tuscany.host.embedded.SCADomain.newInstance(SCADomain.java :73) at org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCas e.setUp(TrafficAdvisoryTestCase.java:40) at junit.framework.TestCase.runBare(TestCase.java:132) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) getInterfaceContract *** interfaceContract [null] *** provider not null, bindingContract [null] getInterfaceContract, interfaceContract [null] *** bindingContract [null] *** bindingContract.getInterface() [null] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 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:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:818) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.core.runtime .ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:136) at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:186) ... 20 more Caused by: org.apache.tuscany.core.runtime.ActivationException: java.lang.NullPo interException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:587) at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:134) ... 21 more Caused by: java.lang.NullPointerException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.createWires (DefaultCompositeActivator.java:371) at
[jira] Commented: (TUSCANY-1260) NPE when component reference has target composite with custom implementation
[ https://issues.apache.org/jira/browse/TUSCANY-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495733 ] Ignacio Silva-Lepe commented on TUSCANY-1260: - It seems like the distribution has the same problem, is the distribution supposed to work now? After issuing the command: C:\Devt\NotificationComponents\samples\remote-producerjava -Dnotification.httpP ort=8080 -cp target\tuscany-notification-remote-producer-sample-1.0-incubating- SNAPSHOT.jar;..\..\local\target\tuscany-notification-local-1.0-incubating-SNAPSH OT.jar;..\..\binding\target\tuscany-notification-binding-1.0-incubating-SNAPSHOT .jar;\Documents and Settings\Administrator\.m2\repository\stax\stax\1.1.1-dev\st ax-1.1.1-dev.jar;\Devt\tuscany-sca-distr\tuscany-sca-1.0-incubating-SNAPSHOT\lib \tuscany-sca-manifest.jar org.apache.tuscany.notification.remoteProducer.Traffi cAdvisoryServer I get the following: *** Activating local notification module *** Activating notification binding module, localBaseUrl [http://spyder.watson.i bm.com:8080] *** binding ntm [null], notificationType [trafficAdvisory] NotificationImplementationLoader.resolve, tmpUri [TrafficAdvisoryNotificatio nTest.componentType], ctUri [jar:file:/C:/Devt/NotificationComponents/samples/re mote-producer/target/tuscany-notification-remote-producer-sample-1.0-incubating- SNAPSHOT.jar!/TrafficAdvisoryNotificationTest.componentType] Composite assembly problem: No implementation for component: TrafficAdvisoryProd ucer Composite assembly problem: Reference not found for component reference: Traffic AdvisoryProducer/destination org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.sca.core.runtime.ActivationException: java.lang.NullPointerExcept ion at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCAD omain.java:230) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain. java:90) at org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryServer. main(TrafficAdvisoryServer.java:31) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.core.run time.ActivationException: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(Def aultSCADomain.java:136) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCAD omain.java:212) ... 2 more Caused by: org.apache.tuscany.sca.core.runtime.ActivationException: java.lang.Nu llPointerException at org.apache.tuscany.sca.core.runtime.DefaultCompositeActivator.start(D efaultCompositeActivator.java:573) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(Def aultSCADomain.java:134) ... 3 more Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.core.runtime.DefaultCompositeActivator.createW ires(DefaultCompositeActivator.java:357) at org.apache.tuscany.sca.core.runtime.DefaultCompositeActivator.createR untimeWires(DefaultCompositeActivator.java:251) at org.apache.tuscany.sca.core.runtime.DefaultCompositeActivator.start(D efaultCompositeActivator.java:570) ... 4 more which is pretty much the same issue. I have verified that the modules dir in the distribution contains tuscany-interface-java-runtime-1.0-incubating-SNAPSHOT.jar, and that the manifest file in lib\tuscany-sca-manifest.jar contains a reference to it. I should point out that the main build of the trunk gave me a failure in [INFO] - --- [INFO] Building Apache Tuscany DAS Pojo Service Sample - Service [INFO]task-segment: [install] [INFO] - --- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/t uscany/das/tuscany-das-rdb/1.0-incubating-SNAPSHOT/tuscany-das-rdb-1.0-incubatin g-SNAPSHOT.pom [WARNING] Unable to get resource from repository apache.incubator (http://people .apache.org/repo/m2-incubating-repository) Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/tus cany/das/tuscany-das-rdb/1.0-incubating-SNAPSHOT/tuscany-das-rdb-1.0-incubating- SNAPSHOT.pom [WARNING] Unable to get resource from repository apache.snapshots (http://people .apache.org/repo/m2-snapshot-repository) Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/t uscany/das/tuscany-das-rdb/1.0-incubating-SNAPSHOT/tuscany-das-rdb-1.0-incubatin g-SNAPSHOT.jar [WARNING] Unable to get resource from repository apache.incubator (http://people .apache.org/repo/m2-incubating-repository) Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/tus
[jira] Reopened: (TUSCANY-1260) NPE when component reference has target composite with custom implementation
[ https://issues.apache.org/jira/browse/TUSCANY-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe reopened TUSCANY-1260: - Here's hoping this is the last time, and to make sure that the distro also works NPE when component reference has target composite with custom implementation Key: TUSCANY-1260 URL: https://issues.apache.org/jira/browse/TUSCANY-1260 Project: Tuscany Issue Type: Bug Components: Java SCA Model Affects Versions: Java-SCA-0.90 Environment: Windows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.90 A NPE occurs in DefaultCompositeActivator.createWires() when component reference has target composite with custom implementation. This used to work before the last refactor. Running org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCase *** binding ntm [null], notificationType [trafficAdvisory] NotificationImplementationLoader.resolve, tmpUri [TrafficAdvisoryNotificatio n.componentType], ctUri [file:/C:/Devt/NotificationComponents/samples/remote-pro ducer/target/test-classes/TrafficAdvisoryNotification.componentType] Composite assembly problem: No implementation for component: TrafficAdvisoryProd ucer Composite assembly problem: Reference not found for component reference: Traffic AdvisoryProducer/destination createWires, component [TrafficAdvisoryProducer], reference [destination], b inding [EMAIL PROTECTED] org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.core.runtime.ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:197) at org.apache.tuscany.host.embedded.SCADomain.newInstance(SCADomain.java :73) at org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCas e.setUp(TrafficAdvisoryTestCase.java:40) at junit.framework.TestCase.runBare(TestCase.java:132) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) getInterfaceContract *** interfaceContract [null] *** provider not null, bindingContract [null] getInterfaceContract, interfaceContract [null] *** bindingContract [null] *** bindingContract.getInterface() [null] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 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:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:818) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.core.runtime .ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:136) at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:186) ... 20 more Caused by: org.apache.tuscany.core.runtime.ActivationException: java.lang.NullPo interException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:587) at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:134) ... 21 more Caused by: java.lang.NullPointerException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.createWires (DefaultCompositeActivator.java:371) at org.apache.tuscany.core.runtime.DefaultCompositeActivator.createRunti meWires(DefaultCompositeActivator.java:255) at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:584) ... 22 more
[jira] Resolved: (TUSCANY-1260) NPE when component reference has target composite with custom implementation
[ https://issues.apache.org/jira/browse/TUSCANY-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe resolved TUSCANY-1260. - Resolution: Fixed Ok, trying with r537950 the problem is gone in the distro as well. Notice that the main build still fails for me at Building Apache Tuscany DAS Pojo Service Sample - Service NPE when component reference has target composite with custom implementation Key: TUSCANY-1260 URL: https://issues.apache.org/jira/browse/TUSCANY-1260 Project: Tuscany Issue Type: Bug Components: Java SCA Model Affects Versions: Java-SCA-0.90 Environment: Windows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.90 A NPE occurs in DefaultCompositeActivator.createWires() when component reference has target composite with custom implementation. This used to work before the last refactor. Running org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCase *** binding ntm [null], notificationType [trafficAdvisory] NotificationImplementationLoader.resolve, tmpUri [TrafficAdvisoryNotificatio n.componentType], ctUri [file:/C:/Devt/NotificationComponents/samples/remote-pro ducer/target/test-classes/TrafficAdvisoryNotification.componentType] Composite assembly problem: No implementation for component: TrafficAdvisoryProd ucer Composite assembly problem: Reference not found for component reference: Traffic AdvisoryProducer/destination createWires, component [TrafficAdvisoryProducer], reference [destination], b inding [EMAIL PROTECTED] org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.core.runtime.ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:197) at org.apache.tuscany.host.embedded.SCADomain.newInstance(SCADomain.java :73) at org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCas e.setUp(TrafficAdvisoryTestCase.java:40) at junit.framework.TestCase.runBare(TestCase.java:132) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) getInterfaceContract *** interfaceContract [null] *** provider not null, bindingContract [null] getInterfaceContract, interfaceContract [null] *** bindingContract [null] *** bindingContract.getInterface() [null] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 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:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:818) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.core.runtime .ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:136) at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:186) ... 20 more Caused by: org.apache.tuscany.core.runtime.ActivationException: java.lang.NullPo interException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:587) at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:134) ... 21 more Caused by: java.lang.NullPointerException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.createWires (DefaultCompositeActivator.java:371) at org.apache.tuscany.core.runtime.DefaultCompositeActivator.createRunti meWires(DefaultCompositeActivator.java:255) at
[jira] Commented: (TUSCANY-1260) NPE when component reference has target composite with custom implementation
[ https://issues.apache.org/jira/browse/TUSCANY-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495765 ] Ignacio Silva-Lepe commented on TUSCANY-1260: - BTW, would it be possible to check for an implementation runtime to be available when an implementation.XXX element is trying to be loaded (or processed)? I have not pinpointed the piece of code that should do it, but perhaps someone has more immediate access to it. NPE when component reference has target composite with custom implementation Key: TUSCANY-1260 URL: https://issues.apache.org/jira/browse/TUSCANY-1260 Project: Tuscany Issue Type: Bug Components: Java SCA Model Affects Versions: Java-SCA-0.90 Environment: Windows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.90 A NPE occurs in DefaultCompositeActivator.createWires() when component reference has target composite with custom implementation. This used to work before the last refactor. Running org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCase *** binding ntm [null], notificationType [trafficAdvisory] NotificationImplementationLoader.resolve, tmpUri [TrafficAdvisoryNotificatio n.componentType], ctUri [file:/C:/Devt/NotificationComponents/samples/remote-pro ducer/target/test-classes/TrafficAdvisoryNotification.componentType] Composite assembly problem: No implementation for component: TrafficAdvisoryProd ucer Composite assembly problem: Reference not found for component reference: Traffic AdvisoryProducer/destination createWires, component [TrafficAdvisoryProducer], reference [destination], b inding [EMAIL PROTECTED] org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.core.runtime.ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:197) at org.apache.tuscany.host.embedded.SCADomain.newInstance(SCADomain.java :73) at org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCas e.setUp(TrafficAdvisoryTestCase.java:40) at junit.framework.TestCase.runBare(TestCase.java:132) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) getInterfaceContract *** interfaceContract [null] *** provider not null, bindingContract [null] getInterfaceContract, interfaceContract [null] *** bindingContract [null] *** bindingContract.getInterface() [null] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 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:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:818) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.core.runtime .ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:136) at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:186) ... 20 more Caused by: org.apache.tuscany.core.runtime.ActivationException: java.lang.NullPo interException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:587) at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:134) ... 21 more Caused by: java.lang.NullPointerException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.createWires (DefaultCompositeActivator.java:371) at
[jira] Created: (TUSCANY-1260) NPE when component reference has target composite with custom implementation
NPE when component reference has target composite with custom implementation Key: TUSCANY-1260 URL: https://issues.apache.org/jira/browse/TUSCANY-1260 Project: Tuscany Issue Type: Bug Components: Java SCA Model Affects Versions: Java-SCA-0.90 Environment: Windows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.90 A NPE occurs in DefaultCompositeActivator.createWires() when component reference has target composite with custom implementation. This used to work before the last refactor. Running org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCase *** binding ntm [null], notificationType [trafficAdvisory] NotificationImplementationLoader.resolve, tmpUri [TrafficAdvisoryNotificatio n.componentType], ctUri [file:/C:/Devt/NotificationComponents/samples/remote-pro ducer/target/test-classes/TrafficAdvisoryNotification.componentType] Composite assembly problem: No implementation for component: TrafficAdvisoryProd ucer Composite assembly problem: Reference not found for component reference: Traffic AdvisoryProducer/destination createWires, component [TrafficAdvisoryProducer], reference [destination], b inding [EMAIL PROTECTED] org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.core.runtime.ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:197) at org.apache.tuscany.host.embedded.SCADomain.newInstance(SCADomain.java :73) at org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCas e.setUp(TrafficAdvisoryTestCase.java:40) at junit.framework.TestCase.runBare(TestCase.java:132) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) getInterfaceContract *** interfaceContract [null] *** provider not null, bindingContract [null] getInterfaceContract, interfaceContract [null] *** bindingContract [null] *** bindingContract.getInterface() [null] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 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:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:818) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.core.runtime .ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:136) at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:186) ... 20 more Caused by: org.apache.tuscany.core.runtime.ActivationException: java.lang.NullPo interException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:587) at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:134) ... 21 more Caused by: java.lang.NullPointerException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.createWires (DefaultCompositeActivator.java:371) at org.apache.tuscany.core.runtime.DefaultCompositeActivator.createRunti meWires(DefaultCompositeActivator.java:255) at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:584) ... 22 more Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.932 sec FA ILURE! Results : Tests in error: testTrafficAdvisoryNotification(org.apache.tuscany.notification.remoteProducer .TrafficAdvisoryTestCase) Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 The composite being used is: composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
[jira] Commented: (TUSCANY-1260) NPE when component reference has target composite with custom implementation
[ https://issues.apache.org/jira/browse/TUSCANY-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494795 ] Ignacio Silva-Lepe commented on TUSCANY-1260: - Notice that the line getInterfaceContract, interfaceContract [null] , which prints the return value of DefaultCompositeActivator.getInterfaceContract seems to say that the reference's contract has not been determined. Could this be because the code to match the Java interface, that the reference expects, to the WSDL interface defined by the target component, does not work any more? I am trying to figure out where this code is, but on the off chance that anyone can tell whether or not this may be the actual problem, I bring it up. NPE when component reference has target composite with custom implementation Key: TUSCANY-1260 URL: https://issues.apache.org/jira/browse/TUSCANY-1260 Project: Tuscany Issue Type: Bug Components: Java SCA Model Affects Versions: Java-SCA-0.90 Environment: Windows XP Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-0.90 A NPE occurs in DefaultCompositeActivator.createWires() when component reference has target composite with custom implementation. This used to work before the last refactor. Running org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCase *** binding ntm [null], notificationType [trafficAdvisory] NotificationImplementationLoader.resolve, tmpUri [TrafficAdvisoryNotificatio n.componentType], ctUri [file:/C:/Devt/NotificationComponents/samples/remote-pro ducer/target/test-classes/TrafficAdvisoryNotification.componentType] Composite assembly problem: No implementation for component: TrafficAdvisoryProd ucer Composite assembly problem: Reference not found for component reference: Traffic AdvisoryProducer/destination createWires, component [TrafficAdvisoryProducer], reference [destination], b inding [EMAIL PROTECTED] org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: org. apache.tuscany.core.runtime.ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:197) at org.apache.tuscany.host.embedded.SCADomain.newInstance(SCADomain.java :73) at org.apache.tuscany.notification.remoteProducer.TrafficAdvisoryTestCas e.setUp(TrafficAdvisoryTestCase.java:40) at junit.framework.TestCase.runBare(TestCase.java:132) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) getInterfaceContract *** interfaceContract [null] *** provider not null, bindingContract [null] getInterfaceContract, interfaceContract [null] *** bindingContract [null] *** bindingContract.getInterface() [null] at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) 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:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:818) Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.core.runtime .ActivationException: java.lang.NullPointerException at org.apache.tuscany.host.embedded.impl.DefaultSCADomain.init(Default SCADomain.java:136) at org.apache.tuscany.host.embedded.SCADomain.createNewInstance(SCADomai n.java:186) ... 20 more Caused by: org.apache.tuscany.core.runtime.ActivationException: java.lang.NullPo interException at org.apache.tuscany.core.runtime.DefaultCompositeActivator.start(Defau ltCompositeActivator.java:587) at
[jira] Resolved: (TUSCANY-1003) NPE thrown by AxisEngine.send in service side of axis2 binding for async callbacks
[ https://issues.apache.org/jira/browse/TUSCANY-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe resolved TUSCANY-1003. - Resolution: Fixed Fix Version/s: (was: Java-SCA-Mx) Java-SCA-M3 Fixed in r499126 NPE thrown by AxisEngine.send in service side of axis2 binding for async callbacks -- Key: TUSCANY-1003 URL: https://issues.apache.org/jira/browse/TUSCANY-1003 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Affects Versions: Java-SCA-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-M3 I'm seeing an NPE thrown by AxisEngine.send in the service side of the axis2 binding for async callbacks. The trace is below. My current guess is that this may have something to do with the pass-by-value interceptor but I have not delved to deeply into the possible cause. For now I am leaving this in the Java SCA Axis binding component but that may change depending on the actual reason for the exception. org.apache.tuscany.binding.axis2.Axis2BindingRunTimeException: java.lang.NullPoi nterException at org.apache.tuscany.binding.axis2.Axis2ServiceCallbackTargetInvoker.in vokeTarget(Axis2ServiceCallbackTargetInvoker.java:78) at org.apache.tuscany.binding.axis2.Axis2ServiceCallbackTargetInvoker.in voke(Axis2ServiceCallbackTargetInvoker.java:90) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:65) at org.apache.tuscany.core.wire.SynchronousBridgingInterceptor.invoke(Sy nchronousBridgingInterceptor.java:41) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:70) at org.apache.tuscany.spi.wire.AbstractOutboundInvocationHandler.invoke( AbstractOutboundInvocationHandler.java:91) at org.apache.tuscany.core.wire.jdk.JDKCallbackInvocationHandler.invoke( JDKCallbackInvocationHandler.java:103) at $Proxy21.getGreetingsCallback(Unknown Source) at helloworld.HelloWorldImpl.getGreetings(HelloWorldImpl.java:43) 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.tuscany.core.implementation.java.JavaTargetInvoker.invokeT arget(JavaTargetInvoker.java:90) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(Target InvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:65) at org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(Non BlockingBridgingInterceptor.java:79) at org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr2 37Work.run(Jsr237WorkScheduler.java:212) at org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo rkManager$DecoratingWork.run(ThreadPoolWorkManager.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(Internal OutputBuffer.java:746) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433) at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuf fer.java:304) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java: 991) at org.apache.coyote.Response.action(Response.java:182) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java: 322) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:29 3) at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputSt ream.java:97) at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:410) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213) at java.io.BufferedWriter.flush(BufferedWriter.java:236) at
[jira] Commented: (TUSCANY-1003) NPE thrown by AxisEngine.send in service side of axis2 binding for async callbacks
[ https://issues.apache.org/jira/browse/TUSCANY-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465774 ] Ignacio Silva-Lepe commented on TUSCANY-1003: - Ok, I am past the ServiceRuntimeException, I was missing a @Service declaration. But now I am getting the following TransformationException: org.apache.tuscany.spi.databinding.TransformationException: java.lang.NullPointe rException at org.apache.tuscany.core.databinding.impl.Output2OutputTransformer.tra nsform(Output2OutputTransformer.java:197) at org.apache.tuscany.core.databinding.impl.MediatorImpl.mediate(Mediato rImpl.java:91) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.transf orm(DataBindingInteceptor.java:106) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:92) at org.apache.tuscany.spi.wire.AbstractOutboundInvocationHandler.invoke( AbstractOutboundInvocationHandler.java:91) at org.apache.tuscany.core.wire.jdk.JDKOutboundInvocationHandler.invoke( JDKOutboundInvocationHandler.java:166) at $Proxy25.getGreetings(Unknown Source) at helloworld.HelloWorldServiceComponent.getGreetings(HelloWorldServiceC omponent.java:40) Caused by: java.lang.NullPointerException at org.apache.tuscany.databinding.axiom.OMElementWrapperHandler.getChild (OMElementWrapperHandler.java:50) at org.apache.tuscany.databinding.axiom.OMElementWrapperHandler.getChild (OMElementWrapperHandler.java:34) at org.apache.tuscany.core.databinding.impl.Output2OutputTransformer.tra nsform(Output2OutputTransformer.java:187) Any ideas? NPE thrown by AxisEngine.send in service side of axis2 binding for async callbacks -- Key: TUSCANY-1003 URL: https://issues.apache.org/jira/browse/TUSCANY-1003 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Affects Versions: Java-SCA-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-SCA-Mx I'm seeing an NPE thrown by AxisEngine.send in the service side of the axis2 binding for async callbacks. The trace is below. My current guess is that this may have something to do with the pass-by-value interceptor but I have not delved to deeply into the possible cause. For now I am leaving this in the Java SCA Axis binding component but that may change depending on the actual reason for the exception. org.apache.tuscany.binding.axis2.Axis2BindingRunTimeException: java.lang.NullPoi nterException at org.apache.tuscany.binding.axis2.Axis2ServiceCallbackTargetInvoker.in vokeTarget(Axis2ServiceCallbackTargetInvoker.java:78) at org.apache.tuscany.binding.axis2.Axis2ServiceCallbackTargetInvoker.in voke(Axis2ServiceCallbackTargetInvoker.java:90) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:65) at org.apache.tuscany.core.wire.SynchronousBridgingInterceptor.invoke(Sy nchronousBridgingInterceptor.java:41) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:70) at org.apache.tuscany.spi.wire.AbstractOutboundInvocationHandler.invoke( AbstractOutboundInvocationHandler.java:91) at org.apache.tuscany.core.wire.jdk.JDKCallbackInvocationHandler.invoke( JDKCallbackInvocationHandler.java:103) at $Proxy21.getGreetingsCallback(Unknown Source) at helloworld.HelloWorldImpl.getGreetings(HelloWorldImpl.java:43) 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.tuscany.core.implementation.java.JavaTargetInvoker.invokeT arget(JavaTargetInvoker.java:90) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(Target InvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:65) at org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(Non BlockingBridgingInterceptor.java:79) at org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr2 37Work.run(Jsr237WorkScheduler.java:212) at org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo
[jira] Resolved: (TUSCANY-965) Context Injection is not functioning
[
https://issues.apache.org/jira/browse/TUSCANY-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe resolved TUSCANY-965.
Resolution: Fixed
Testing with r497459 shows this working, can you verify as well?
Context Injection is not functioning
Key: TUSCANY-965
URL: https://issues.apache.org/jira/browse/TUSCANY-965
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core, Java SCA Integration Tests
Affects Versions: Java-SCA-M3
Reporter: Lou Amodeo
Fix For: Java-SCA-M3
Appears that Contesxt injection when using setters and attributes is not
working. In each case the context attribute is null.
a) setter method
package org.apache.tuscany.sca.test;
import org.osoa.sca.CurrentCompositeContext;
import org.osoa.sca.ServiceReference;
import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Remotable;
import org.osoa.sca.annotations.Scope;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import junit.framework.Assert;
@Service(CallBackSetCallbackClient.class)
public class CallBackSetCallbackClientImpl implements
CallBackSetCallbackClient {
@Reference
protected CallBackSetCalbackService aCallBackService;
@Reference
protected CallBackSetCallbackCallback callBack;
private CompositeContext context;
@Context
public void setContext(CompositeContext aContext)
{
context = aContext;
}
public void run() {
if (context == null)
System.out.println(Context is null);
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
Context is null
b) attribute
package org.apache.tuscany.sca.test;
import org.osoa.sca.CurrentCompositeContext;
import org.osoa.sca.ServiceReference;
import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Remotable;
import org.osoa.sca.annotations.Scope;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import junit.framework.Assert;
@Service(CallBackSetCallbackClient.class)
public class CallBackSetCallbackClientImpl implements
CallBackSetCallbackClient {
@Reference
protected CallBackSetCalbackService aCallBackService;
@Reference
protected CallBackSetCallbackCallback callBack;
@Context
protected CompositeContext context;
public void run() {
if (context == null)
System.out.println(Context is null);
[WARNING] Unable to get resource from repository central
(http://repo1.maven.or
/maven2)
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
Context is null
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-966) getRequestContext() does not return a Context
[
https://issues.apache.org/jira/browse/TUSCANY-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465795
]
Ignacio Silva-Lepe commented on TUSCANY-966:
Although context injection works now (see TUSCANY-965), its api is still not
implemented
getRequestContext() does not return a Context
-
Key: TUSCANY-966
URL: https://issues.apache.org/jira/browse/TUSCANY-966
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core, Java SCA Integration Tests
Affects Versions: Java-SCA-M3
Reporter: Lou Amodeo
Assigned To: Jim Marino
Fix For: Java-SCA-M3
Remote Service hangs obtaining the request context using getRequestContext().
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
CallBackApiServiceImpl message received: Knock Knock
CallBackApiServiceImpl getting request context
[INFO] Test results: {skipped=0, completedCount=1, failures=1, errors=0}
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There were test failures
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 37 seconds
[INFO] Finished at: Fri Dec 01 08:14:20 EST 2006
[INFO] Final Memory: 7M/18M
[INFO]
---
Test set: org.apache.tuscany.sca.test.CallBackApiITest
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 30.023 sec
FAILURE!
testCallBackBasic(org.apache.tuscany.sca.test.CallBackApiITest) Time
elapsed: 30.023 sec FAILURE!
junit.framework.ComparisonFailure: CallBackBasicITest expected:Who's There
but was:null
at junit.framework.Assert.assertEquals(Assert.java:81)
at
org.apache.tuscany.sca.test.CallBackApiClientImpl.test1(CallBackApiClientImpl.java:55)
at
org.apache.tuscany.sca.test.CallBackApiClientImpl.run(CallBackApiClientImpl.java:21)
at
org.apache.tuscany.sca.test.CallBackApiITest.testCallBackBasic(CallBackApiITest.java:12)
package org.apache.tuscany.sca.test;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import org.osoa.sca.RequestContext;
@Service(CallBackApiService.class)
public class CallBackApiServiceImpl implements CallBackApiService {
@Context
protected CompositeContext compositeContext;
protected CallBackApiCallBack callback;
public void knockKnock(String aString) {
System.out.println(CallBackApiServiceImpl message received: +
aString);
callback = this.getCallBackInterface();
callback.callBackMessage(Who's There);
System.out.println(CallBackApiServiceImpl response sent);
return;
}
private CallBackApiCallBack getCallBackInterface()
{
System.out.println(CallBackApiServiceImpl getting request context);
RequestContext rc = compositeContext.getRequestContext();
System.out.println(CallBackApiServiceImpl getting callback from
request context);
callback = (CallBackApiCallBack)
rc.getServiceReference().getCallback();
System.out.println(CallBackApiServiceImpl returning callback);
return callback;
}
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1046) NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION)
[ https://issues.apache.org/jira/browse/TUSCANY-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465858 ] Ignacio Silva-Lepe commented on TUSCANY-1046: - To indicate to the client runtime that a conversation needs to be started, the interface used by the client needs to be marked as conversational. In other words, there needs to be an indication in the contract between the client and the service that the interaction is conversational. The actual syntax to use is, at the moment, @Scope(CONVERSATION) [notice that the spec illustrates this by using @Scope(session)] but I believe that is supposed to change, probably to something like @Conversational. The fact that the contract between the client and the service is conversational does not necessarily imply that the service implementation must be managed as conversational by the container. So it is possible to have a conversational client interface but not a service implementation managed as conversational. The opposite case, a non-conversational client interface and a conversational service implementation, does not make sense if any client at all wants to interact conversationally with the service, and so the client runtime does not start a conversation. This case can still be useful for handling conversational callbacks, for instance, in which case some other mechanism for starting the conversation will be implemented, but it is not there yet. NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION) -- Key: TUSCANY-1046 URL: https://issues.apache.org/jira/browse/TUSCANY-1046 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe Fix For: Java-SCA-Mx Attachments: test-CallBackSetCallbackConv.zip r494421 test-CallBackSetCallbackConv - This test attempts to use @Scope(CONVERSATION). Upon launch of test case using integration test environment the following NPE occurs. --- Test set: org.apache.tuscany.sca.test.CallBackSetCallbackConvITest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.02 sec FAILURE! testCallBackSetCallback(org.apache.tuscany.sca.test.CallBackSetCallbackConvITest) Time elapsed: 0.01 sec ERROR! java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:172) at java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:760) at org.apache.tuscany.core.services.store.memory.MemoryStore.insertRecord(MemoryStore.java:110) at org.apache.tuscany.core.component.scope.ConversationalScopeContainer.getInstance(ConversationalScopeContainer.java:92) at org.apache.tuscany.core.implementation.PojoAtomicComponent.getTargetInstance(PojoAtomicComponent.java:122) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.getInstance(JavaTargetInvoker.java:127) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.invokeTarget(JavaTargetInvoker.java:75) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(TargetInvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:44) at org.apache.tuscany.spi.wire.AbstractInboundInvocationHandler.invoke(AbstractInboundInvocationHandler.java:45) at org.apache.tuscany.core.wire.jdk.JDKInboundInvocationHandler.invoke(JDKInboundInvocationHandler.java:122) at $Proxy22.run(Unknown Source) at org.apache.tuscany.sca.test.CallBackSetCallbackConvITest.testCallBackSetCallback(CallBackSetCallbackConvITest.java:12) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-965) Context Injection is not functioning
[
https://issues.apache.org/jira/browse/TUSCANY-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe closed TUSCANY-965.
--
Context Injection is not functioning
Key: TUSCANY-965
URL: https://issues.apache.org/jira/browse/TUSCANY-965
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core, Java SCA Integration Tests
Affects Versions: Java-SCA-M3
Reporter: Lou Amodeo
Fix For: Java-SCA-M3
Appears that Contesxt injection when using setters and attributes is not
working. In each case the context attribute is null.
a) setter method
package org.apache.tuscany.sca.test;
import org.osoa.sca.CurrentCompositeContext;
import org.osoa.sca.ServiceReference;
import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Remotable;
import org.osoa.sca.annotations.Scope;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import junit.framework.Assert;
@Service(CallBackSetCallbackClient.class)
public class CallBackSetCallbackClientImpl implements
CallBackSetCallbackClient {
@Reference
protected CallBackSetCalbackService aCallBackService;
@Reference
protected CallBackSetCallbackCallback callBack;
private CompositeContext context;
@Context
public void setContext(CompositeContext aContext)
{
context = aContext;
}
public void run() {
if (context == null)
System.out.println(Context is null);
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
Context is null
b) attribute
package org.apache.tuscany.sca.test;
import org.osoa.sca.CurrentCompositeContext;
import org.osoa.sca.ServiceReference;
import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Remotable;
import org.osoa.sca.annotations.Scope;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import junit.framework.Assert;
@Service(CallBackSetCallbackClient.class)
public class CallBackSetCallbackClientImpl implements
CallBackSetCallbackClient {
@Reference
protected CallBackSetCalbackService aCallBackService;
@Reference
protected CallBackSetCallbackCallback callBack;
@Context
protected CompositeContext context;
public void run() {
if (context == null)
System.out.println(Context is null);
[WARNING] Unable to get resource from repository central
(http://repo1.maven.or
/maven2)
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
Context is null
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1003) NPE thrown by AxisEngine.send in service side of axis2 binding for async callbacks
[ https://issues.apache.org/jira/browse/TUSCANY-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465547 ] Ignacio Silva-Lepe commented on TUSCANY-1003: - I am not sure exactly how run.bat is put together, but I am not even able to get as far as you are, I get the following: C:\Devt\eclipse-311\eclipse\workspace\trunk\samples\sca\helloworldwsclient-async run java.io.FileNotFoundException: C:\Documents and Settings\Administrator\.m2\repos itory\org\apache\tuscany\standalone\1.0-SNAPSHOT\standalone-1.0-SNAPSHOT-bin.zip (The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at java.io.FileInputStream.init(FileInputStream.java:66) at sun.tools.jar.Main.run(Main.java:184) at sun.tools.jar.Main.main(Main.java:903) The system cannot find the file specified. ... The system cannot find the file specified. Unable to access jarfile target\standalone\bin\launcher.jar Following Rick's advice, I have used o/a/t/sca/runtime/standalone/assembly to run standalone. Before that, I have just used junit and run the test in the build by adding a TestCase suffixed copy of the client class. But even that at the moment is giving me: Running helloworld.HelloWorldWSAsyncClientTestCase log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAX Utils). log4j:WARN Please initialize the log4j system properly. org.osoa.sca.ServiceRuntimeException: Service not found [null] at org.apache.tuscany.core.implementation.composite.AbstractCompositeCon text.getInboundWire(AbstractCompositeContext.java:85) at org.apache.tuscany.core.implementation.composite.AbstractCompositeCon text.locateService(AbstractCompositeContext.java:67) at helloworld.HelloWorldWSAsyncClientTestCase.setUp(HelloWorldWSAsyncCli entTestCase.java:25) 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:288) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:816) Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.955 sec FA ILURE! I believe this is due to some of the refactoring that has been going on, but I have not actually investigated in detail to fix it, yet NPE thrown by AxisEngine.send in service side of axis2 binding for async callbacks -- Key: TUSCANY-1003 URL: https://issues.apache.org/jira/browse/TUSCANY-1003 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx I'm seeing an NPE thrown by AxisEngine.send in the service side of the axis2 binding for async callbacks. The trace is below. My current guess is that this may have something to do with the pass-by-value interceptor but I have not delved to deeply into the possible cause. For now I am leaving this in the Java SCA Axis binding component but that may change depending on the actual reason for the exception. org.apache.tuscany.binding.axis2.Axis2BindingRunTimeException: java.lang.NullPoi nterException at org.apache.tuscany.binding.axis2.Axis2ServiceCallbackTargetInvoker.in
[jira] Updated: (TUSCANY-965) Context Injection is not functioning
[
https://issues.apache.org/jira/browse/TUSCANY-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe updated TUSCANY-965:
---
Fix Version/s: Java-M3
Affects Version/s: Java-M3
Context Injection is not functioning
Key: TUSCANY-965
URL: https://issues.apache.org/jira/browse/TUSCANY-965
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core, Java SCA Integration Tests
Affects Versions: Java-M3
Reporter: Lou Amodeo
Fix For: Java-M3
Appears that Contesxt injection when using setters and attributes is not
working. In each case the context attribute is null.
a) setter method
package org.apache.tuscany.sca.test;
import org.osoa.sca.CurrentCompositeContext;
import org.osoa.sca.ServiceReference;
import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Remotable;
import org.osoa.sca.annotations.Scope;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import junit.framework.Assert;
@Service(CallBackSetCallbackClient.class)
public class CallBackSetCallbackClientImpl implements
CallBackSetCallbackClient {
@Reference
protected CallBackSetCalbackService aCallBackService;
@Reference
protected CallBackSetCallbackCallback callBack;
private CompositeContext context;
@Context
public void setContext(CompositeContext aContext)
{
context = aContext;
}
public void run() {
if (context == null)
System.out.println(Context is null);
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
Context is null
b) attribute
package org.apache.tuscany.sca.test;
import org.osoa.sca.CurrentCompositeContext;
import org.osoa.sca.ServiceReference;
import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Remotable;
import org.osoa.sca.annotations.Scope;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import junit.framework.Assert;
@Service(CallBackSetCallbackClient.class)
public class CallBackSetCallbackClientImpl implements
CallBackSetCallbackClient {
@Reference
protected CallBackSetCalbackService aCallBackService;
@Reference
protected CallBackSetCallbackCallback callBack;
@Context
protected CompositeContext context;
public void run() {
if (context == null)
System.out.println(Context is null);
[WARNING] Unable to get resource from repository central
(http://repo1.maven.or
/maven2)
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
Context is null
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-966) getRequestContext() does not return a Context
[
https://issues.apache.org/jira/browse/TUSCANY-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe updated TUSCANY-966:
---
Fix Version/s: Java-M3
Affects Version/s: Java-M3
getRequestContext() does not return a Context
-
Key: TUSCANY-966
URL: https://issues.apache.org/jira/browse/TUSCANY-966
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core, Java SCA Integration Tests
Affects Versions: Java-M3
Reporter: Lou Amodeo
Assigned To: Jim Marino
Fix For: Java-M3
Remote Service hangs obtaining the request context using getRequestContext().
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
CallBackApiServiceImpl message received: Knock Knock
CallBackApiServiceImpl getting request context
[INFO] Test results: {skipped=0, completedCount=1, failures=1, errors=0}
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There were test failures
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 37 seconds
[INFO] Finished at: Fri Dec 01 08:14:20 EST 2006
[INFO] Final Memory: 7M/18M
[INFO]
---
Test set: org.apache.tuscany.sca.test.CallBackApiITest
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 30.023 sec
FAILURE!
testCallBackBasic(org.apache.tuscany.sca.test.CallBackApiITest) Time
elapsed: 30.023 sec FAILURE!
junit.framework.ComparisonFailure: CallBackBasicITest expected:Who's There
but was:null
at junit.framework.Assert.assertEquals(Assert.java:81)
at
org.apache.tuscany.sca.test.CallBackApiClientImpl.test1(CallBackApiClientImpl.java:55)
at
org.apache.tuscany.sca.test.CallBackApiClientImpl.run(CallBackApiClientImpl.java:21)
at
org.apache.tuscany.sca.test.CallBackApiITest.testCallBackBasic(CallBackApiITest.java:12)
package org.apache.tuscany.sca.test;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import org.osoa.sca.RequestContext;
@Service(CallBackApiService.class)
public class CallBackApiServiceImpl implements CallBackApiService {
@Context
protected CompositeContext compositeContext;
protected CallBackApiCallBack callback;
public void knockKnock(String aString) {
System.out.println(CallBackApiServiceImpl message received: +
aString);
callback = this.getCallBackInterface();
callback.callBackMessage(Who's There);
System.out.println(CallBackApiServiceImpl response sent);
return;
}
private CallBackApiCallBack getCallBackInterface()
{
System.out.println(CallBackApiServiceImpl getting request context);
RequestContext rc = compositeContext.getRequestContext();
System.out.println(CallBackApiServiceImpl getting callback from
request context);
callback = (CallBackApiCallBack)
rc.getServiceReference().getCallback();
System.out.println(CallBackApiServiceImpl returning callback);
return callback;
}
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-882) Async samples fail in stanalone launcher
[ https://issues.apache.org/jira/browse/TUSCANY-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe reassigned TUSCANY-882: -- Assignee: Ignacio Silva-Lepe Async samples fail in stanalone launcher Key: TUSCANY-882 URL: https://issues.apache.org/jira/browse/TUSCANY-882 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-M2 Reporter: ant elder Assigned To: Ignacio Silva-Lepe Fix For: Java-M2 Simplecallback sample fails in stanalone launcher with the following exception: C:\SCA\SVN\TRUNK\samples\sca\simplecallbackjava -jar ..\..\..\..\..\StandaloneT\bin\launcher.jar target\sample-simplecallback-1.0-incubator-M2-SNAPSHOT.jar Main thread Thread[main,5,main] java.lang.IllegalStateException: Scope not running [6] at org.apache.tuscany.core.component.scope.AbstractScopeContainer.checkInit(AbstractScopeContainer.java:124) at org.apache.tuscany.core.component.scope.ModuleScopeContainer.getInstanceWrapper(ModuleScopeContainer.java:118) at org.apache.tuscany.core.component.scope.AbstractScopeContainer.getInstance(AbstractScopeContainer.java:105) at org.apache.tuscany.core.implementation.PojoAtomicComponent.getTargetInstance(PojoAtomicComponent.java:117) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.getInstance(JavaTargetInvoker.java:94) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.invokeTarget(JavaTargetInvoker.java:59) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(TargetInvokerExtension.java:60) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:44) at org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(NonBlockingBridgingInterceptor.java:70) at org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr237Work.run(Jsr237WorkScheduler.java:212) at org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-882) Async samples fail in stanalone launcher
[ https://issues.apache.org/jira/browse/TUSCANY-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-882. -- Resolution: Fixed Fix Version/s: (was: Java-M2) Java-Mx This now works with sca\runtime\standalone\assembly Async samples fail in stanalone launcher Key: TUSCANY-882 URL: https://issues.apache.org/jira/browse/TUSCANY-882 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-M2 Reporter: ant elder Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Simplecallback sample fails in stanalone launcher with the following exception: C:\SCA\SVN\TRUNK\samples\sca\simplecallbackjava -jar ..\..\..\..\..\StandaloneT\bin\launcher.jar target\sample-simplecallback-1.0-incubator-M2-SNAPSHOT.jar Main thread Thread[main,5,main] java.lang.IllegalStateException: Scope not running [6] at org.apache.tuscany.core.component.scope.AbstractScopeContainer.checkInit(AbstractScopeContainer.java:124) at org.apache.tuscany.core.component.scope.ModuleScopeContainer.getInstanceWrapper(ModuleScopeContainer.java:118) at org.apache.tuscany.core.component.scope.AbstractScopeContainer.getInstance(AbstractScopeContainer.java:105) at org.apache.tuscany.core.implementation.PojoAtomicComponent.getTargetInstance(PojoAtomicComponent.java:117) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.getInstance(JavaTargetInvoker.java:94) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.invokeTarget(JavaTargetInvoker.java:59) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(TargetInvokerExtension.java:60) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:44) at org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(NonBlockingBridgingInterceptor.java:70) at org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr237Work.run(Jsr237WorkScheduler.java:212) at org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1046) NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION)
[ https://issues.apache.org/jira/browse/TUSCANY-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464223 ] Ignacio Silva-Lepe commented on TUSCANY-1046: - Just to make sure. Is the interface implemented by the conversational service annotated as conversational (ie, with @Scope(CONVERSATION)) ? NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION) -- Key: TUSCANY-1046 URL: https://issues.apache.org/jira/browse/TUSCANY-1046 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Reporter: Lou Amodeo Attachments: test-CallBackSetCallbackConv.zip r494421 test-CallBackSetCallbackConv - This test attempts to use @Scope(CONVERSATION). Upon launch of test case using integration test environment the following NPE occurs. --- Test set: org.apache.tuscany.sca.test.CallBackSetCallbackConvITest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.02 sec FAILURE! testCallBackSetCallback(org.apache.tuscany.sca.test.CallBackSetCallbackConvITest) Time elapsed: 0.01 sec ERROR! java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:172) at java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:760) at org.apache.tuscany.core.services.store.memory.MemoryStore.insertRecord(MemoryStore.java:110) at org.apache.tuscany.core.component.scope.ConversationalScopeContainer.getInstance(ConversationalScopeContainer.java:92) at org.apache.tuscany.core.implementation.PojoAtomicComponent.getTargetInstance(PojoAtomicComponent.java:122) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.getInstance(JavaTargetInvoker.java:127) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.invokeTarget(JavaTargetInvoker.java:75) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(TargetInvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:44) at org.apache.tuscany.spi.wire.AbstractInboundInvocationHandler.invoke(AbstractInboundInvocationHandler.java:45) at org.apache.tuscany.core.wire.jdk.JDKInboundInvocationHandler.invoke(JDKInboundInvocationHandler.java:122) at $Proxy22.run(Unknown Source) at org.apache.tuscany.sca.test.CallBackSetCallbackConvITest.testCallBackSetCallback(CallBackSetCallbackConvITest.java:12) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1001) @SessionID injection is not working..
[ https://issues.apache.org/jira/browse/TUSCANY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464227 ] Ignacio Silva-Lepe commented on TUSCANY-1001: - I don't think this is a blocker for TUSCANY-1046. Actually, the reason you don't see a conversation id injected is that there is none, which may be caused by the interface not being annotated as conversational. See comment to TUSCANY-1046. I have verified in the loanappconversation sample that when there is a conversation id available, it does get injected into the member annotated by @ConversationID. But this annotation per se is not the way to get a conversation id created. @SessionID injection is not working.. -- Key: TUSCANY-1001 URL: https://issues.apache.org/jira/browse/TUSCANY-1001 Project: Tuscany Issue Type: Bug Components: Java SCA Core, Java SCA Integration Tests Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe When using the @SessionID annotation and instance variable protected String sessionID the session is not being injected and sessionID is null. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-1046) NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION)
[ https://issues.apache.org/jira/browse/TUSCANY-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe reassigned TUSCANY-1046: --- Assignee: Ignacio Silva-Lepe NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION) -- Key: TUSCANY-1046 URL: https://issues.apache.org/jira/browse/TUSCANY-1046 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe Attachments: test-CallBackSetCallbackConv.zip r494421 test-CallBackSetCallbackConv - This test attempts to use @Scope(CONVERSATION). Upon launch of test case using integration test environment the following NPE occurs. --- Test set: org.apache.tuscany.sca.test.CallBackSetCallbackConvITest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.02 sec FAILURE! testCallBackSetCallback(org.apache.tuscany.sca.test.CallBackSetCallbackConvITest) Time elapsed: 0.01 sec ERROR! java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:172) at java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:760) at org.apache.tuscany.core.services.store.memory.MemoryStore.insertRecord(MemoryStore.java:110) at org.apache.tuscany.core.component.scope.ConversationalScopeContainer.getInstance(ConversationalScopeContainer.java:92) at org.apache.tuscany.core.implementation.PojoAtomicComponent.getTargetInstance(PojoAtomicComponent.java:122) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.getInstance(JavaTargetInvoker.java:127) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.invokeTarget(JavaTargetInvoker.java:75) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(TargetInvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:44) at org.apache.tuscany.spi.wire.AbstractInboundInvocationHandler.invoke(AbstractInboundInvocationHandler.java:45) at org.apache.tuscany.core.wire.jdk.JDKInboundInvocationHandler.invoke(JDKInboundInvocationHandler.java:122) at $Proxy22.run(Unknown Source) at org.apache.tuscany.sca.test.CallBackSetCallbackConvITest.testCallBackSetCallback(CallBackSetCallbackConvITest.java:12) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1046) NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION)
[ https://issues.apache.org/jira/browse/TUSCANY-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464332 ] Ignacio Silva-Lepe commented on TUSCANY-1046: - For conversations, the annotation can be used on both the interface, to denote a conversational contract with the client, and the implementation, to indicate to the component's container to keep track of the component's conversational state. So, depending on the scenario, both uses can occur at the same time. The loanappconversation sample does this, for instance. I agree that the wording of the spec does not reflect this, so it most likely will be changed. Since you are past the problem, I assume that this issue can be closed? NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION) -- Key: TUSCANY-1046 URL: https://issues.apache.org/jira/browse/TUSCANY-1046 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe Attachments: test-CallBackSetCallbackConv.zip r494421 test-CallBackSetCallbackConv - This test attempts to use @Scope(CONVERSATION). Upon launch of test case using integration test environment the following NPE occurs. --- Test set: org.apache.tuscany.sca.test.CallBackSetCallbackConvITest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.02 sec FAILURE! testCallBackSetCallback(org.apache.tuscany.sca.test.CallBackSetCallbackConvITest) Time elapsed: 0.01 sec ERROR! java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:172) at java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:760) at org.apache.tuscany.core.services.store.memory.MemoryStore.insertRecord(MemoryStore.java:110) at org.apache.tuscany.core.component.scope.ConversationalScopeContainer.getInstance(ConversationalScopeContainer.java:92) at org.apache.tuscany.core.implementation.PojoAtomicComponent.getTargetInstance(PojoAtomicComponent.java:122) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.getInstance(JavaTargetInvoker.java:127) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.invokeTarget(JavaTargetInvoker.java:75) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(TargetInvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:44) at org.apache.tuscany.spi.wire.AbstractInboundInvocationHandler.invoke(AbstractInboundInvocationHandler.java:45) at org.apache.tuscany.core.wire.jdk.JDKInboundInvocationHandler.invoke(JDKInboundInvocationHandler.java:122) at $Proxy22.run(Unknown Source) at org.apache.tuscany.sca.test.CallBackSetCallbackConvITest.testCallBackSetCallback(CallBackSetCallbackConvITest.java:12) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1001) @SessionID injection is not working..
[ https://issues.apache.org/jira/browse/TUSCANY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464334 ] Ignacio Silva-Lepe commented on TUSCANY-1001: - Since you are past the TUSCANY-1046 problem, I assume that this issue can be closed as well? @SessionID injection is not working.. -- Key: TUSCANY-1001 URL: https://issues.apache.org/jira/browse/TUSCANY-1001 Project: Tuscany Issue Type: Bug Components: Java SCA Core, Java SCA Integration Tests Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe When using the @SessionID annotation and instance variable protected String sessionID the session is not being injected and sessionID is null. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-1001) @SessionID injection is not working..
[ https://issues.apache.org/jira/browse/TUSCANY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-1001. --- Resolution: Fixed Fix Version/s: Java-Mx @SessionID injection is not working.. -- Key: TUSCANY-1001 URL: https://issues.apache.org/jira/browse/TUSCANY-1001 Project: Tuscany Issue Type: Bug Components: Java SCA Core, Java SCA Integration Tests Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx When using the @SessionID annotation and instance variable protected String sessionID the session is not being injected and sessionID is null. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-1046) NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION)
[ https://issues.apache.org/jira/browse/TUSCANY-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-1046. --- Resolution: Fixed Fix Version/s: Java-Mx NPE in MemoryStore.insertRecord() when @SCOPE(CONVERSATION) -- Key: TUSCANY-1046 URL: https://issues.apache.org/jira/browse/TUSCANY-1046 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: test-CallBackSetCallbackConv.zip r494421 test-CallBackSetCallbackConv - This test attempts to use @Scope(CONVERSATION). Upon launch of test case using integration test environment the following NPE occurs. --- Test set: org.apache.tuscany.sca.test.CallBackSetCallbackConvITest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.02 sec FAILURE! testCallBackSetCallback(org.apache.tuscany.sca.test.CallBackSetCallbackConvITest) Time elapsed: 0.01 sec ERROR! java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:172) at java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:760) at org.apache.tuscany.core.services.store.memory.MemoryStore.insertRecord(MemoryStore.java:110) at org.apache.tuscany.core.component.scope.ConversationalScopeContainer.getInstance(ConversationalScopeContainer.java:92) at org.apache.tuscany.core.implementation.PojoAtomicComponent.getTargetInstance(PojoAtomicComponent.java:122) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.getInstance(JavaTargetInvoker.java:127) at org.apache.tuscany.core.implementation.java.JavaTargetInvoker.invokeTarget(JavaTargetInvoker.java:75) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(TargetInvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:44) at org.apache.tuscany.spi.wire.AbstractInboundInvocationHandler.invoke(AbstractInboundInvocationHandler.java:45) at org.apache.tuscany.core.wire.jdk.JDKInboundInvocationHandler.invoke(JDKInboundInvocationHandler.java:122) at $Proxy22.run(Unknown Source) at org.apache.tuscany.sca.test.CallBackSetCallbackConvITest.testCallBackSetCallback(CallBackSetCallbackConvITest.java:12) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1043) NPE with Pass By Value Interceptor during multiple callbacks
[
https://issues.apache.org/jira/browse/TUSCANY-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463600
]
Ignacio Silva-Lepe commented on TUSCANY-1043:
-
I believe this is related to TUSCANY-1004, where the greeterws sample (both at
the client and the server sides) gets the same NPE with a similar trace. I
would not call this issue duplicate but I believe a fix to TUSCANY-1004 will
resolve this issue as well.
NPE with Pass By Value Interceptor during multiple callbacks
Key: TUSCANY-1043
URL: https://issues.apache.org/jira/browse/TUSCANY-1043
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core, Java SCA Integration Tests
Reporter: Lou Amodeo
r494421 - NullPointerException is thrown by PassByValueInterceptor when
processing the 2 nd of 3 callbacks. A multiple callbacks issue was fixed
in JIRA-976 and this integration testcase was functioning. This issue that
is now occurring appears to be completely different than -976. Please see
the testcase attached to -976 to reproduce.
.apache.org/repo/m2-incubating-repository/)
Downloading:
http://ws.zones.apache.org/repository/woodstox/poms/wstx-asl-3.0.1.
pom
[WARNING] Unable to get resource from repository apache.ws.m1.snapshots
(http://
ws.zones.apache.org/repository)
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.0.1/wstx-asl-3.0.
1.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org
/maven2)
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
CallBackBasicServiceImpl message received: Knock Knock
Entering callback callBackMessage: Who's There
CallBackBasicServiceImpl message received: No Reply Desired
CallBackBasicServiceImpl No response desired
java.lang.NullPointerException
at
org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.copy(
PassByValueInterceptor.java:110)
at
org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok
e(PassByValueInterceptor.java:71)
at
org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(Non
BlockingBridgingInterceptor.java:79)
at
org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr2
37Work.run(Jsr237WorkScheduler.java:212)
at
org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo
rkManager$DecoratingWork.run(ThreadPoolWorkManager.java:206)
CallBackBasicServiceImpl message received: Call me back 3 times
Entering callback increment: Who's There 1
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:665)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:690)
at java.lang.Thread.run(Thread.java:797)
[INFO] Test results: {skipped=0, completedCount=1, failures=1, errors=0}
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There were test failures
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: There were test failures
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:555)
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
[jira] Closed: (TUSCANY-977) NoRegisteredCallbackException not thrown to client
[
https://issues.apache.org/jira/browse/TUSCANY-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe closed TUSCANY-977.
--
Resolution: Fixed
Fix Version/s: Java-Mx
NoRegisteredCallbackException not thrown to client
--
Key: TUSCANY-977
URL: https://issues.apache.org/jira/browse/TUSCANY-977
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Assigned To: Ignacio Silva-Lepe
Fix For: Java-Mx
NoRegisteredCallbackException not thrown to client.
The client does not implement the callback interface and does not call
setCallback prior to calling the service. I was expecting to receive an
exception and instead the service was invoked.
try
{
aCallBackService.knockKnock(Knock Knock);
}
catch (NoRegisteredCallbackException NotRegEx)
{
correctException = true;
}
catch (Exception ex)
{
ex.printStackTrace();
}
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
CallBackBasicServiceImpl message received: Knock Knock
java.lang.NullPointerException
at
org.apache.tuscany.sca.test.CallBackSetCallbackServiceImpl.knockKnock
(CallBackSetCallbackServiceImpl.java:29)
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.apache.tuscany.core.implementation.java.JavaTargetInvoker.invokeT
arget(JavaTargetInvoker.java:71)
at
org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(Target
InvokerExtension.java:64)
at
org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce
ptor.java:44)
at
org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(Non
BlockingBridgingInterceptor.java:80)
at
org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr2
37Work.run(Jsr237WorkScheduler.java:212)
at
org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo
rkManager$DecoratingWork.run(ThreadPoolWorkManager.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:665)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:690)
at java.lang.Thread.run(Thread.java:797)
[INFO] Test results: {skipped=0, completedCount=1, failures=1, errors=0}
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There were test failures
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 9 seconds
[INFO] Finished at: Wed Dec 06 14:06:57 EST 2006
[INFO] Final Memory: 7M/19M
[INFO]
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1004) NPE thrown by PassByValueInterceptor in one-way async ws sample (greeterws-oneway)
[ https://issues.apache.org/jira/browse/TUSCANY-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463122 ] Ignacio Silva-Lepe commented on TUSCANY-1004: - I am now seeing a related NPE thrown by AxiomDataBinding in this case, called by PassByValueInterceptor at about the same spot as the previous NPE, i.e., after the invocation of the service returns null. This happens in the client side of the sample though. Running greeter.GreeterWSOneWayClientTestCase log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAX Utils). log4j:WARN Please initialize the log4j system properly. java.lang.NullPointerException at org.apache.tuscany.databinding.axiom.AxiomDataBinding.copy(AxiomDataB inding.java:56) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.copy( PassByValueInterceptor.java:105) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:71) at org.apache.tuscany.core.wire.SynchronousBridgingInterceptor.invoke(Sy nchronousBridgingInterceptor.java:41) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:71) at org.apache.tuscany.spi.wire.AbstractOutboundInvocationHandler.invoke( AbstractOutboundInvocationHandler.java:91) at org.apache.tuscany.core.wire.jdk.JDKOutboundInvocationHandler.invoke( JDKOutboundInvocationHandler.java:166) at $Proxy25.greet(Unknown Source) at greeter.GreeterImpl.greet(GreeterImpl.java:35) 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.tuscany.core.implementation.java.JavaTargetInvoker.invokeT arget(JavaTargetInvoker.java:93) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(Target InvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44) at org.apache.tuscany.spi.wire.AbstractInboundInvocationHandler.invoke(A bstractInboundInvocationHandler.java:45) at org.apache.tuscany.core.wire.jdk.JDKInboundInvocationHandler.invoke(J DKInboundInvocationHandler.java:122) at $Proxy24.greet(Unknown Source) at greeter.GreeterWSOneWayClientTestCase.testWSClient(GreeterWSOneWayCli entTestCase.java:47) NPE thrown by PassByValueInterceptor in one-way async ws sample (greeterws-oneway) -- Key: TUSCANY-1004 URL: https://issues.apache.org/jira/browse/TUSCANY-1004 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding, Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx I'm seeing an NPE thrown by PassByValueInterceptor in the greeterws-oneway sample, service side. The trace is below. This happens after the invocation of the service returns (with a null, since it is a void return type). The target invoker puts the null return value in the message body and returns the message. The interceptor then gets the body and tries to do something with it. My thought then was that the supplychain sample should also fail, but it does not, not sure why, perhaps the interceptor is not used there. Notice that the databinding interceptor does check to see if the operation is non-blocking (ie, one-way) before it tries to do something with the result, but in that case the interceptor returns immediately and does not do any more transformation. Not sure what the correct behavior for the pass-by-value interceptor should be here. Trace from tomcat: INFO: Server startup in 5155 ms Hello John java.lang.NullPointerException at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.copy( PassByValueInterceptor.java:108) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:68) at org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(Non BlockingBridgingInterceptor.java:79) at org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr2 37Work.run(Jsr237WorkScheduler.java:212) at org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo rkManager$DecoratingWork.run(ThreadPoolWorkManager.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:675) at java.lang.Thread.run(Thread.java:595)
[jira] Closed: (TUSCANY-270) Bigbank sample should demonstrate the SCA async PM
[ https://issues.apache.org/jira/browse/TUSCANY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-270. -- Resolution: Fixed The basic mediator idea has been implemented. Also the sample has been evolving. If more functionality related to this JIRA is needed, it may be more appropriate to open a new JIRA. Bigbank sample should demonstrate the SCA async PM -- Key: TUSCANY-270 URL: https://issues.apache.org/jira/browse/TUSCANY-270 Project: Tuscany Issue Type: Bug Components: Java BigBank Scenario Affects Versions: Java-Mx Reporter: Jean-Sebastien Delfino Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: async-bigbank-mediator.txt, async-bigbank-new.txt, async-bigbank.txt The Bigbank sample should demonstrate the SCA async PM. Rick, Jim, could you please add comments to this JIRA with your suggestions to improve the sample to demonstrate the SCA async PM? Thanks. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-334) @SessionId is not injected
[ https://issues.apache.org/jira/browse/TUSCANY-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-334. -- Resolution: Duplicate This is also dealt with in the more recent TUSCANY-1001 @SessionId is not injected -- Key: TUSCANY-334 URL: https://issues.apache.org/jira/browse/TUSCANY-334 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-Mx Reporter: Yang Lei Assigned To: Ignacio Silva-Lepe Priority: Minor Fix For: Java-Mx Declared a field with annotation of @SessionID , the field value is not injected during runtime. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-334) @SessionId is not injected
[ https://issues.apache.org/jira/browse/TUSCANY-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe reassigned TUSCANY-334: -- Assignee: Ignacio Silva-Lepe (was: Jim Marino) @SessionId is not injected -- Key: TUSCANY-334 URL: https://issues.apache.org/jira/browse/TUSCANY-334 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-Mx Reporter: Yang Lei Assigned To: Ignacio Silva-Lepe Priority: Minor Fix For: Java-Mx Declared a field with annotation of @SessionID , the field value is not injected during runtime. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-976) Multiple Callbacks fail
[
https://issues.apache.org/jira/browse/TUSCANY-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe closed TUSCANY-976.
--
Multiple Callbacks fail
---
Key: TUSCANY-976
URL: https://issues.apache.org/jira/browse/TUSCANY-976
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Assigned To: Ignacio Silva-Lepe
Fix For: Java-Mx
Attachments: test-CallBackBasic.zip
I have a stateless service that performs multiple callbacks. The first
callback is successful. The next callback hangs during the call to the
callback method.
public void multiCallBack(String aString) {
System.out.println(CallBackBasicServiceImpl message received: +
aString);
callback.callBackIncrement(Who's There 1);
System.out.println(CallBackBasicServiceImpl response sent);
callback.callBackIncrement(Who's There 2);
System.out.println(CallBackBasicServiceImpl response sent);
callback.callBackIncrement(Who's There 3);
System.out.println(CallBackBasicServiceImpl response sent);
return;
}
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-955) IllegalPropertyException thrown when loading MemoryStore
[ https://issues.apache.org/jira/browse/TUSCANY-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-955. -- IllegalPropertyException thrown when loading MemoryStore Key: TUSCANY-955 URL: https://issues.apache.org/jira/browse/TUSCANY-955 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Raymond Feng Fix For: Java-Mx As a result of autowiring MemoryStore, an IllegalPropertyException is thrown on getExpirationOffset. A trace follows. To reproduce, uncomment the property annotation on getExpirationOffset. Running loanappconversation.LoanAppConversationTestCase org.apache.tuscany.spi.implementation.java.IllegalPropertyException: Method does not have void return type [public long org.apache.tuscany.core.services.store.m emory.MemoryStore.getExpirationOffset()] Context stack trace: [tuscany.system][store] at org.apache.tuscany.spi.implementation.java.AbstractPropertyProcessor. visitMethod(AbstractPropertyProcessor.java:55) at org.apache.tuscany.core.implementation.IntrospectionRegistryImpl.intr ospect(IntrospectionRegistryImpl.java:90) at org.apache.tuscany.core.implementation.system.loader.SystemComponentT ypeLoader.loadByIntrospection(SystemComponentTypeLoader.java:89) at org.apache.tuscany.core.implementation.system.loader.SystemComponentT ypeLoader.load(SystemComponentTypeLoader.java:72) at org.apache.tuscany.core.implementation.system.loader.SystemComponentT ypeLoader.load(SystemComponentTypeLoader.java:45) at org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(L oaderRegistryImpl.java:163) at org.apache.tuscany.core.implementation.system.loader.SystemImplementa tionLoader.load(SystemImplementationLoader.java:61) at org.apache.tuscany.core.implementation.system.loader.SystemImplementa tionLoader.load(SystemImplementationLoader.java:42) at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistry Impl.java:94) at org.apache.tuscany.core.loader.ComponentLoader.loadImplementation(Com ponentLoader.java:184) at org.apache.tuscany.core.loader.ComponentLoader.load(ComponentLoader.j ava:128) at org.apache.tuscany.core.loader.ComponentLoader.load(ComponentLoader.j ava:70) at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistry Impl.java:94) at org.apache.tuscany.core.implementation.composite.CompositeLoader.load (CompositeLoader.java:88) at org.apache.tuscany.core.implementation.composite.CompositeLoader.load (CompositeLoader.java:64) at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistry Impl.java:94) at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistry Impl.java:112) at org.apache.tuscany.core.implementation.system.loader.SystemCompositeC omponentTypeLoader.loadFromSidefile(SystemCompositeComponentTypeLoader.java:68) at org.apache.tuscany.core.implementation.system.loader.SystemCompositeC omponentTypeLoader.load(SystemCompositeComponentTypeLoader.java:59) at org.apache.tuscany.core.implementation.system.loader.SystemCompositeC omponentTypeLoader.load(SystemCompositeComponentTypeLoader.java:38) at org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(L oaderRegistryImpl.java:163) at org.apache.tuscany.core.deployer.DeployerImpl.load(DeployerImpl.java: 101) at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav a:76) at org.apache.tuscany.core.launcher.LauncherImpl.bootRuntime(LauncherImp l.java:101) at org.apache.tuscany.core.launcher.LauncherImpl.bootRuntime(LauncherImp l.java:158) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-823) Adding one way samples for ws/axis2
[ https://issues.apache.org/jira/browse/TUSCANY-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-823. -- Resolution: Fixed Adding one way samples for ws/axis2 --- Key: TUSCANY-823 URL: https://issues.apache.org/jira/browse/TUSCANY-823 Project: Tuscany Issue Type: New Feature Components: Java SCA Axis Binding Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: ws-ow-sample-client.patch, ws-ow-sample.patch Two samples are added that exercise a one-way ws/axis2 interaction -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-642) Composite references and services - model and runtime representations
[ https://issues.apache.org/jira/browse/TUSCANY-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-642. -- Resolution: Fixed Assignee: Ignacio Silva-Lepe (was: Jim Marino) Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: https://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch, SimplerCompositeReferenceInvocation.patch, SimplerCompositeReferenceInvocation2.patch, SimplerCompositeReferenceInvocation3.patch, SimplerCompositeReferenceInvocation4.patch, SimplerCompositeReferenceInvocation5.patch, SimplerCompositeReferenceInvocation6.patch, SimplerCompositeReferenceInvocation7.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-768) SynchronousBridgingInterceptor seems to be catching NPE
[ https://issues.apache.org/jira/browse/TUSCANY-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignacio Silva-Lepe closed TUSCANY-768. -- Resolution: Fixed Assignee: Ignacio Silva-Lepe SynchronousBridgingInterceptor seems to be catching NPE --- Key: TUSCANY-768 URL: https://issues.apache.org/jira/browse/TUSCANY-768 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Trying the plain inner.composite sample without a fix for TUSCANY-767, gives the failure below. It seems like the SynchronousBridgingInterceptor may be having a problem. Having tried to look yet. It may be related to TUSCANY-767, but in case it is not. --- T E S T S --- Running innercomposite.InnerCompositeTestCase Main thread Thread[main,5,main] org.apache.tuscany.spi.wire.InvocationRuntimeException: java.lang.NullPointerExc eption at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:76) at org.apache.tuscany.core.wire.AbstractOutboundInvocationHandler.invoke (AbstractOutboundInvocationHandler.java:65) at org.apache.tuscany.core.wire.jdk.JDKOutboundInvocationHandler.invoke( JDKOutboundInvocationHandler.java:121) at $Proxy17.clientMethod(Unknown Source) at innercomposite.InnerCompositeTestCase.test(InnerCompositeTestCase.jav a:39) 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 junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) 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:269) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:788) Caused by: java.lang.NullPointerException at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:71) at org.apache.tuscany.core.wire.SynchronousBridgingInterceptor.invoke(Sy nchronousBridgingInterceptor.java:41) at org.apache.tuscany.core.wire.SynchronousBridgingInterceptor.invoke(Sy nchronousBridgingInterceptor.java:41) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:71) at org.apache.tuscany.core.wire.AbstractOutboundInvocationHandler.invoke (AbstractOutboundInvocationHandler.java:65) at org.apache.tuscany.core.wire.jdk.JDKOutboundInvocationHandler.invoke( JDKOutboundInvocationHandler.java:121) at $Proxy18.someMethod(Unknown Source) at innercomposite.SourceImpl.clientMethod(SourceImpl.java:43) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at
[jira] Created: (TUSCANY-1022) Conversation id injection for conversational service provider -- annotation and field access
Conversation id injection for conversational service provider -- annotation and field access Key: TUSCANY-1022 URL: https://issues.apache.org/jira/browse/TUSCANY-1022 Project: Tuscany Issue Type: Bug Components: Specification Reporter: Ignacio Silva-Lepe Assigned To: Michael John Edwards Section 1.5.2.2 of the Client and Implementation for Java spec shows the use of a @SessionID annotation to inject a conversation id to a conversational service provider, the annotation should be @ConversationID In addition, section 1.5.2.2 of the spec illustrates the use of the injection annotation with a field that has private access. The annotation should be used on protected or public fields only. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-1001) @SessionID injection is not working..
[ http://issues.apache.org/jira/browse/TUSCANY-1001?page=all ] Ignacio Silva-Lepe reassigned TUSCANY-1001: --- Assignee: Ignacio Silva-Lepe @SessionID injection is not working.. -- Key: TUSCANY-1001 URL: http://issues.apache.org/jira/browse/TUSCANY-1001 Project: Tuscany Issue Type: Bug Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe When using the @SessionID annotation and instance variable protected String sessionID the session is not being injected and sessionID is null. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1001) @SessionID injection is not working..
[ http://issues.apache.org/jira/browse/TUSCANY-1001?page=comments#action_12460269 ] Ignacio Silva-Lepe commented on TUSCANY-1001: - I am assuming you are trying to get a conversation id injected. I may be wrong, but I believe the annotation to use is going to be @ConversationID. I have checked in a fix with r489355 that adds support for @ConversationID injection. If it turns out that @SessionID is also, or only, needed for this, it should be pretty simple to add/change it. For now, can you verify using @ConversationID and let me know? Notice that, at least for now also, the qualifier for the field/method should be protected and not private. @SessionID injection is not working.. -- Key: TUSCANY-1001 URL: http://issues.apache.org/jira/browse/TUSCANY-1001 Project: Tuscany Issue Type: Bug Reporter: Lou Amodeo Assigned To: Ignacio Silva-Lepe When using the @SessionID annotation and instance variable protected String sessionID the session is not being injected and sessionID is null. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1003) NPE thrown by AxisEngine.send in service side of axis2 binding for async callbacks
NPE thrown by AxisEngine.send in service side of axis2 binding for async callbacks -- Key: TUSCANY-1003 URL: http://issues.apache.org/jira/browse/TUSCANY-1003 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx I'm seeing an NPE thrown by AxisEngine.send in the service side of the axis2 binding for async callbacks. The trace is below. My current guess is that this may have something to do with the pass-by-value interceptor but I have not delved to deeply into the possible cause. For now I am leaving this in the Java SCA Axis binding component but that may change depending on the actual reason for the exception. org.apache.tuscany.binding.axis2.Axis2BindingRunTimeException: java.lang.NullPoi nterException at org.apache.tuscany.binding.axis2.Axis2ServiceCallbackTargetInvoker.in vokeTarget(Axis2ServiceCallbackTargetInvoker.java:78) at org.apache.tuscany.binding.axis2.Axis2ServiceCallbackTargetInvoker.in voke(Axis2ServiceCallbackTargetInvoker.java:90) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:65) at org.apache.tuscany.core.wire.SynchronousBridgingInterceptor.invoke(Sy nchronousBridgingInterceptor.java:41) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:70) at org.apache.tuscany.spi.wire.AbstractOutboundInvocationHandler.invoke( AbstractOutboundInvocationHandler.java:91) at org.apache.tuscany.core.wire.jdk.JDKCallbackInvocationHandler.invoke( JDKCallbackInvocationHandler.java:103) at $Proxy21.getGreetingsCallback(Unknown Source) at helloworld.HelloWorldImpl.getGreetings(HelloWorldImpl.java:43) 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.tuscany.core.implementation.java.JavaTargetInvoker.invokeT arget(JavaTargetInvoker.java:90) at org.apache.tuscany.spi.extension.TargetInvokerExtension.invoke(Target InvokerExtension.java:67) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:65) at org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(Non BlockingBridgingInterceptor.java:79) at org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr2 37Work.run(Jsr237WorkScheduler.java:212) at org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo rkManager$DecoratingWork.run(ThreadPoolWorkManager.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(Internal OutputBuffer.java:746) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433) at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuf fer.java:304) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java: 991) at org.apache.coyote.Response.action(Response.java:182) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java: 322) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:29 3) at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputSt ream.java:97) at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:410) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213) at java.io.BufferedWriter.flush(BufferedWriter.java:236) at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:184) at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:269) at org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWrite r.java:119) at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeIm pl.java:412) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingO utputStream(CommonsHTTPTransportSender.java:275) at
[jira] Created: (TUSCANY-1004) NPE thrown by PassByValueInterceptor in one-way async ws sample (greeterws-oneway)
NPE thrown by PassByValueInterceptor in one-way async ws sample (greeterws-oneway) -- Key: TUSCANY-1004 URL: http://issues.apache.org/jira/browse/TUSCANY-1004 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding, Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx I'm seeing an NPE thrown by PassByValueInterceptor in the greeterws-oneway sample, service side. The trace is below. This happens after the invocation of the service returns (with a null, since it is a void return type). The target invoker puts the null return value in the message body and returns the message. The interceptor then gets the body and tries to do something with it. My thought then was that the supplychain sample should also fail, but it does not, not sure why, perhaps the interceptor is not used there. Notice that the databinding interceptor does check to see if the operation is non-blocking (ie, one-way) before it tries to do something with the result, but in that case the interceptor returns immediately and does not do any more transformation. Not sure what the correct behavior for the pass-by-value interceptor should be here. Trace from tomcat: INFO: Server startup in 5155 ms Hello John java.lang.NullPointerException at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.copy( PassByValueInterceptor.java:108) at org.apache.tuscany.core.databinding.impl.PassByValueInterceptor.invok e(PassByValueInterceptor.java:68) at org.apache.tuscany.core.wire.NonBlockingBridgingInterceptor$1.run(Non BlockingBridgingInterceptor.java:79) at org.apache.tuscany.core.services.work.jsr237.Jsr237WorkScheduler$Jsr2 37Work.run(Jsr237WorkScheduler.java:212) at org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo rkManager$DecoratingWork.run(ThreadPoolWorkManager.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:675) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-975) Scope object factory not registered for scope [CONVERSATION]
[
http://issues.apache.org/jira/browse/TUSCANY-975?page=comments#action_12458491
]
Ignacio Silva-Lepe commented on TUSCANY-975:
I have added ConversationalScopeObjectFactory to embeddedMaven.scdl with
r487218, can you test to see if this fixes it?
Scope object factory not registered for scope [CONVERSATION]
Key: TUSCANY-975
URL: http://issues.apache.org/jira/browse/TUSCANY-975
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Conversation scope is not recognized.
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Scope object factory not registered for scope [CONVERSATION]
[INFO]
[INFO] Trace
org.apache.tuscany.spi.component.ScopeNotFoundException: Scope object factory
n
t registered for scope [CONVERSATION]
at
org.apache.tuscany.core.component.scope.ScopeRegistryImpl.getScopeCo
tainer(ScopeRegistryImpl.java:65)
at
org.apache.tuscany.core.implementation.java.JavaComponentBuilder.bui
d(JavaComponentBuilder.java:76)
at
org.apache.tuscany.core.implementation.java.JavaComponentBuilder.bui
d(JavaComponentBuilder.java:53)
at
org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderReg
stryImpl.java:115)
at
org.apache.tuscany.core.implementation.composite.CompositeBuilder.bu
ld(CompositeBuilder.java:93)
at
org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderReg
stryImpl.java:115)
at
org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.jav
:115)
at
org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.ja
a:81)
at
org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScd
(AbstractRuntime.java:136)
at
org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(
avenEmbeddedRuntime.java:85)
at
org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(Tuscany
tartMojo.java:102)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlug
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Def
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defa
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultL
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(DelegatingMethodAcce
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: Wed Dec 06 13:43:48 EST 2006
[INFO] Final Memory: 6M/17M
[INFO]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-923) @Scope(REQUEST) causes ScopeNotFoundException
[ http://issues.apache.org/jira/browse/TUSCANY-923?page=comments#action_12458492 ] Ignacio Silva-Lepe commented on TUSCANY-923: I have added RequestScopeObjectFactory to embeddedMaven.scdl with r487218, can you test to see if this fixes it? @Scope(REQUEST) causes ScopeNotFoundException --- Key: TUSCANY-923 URL: http://issues.apache.org/jira/browse/TUSCANY-923 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-Mx Reporter: Greg Dritschler Assigned To: Jim Marino Using @Scope(REQUEST) in an implementation class causes the following error at build time. [INFO] [INFO] Scope object factory not registered for scope [REQUEST] [INFO] [INFO] Trace org.apache.tuscany.spi.component.ScopeNotFoundException: Scope object factory not registered for scope [REQUEST] at org.apache.tuscany.core.component.scope.ScopeRegistryImpl.getScopeContainer(ScopeRegistryImpl.java:65) at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.build(JavaComponentBuilder.java:75) at org.apache.tuscany.core.implementation.java.JavaComponentBuilder.build(JavaComponentBuilder.java:52) at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegistryImpl.java:115) at org.apache.tuscany.core.implementation.composite.CompositeBuilder.build(CompositeBuilder.java:93) at org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderRegistryImpl.java:115) at org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.java:115) at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.java:81) RequestScopeObjectFactory is not registering with the ScopeRegistry. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-975) Scope object factory not registered for scope [CONVERSATION]
[ http://issues.apache.org/jira/browse/TUSCANY-975?page=all ]
Ignacio Silva-Lepe reassigned TUSCANY-975:
--
Assignee: Ignacio Silva-Lepe
Scope object factory not registered for scope [CONVERSATION]
Key: TUSCANY-975
URL: http://issues.apache.org/jira/browse/TUSCANY-975
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Assigned To: Ignacio Silva-Lepe
Conversation scope is not recognized.
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Scope object factory not registered for scope [CONVERSATION]
[INFO]
[INFO] Trace
org.apache.tuscany.spi.component.ScopeNotFoundException: Scope object factory
n
t registered for scope [CONVERSATION]
at
org.apache.tuscany.core.component.scope.ScopeRegistryImpl.getScopeCo
tainer(ScopeRegistryImpl.java:65)
at
org.apache.tuscany.core.implementation.java.JavaComponentBuilder.bui
d(JavaComponentBuilder.java:76)
at
org.apache.tuscany.core.implementation.java.JavaComponentBuilder.bui
d(JavaComponentBuilder.java:53)
at
org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderReg
stryImpl.java:115)
at
org.apache.tuscany.core.implementation.composite.CompositeBuilder.bu
ld(CompositeBuilder.java:93)
at
org.apache.tuscany.core.builder.BuilderRegistryImpl.build(BuilderReg
stryImpl.java:115)
at
org.apache.tuscany.core.deployer.DeployerImpl.build(DeployerImpl.jav
:115)
at
org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.ja
a:81)
at
org.apache.tuscany.core.runtime.AbstractRuntime.deployApplicationScd
(AbstractRuntime.java:136)
at
org.apache.tuscany.sca.plugin.itest.MavenEmbeddedRuntime.initialize(
avenEmbeddedRuntime.java:85)
at
org.apache.tuscany.sca.plugin.itest.TuscanyStartMojo.execute(Tuscany
tartMojo.java:102)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlug
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Def
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defa
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultL
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(DelegatingMethodAcce
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: Wed Dec 06 13:43:48 EST 2006
[INFO] Final Memory: 6M/17M
[INFO]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-965) Context Injection is not functioning
[
http://issues.apache.org/jira/browse/TUSCANY-965?page=comments#action_12458570
]
Ignacio Silva-Lepe commented on TUSCANY-965:
AFAICT, the implementation to support context injection has not been completed
yet. There is a ContextProcessor but it curently throws
UnsupportedOperationException and it is not included in implementation.scdl.
Also, CompositeContextImpl is for the most part stubbed out.
Context Injection is not functioning
Key: TUSCANY-965
URL: http://issues.apache.org/jira/browse/TUSCANY-965
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Appears that Contesxt injection when using setters and attributes is not
working. In each case the context attribute is null.
a) setter method
package org.apache.tuscany.sca.test;
import org.osoa.sca.CurrentCompositeContext;
import org.osoa.sca.ServiceReference;
import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Remotable;
import org.osoa.sca.annotations.Scope;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import junit.framework.Assert;
@Service(CallBackSetCallbackClient.class)
public class CallBackSetCallbackClientImpl implements
CallBackSetCallbackClient {
@Reference
protected CallBackSetCalbackService aCallBackService;
@Reference
protected CallBackSetCallbackCallback callBack;
private CompositeContext context;
@Context
public void setContext(CompositeContext aContext)
{
context = aContext;
}
public void run() {
if (context == null)
System.out.println(Context is null);
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
Context is null
b) attribute
package org.apache.tuscany.sca.test;
import org.osoa.sca.CurrentCompositeContext;
import org.osoa.sca.ServiceReference;
import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Remotable;
import org.osoa.sca.annotations.Scope;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import junit.framework.Assert;
@Service(CallBackSetCallbackClient.class)
public class CallBackSetCallbackClientImpl implements
CallBackSetCallbackClient {
@Reference
protected CallBackSetCalbackService aCallBackService;
@Reference
protected CallBackSetCallbackCallback callBack;
@Context
protected CompositeContext context;
public void run() {
if (context == null)
System.out.println(Context is null);
[WARNING] Unable to get resource from repository central
(http://repo1.maven.or
/maven2)
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
Context is null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-966) getRequestContext() does not return a Context
[
http://issues.apache.org/jira/browse/TUSCANY-966?page=comments#action_12458575
]
Ignacio Silva-Lepe commented on TUSCANY-966:
Implementation of context injection is not complete (see TUSCANY-965) and the
CompositeContext api has not been implemented yet, including
getServiceReference and getCallback.
getRequestContext() does not return a Context
-
Key: TUSCANY-966
URL: http://issues.apache.org/jira/browse/TUSCANY-966
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Remote Service hangs obtaining the request context using getRequestContext().
[INFO] [tuscany-itest:start {execution: start}]
[INFO] Starting Tuscany...
[INFO] [tuscany-itest:test {execution: test}]
[INFO] Executing tests...
CallBackApiServiceImpl message received: Knock Knock
CallBackApiServiceImpl getting request context
[INFO] Test results: {skipped=0, completedCount=1, failures=1, errors=0}
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There were test failures
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 37 seconds
[INFO] Finished at: Fri Dec 01 08:14:20 EST 2006
[INFO] Final Memory: 7M/18M
[INFO]
---
Test set: org.apache.tuscany.sca.test.CallBackApiITest
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 30.023 sec
FAILURE!
testCallBackBasic(org.apache.tuscany.sca.test.CallBackApiITest) Time
elapsed: 30.023 sec FAILURE!
junit.framework.ComparisonFailure: CallBackBasicITest expected:Who's There
but was:null
at junit.framework.Assert.assertEquals(Assert.java:81)
at
org.apache.tuscany.sca.test.CallBackApiClientImpl.test1(CallBackApiClientImpl.java:55)
at
org.apache.tuscany.sca.test.CallBackApiClientImpl.run(CallBackApiClientImpl.java:21)
at
org.apache.tuscany.sca.test.CallBackApiITest.testCallBackBasic(CallBackApiITest.java:12)
package org.apache.tuscany.sca.test;
import org.osoa.sca.annotations.Service;
import org.osoa.sca.annotations.Context;
import org.osoa.sca.CompositeContext;
import org.osoa.sca.RequestContext;
@Service(CallBackApiService.class)
public class CallBackApiServiceImpl implements CallBackApiService {
@Context
protected CompositeContext compositeContext;
protected CallBackApiCallBack callback;
public void knockKnock(String aString) {
System.out.println(CallBackApiServiceImpl message received: +
aString);
callback = this.getCallBackInterface();
callback.callBackMessage(Who's There);
System.out.println(CallBackApiServiceImpl response sent);
return;
}
private CallBackApiCallBack getCallBackInterface()
{
System.out.println(CallBackApiServiceImpl getting request context);
RequestContext rc = compositeContext.getRequestContext();
System.out.println(CallBackApiServiceImpl getting callback from
request context);
callback = (CallBackApiCallBack)
rc.getServiceReference().getCallback();
System.out.println(CallBackApiServiceImpl returning callback);
return callback;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-976) Multiple Callbacks fail
[
http://issues.apache.org/jira/browse/TUSCANY-976?page=comments#action_12456542
]
Ignacio Silva-Lepe commented on TUSCANY-976:
I have checked in a fix with r483607. Can you verify and let me know to mark
this issue as resolved?
Multiple Callbacks fail
---
Key: TUSCANY-976
URL: http://issues.apache.org/jira/browse/TUSCANY-976
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Assigned To: Ignacio Silva-Lepe
Attachments: test-CallBackBasic.zip
I have a stateless service that performs multiple callbacks. The first
callback is successful. The next callback hangs during the call to the
callback method.
public void multiCallBack(String aString) {
System.out.println(CallBackBasicServiceImpl message received: +
aString);
callback.callBackIncrement(Who's There 1);
System.out.println(CallBackBasicServiceImpl response sent);
callback.callBackIncrement(Who's There 2);
System.out.println(CallBackBasicServiceImpl response sent);
callback.callBackIncrement(Who's There 3);
System.out.println(CallBackBasicServiceImpl response sent);
return;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-976) Multiple Callbacks fail
[ http://issues.apache.org/jira/browse/TUSCANY-976?page=all ]
Ignacio Silva-Lepe reassigned TUSCANY-976:
--
Assignee: Ignacio Silva-Lepe
Multiple Callbacks fail
---
Key: TUSCANY-976
URL: http://issues.apache.org/jira/browse/TUSCANY-976
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Assigned To: Ignacio Silva-Lepe
I have a stateless service that performs multiple callbacks. The first
callback is successful. The next callback hangs during the call to the
callback method.
public void multiCallBack(String aString) {
System.out.println(CallBackBasicServiceImpl message received: +
aString);
callback.callBackIncrement(Who's There 1);
System.out.println(CallBackBasicServiceImpl response sent);
callback.callBackIncrement(Who's There 2);
System.out.println(CallBackBasicServiceImpl response sent);
callback.callBackIncrement(Who's There 3);
System.out.println(CallBackBasicServiceImpl response sent);
return;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-976) Multiple Callbacks fail
[
http://issues.apache.org/jira/browse/TUSCANY-976?page=comments#action_12456163
]
Ignacio Silva-Lepe commented on TUSCANY-976:
Can you attach a trace and possibly some additional relevant code? Thanks
Multiple Callbacks fail
---
Key: TUSCANY-976
URL: http://issues.apache.org/jira/browse/TUSCANY-976
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core
Reporter: Lou Amodeo
Assigned To: Ignacio Silva-Lepe
I have a stateless service that performs multiple callbacks. The first
callback is successful. The next callback hangs during the call to the
callback method.
public void multiCallBack(String aString) {
System.out.println(CallBackBasicServiceImpl message received: +
aString);
callback.callBackIncrement(Who's There 1);
System.out.println(CallBackBasicServiceImpl response sent);
callback.callBackIncrement(Who's There 2);
System.out.println(CallBackBasicServiceImpl response sent);
callback.callBackIncrement(Who's There 3);
System.out.println(CallBackBasicServiceImpl response sent);
return;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-955) IllegalPropertyException thrown when loading MemoryStore
IllegalPropertyException thrown when loading MemoryStore Key: TUSCANY-955 URL: http://issues.apache.org/jira/browse/TUSCANY-955 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx As a result of autowiring MemoryStore, an IllegalPropertyException is thrown on getExpirationOffset. A trace follows. To reproduce, uncomment the property annotation on getExpirationOffset. Running loanappconversation.LoanAppConversationTestCase org.apache.tuscany.spi.implementation.java.IllegalPropertyException: Method does not have void return type [public long org.apache.tuscany.core.services.store.m emory.MemoryStore.getExpirationOffset()] Context stack trace: [tuscany.system][store] at org.apache.tuscany.spi.implementation.java.AbstractPropertyProcessor. visitMethod(AbstractPropertyProcessor.java:55) at org.apache.tuscany.core.implementation.IntrospectionRegistryImpl.intr ospect(IntrospectionRegistryImpl.java:90) at org.apache.tuscany.core.implementation.system.loader.SystemComponentT ypeLoader.loadByIntrospection(SystemComponentTypeLoader.java:89) at org.apache.tuscany.core.implementation.system.loader.SystemComponentT ypeLoader.load(SystemComponentTypeLoader.java:72) at org.apache.tuscany.core.implementation.system.loader.SystemComponentT ypeLoader.load(SystemComponentTypeLoader.java:45) at org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(L oaderRegistryImpl.java:163) at org.apache.tuscany.core.implementation.system.loader.SystemImplementa tionLoader.load(SystemImplementationLoader.java:61) at org.apache.tuscany.core.implementation.system.loader.SystemImplementa tionLoader.load(SystemImplementationLoader.java:42) at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistry Impl.java:94) at org.apache.tuscany.core.loader.ComponentLoader.loadImplementation(Com ponentLoader.java:184) at org.apache.tuscany.core.loader.ComponentLoader.load(ComponentLoader.j ava:128) at org.apache.tuscany.core.loader.ComponentLoader.load(ComponentLoader.j ava:70) at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistry Impl.java:94) at org.apache.tuscany.core.implementation.composite.CompositeLoader.load (CompositeLoader.java:88) at org.apache.tuscany.core.implementation.composite.CompositeLoader.load (CompositeLoader.java:64) at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistry Impl.java:94) at org.apache.tuscany.core.loader.LoaderRegistryImpl.load(LoaderRegistry Impl.java:112) at org.apache.tuscany.core.implementation.system.loader.SystemCompositeC omponentTypeLoader.loadFromSidefile(SystemCompositeComponentTypeLoader.java:68) at org.apache.tuscany.core.implementation.system.loader.SystemCompositeC omponentTypeLoader.load(SystemCompositeComponentTypeLoader.java:59) at org.apache.tuscany.core.implementation.system.loader.SystemCompositeC omponentTypeLoader.load(SystemCompositeComponentTypeLoader.java:38) at org.apache.tuscany.core.loader.LoaderRegistryImpl.loadComponentType(L oaderRegistryImpl.java:163) at org.apache.tuscany.core.deployer.DeployerImpl.load(DeployerImpl.java: 101) at org.apache.tuscany.core.deployer.DeployerImpl.deploy(DeployerImpl.jav a:76) at org.apache.tuscany.core.launcher.LauncherImpl.bootRuntime(LauncherImp l.java:101) at org.apache.tuscany.core.launcher.LauncherImpl.bootRuntime(LauncherImp l.java:158) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: SimplerCompositeReferenceInvocation6.patch This patch replaces stacks for linked lists in the implementation of callback routing chains. The patch passes all test cases in spi, core and bindings.axis2, as well as the supplychain, simplecallback and inner.composite samples, and the ws async samples. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch, SimplerCompositeReferenceInvocation.patch, SimplerCompositeReferenceInvocation2.patch, SimplerCompositeReferenceInvocation3.patch, SimplerCompositeReferenceInvocation4.patch, SimplerCompositeReferenceInvocation5.patch, SimplerCompositeReferenceInvocation6.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: SimplerCompositeReferenceInvocation7.patch This patch eliminates the need for AbstractOperationOutboundInvocationHandler by refactoring the code around the AbstractCompositeReferenceTargetInvoker hierarchy. The patch passes all test cases in spi, core and bindings.axis2, as well as the supplychain, simplecallback and inner.composite samples, and the ws async samples. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch, SimplerCompositeReferenceInvocation.patch, SimplerCompositeReferenceInvocation2.patch, SimplerCompositeReferenceInvocation3.patch, SimplerCompositeReferenceInvocation4.patch, SimplerCompositeReferenceInvocation5.patch, SimplerCompositeReferenceInvocation6.patch, SimplerCompositeReferenceInvocation7.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: SimplerCompositeReferenceInvocation5.patch This patch eliminates the use of routing tables by message id at each inbound wire and instead uses a callback routing chain (implemented as a stack) carried in a message. The patch passes all test cases in spi, core and bindings.axis2, as well as the supplychain, simplecallback and inner.composite samples. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch, SimplerCompositeReferenceInvocation.patch, SimplerCompositeReferenceInvocation2.patch, SimplerCompositeReferenceInvocation3.patch, SimplerCompositeReferenceInvocation4.patch, SimplerCompositeReferenceInvocation5.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: SimplerCompositeReferenceInvocation4.patch This patch changes the AbstractOutboundInvocationHandler spi, as well as Axis2Service to take the messageId and correlationId as parms. This avoids having to cache the ids in the handler subclasses, which can be thread unsafe. The patch passes all test cases in spi, core and bindings.axis2, as well as the supplychain, simplecallback and inner.composite samples. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch, SimplerCompositeReferenceInvocation.patch, SimplerCompositeReferenceInvocation2.patch, SimplerCompositeReferenceInvocation3.patch, SimplerCompositeReferenceInvocation4.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: SimplerCompositeReferenceInvocation3.patch This patch further simplifies invocation handlers to only use a message id for the callback case; note that Axis2Service also plays the role of an invocation handler. In the process, workContext becomes unnecessary for JDKOutboundInvocationHandler and so its constructor is simplified. The patch updates and passes test cases in core and spi, as well as the supplychain, simplecallback, inner.composite, greeterws-oneway and helloworldws-async samples. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch, SimplerCompositeReferenceInvocation.patch, SimplerCompositeReferenceInvocation2.patch, SimplerCompositeReferenceInvocation3.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: SimplerCompositeReferenceInvocation2.patch This patch changes composite and JDK invocation handlers to only set fromAddress in the message in the forward direction. It passes all test cases in core and spi as well as the inner.composite, supplychain and simplecallback sample. This latter sample is updated to set the application scdl for its parent SCATestCase. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch, SimplerCompositeReferenceInvocation.patch, SimplerCompositeReferenceInvocation2.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: SimplerCompositeReferenceInvocation.patch This patch provides a simpler implementation of composite reference and composite service outbound invocation handler and callback invocation handler. The invocation handlers now: (1) take in a message as a parameter, and (2) do not create a new message to pass on to the head interceptor. This also allows eliminating the use of a work context to carry message id info from the corresponding target invokers. These changes follow up on the conversation in http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg08182.html The patch updates and passes all test cases in core, as well as the inner.composite sample. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch, SimplerCompositeReferenceInvocation.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-823) Adding one way samples for ws/axis2
[ http://issues.apache.org/jira/browse/TUSCANY-823?page=comments#action_12442081 ] Ignacio Silva-Lepe commented on TUSCANY-823: As this is done, I can resolve/close it if that's not a problem Adding one way samples for ws/axis2 --- Key: TUSCANY-823 URL: http://issues.apache.org/jira/browse/TUSCANY-823 Project: Tuscany Issue Type: New Feature Components: Java SCA Axis Binding Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: ws-ow-sample-client.patch, ws-ow-sample.patch Two samples are added that exercise a one-way ws/axis2 interaction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-823) Adding one way samples for ws/axis2
Adding one way samples for ws/axis2 --- Key: TUSCANY-823 URL: http://issues.apache.org/jira/browse/TUSCANY-823 Project: Tuscany Issue Type: New Feature Components: Java SCA Axis Binding Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx Two samples are added that exercise a one-way ws/axis2 interaction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-823) Adding one way samples for ws/axis2
[ http://issues.apache.org/jira/browse/TUSCANY-823?page=all ] Ignacio Silva-Lepe updated TUSCANY-823: --- Attachment: ws-ow-sample.patch Here's an initial patch for the server side. I'm seeing some problems with the target invoker on the client side so this has not been tested successfully yet. Adding one way samples for ws/axis2 --- Key: TUSCANY-823 URL: http://issues.apache.org/jira/browse/TUSCANY-823 Project: Tuscany Issue Type: New Feature Components: Java SCA Axis Binding Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: ws-ow-sample.patch Two samples are added that exercise a one-way ws/axis2 interaction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-823) Adding one way samples for ws/axis2
[ http://issues.apache.org/jira/browse/TUSCANY-823?page=all ] Ignacio Silva-Lepe updated TUSCANY-823: --- Attachment: ws-ow-sample-client.patch Here's an initial patch for the client side. I'm seeing some problems with the target invoker so this has not been tested successfully yet. Adding one way samples for ws/axis2 --- Key: TUSCANY-823 URL: http://issues.apache.org/jira/browse/TUSCANY-823 Project: Tuscany Issue Type: New Feature Components: Java SCA Axis Binding Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: ws-ow-sample-client.patch, ws-ow-sample.patch Two samples are added that exercise a one-way ws/axis2 interaction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-803) Association of callback methods with request methods
Association of callback methods with request methods Key: TUSCANY-803 URL: http://issues.apache.org/jira/browse/TUSCANY-803 Project: Tuscany Issue Type: Improvement Components: Specification Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Michael John Edwards Fix For: Java-Mx The specs (assembly and CI) do not seem to be very explicit about what should happen with an interface that is annotated as @Callback and that defines more than one method. But notice that if this is the case then the next question pertains to a previous question, which is what happens when the callback interface (the one in the annotation, not the annotated one) has more than one method. Let i1 be an intrerface annotated with @Callback(c1), where c1 is the callback interface. The simplest case is when both i1 and c1 have only one method. If i1 has 1 methods there are two cases: c1 has only one method, and c1 has 1 methods. The first case is the case at hand. Notice that one last case is where i1 has one method and c1 has 1, but that really is a special case of the second case. The second case is the one we had asked about before, how do we associate methods in c1 with methods in i1. Again, the specs are not explicit about this. In general, this association may require knowledge about the implementation of i1. That is, i1Impl will get an injected instance of c1 which then it will use in its method(s) to make callback invocations. Which c1 method is invoked in i1 is arbitrary and we may have to resort to non-trivial introspection to figure it out. Btw, nontice that this case also includes the first case. So it seems we have a choice of how to interpret the specs. 1- The simplest choice is to assume i1 and c1 both have only one method. 2- We can assume that c1 has only one method (case at hand) and introspect each method in i1 to figure out which is intended as async with callback and which is not. In addition, here we also have a choice of whether to treat non-callback methods as sync or async. 3- We can try go for the general case. My vote is to go with choice 1, which is what I have been assuming so far, at least for the coming release. And if we don't feel comfortable with this choice long term, then we can try for choice 2 or maybe even choice 3, if we can make sense of it. It would also be useful to try to go back to the spec collaboration to try to calrify the intent. More details: http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg08617.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-767) NPE in CompositeReference.java when service is defined using interface wsdl
[ http://issues.apache.org/jira/browse/TUSCANY-767?page=all ] Ignacio Silva-Lepe updated TUSCANY-767: --- Attachment: OperationInvocationHandlersWithTestCase.patch Here's a new patch that also contains a test case. As soon as TUSCAY-768 is resolved I should be able to verify this patch with the inner.composite sample as well. NPE in CompositeReference.java when service is defined using interface wsdl --- Key: TUSCANY-767 URL: http://issues.apache.org/jira/browse/TUSCANY-767 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-M2 Reporter: Rick Rineholt Assigned To: Jim Marino Priority: Blocker Fix For: Java-M2 Attachments: OperationInvocationHandlers.patch, OperationInvocationHandlersWithTestCase.patch If a service is defined using interface wsdl the service contract does not have an interface class this results in org.apache.tuscany.core.implementation.composite.CompositeReference getting an NPE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-767) NPE in CompositeReference.java when service is defined using interface wsdl
[ http://issues.apache.org/jira/browse/TUSCANY-767?page=all ] Ignacio Silva-Lepe reassigned TUSCANY-767: -- Assignee: Ignacio Silva-Lepe NPE in CompositeReference.java when service is defined using interface wsdl --- Key: TUSCANY-767 URL: http://issues.apache.org/jira/browse/TUSCANY-767 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-M2 Reporter: Rick Rineholt Assigned To: Ignacio Silva-Lepe Priority: Blocker Fix For: Java-M2 If a service is defined using interface wsdl the service contract does not have an interface class this results in org.apache.tuscany.core.implementation.composite.CompositeReference getting an NPE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-767) NPE in CompositeReference.java when service is defined using interface wsdl
[ http://issues.apache.org/jira/browse/TUSCANY-767?page=all ] Ignacio Silva-Lepe updated TUSCANY-767: --- Attachment: OperationInvocationHandlers.patch Here's a patch that removes the dependency of CompositeReference target invokers on PojoTargetInvoker and Java reflection. This eliminates the need for CompositeReference to access a null interface class, which should also eliminate the NPE. Because of TUSCANY-768, I have not been able to verify this patch using the inner.composite sample. NPE in CompositeReference.java when service is defined using interface wsdl --- Key: TUSCANY-767 URL: http://issues.apache.org/jira/browse/TUSCANY-767 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-M2 Reporter: Rick Rineholt Assigned To: Ignacio Silva-Lepe Priority: Blocker Fix For: Java-M2 Attachments: OperationInvocationHandlers.patch If a service is defined using interface wsdl the service contract does not have an interface class this results in org.apache.tuscany.core.implementation.composite.CompositeReference getting an NPE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-768) SynchronousBridgingInterceptor seems to be catching NPE
SynchronousBridgingInterceptor seems to be catching NPE --- Key: TUSCANY-768 URL: http://issues.apache.org/jira/browse/TUSCANY-768 Project: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx Trying the plain inner.composite sample without a fix for TUSCANY-767, gives the failure below. It seems like the SynchronousBridgingInterceptor may be having a problem. Having tried to look yet. It may be related to TUSCANY-767, but in case it is not. --- T E S T S --- Running innercomposite.InnerCompositeTestCase Main thread Thread[main,5,main] org.apache.tuscany.spi.wire.InvocationRuntimeException: java.lang.NullPointerExc eption at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:76) at org.apache.tuscany.core.wire.AbstractOutboundInvocationHandler.invoke (AbstractOutboundInvocationHandler.java:65) at org.apache.tuscany.core.wire.jdk.JDKOutboundInvocationHandler.invoke( JDKOutboundInvocationHandler.java:121) at $Proxy17.clientMethod(Unknown Source) at innercomposite.InnerCompositeTestCase.test(InnerCompositeTestCase.jav a:39) 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 junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) 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:269) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:788) Caused by: java.lang.NullPointerException at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:71) at org.apache.tuscany.core.wire.SynchronousBridgingInterceptor.invoke(Sy nchronousBridgingInterceptor.java:41) at org.apache.tuscany.core.wire.SynchronousBridgingInterceptor.invoke(Sy nchronousBridgingInterceptor.java:41) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:71) at org.apache.tuscany.core.wire.AbstractOutboundInvocationHandler.invoke (AbstractOutboundInvocationHandler.java:65) at org.apache.tuscany.core.wire.jdk.JDKOutboundInvocationHandler.invoke( JDKOutboundInvocationHandler.java:121) at $Proxy18.someMethod(Unknown Source) at innercomposite.SourceImpl.clientMethod(SourceImpl.java:43) 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.tuscany.core.wire.PojoTargetInvoker.invokeTarget(PojoTarge tInvoker.java:63) at org.apache.tuscany.core.wire.PojoTargetInvoker.invoke(PojoTargetInvok er.java:72) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44)
[jira] Created: (TUSCANY-766) NoClassDefFoundError, apparently in Axis2
NoClassDefFoundError, apparently in Axis2 - Key: TUSCANY-766 URL: http://issues.apache.org/jira/browse/TUSCANY-766 Project: Tuscany Issue Type: Bug Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Fix For: Java-Mx I am trying to run the hellowordwsclient sample by changing the bound reference to use an interface.java, with which it runs ok. But if I then add a callbackInterface I get the error below. By using a callbackInterface, an Axis2AsyncTargetInvoker is chosen that calls Axis2's operationClient.execute(false), i.e. non-blocking. Without the callbackInterface an Axis2TargetInvoker is chosen which calls operationClient.execute(true). So it seems as if trying to using a non-blocking operation client execute triggers the error. I have to wonder whether this may be an Axis2 dependency that has not been set up. Any ideas? --- T E S T S --- Running helloworld.HelloWorldWSClientTestCase log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAX Utils). log4j:WARN Please initialize the log4j system properly. org.apache.tuscany.spi.wire.InvocationRuntimeException: java.lang.NoClassDefFoun dError: edu/emory/mathcs/backport/java/util/concurrent/BlockingQueue at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:76) at org.apache.tuscany.core.wire.BridgingInterceptor.invoke(BridgingInter ceptor.java:41) at org.apache.tuscany.core.databinding.impl.DataBindingInteceptor.invoke (DataBindingInteceptor.java:71) at org.apache.tuscany.core.wire.AbstractOutboundInvocationHandler.invoke (AbstractOutboundInvocationHandler.java:65) at org.apache.tuscany.core.wire.jdk.JDKOutboundInvocationHandler.invoke( JDKOutboundInvocationHandler.java:121) at $Proxy20.getGreetings(Unknown Source) at helloworld.HelloWorldServiceComponent.getGreetings(HelloWorldServiceC omponent.java:39) at helloworld.HelloWorldWSClientTestCase.testWSClient(HelloWorldWSClient TestCase.java:43) 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 junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) 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:269) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:788) Caused by: java.lang.NoClassDefFoundError: edu/emory/mathcs/backport/java/util/c oncurrent/BlockingQueue at org.apache.axis2.context.ConfigurationContext.getThreadPool(Configura tionContext.java:296) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAx isOperation.java:306) at org.apache.tuscany.binding.axis2.Axis2AsyncTargetInvoker.invokeTarget (Axis2AsyncTargetInvoker.java:58) at org.apache.tuscany.binding.axis2.Axis2AsyncTargetInvoker.invoke(Axis2 AsyncTargetInvoker.java:70) at org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterce ptor.java:44) at
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: CommentsOut.patch Trivial change to remove some commented out code Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CommentsOut.patch, CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-721) Adding support for callbacks over bindings.axis2
Adding support for callbacks over bindings.axis2 Key: TUSCANY-721 URL: http://issues.apache.org/jira/browse/TUSCANY-721 Project: Tuscany Issue Type: New Feature Components: Java SCA Axis Binding Affects Versions: Java-M2 Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-M2 Support for callbacks over Axis2 binding is added. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-721) Adding support for callbacks over bindings.axis2
[ http://issues.apache.org/jira/browse/TUSCANY-721?page=all ] Ignacio Silva-Lepe updated TUSCANY-721: --- Attachment: Axis2Callbacks.patch This patch contains the main code and preliminary test cases added to the existing ones. More testing, including integration testing with data binding and across client and server is needed, which depends on Raymond's work on data binding integration. So, this patch is not quite ready to be committed. It is being posted to allow Raymond (and anyone else interested) to perform more testing. It is also posted in the interest of not letting it become stale as the work on data binding integration proceeds. The code in this patch makes the (rather major) assumption that there is only one callback method. Relaxing this assumption, however, does not seem to be trivial, it may depend on knowledge of what actual callback method was invoked by the service at the other end. In addition, the assumption is made for now that the transport mep is synchronous. That is, options.isUseSeparateListener remains false on the operation client. If/when there is an architected way to change this option, the assumption can be relaxed. Adding support for callbacks over bindings.axis2 Key: TUSCANY-721 URL: http://issues.apache.org/jira/browse/TUSCANY-721 Project: Tuscany Issue Type: New Feature Components: Java SCA Axis Binding Affects Versions: Java-M2 Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-M2 Attachments: Axis2Callbacks.patch Support for callbacks over Axis2 binding is added. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: RevisedInnerCompositeCallback.patch This patch replaces InnerCompositeCallback2.patch. It integrates its contents with the latest trunk to account for the new service contract changes. it also updates callbacks across composites to use split callback invocation chains, and callback correlation and routing. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Jim Marino Fix For: Java-Mx Attachments: CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch, RevisedInnerCompositeCallback.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-706) Revised approach for callback invocation chains, callback correlation and routing
Revised approach for callback invocation chains, callback correlation and routing - Key: TUSCANY-706 URL: http://issues.apache.org/jira/browse/TUSCANY-706 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: RevisedCallbackChainsCorrelationAndRouting.patch A revised approach is provided for callback invocation chains. Source callback chains, which used to be located in outbound wires, are now located in inbound wires. In addition, since more than one outbound wire can be connected to an inbound wire, it is necessary to maintain one source callback chain per operation per target outbound wire. This is maintained by an inbound wire in a table keyed by outbound wire container 'address' (currently SCAObject name). In addition, correlation and routing of callback messages needs to take into account this revised callback chain approach. As a starting approach, a routing table is maintained by an inbound wire that maps message ids to target outbound wire container addresses. A forward message carries with it a message id that becomes the corresponding callback message's correlation id. This allows a callback message to be correlated with the source callback chain whose target outbound wire originated the forward message. The attached patch implements the revised callback invocation chain approach, callback correlation and routing. It passes all core test cases and the simple callback sample. In addition, it was necessary to make a couple of changes to the groovy container. The patch passes all groovy test cases, but more extensive testing of the groovy container may be appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-706) Revised approach for callback invocation chains, callback correlation and routing
[ http://issues.apache.org/jira/browse/TUSCANY-706?page=all ] Ignacio Silva-Lepe updated TUSCANY-706: --- Attachment: RevisedCallbackChainsCorrelationAndRouting.patch At issue creation time, it is possible to attach a file but there does not seem to be a way to grant a license to the attachment, so I do that now. Revised approach for callback invocation chains, callback correlation and routing - Key: TUSCANY-706 URL: http://issues.apache.org/jira/browse/TUSCANY-706 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: RevisedCallbackChainsCorrelationAndRouting.patch, RevisedCallbackChainsCorrelationAndRouting.patch A revised approach is provided for callback invocation chains. Source callback chains, which used to be located in outbound wires, are now located in inbound wires. In addition, since more than one outbound wire can be connected to an inbound wire, it is necessary to maintain one source callback chain per operation per target outbound wire. This is maintained by an inbound wire in a table keyed by outbound wire container 'address' (currently SCAObject name). In addition, correlation and routing of callback messages needs to take into account this revised callback chain approach. As a starting approach, a routing table is maintained by an inbound wire that maps message ids to target outbound wire container addresses. A forward message carries with it a message id that becomes the corresponding callback message's correlation id. This allows a callback message to be correlated with the source callback chain whose target outbound wire originated the forward message. The attached patch implements the revised callback invocation chain approach, callback correlation and routing. It passes all core test cases and the simple callback sample. In addition, it was necessary to make a couple of changes to the groovy container. The patch passes all groovy test cases, but more extensive testing of the groovy container may be appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: InnerCompositeCallback2.patch This patch subsumes InnerCompositeCallback.patch. It incorporates local invocations and callbacks over composite services. The same approach is used to provide the callback invocation handler with the outbound wire that is connected to the composite service's inbound wire. In addition, since bound services do not need a target invoker, there is no method to set it (or a callback target invoker) in the spi. It seems like at least a callback target invoker will be needed for bound services and since both are needed for bindless services, we may want to define them in the spi. This can be done as part of a callbacks over ws (axis2) binding patch. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch, InnerCompositeCallback2.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-673) support scdlLocation attribute on implementation.composite
[ http://issues.apache.org/jira/browse/TUSCANY-673?page=all ] Ignacio Silva-Lepe updated TUSCANY-673: --- Attachment: ImplementationCompositeLoader.patch support scdlLocation attribute on implementation.composite Key: TUSCANY-673 URL: http://issues.apache.org/jira/browse/TUSCANY-673 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Reporter: Jeremy Boynes Assigned To: Ignacio Silva-Lepe Attachments: ImplementationCompositeLoader.patch When using a composite as an implementation, we should provide a way for the user to specify the location of the SCDL for the composite component name=Foo implementation.composite name=Bar scdlLocation=bar.scdl/ ... The location should be resolved relative to the location of the outer composite. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-673) support scdlLocation attribute on implementation.composite
[ http://issues.apache.org/jira/browse/TUSCANY-673?page=all ] Ignacio Silva-Lepe updated TUSCANY-673: --- Attachment: ImplementationCompositeLoaderAndTest.patch support scdlLocation attribute on implementation.composite Key: TUSCANY-673 URL: http://issues.apache.org/jira/browse/TUSCANY-673 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Reporter: Jeremy Boynes Assigned To: Ignacio Silva-Lepe Attachments: ImplementationCompositeLoader.patch, ImplementationCompositeLoaderAndTest.patch When using a composite as an implementation, we should provide a way for the user to specify the location of the SCDL for the composite component name=Foo implementation.composite name=Bar scdlLocation=bar.scdl/ ... The location should be resolved relative to the location of the outer composite. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: InnerCompositeCallback.patch This newer patch subsumes InnerComposite.patch (assuming that the latter has not been applied). It incorporates callbacks over composite references. A less than elegant approach is used however. A complete hack is used to provide a callback invocation handler with the outbound wire that is connected to the composite reference's inbound wire. Notice that the same approach cannot be used as was used with async target invoker. This is because the thread that places the outbound wire on the work context in that instance is the same that retrieves the outbound wire. In the composite reference case, the two threads are not the same, so a different mechanism seems necessary, perhaps a more general correlation mechanism. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch, InnerCompositeCallback.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: InnerComposite.patch Here's a new patch that modifies CompositeBuilderTestCase to verify that the Connector also works for composite services and references. This patch also includes a more complete sample with an inner composite that has an inner service, inner component and inner reference; the inner composite is wired from an outer composite to a sibling component and the inner component then invokes the outer component. This patch also fixes a bug, where the loader for implementation composite was not being called, by adding a component to composite.scdl in sca/test, sca/commands/launcher and sca/runtime/webapp-host. Finally, for some reason having to do with class loaders, the class for the sample's inner service interface was not being found. This has not been resolved, at least not well enough. To get over the hurdle I hacked LoaderUtil.loadClass to try the old class loader if the one in the deployment context does not work. This seems to work but is obviously not adequate (not to mention the glaring println). In the interest of making progress, I include the hack in this patch. Hopefully the real fix can be incorporated during commit of this patch or in a subsequent one. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: CompositeRefsAndSvcs.txt, CompositeRefsAndSvcs2.txt, InnerComposite.patch Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-642) Composite references and services - model and runtime representations
Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-642) Composite references and services - model and runtime representations
[ http://issues.apache.org/jira/browse/TUSCANY-642?page=all ] Ignacio Silva-Lepe updated TUSCANY-642: --- Attachment: CompositeRefsAndSvcs.txt Here's the patch with the code to support composite reference and services. Composite references and services - model and runtime representations - Key: TUSCANY-642 URL: http://issues.apache.org/jira/browse/TUSCANY-642 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: CompositeRefsAndSvcs.txt Support is added to represent composite references and services (those in a composite and without a binding) in the model and runtime. The CompositeBuilder is updated to build a composite component that includes composite references and services without bindings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-585) Initial support for callbacks
[ http://issues.apache.org/jira/browse/TUSCANY-585?page=all ] Ignacio Silva-Lepe updated TUSCANY-585: --- Attachment: CallbackPatch.txt Patch with code and sample attached Initial support for callbacks - Key: TUSCANY-585 URL: http://issues.apache.org/jira/browse/TUSCANY-585 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: CallbackPatch.txt Initial support for local callbacks is provided, along with a simple callback sample -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-585) Initial support for callbacks
[ http://issues.apache.org/jira/browse/TUSCANY-585?page=all ] Ignacio Silva-Lepe updated TUSCANY-585: --- Attachment: CallbackPatch.txt Including JavaMappedCallback and IllegalCallbackException that had not been added to version control, apologies Initial support for callbacks - Key: TUSCANY-585 URL: http://issues.apache.org/jira/browse/TUSCANY-585 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: CallbackPatch.txt, CallbackPatch.txt Initial support for local callbacks is provided, along with a simple callback sample -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-550) Supply chain sample for chianti
Supply chain sample for chianti --- Key: TUSCANY-550 URL: http://issues.apache.org/jira/browse/TUSCANY-550 Project: Tuscany Issue Type: Test Components: Java SCA Samples Affects Versions: Java-Mx Reporter: Ignacio Silva-Lepe Assigned To: Ignacio Silva-Lepe Fix For: Java-Mx Upgrading supply chain sample to work with new version of spec under chianti -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-270) Bigbank sample should demonstrate the SCA async PM
[ http://issues.apache.org/jira/browse/TUSCANY-270?page=comments#action_12412968 ] Ignacio Silva-Lepe commented on TUSCANY-270: In stock sell, it turns out that the DAS select command issued by the data service was not including symbol and purchaseLotNumber to be retrieved, so just changing the stockbylotSelect command to the following, fixes the problem: Command name=stockbylotSelect SQL=select purchaseLotNumber, symbol, quantity from STOCKS WHERE purchaseLotNumber = :PURCHASELOTNUMBER kind=Select However, it turns out that purchase stock also has a semi-populated stock summary object to work with. Unfortunately, in this case the value is coming from the client and it is missing the purchaseLotNumber, which is the key. Fixing the client will require somehow passing this value to purchaseStock.jsp Bigbank sample should demonstrate the SCA async PM -- Key: TUSCANY-270 URL: http://issues.apache.org/jira/browse/TUSCANY-270 Project: Tuscany Type: Bug Components: Java BigBank Scenario Versions: Java-Mx Reporter: Jean-Sebastien Delfino Assignee: Ignacio Silva-Lepe Fix For: Java-Mx Attachments: async-bigbank-mediator.txt, async-bigbank-new.txt, async-bigbank.txt The Bigbank sample should demonstrate the SCA async PM. Rick, Jim, could you please add comments to this JIRA with your suggestions to improve the sample to demonstrate the SCA async PM? Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
