[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603844#action_12603844 ] Daniel Stucky commented on TUSCANY-2343: Hi Rajini, I finally managed to get the SCADomain and our JUnit tests to run locally on my machine (at least inside eclipse. PDEBuild is running as well, but not the JUnit tests). With all the small modifications it is just a temporary solution for testing. At the moment it makes no sense to adopt our bundles / 3rd party bundles as long as the Tuscany bundles will change. We're looking forward to a clean integration with Tuscany. Could you form an estimate when the the bundle versioning and import/exports might be available? Besides, it would be great if the Maven build could generate all bundles (Tuscany and Tuscany 3rd party). Thanks in advance. Bye, Daniel > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 > Project: Tuscany > Issue Type: Bug >Reporter: Georg Schmidt > Attachments: Libary Versions.xls, test_bundles.zip > > > Currently the design of the OSGi bundles leads to class loading exceptions. > There seem to be several reasons for this behavior: > * reexporting of all libraries without version numbers > * imports without version numbers > Please use distinct bundles for 3rd party libraries. That would lead to > easier reusage of your bundles in a larger OSGi project. > The current status leads to undefined system behaviour due to the OSGi class > loading concept. > Please tell if you see a way, how we could support you by achieving this > goal. (If a solution is interesting for you) We are willing to contribute > because its a critical project issue for us. > The problems occur with the current snapshot release. Sorry, I do not know > which version to take. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603525#action_12603525 ] Daniel Stucky commented on TUSCANY-2343: Hi Rajini, yes, you were right. There were some duplicate SDO bundles - the ones provided by Tuscany. I'm a little confused now as SDO bundles are included in the Tuscany 3rd party (the ones created by the installer) and SDO bundles in the Maven repository ( referenced in the installers classpath) Not noticing it, I had installed both versions in my OSGi runtime: MVN repository .m2\repository\org\apache\tuscany\sca\tuscany-databinding-sdo\2.0-incubating-SNAPSHOT\tuscany-databinding-sdo-2.0-incubating-SNAPSHOT.jar .m2\repository\org\apache\tuscany\sca\tuscany-databinding-sdo-axiom\2.0-incubating-SNAPSHOT\tuscany-databinding-sdo-axiom-2.0-incubating-SNAPSHOT.jar; .m2\repository\org\apache\tuscany\sdo\tuscany-sdo-api-r2.1\1.1-incubating\tuscany-sdo-api-r2.1-1.1-incubating.jar; .m2\repository\org\apache\tuscany\sdo\tuscany-sdo-impl\1.1-incubating\tuscany-sdo-impl-1.1-incubating.jar; .m2\repository\org\apache\tuscany\sdo\tuscany-sdo-lib\1.1-incubating\tuscany-sdo-lib-1.1-incubating.jar; .m2\repository\org\apache\tuscany\sdo\tuscany-sdo-tools\1.1-incubating\tuscany-sdo-tools-1.1-incubating.jar; 3rd party org.apache.tuscany.sca.tuscany-sdo-api-r2.1-1.1-incubating.jar org.apache.tuscany.sca.tuscany-sdo-impl-1.1-incubating.jar org.apache.tuscany.sca.tuscany-sdo-lib-1.1-incubating.jar org.apache.tuscany.sca.tuscany-sdo-tools-1.1-incubating.jar Which ones are the right ones to use ? For testing I just removed the 3rd party bundles (because it's a subset of the others) and now my SCA Domain starts successfully !!! Thanks for your help !!! Now I'll try to get our JUnit tests run to check execution of the components. Daniel > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 > Project: Tuscany > Issue Type: Bug >Reporter: Georg Schmidt > Attachments: Libary Versions.xls, test_bundles.zip > > > Currently the design of the OSGi bundles leads to class loading exceptions. > There seem to be several reasons for this behavior: > * reexporting of all libraries without version numbers > * imports without version numbers > Please use distinct bundles for 3rd party libraries. That would lead to > easier reusage of your bundles in a larger OSGi project. > The current status leads to undefined system behaviour due to the OSGi class > loading concept. > Please tell if you see a way, how we could support you by achieving this > goal. (If a solution is interesting for you) We are willing to contribute > because its a critical project issue for us. > The problems occur with the current snapshot release. Sorry, I do not know > which version to take. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603010#action_12603010 ] Daniel Stucky commented on TUSCANY-2343: Hi Rajini, Thanks again for your help ! I removed the exporting of META-INF.services in our xerces and xalan bundles. Now the SCADomain starts without errors. However, now I get an exception when adding my contribution to the contribution service: java.lang.NullPointerException at commonj.sdo.impl.HelperProvider.getDefaultContext(HelperProvider.java:388) at org.apache.tuscany.sca.databinding.sdo.SDODataBinding$1.run(SDODataBinding.java:67) at org.apache.tuscany.sca.databinding.sdo.SDODataBinding$1.run(SDODataBinding.java:66) at java.security.AccessController.doPrivileged(Native Method) at org.apache.tuscany.sca.databinding.sdo.SDODataBinding.introspect(SDODataBinding.java:65) at org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.introspect(DefaultDataBindingExtensionPoint.java:195) at org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:250) at org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSFaultExceptionMapper.introspectFaultDataType(JAXWSFaultExceptionMapper.java:240) at org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.introspectFaultTypes(JAXWSJavaInterfaceProcessor.java:272) at org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.visitInterface(JAXWSJavaInterfaceProcessor.java:112) at org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl.introspectInterface(JavaInterfaceIntrospectorImpl.java:114) at org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceFactoryImpl.createJavaInterface(JavaInterfaceFactoryImpl.java:55) at org.apache.tuscany.sca.interfacedef.java.xml.JavaInterfaceProcessor.resolveJavaInterface(JavaInterfaceProcessor.java:131) at org.apache.tuscany.sca.interfacedef.java.xml.JavaInterfaceProcessor.resolve(JavaInterfaceProcessor.java:148) at org.apache.tuscany.sca.interfacedef.java.xml.JavaInterfaceProcessor.resolve(JavaInterfaceProcessor.java:50) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:332) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:156) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:405) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:364) at org.apache.tuscany.sca.assembly.xml.ComponentTypeProcessor.resolve(ComponentTypeProcessor.java:356) at org.apache.tuscany.sca.assembly.xml.ComponentTypeProcessor.resolve(ComponentTypeProcessor.java:59) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:332) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:156) at org.apache.tuscany.sca.assembly.xml.ComponentTypeDocumentProcessor.resolve(ComponentTypeDocumentProcessor.java:133) at org.apache.tuscany.sca.assembly.xml.ComponentTypeDocumentProcessor.resolve(ComponentTypeDocumentProcessor.java:47) at org.apache.tuscany.sca.contribution.processor.DefaultURLArtifactProcessorExtensionPoint$LazyURLArtifactProcessor.resolve(DefaultURLArtifactProcessorExtensionPoint.java:208) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:106) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:519) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:394) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:187) at org.eclipse.eilf.connectivity.framework.sca.ScaDomainActivator.initDomainByContribution(ScaDomainActivator.java:120) at org.eclipse.eilf.connectivity.framework.sca.ScaDomainActivator.start(ScaDomainActivator.java:58) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993)
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602951#action_12602951
]
Daniel Stucky commented on TUSCANY-2343:
Hi Rajini,
as suggested I debugged the Equinox code and found out different behavior in
class org.eclipse.osgi.framework.internal.core.BundleLoader#findResource(String
name, boolean checkParent).
The 1st call does not find a PackageSource, so it falls back to
findLocalResource() which locates the class.
The 2nd call finds a PackageSource via method findImportedSource(pkgName), as
this time org.apache.xerces is in the list of imports. It does not contain the
desired class. No fallback logic is executed but null is returned.
Here are some details
1st call:
findImportedSource(pkgName);
imports = {com.ctc.wstx.dtd ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.stax -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1", com.ctc.wstx.io ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
org.codehaus.stax2.validation ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.ent -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1", org.codehaus.stax2.io ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.util -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1", com.ctc.wstx.sr ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.sw -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1", org.codehaus.stax2 ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.exc -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1", com.ctc.wstx.compat ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.sax -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1", com.ctc.wstx.evt ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.cfg -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1", org.codehaus.stax2.evt ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.msv -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1", com.ctc.wstx.dom ->
org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1; bundle-version="3.2.1",
com.ctc.wstx.api -> org.apache.tuscany.sca.3rdparty.wstx-asl-3.2.1;
bundle-version="3.2.1"}
-> source=null
findRequiredSource(pkgName);
-> source=null
findLocalResource(name);
-> result =
bundleresource://27/META-INF/services/javax.xml.stream.XMLInputFactory
2nd call:
findImportedSource(pkgName);
imports = {javax.xml.stream.events ->
org.apache.tuscany.sca.3rdparty.stax-api-1.0.1; bundle-version="1.0.1",
javax.xml.stream.util -> org.apache.tuscany.sca.3rdparty.stax-api-1.0.1;
bundle-version="1.0.1", org.apache.log4j ->
org.apache.tuscany.sca.3rdparty.log4j-1.2.12; bundle-version="1.2.12",
javax.xml.stream -> org.apache.tuscany.sca.3rdparty.stax-api-1.0.1;
bundle-version="1.0.1", META-INF.services -> org.apache.xerces;
bundle-version="2.9.0"}
-> source = META-INF.services -> org.apache.xerces; bundle-version="2.9.0"
-> result = null
So the questions are:
- why is the list of imports different ?
- is there a bug in the execution logic of
org.eclipse.osgi.framework.internal.core.BundleLoader#findResource(String name,
boolean checkParent). The search is terminated, as the comment "// 3) found
import source terminate search at the source" clearly says. Perhaps it should
continue the search nothing is found ?
Bye,
Daniel
> OSGi bundle design leads to class loading issues
>
>
> Key: TUSCANY-2343
> URL: https://issues.apache.org/jira/browse/TUSCANY-2343
> Project: Tuscany
> Issue Type: Bug
>Reporter: Georg Schmidt
> Attachments: Libary Versions.xls, test_bundles.zip
>
>
> Currently the design of the OSGi bundles leads to class loading exceptions.
> There seem to be several reasons for this behavior:
> * reexporting of all libraries without version numbers
> * imports without version numbers
> Please use distinct bundles for 3rd party libraries. That would lead to
> easier reusage of your bundles in a larger OSGi project.
> The current status leads to undefined system behaviour due to the OSGi class
> loading concept.
> Please tell if you see a way, how we could support you by achieving this
> goal. (If a solution is interesting for you) We are willing to contribute
> because its a critical project issue for us.
> The problems occur with the current snapshot release. Sorry, I do not know
> which version to
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602641#action_12602641 ] Daniel Stucky commented on TUSCANY-2343: One more comment: During the 1st call the URL is found in bundle org.apache.tuscany.sca.wstx-asl-3.2.1.jar During the 2nd call this bundle is listet in bundles, but the URL is not found! Daniel > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 > Project: Tuscany > Issue Type: Bug >Reporter: Georg Schmidt > Attachments: Libary Versions.xls, test_bundles.zip > > > Currently the design of the OSGi bundles leads to class loading exceptions. > There seem to be several reasons for this behavior: > * reexporting of all libraries without version numbers > * imports without version numbers > Please use distinct bundles for 3rd party libraries. That would lead to > easier reusage of your bundles in a larger OSGi project. > The current status leads to undefined system behaviour due to the OSGi class > loading concept. > Please tell if you see a way, how we could support you by achieving this > goal. (If a solution is interesting for you) We are willing to contribute > because its a critical project issue for us. > The problems occur with the current snapshot release. Sorry, I do not know > which version to take. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602637#action_12602637 ] Daniel Stucky commented on TUSCANY-2343: I was not able to set a breakpoint in method findClass(...). Eclipse did just not allow it. It was possible in all other methods, though. Here are the results of the breakpoint in getResource(...) and following code 1st call: OSGiBundleActivator$BundleClassLoader (id=84) bundle.size() = 230 resName=META-INF/services/javax.xml.stream.XMLInputFactory URL=bundleresource://52/META-INF/services/javax.xml.stream.XMLInputFactory factoryClassname=com.ctc.wstx.stax.WstxInputFactory 2nd call: OSGiBundleActivator$BundleClassLoader (id=84) bundle.size() = 230 resName=META-INF/services/javax.xml.stream.XMLInputFactory URL=null As you can see, the URL in the 2nd call is null. > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 > Project: Tuscany > Issue Type: Bug >Reporter: Georg Schmidt > Attachments: Libary Versions.xls, test_bundles.zip > > > Currently the design of the OSGi bundles leads to class loading exceptions. > There seem to be several reasons for this behavior: > * reexporting of all libraries without version numbers > * imports without version numbers > Please use distinct bundles for 3rd party libraries. That would lead to > easier reusage of your bundles in a larger OSGi project. > The current status leads to undefined system behaviour due to the OSGi class > loading concept. > Please tell if you see a way, how we could support you by achieving this > goal. (If a solution is interesting for you) We are willing to contribute > because its a critical project issue for us. > The problems occur with the current snapshot release. Sorry, I do not know > which version to take. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2281) How to create ServiceReferences for references using multiplicity="1..n"
[ https://issues.apache.org/jira/browse/TUSCANY-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602589#action_12602589 ] Daniel Stucky commented on TUSCANY-2281: Hi all, I just wanted to ask if there are any plans when this issue could be solved. I'd really like to make use of this feature in the EILF project. Bye, Daniel > How to create ServiceReferences for references using multiplicity="1..n" > > > Key: TUSCANY-2281 > URL: https://issues.apache.org/jira/browse/TUSCANY-2281 > Project: Tuscany > Issue Type: New Feature > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 >Reporter: Daniel Stucky > Fix For: Java-SCA-Next > > > At the moment it is not possible to create ServiceReferences for specific > targets of references with multiplicity="1..n". > See the mailing list for details: http://www.mail-archive.com/[EMAIL > PROTECTED]/msg03024.html > A quote from Simon Laws' answer: > "The OASIS TC has proposed a solution to this issue > (http://www.osoa.org/jira/browse/JAVA-9) but this isn't part of the API we > have implemented as we have taken the V1 API. Can you raise a JIRA for this > as I can't see one already and at least in that way we can track it." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602588#action_12602588 ] Daniel Stucky commented on TUSCANY-2343: Hi Rajini, I added your code snippet. Here is the output: output of 1st snippet just before scaDomain.start(). no exception is thrown - TCCL : class org.apache.tuscany.sca.osgi.runtime.OSGiBundleActivator$BundleClassLoader output of 2nd snippet in catch block after scaDomain.start() - TCCL : class org.apache.tuscany.sca.osgi.runtime.OSGiBundleActivator$BundleClassLoader but this time javax.xml.stream.XMLInputFactory.newInstance() throws the following exception - javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParserFactory not found Bye, Daniel > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 > Project: Tuscany > Issue Type: Bug >Reporter: Georg Schmidt > Attachments: Libary Versions.xls, test_bundles.zip > > > Currently the design of the OSGi bundles leads to class loading exceptions. > There seem to be several reasons for this behavior: > * reexporting of all libraries without version numbers > * imports without version numbers > Please use distinct bundles for 3rd party libraries. That would lead to > easier reusage of your bundles in a larger OSGi project. > The current status leads to undefined system behaviour due to the OSGi class > loading concept. > Please tell if you see a way, how we could support you by achieving this > goal. (If a solution is interesting for you) We are willing to contribute > because its a critical project issue for us. > The problems occur with the current snapshot release. Sorry, I do not know > which version to take. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602328#action_12602328 ] Daniel Stucky commented on TUSCANY-2343: Hi, yes, the activator sets TCCL and I also use option -clean. The difference is in line 3: at org.apache.tuscany.sca.extension.helper.impl.BindingsActivator.start(BindingsActivator.java:72) (former exception) vs. at org.apache.tuscany.sca.implementation.notification.NotificationModuleActivator.start(NotificationModuleActivator.java:34) (current exception) I debugged a little, it happens when Tuscany tries to find the interface org.apache.tuscany.sca.contribution.processor.StAXArtifactProcessorExtensionPoint. Perhaps this is somehow related to the problems we encountered with JAXB ? Bye, Daniel > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 > Project: Tuscany > Issue Type: Bug >Reporter: Georg Schmidt > Attachments: Libary Versions.xls, test_bundles.zip > > > Currently the design of the OSGi bundles leads to class loading exceptions. > There seem to be several reasons for this behavior: > * reexporting of all libraries without version numbers > * imports without version numbers > Please use distinct bundles for 3rd party libraries. That would lead to > easier reusage of your bundles in a larger OSGi project. > The current status leads to undefined system behaviour due to the OSGi class > loading concept. > Please tell if you see a way, how we could support you by achieving this > goal. (If a solution is interesting for you) We are willing to contribute > because its a critical project issue for us. > The problems occur with the current snapshot release. Sorry, I do not know > which version to take. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602316#action_12602316 ] Daniel Stucky commented on TUSCANY-2343: Hi all, I just set up a launch configuration for our "productive" bundle. Whitout the Activator fix from Rajini I get the same exception as in the "test" bundle. (see above) Then I added the to the activator and now I get the following exception: java.lang.IllegalArgumentException: java.lang.reflect.InvocationTargetException at org.apache.tuscany.sca.core.DefaultExtensionPointRegistry.getExtensionPoint(DefaultExtensionPointRegistry.java:128) at org.apache.tuscany.sca.implementation.notification.NotificationModuleActivator.start(NotificationModuleActivator.java:34) at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.startModules(ReallySmallRuntime.java:354) at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.start(ReallySmallRuntime.java:139) at org.apache.tuscany.sca.host.embedded.impl.EmbeddedSCADomain.start(EmbeddedSCADomain.java:79) at org.eclipse.eilf.connectivity.framework.sca.ScaDomainActivator.initDomainByContribution(ScaDomainActivator.java:96) at org.eclipse.eilf.connectivity.framework.sca.ScaDomainActivator.start(ScaDomainActivator.java:57) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.apache.tuscany.sca.core.DefaultExtensionPointRegistry.getExtensionPoint(DefaultExtensionPointRegistry.java:113) ... 19 more Caused by: java.lang.IllegalArgumentException: java.lang.reflect.InvocationTargetException at org.apache.tuscany.sca.contribution.DefaultModelFactoryExtensionPoint.getFactory(DefaultModelFactoryExtensionPoint.java:122) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint.(DefaultStAXArtifactProcessorExtensionPoint.java:68) ... 24 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tuscany.sca.contribution.DefaultModelFactoryExtensionPoint.getFactory(DefaultModelFactoryExtensionPoint.java:120) ... 25 more Caused by: javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParserFactory not found at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72) at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:178) at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92) at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136) ... 30 more Are there other Threads that need to get set the ContextClassLoader ? Daniel > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 >
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602296#action_12602296 ] Daniel Stucky commented on TUSCANY-2343: Hi Rajini, yes, calling Thread.currentThread().setContextClassLoader(OSGiRuntime.getRuntime().getContextClassLoader()); befor creating the SCADomain does the trick. At least for this test bundle. I will do some more testing with our real bundles (more 3rd party dependencies). Thanks a lot! Bye, Daniel > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 > Project: Tuscany > Issue Type: Bug >Reporter: Georg Schmidt > Attachments: Libary Versions.xls, test_bundles.zip > > > Currently the design of the OSGi bundles leads to class loading exceptions. > There seem to be several reasons for this behavior: > * reexporting of all libraries without version numbers > * imports without version numbers > Please use distinct bundles for 3rd party libraries. That would lead to > easier reusage of your bundles in a larger OSGi project. > The current status leads to undefined system behaviour due to the OSGi class > loading concept. > Please tell if you see a way, how we could support you by achieving this > goal. (If a solution is interesting for you) We are willing to contribute > because its a critical project issue for us. > The problems occur with the current snapshot release. Sorry, I do not know > which version to take. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602264#action_12602264 ] Daniel Stucky commented on TUSCANY-2343: Hi, I just tried to install and start the same bundles as when using the installer. To achieve this, I had to remove the Import-Package entry for "sun.misc" in tuscany-databinding-xstream-2.0-incubating-SNAPSHOT.jar Below is the list, the only difference is that when using the installer it's bundle is started and bundle org.eclipse.eilf.scatestdomain_0.5.0 is started: id State Bundle 0 ACTIVE org.eclipse.osgi_3.3.0.v20070530 1 RESOLVEDorg.apache.tuscany.sca.binding.jms_2.0.0 2 RESOLVEDorg.apache.tuscany.sca.3rdparty.commons-lang-2.1_2.1.0 3 RESOLVEDorg.apache.tuscany.sca.binding.rss.rome_2.0.0 4 RESOLVEDorg.apache.tuscany.sca.api_2.0.0 5 RESOLVEDorg.apache.tuscany.sca.3rdparty.saxon-api-9.0.0.2_9.0.0.2 6 RESOLVEDorg.apache.tuscany.sca.definitions.xml_2.0.0 7 RESOLVEDorg.apache.tuscany.sca.implementation.java.runtime_2.0.0 8 RESOLVEDorg.apache.tuscany.sca.domain.manager_2.0.0 9 RESOLVEDorg.apache.tuscany.sca.3rdparty.commons-discovery-0.2_0.2.0 10 RESOLVEDorg.apache.tuscany.sca.3rdparty.xalan-2.7.0_2.7.0 11 RESOLVEDorg.apache.tuscany.sca.data.engine.helper_2.0.0 12 RESOLVEDorg.apache.tuscany.sca.3rdparty.json-rpc-1.0_1.0.0 13 RESOLVEDorg.apache.tuscany.sca.implementation.java_2.0.0 14 RESOLVEDorg.apache.tuscany.sca.interface.wsdl.xml_2.0.0 15 RESOLVEDorg.apache.tuscany.sca.binding.sca.axis2_2.0.0 16 RESOLVEDorg.apache.tuscany.sca.3rdparty.stax-api-1.0.1_1.0.1 17 RESOLVEDorg.apache.tuscany.sca.3rdparty.ecore-2.2.3_2.2.3 18 RESOLVEDorg.apache.tuscany.sca.3rdparty.codegen-ecore-2.2.3_2.2.3 19 RESOLVEDorg.apache.tuscany.sca.3rdparty.stax-api-1.0-2_1.0.0 20 RESOLVEDorg.apache.tuscany.sca.3rdparty.axiom-api-1.2.5_1.2.5 21 RESOLVED org.apache.tuscany.sca.3rdparty.abdera-parser-0.3.0-incubating_0.3.0 22 RESOLVED org.apache.tuscany.sca.3rdparty.commons-collections-3.1_3.1.0 23 RESOLVED org.apache.tuscany.sca.3rdparty.backport-util-concurrent-3.0_3.0.0 24 RESOLVEDorg.apache.tuscany.sca.binding.sca_2.0.0 25 RESOLVEDorg.apache.tuscany.sca.3rdparty.axis2-codegen-1.3_1.3.0 26 RESOLVEDorg.apache.tuscany.sdo.spec_2.1.0 27 RESOLVEDorg.apache.tuscany.sca.3rdparty.easymock-2.2_2.2.0 28 RESOLVEDorg.apache.tuscany.sca.binding.rss_2.0.0 29 RESOLVEDorg.apache.tuscany.sca.3rdparty.jaxb2-reflection-2.1.4_2.1.4 30 RESOLVEDorg.apache.tuscany.sca.3rdparty.xercesImpl-2.8.1_2.8.1 31 ACTIVE org.eclipse.osgi.services_3.1.200.v20070605 32 RESOLVEDorg.apache.tuscany.sca.databinding.saxon_2.0.0 33 RESOLVEDorg.apache.tuscany.sca.3rdparty.axis2-adb-codegen-1.3_1.3.0 34 RESOLVEDorg.apache.tuscany.sca.3rdparty.spring-beans-2.0.6_2.0.6 35 RESOLVEDorg.mortbay.jetty.server_6.1.7 36 RESOLVEDorg.apache.tuscany.sca.contribution_2.0.0 37 RESOLVEDorg.apache.tuscany.sca.3rdparty.activation-1.1_1.1.0 38 RESOLVEDorg.apache.tuscany.sca.workspace_2.0.0 39 RESOLVEDorg.apache.tuscany.sca.interface.java.xml_2.0.0 40 RESOLVEDorg.apache.tuscany.sca.binding.feed_2.0.0 41 RESOLVEDorg.apache.tuscany.sca.3rdparty.servlet-api-2.5_2.5.0 42 RESOLVEDorg.apache.tuscany.sca.3rdparty.mail-1.4_1.4.0 43 RESOLVED org.apache.tuscany.sca.3rdparty.abdera-core-0.3.0-incubating_0.3.0 44 RESOLVEDorg.apache.tuscany.sca.3rdparty.axis2-mtompolicy-1.3_1.3.0 45 RESOLVEDorg.apache.tuscany.sca.3rdparty.wsdl4j-1.6.2_1.6.2 46 RESOLVEDorg.apache.tuscany.sca.3rdparty.axis2-java2wsdl-1.3_1.3.0 47 RESOLVEDorg.apache.tuscany.sca.3rdparty.rampart-trust-1.3_1.3.0 48 RESOLVEDorg.apache.tuscany.sca.contribution.groovy_2.0.0 49 RESOLVEDorg.apache.tuscany.sca.binding.atom_2.0.0 50 RESOLVEDorg.apache.tuscany.sca.3rdparty.saaj-api-1.3_1.3.0 51 RESOLVEDorg.apache.tuscany.sca.assembly.xsd_2.0.0 52 RESOLVEDorg.apache.tuscany.sca.implementation.xquery_2.0.0 53 RESOLVED org.apache.tuscany.sca.3rdparty.tuscany-sdo-impl-1.1-incubating_1.1.0 54 RESOLVEDorg.apache.tuscany.sca.binding.dwr_2.0.0 55 RESOLVEDorg.apache.tuscany.sca.monitor.logging_2.0.0 56 RESOLVED org.apache.tuscany.sca.3rdparty.woden-1.0-incubating-M7b_1.0.0 57 RESOLVEDorg.apache.tuscany.sca.binding.atom.abdera_2.0.0 58 RESOLVEDorg.apache.tuscany.sca.definitions_2.0.0 59 RESOLVED org.apache.tuscany.sca.3rdparty.tuscany-sdo-tools-1.1-incubating_1.1.0 60 RESOLVEDorg.apache.tuscany.sca.binding.jsonrpc_2.0.0 61 RESOLVED org
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602221#action_12602221
]
Daniel Stucky commented on TUSCANY-2343:
Hi all,
thanks for your quick response.
No, we do not use any security. To check I just added 2 lines of code to the
BundleActivator:
String prop = System.getProperty("java.security.manager");
SecurityManager manager = System.getSecurityManager();
Both prop and manager are null.
I also added -clean to the launch. No change there. I still get the
NullPointerException.
Yes, if you see the output
"Starting ... test.composite ready !!!
did something"
the SCADomain was created and a method on the Test service was executed.
Rajini, did you install and start only the bundles that I used in my launch
files or did you use more/less bundles or even all Tuscany and Tuscany 3rd
party bundles?
Could this be some eclipse issue, as you said you are not using eclipse.
Bye,
Daniel
> OSGi bundle design leads to class loading issues
>
>
> Key: TUSCANY-2343
> URL: https://issues.apache.org/jira/browse/TUSCANY-2343
> Project: Tuscany
> Issue Type: Bug
>Reporter: Georg Schmidt
> Attachments: Libary Versions.xls, test_bundles.zip
>
>
> Currently the design of the OSGi bundles leads to class loading exceptions.
> There seem to be several reasons for this behavior:
> * reexporting of all libraries without version numbers
> * imports without version numbers
> Please use distinct bundles for 3rd party libraries. That would lead to
> easier reusage of your bundles in a larger OSGi project.
> The current status leads to undefined system behaviour due to the OSGi class
> loading concept.
> Please tell if you see a way, how we could support you by achieving this
> goal. (If a solution is interesting for you) We are willing to contribute
> because its a critical project issue for us.
> The problems occur with the current snapshot release. Sorry, I do not know
> which version to take.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[ https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stucky updated TUSCANY-2343: --- Attachment: test_bundles.zip Hi Rajini, I build the 3rd party bundles with the installer. I had to remove the activemq bundle (we also use one) because during pdebuild it generated a cycle. After that pdebuild works. However, suddenly our test bundles did not run anymore in eclipse. Attached are 2 test bundles that simulate the usage in our project, without any additional 3rd party dependencies). One contains a DeclerativeService, the other starts a SCA Domain that uses this DS (via implementation.type osgi). I provided 2 eclipse launch configurations. One uses the the osgi.installer bundle, the other does not use the installer but uses the required tuscany and 3rd party bundles directly. (you will also need the bundles org.eclipse.equinox.ds and org.eclipse.equinox.util) The launch with the installer works fine. The launch using the bundles stops with the following exception: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.start(ReallySmallRuntime.java:124) at org.apache.tuscany.sca.host.embedded.impl.EmbeddedSCADomain.start(EmbeddedSCADomain.java:79) at org.eclipse.eilf.scatestdomain.ScaDomainActivator.initDomainByContribution(ScaDomainActivator.java:100) at org.eclipse.eilf.scatestdomain.ScaDomainActivator.start(ScaDomainActivator.java:56) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297) The problem ist that the ServiceDiscovery does not find "META-INF/services/org.apache.tuscany.sca.work.WorkScheduler". So in class ReallySmallRuntime the - member variable workScheduler is null - variable factories is null (wich leads to the NPE) This is a classloading problem I was not able to solve. BTW: is this a feasible way to create a SCADomain within OSGi ? > OSGi bundle design leads to class loading issues > > > Key: TUSCANY-2343 > URL: https://issues.apache.org/jira/browse/TUSCANY-2343 > Project: Tuscany > Issue Type: Bug >Reporter: Georg Schmidt > Attachments: Libary Versions.xls, test_bundles.zip > > > Currently the design of the OSGi bundles leads to class loading exceptions. > There seem to be several reasons for this behavior: > * reexporting of all libraries without version numbers > * imports without version numbers > Please use distinct bundles for 3rd party libraries. That would lead to > easier reusage of your bundles in a larger OSGi project. > The current status leads to undefined system behaviour due to the OSGi class > loading concept. > Please tell if you see a way, how we could support you by achieving this > goal. (If a solution is interesting for you) We are willing to contribute > because its a critical project issue for us. > The problems occur with the current snapshot release. Sorry, I do not know > which version to take. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2343) OSGi bundle design leads to class loading issues
[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601171#action_12601171
]
Daniel Stucky commented on TUSCANY-2343:
Hi Rajini,
this week I've been testing the new Tuscany bundles with the installer bundle.
In eclipse our bundles compile and the tests run sucessfully.
There are is a minor issue concerning the InstallerBundleActivator. All Tuscany
bundles (including the installer) and all 3rd party jars are located in the
same directory. In the installer's classpath all entries are absolute paths to
the maven repository. On machines without the repository, the jars are not
found. As I unsterstand there should be some code in the
InstallerBundleActivator that checks this and tries to find the jars relative
to the installer., but this does not work. I guess the boolean logic at line
169 is not correct:
...
if (!jar.isAbsolute()&&!jar.exists()) {
jar = new File(tuscanyInstallDir, jar.getName());
}
...
Another problem is that we are trying to build our application automatically
using ant and eclipse pdebuild. So far we did not get it running. An error
occurs in the first bundle that makes use of Tuscany classes. If we exclude
those bundles from the build everything works fine. There are lots of warnings
regarding "Unsatisfied import package".
Has anyone experience using pdebuild and tuscany ?
Bye,
Daniel
> OSGi bundle design leads to class loading issues
>
>
> Key: TUSCANY-2343
> URL: https://issues.apache.org/jira/browse/TUSCANY-2343
> Project: Tuscany
> Issue Type: Bug
>Reporter: Georg Schmidt
> Attachments: Libary Versions.xls
>
>
> Currently the design of the OSGi bundles leads to class loading exceptions.
> There seem to be several reasons for this behavior:
> * reexporting of all libraries without version numbers
> * imports without version numbers
> Please use distinct bundles for 3rd party libraries. That would lead to
> easier reusage of your bundles in a larger OSGi project.
> The current status leads to undefined system behaviour due to the OSGi class
> loading concept.
> Please tell if you see a way, how we could support you by achieving this
> goal. (If a solution is interesting for you) We are willing to contribute
> because its a critical project issue for us.
> The problems occur with the current snapshot release. Sorry, I do not know
> which version to take.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2281) How to create ServiceReferences for references using multiplicity="1..n"
How to create ServiceReferences for references using multiplicity="1..n" Key: TUSCANY-2281 URL: https://issues.apache.org/jira/browse/TUSCANY-2281 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Reporter: Daniel Stucky At the moment it is not possible to create ServiceReferences for specific targets of references with multiplicity="1..n". See the mailing list for details: http://www.mail-archive.com/[EMAIL PROTECTED]/msg03024.html A quote from Simon Laws' answer: "The OASIS TC has proposed a solution to this issue (http://www.osoa.org/jira/browse/JAVA-9) but this isn't part of the API we have implemented as we have taken the V1 API. Can you raise a JIRA for this as I can't see one already and at least in that way we can track it." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2270) Conversations do not to work with binding.rmi
Conversations do not to work with binding.rmi
-
Key: TUSCANY-2270
URL: https://issues.apache.org/jira/browse/TUSCANY-2270
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.2
Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
1.5.0_10
Reporter: Daniel Stucky
I have implemented a Service that uses conversations. The interface is
annotated with @Conversational, the implementation is annotated with
@Scope("CONVERSATION") and has a member protected String conversationId
annotated with @ConversationID.
The Service runs fine when using binding.sca or binding.ws. If I use
binding.rmi I get the following exception:
org.osoa.sca.ServiceRuntimeException: java.lang.NullPointerException
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:123)
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:89)
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:83)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(RuntimeWireImpl.java:134)
at
org.apache.tuscany.sca.binding.rmi.RMIService.invokeTarget(RMIService.java:110)
at
org.apache.tuscany.sca.binding.rmi.RMIService$1.intercept(RMIService.java:95)
at
$java.rmi.server.UnicastRemoteObject$$EnhancerByCGLIB$$8c0275ac.setup()
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
at
java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
at
java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
at $Proxy14.setup(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tuscany.sca.binding.rmi.RMIReferenceInvoker.invokeTarget(RMIReferenceInvoker.java:74)
at
org.apache.tuscany.sca.binding.rmi.RMIReferenceInvoker.invoke(RMIReferenceInvoker.java:51)
at
org.apache.tuscany.sca.extension.helper.impl.InvokerProxy.invoke(BindingsActivator.java:252)
at
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
at $Proxy13.setup(Unknown Source)
at impl.CrawlerControllerImpl.doImport(CrawlerControllerImpl.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109)
at
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
at
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
at
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.in
[jira] Commented: (TUSCANY-2209) Question about Conversational OSGi Services and Service References
[ https://issues.apache.org/jira/browse/TUSCANY-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587132#action_12587132 ] Daniel Stucky commented on TUSCANY-2209: Hi Rajini, I just tested your fix and I'm not able to reproduce the former errors. Everything seems to work fine now ! Thanks for your help and the quick fix. Bye, Daniel > Question about Conversational OSGi Services and Service References > -- > > Key: TUSCANY-2209 > URL: https://issues.apache.org/jira/browse/TUSCANY-2209 > Project: Tuscany > Issue Type: Bug > Components: Java SCA OSGi Integration >Affects Versions: Java-SCA-1.2 > Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk > 1.5.0_10 >Reporter: Daniel Stucky >Assignee: Rajini Sivaram > Attachments: OneWay_Conversation_OSGi_SCA_test.zip > > > For an overview of the problem please check this thread on the mailing-list: > http://www.mail-archive.com/[EMAIL PROTECTED]/msg02833.html -- 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-2209) Question about Conversational OSGi Services and Service References
[ https://issues.apache.org/jira/browse/TUSCANY-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stucky updated TUSCANY-2209: --- Attachment: OneWay_Conversation_OSGi_SCA_test.zip I attached one of our EILF test implementations. It contains 5 osgi bundles and runs in eclipse. Bundle tuscany.osgi.sample.launch contains a readme file with some additional information. Start at DomainActivator. The former mentioned classes translate as follows: Alpha -> CrawlerController Beta -> Crawler Gamma -> Iterator The code will be self explaining (hopefully :-) ) The sample illustrates a filesystem crawler. In order to get it work, you have to create two folders (data and data2) right beneath tuscany.osgi.sample.launch and copy some small txt or html files (about 30) in each folder. If there are any question, please don't hesitate to contact me. Bye, Daniel > Question about Conversational OSGi Services and Service References > -- > > Key: TUSCANY-2209 > URL: https://issues.apache.org/jira/browse/TUSCANY-2209 > Project: Tuscany > Issue Type: Bug > Components: Java SCA OSGi Integration >Affects Versions: Java-SCA-1.2 > Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk > 1.5.0_10 >Reporter: Daniel Stucky > Attachments: OneWay_Conversation_OSGi_SCA_test.zip > > > For an overview of the problem please check this thread on the mailing-list: > http://www.mail-archive.com/[EMAIL PROTECTED]/msg02833.html -- 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-2209) Question about Conversational OSGi Services and Service References
Question about Conversational OSGi Services and Service References -- Key: TUSCANY-2209 URL: https://issues.apache.org/jira/browse/TUSCANY-2209 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Affects Versions: Java-SCA-1.2 Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk 1.5.0_10 Reporter: Daniel Stucky For an overview of the problem please check this thread on the mailing-list: http://www.mail-archive.com/[EMAIL PROTECTED]/msg02833.html -- 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-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stucky updated TUSCANY-2056: --- Attachment: testoneway.zip Attached is an eclipse project with the described setup. Please don't get confused by the name "oneway" and some commented code. I was trying to test something different when I ran into this conversationId problem. > Conversation does not continue if a Service Reference is passed as a return > value (not as a parameter) when using binding.ws > > > Key: TUSCANY-2056 > URL: https://issues.apache.org/jira/browse/TUSCANY-2056 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk > 1.5.0_10 >Reporter: Daniel Stucky >Assignee: Simon Laws > Fix For: Java-SCA-1.2 > > Attachments: test.zip, test.zip, testoneway.zip > > > This problem is related to TUSCANY-2028. It is exactly the same use case, but > instead of the default binding (sca) I now use binding.ws. > And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I > guess the fix that went into Tuscany 1.1 did only affect binding.sca and not > binding.ws. -- 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] Reopened: (TUSCANY-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stucky reopened TUSCANY-2056: Hi Simon, I did some modifications in my test and ran into another problem. The problem does not occur with binding.sca, only with binding.ws. This time I call method run() on Alpha. Alpha calls getRef() on Beta and gets a reference to Gamma. Alpha then calls some methods on Gamma (it's an iterator).This works fine. However, if I call method run() on Alpha a second time after the first one completed I get an exception. Here is the console output: Starting ... 14.03.2008 15:25:47 org.apache.tuscany.sca.http.jetty.JettyServer addServletMapping INFO: Added Servlet mapping: http://AFA-19393:8080/Beta 14.03.2008 15:25:47 org.apache.tuscany.sca.http.jetty.JettyServer addServletMapping INFO: Added Servlet mapping: http://AFA-19393:8080/Gamma test.composite ready !!! 1st run ... GammaImpl:GammaImpl(), conversationId=null Gamma:start(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 value=id_0, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 value=id_1, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 value=id_2, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 value=id_3, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:next(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 value=id_4, conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:hasNext(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 Gamma:stop(), conversationId=06a8dc57-c174-40a5-8d26-576f11482d42 2nd run ... GammaImpl:GammaImpl(), conversationId=null Gamma:start(), conversationId=9631fa34-7ef4-4287-bb3b-b58fc519b7ee GammaImpl:GammaImpl(), conversationId=null Gamma:hasNext(), conversationId=a0484c5f-e5e1-4cb6-ad41-04a244a724ed org.osoa.sca.ServiceRuntimeException: Target fault type cannot be resolved: null at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:134) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155) at $Proxy14.hasNext(Unknown Source) at services.AlphaImpl.run(AlphaImpl.java:26) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155) at $Proxy12.run(Unknown Source) at launch.Launch.main(Launch.java:23) Caused by: org.apache.tuscany.sca.interfacedef.util.FaultException: unknown at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:97) at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78) ... 16 more Caused by: org.apache.axis2.AxisFault: unknown at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.cl
[jira] Updated: (TUSCANY-2077) ConversationIds are not always unique
[ https://issues.apache.org/jira/browse/TUSCANY-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stucky updated TUSCANY-2077: --- Attachment: testoneway.zip Attached is a eclipse project with the my test classes. For debugging I suggest to set a breakpoint in line 26 of file BetaImpl > ConversationIds are not always unique > - > > Key: TUSCANY-2077 > URL: https://issues.apache.org/jira/browse/TUSCANY-2077 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk > 1.5.0_10 >Reporter: Daniel Stucky > Attachments: testoneway.zip > > > The attached test works fine if I do NOT mark method run() in Aplha with > @OneWay. > The goal is to call Alpha.run() multiple times "concurrently" by using > @OneWay. > If I DO mark it with @OneWay sometimes the following error occurs > Here is the command line output with line numbers: > 1: Starting ... > 2: test.composite ready !!! > 3: GammaImpl:GammaImpl(), conversationId=null > 4: Gamma:start(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 5: GammaImpl:GammaImpl(), conversationId=null > 6: Gamma:start(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 7: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 8: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 9: value=id_0, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 10: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 11: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 12: value=id_1, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 13: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 14: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 15: value=id_2, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 16: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 17: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 18: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 19: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 20: value=id_0, conversationId=3c6df219-e61c-4327-94dc-1cd2b3a08f78 > 21: value=id_3, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 22: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 23: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 24: value=id_4, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 25: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 26: Gamma:stop(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 > 27: GammaImpl:GammaImpl(), conversationId=null > 28: Gamma:hasNext(), conversationId=dcde1a3f-8eb0-4e33-84fd-80d7359432b2 > 29: java.lang.NullPointerException > at services.GammaImpl.hasNext(GammaImpl.java:40) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) > at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) > at > org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) > at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) > at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) > at > org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155) > at $Proxy14.hasNext(Unknown Source) > at services.AlphaImpl.run(AlphaImpl.java:26) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) > at > org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) > at > org.apache.tuscany.sca.core.invocation.NonBlockingInterceptor$1.run(NonBlockingInterceptor.java:71) > at org.apache.tuscany.sca.core.work.Jsr237Work.
[jira] Created: (TUSCANY-2077) ConversationIds are not always unique
ConversationIds are not always unique - Key: TUSCANY-2077 URL: https://issues.apache.org/jira/browse/TUSCANY-2077 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk 1.5.0_10 Reporter: Daniel Stucky The attached test works fine if I do NOT mark method run() in Aplha with @OneWay. The goal is to call Alpha.run() multiple times "concurrently" by using @OneWay. If I DO mark it with @OneWay sometimes the following error occurs Here is the command line output with line numbers: 1: Starting ... 2: test.composite ready !!! 3: GammaImpl:GammaImpl(), conversationId=null 4: Gamma:start(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 5: GammaImpl:GammaImpl(), conversationId=null 6: Gamma:start(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 7: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 8: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 9: value=id_0, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 10: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 11: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 12: value=id_1, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 13: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 14: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 15: value=id_2, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 16: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 17: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 18: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 19: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 20: value=id_0, conversationId=3c6df219-e61c-4327-94dc-1cd2b3a08f78 21: value=id_3, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 22: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 23: Gamma:next(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 24: value=id_4, conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 25: Gamma:hasNext(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 26: Gamma:stop(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 27: GammaImpl:GammaImpl(), conversationId=null 28: Gamma:hasNext(), conversationId=dcde1a3f-8eb0-4e33-84fd-80d7359432b2 29: java.lang.NullPointerException at services.GammaImpl.hasNext(GammaImpl.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155) at $Proxy14.hasNext(Unknown Source) at services.AlphaImpl.run(AlphaImpl.java:26) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) at org.apache.tuscany.sca.core.invocation.NonBlockingInterceptor$1.run(NonBlockingInterceptor.java:71) at org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.java:61) at org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:214) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 30: Gamma:stop(), conversationId=5297f3ca-8c6e-4b65-a5e6-5c4fee0457b6 This is a strange problem that is not always reproduceable but
[jira] Commented: (TUSCANY-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577915#action_12577915 ] Daniel Stucky commented on TUSCANY-2056: Hi Simon, the fix you provided works ! Thanks a lot. Bye, Daniel > Conversation does not continue if a Service Reference is passed as a return > value (not as a parameter) when using binding.ws > > > Key: TUSCANY-2056 > URL: https://issues.apache.org/jira/browse/TUSCANY-2056 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk > 1.5.0_10 >Reporter: Daniel Stucky >Assignee: Simon Laws > Fix For: Java-SCA-1.2 > > Attachments: test.zip, test.zip > > > This problem is related to TUSCANY-2028. It is exactly the same use case, but > instead of the default binding (sca) I now use binding.ws. > And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I > guess the fix that went into Tuscany 1.1 did only affect binding.sca and not > binding.ws. -- 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-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577424#action_12577424 ] Daniel Stucky commented on TUSCANY-2056: Hi Simon, I attached an updated version of my test case. The original one did not show the real problem (sorry for that). I added some more output to show that the constructor of class Gamma is called twice. If you switch from binding.ws to binding.sca you will see that the contsructor is called only once. Also I added a println for the conversation id in method start(), to show the inital created conversation id. Here is the output: test.composite ready !!! GammaImpl:GammaImpl(), conversationId=null Gamma:start(), conversationId=e1578e85-2ba4-4695-bb2e-a71952fb2803 Alpha: Conversation to gamma is null > The last line is the real problem. The conversation should exist at this point GammaImpl:GammaImpl(), conversationId=null > the constructor should not be called a second time Gamma:doSomething(), conversationId=ddaffde4-5f90-4d95-9d8b-b0ac9da00557 Alpha: Conversation to gamma exists. conversationId=ddaffde4-5f90-4d95-9d8b-b0ac9da00557 Gamma:stop(), conversationId=ddaffde4-5f90-4d95-9d8b-b0ac9da00557 > These conversations ids are all equal, but they should be equal to the > initial createn conversation id e1578e85-2ba4-4695-bb2e-a71952fb2803 Hope this helps. Bye, Daniel > Conversation does not continue if a Service Reference is passed as a return > value (not as a parameter) when using binding.ws > > > Key: TUSCANY-2056 > URL: https://issues.apache.org/jira/browse/TUSCANY-2056 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk > 1.5.0_10 >Reporter: Daniel Stucky >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: test.zip, test.zip > > > This problem is related to TUSCANY-2028. It is exactly the same use case, but > instead of the default binding (sca) I now use binding.ws. > And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I > guess the fix that went into Tuscany 1.1 did only affect binding.sca and not > binding.ws. -- 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-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stucky updated TUSCANY-2056: --- Attachment: test.zip updated test with additional output and alternative sca binding configuration > Conversation does not continue if a Service Reference is passed as a return > value (not as a parameter) when using binding.ws > > > Key: TUSCANY-2056 > URL: https://issues.apache.org/jira/browse/TUSCANY-2056 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk > 1.5.0_10 >Reporter: Daniel Stucky >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: test.zip, test.zip > > > This problem is related to TUSCANY-2028. It is exactly the same use case, but > instead of the default binding (sca) I now use binding.ws. > And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I > guess the fix that went into Tuscany 1.1 did only affect binding.sca and not > binding.ws. -- 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-2060) Exception using binding.ws if a method is named init()
[
https://issues.apache.org/jira/browse/TUSCANY-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574901#action_12574901
]
Daniel Stucky commented on TUSCANY-2060:
Well, I'm not familiar with Axis2 but I guess there are some reasons behind
that list of excluded method names. Does anybody know what these reasons are?
At the moment it's ok for me to now that there are some method names that are
not allowed (another exception would be nice, though).
> Exception using binding.ws if a method is named init()
> --
>
> Key: TUSCANY-2060
> URL: https://issues.apache.org/jira/browse/TUSCANY-2060
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
>Affects Versions: Java-SCA-1.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
>Reporter: Daniel Stucky
>Assignee: Raymond Feng
> Attachments: test.zip
>
>
> I have the following Java Interface that works with binding.sca:
> public interface Gamma
> {
> void init();
> void doSomething();
> void stop();
> }
> When I use binding.ws (I let Tuscany create the WSDL interfaces automatically
> I get the following exception (see below). The method is NOT marked with
> @Init, it's just the name of the method.
> Exception in thread "main" org.osoa.sca.ServiceRuntimeException:
> org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> 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 launch.Launch.main(Launch.java:10)
> Caused by: org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:183)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
> ... 2 more
> Caused by: org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:756)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:181)
> ... 3 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl.getOperation(WSDLOperationIntrospectorImpl.java:206)
> at
> org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl.Java2WSDLHelper.createWSDLInterfaceContract(Java2WSDLHelper.java:153)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ReferenceBindingProvider.(Axis2ReferenceBindingProvider.java:51)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:53)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:40)
> at
> org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyBindingProviderFactory.createReferenceBindingProvider(DefaultProviderFactoryExtensionPoint.java:190)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addReferenceBindingProvider(CompositeActivatorImpl.java:176)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:133)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:752)
> ... 4 more
> I also tested it with version 1.2. The Exception is the same, with slightly
> different line numbers.
> Exception in thread "main" org.osoa.sca.ServiceRuntimeException:
> org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> 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 launch.Launch.main(Launch.java:10)
> Caused by: org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:215)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
> ... 2 more
> Caused by: org.apache.tuscany.sca.core.assem
[jira] Commented: (TUSCANY-2060) Exception using binding.ws if a method is named init()
[
https://issues.apache.org/jira/browse/TUSCANY-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574899#action_12574899
]
Daniel Stucky commented on TUSCANY-2060:
Well, I'm not familiar with Axis2 but I guess there are some reasons behind
that list of excluded method names. Does anybody know what these reasons are?
At the moment it's ok for me to now that there are some method names that are
not allowed (another exception would be nice, though).
> Exception using binding.ws if a method is named init()
> --
>
> Key: TUSCANY-2060
> URL: https://issues.apache.org/jira/browse/TUSCANY-2060
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
>Affects Versions: Java-SCA-1.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
>Reporter: Daniel Stucky
>Assignee: Raymond Feng
> Attachments: test.zip
>
>
> I have the following Java Interface that works with binding.sca:
> public interface Gamma
> {
> void init();
> void doSomething();
> void stop();
> }
> When I use binding.ws (I let Tuscany create the WSDL interfaces automatically
> I get the following exception (see below). The method is NOT marked with
> @Init, it's just the name of the method.
> Exception in thread "main" org.osoa.sca.ServiceRuntimeException:
> org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> 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 launch.Launch.main(Launch.java:10)
> Caused by: org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:183)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
> ... 2 more
> Caused by: org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:756)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:181)
> ... 3 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl.getOperation(WSDLOperationIntrospectorImpl.java:206)
> at
> org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl.Java2WSDLHelper.createWSDLInterfaceContract(Java2WSDLHelper.java:153)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ReferenceBindingProvider.(Axis2ReferenceBindingProvider.java:51)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:53)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:40)
> at
> org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyBindingProviderFactory.createReferenceBindingProvider(DefaultProviderFactoryExtensionPoint.java:190)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addReferenceBindingProvider(CompositeActivatorImpl.java:176)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:133)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:752)
> ... 4 more
> I also tested it with version 1.2. The Exception is the same, with slightly
> different line numbers.
> Exception in thread "main" org.osoa.sca.ServiceRuntimeException:
> org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> 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 launch.Launch.main(Launch.java:10)
> Caused by: org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:215)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
> ... 2 more
> Caused by: org.apache.tuscany.sca.core.assem
[jira] Updated: (TUSCANY-2060) Exception using binding.ws if a method is named init()
[
https://issues.apache.org/jira/browse/TUSCANY-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stucky updated TUSCANY-2060:
---
Attachment: test.zip
Attached is a small eclipse project with which you can reproduce the described
exception.
> Exception using binding.ws if a method is named init()
> --
>
> Key: TUSCANY-2060
> URL: https://issues.apache.org/jira/browse/TUSCANY-2060
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
>Affects Versions: Java-SCA-1.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
>Reporter: Daniel Stucky
> Attachments: test.zip
>
>
> I have the following Java Interface that works with binding.sca:
> public interface Gamma
> {
> void init();
> void doSomething();
> void stop();
> }
> When I use binding.ws (I let Tuscany create the WSDL interfaces automatically
> I get the following exception (see below). The method is NOT marked with
> @Init, it's just the name of the method.
> Exception in thread "main" org.osoa.sca.ServiceRuntimeException:
> org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> 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 launch.Launch.main(Launch.java:10)
> Caused by: org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:183)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
> ... 2 more
> Caused by: org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:756)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:181)
> ... 3 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl.getOperation(WSDLOperationIntrospectorImpl.java:206)
> at
> org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl.Java2WSDLHelper.createWSDLInterfaceContract(Java2WSDLHelper.java:153)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2ReferenceBindingProvider.(Axis2ReferenceBindingProvider.java:51)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:53)
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:40)
> at
> org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyBindingProviderFactory.createReferenceBindingProvider(DefaultProviderFactoryExtensionPoint.java:190)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addReferenceBindingProvider(CompositeActivatorImpl.java:176)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:133)
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:752)
> ... 4 more
> I also tested it with version 1.2. The Exception is the same, with slightly
> different line numbers.
> Exception in thread "main" org.osoa.sca.ServiceRuntimeException:
> org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> 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 launch.Launch.main(Launch.java:10)
> Caused by: org.osoa.sca.ServiceRuntimeException:
> org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:215)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109)
> at
> org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
> ... 2 more
> Caused by: org.apache.tuscany.sca.core.assembly.ActivationException:
> java.lang.NullPointerException
> at
> org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:756)
> at
> org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADo
[jira] Created: (TUSCANY-2060) Exception using binding.ws if a method is named init()
Exception using binding.ws if a method is named init()
--
Key: TUSCANY-2060
URL: https://issues.apache.org/jira/browse/TUSCANY-2060
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.1
Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
1.5.0_10
Reporter: Daniel Stucky
I have the following Java Interface that works with binding.sca:
public interface Gamma
{
void init();
void doSomething();
void stop();
}
When I use binding.ws (I let Tuscany create the WSDL interfaces automatically I
get the following exception (see below). The method is NOT marked with @Init,
it's just the name of the method.
Exception in thread "main" org.osoa.sca.ServiceRuntimeException:
org.osoa.sca.ServiceRuntimeException:
org.apache.tuscany.sca.core.assembly.ActivationException:
java.lang.NullPointerException
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 launch.Launch.main(Launch.java:10)
Caused by: org.osoa.sca.ServiceRuntimeException:
org.apache.tuscany.sca.core.assembly.ActivationException:
java.lang.NullPointerException
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:183)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
... 2 more
Caused by: org.apache.tuscany.sca.core.assembly.ActivationException:
java.lang.NullPointerException
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:756)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:181)
... 3 more
Caused by: java.lang.NullPointerException
at
org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl.getOperation(WSDLOperationIntrospectorImpl.java:206)
at
org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl.Java2WSDLHelper.createWSDLInterfaceContract(Java2WSDLHelper.java:153)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2ReferenceBindingProvider.(Axis2ReferenceBindingProvider.java:51)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:53)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:40)
at
org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyBindingProviderFactory.createReferenceBindingProvider(DefaultProviderFactoryExtensionPoint.java:190)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addReferenceBindingProvider(CompositeActivatorImpl.java:176)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:133)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:752)
... 4 more
I also tested it with version 1.2. The Exception is the same, with slightly
different line numbers.
Exception in thread "main" org.osoa.sca.ServiceRuntimeException:
org.osoa.sca.ServiceRuntimeException:
org.apache.tuscany.sca.core.assembly.ActivationException:
java.lang.NullPointerException
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 launch.Launch.main(Launch.java:10)
Caused by: org.osoa.sca.ServiceRuntimeException:
org.apache.tuscany.sca.core.assembly.ActivationException:
java.lang.NullPointerException
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:215)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109)
at
org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
... 2 more
Caused by: org.apache.tuscany.sca.core.assembly.ActivationException:
java.lang.NullPointerException
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:756)
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:213)
... 4 more
Caused by: java.lang.NullPointerException
at
org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl.getOperation(WSDLOperationIntrospectorImpl.java:209)
at
org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl.Java2WSDLHelper.createWSDLInterfaceContract(Java2WSDLHelper.java:153)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2ReferenceBindingProvider.(Axis2ReferenceBindingProvider.java:56
[jira] Updated: (TUSCANY-2059) Exception when using binding.ws instead of binding.sca. Interface contains only methods without any in/out parameters and return values
[
https://issues.apache.org/jira/browse/TUSCANY-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stucky updated TUSCANY-2059:
---
Attachment: test.zip
attaches is a small eclipse project with which you can reproduce the described
problem
> Exception when using binding.ws instead of binding.sca. Interface contains
> only methods without any in/out parameters and return values
> ---
>
> Key: TUSCANY-2059
> URL: https://issues.apache.org/jira/browse/TUSCANY-2059
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
>Affects Versions: Java-SCA-1.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
>Reporter: Daniel Stucky
> Attachments: test.zip
>
>
> I have the following Java Interface that works with binding.sca:
> public interface Gamma
> {
> void start();
> void doSomething();
> void stop();
> }
> When I use binding.ws (I let Tuscany create the WSDL interfaces
> automatically), I get the following exception (see below):
> If I add a parameter (e.g. int x) to any of the methods or I replace any
> return type void by a type (e.g. int) it works.
> Does WSDL not allow services without any In/Out parameters ?
> java.lang.reflect.UndeclaredThrowableException
> at $Proxy12.getRef(Unknown Source)
> at services.AlphaImpl.run(AlphaImpl.java:27)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:105)
> at
> org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:88)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:249)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:146)
> at $Proxy11.run(Unknown Source)
> at launch.Launch.main(Launch.java:14) Caused by:
> org.apache.tuscany.sca.interfacedef.util.FaultException: An unknown message
> label has been encountered: In
> at
> org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:80)
> at
> org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:74)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:249)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:146)
> ... 12 more
> I also tried it with version 1.2, the exception changed to this:
> org.osoa.sca.ServiceRuntimeException: Target fault type cannot be resolved:
> null
> at
> org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:134)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:267)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155)
> at $Proxy12.getRef(Unknown Source)
> at services.AlphaImpl.run(AlphaImpl.java:27)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109)
> at
> org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
> at
> org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
> at
> org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:267)
> at
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155)
> at $Proxy11.run(Unknown Source)
> at launch.Launch.main(Launch.java:14)
> Caused by: org.apache.tuscany.sca.interfacedef.util.FaultException: Target
> fault type cannot be
[jira] Created: (TUSCANY-2059) Exception when using binding.ws instead of binding.sca. Interface contains only methods without any in/out parameters and return values
Exception when using binding.ws instead of binding.sca. Interface contains only
methods without any in/out parameters and return values
---
Key: TUSCANY-2059
URL: https://issues.apache.org/jira/browse/TUSCANY-2059
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.1
Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
1.5.0_10
Reporter: Daniel Stucky
I have the following Java Interface that works with binding.sca:
public interface Gamma
{
void start();
void doSomething();
void stop();
}
When I use binding.ws (I let Tuscany create the WSDL interfaces automatically),
I get the following exception (see below):
If I add a parameter (e.g. int x) to any of the methods or I replace any return
type void by a type (e.g. int) it works.
Does WSDL not allow services without any In/Out parameters ?
java.lang.reflect.UndeclaredThrowableException
at $Proxy12.getRef(Unknown Source)
at services.AlphaImpl.run(AlphaImpl.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:105)
at
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:88)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:249)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:146)
at $Proxy11.run(Unknown Source)
at launch.Launch.main(Launch.java:14) Caused by:
org.apache.tuscany.sca.interfacedef.util.FaultException: An unknown message
label has been encountered: In
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:80)
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:74)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:249)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:146)
... 12 more
I also tried it with version 1.2, the exception changed to this:
org.osoa.sca.ServiceRuntimeException: Target fault type cannot be resolved: null
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:134)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:267)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155)
at $Proxy12.getRef(Unknown Source)
at services.AlphaImpl.run(AlphaImpl.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109)
at
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
at
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
at
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:267)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155)
at $Proxy11.run(Unknown Source)
at launch.Launch.main(Launch.java:14)
Caused by: org.apache.tuscany.sca.interfacedef.util.FaultException: Target
fault type cannot be resolved: null
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:97)
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78)
... 16 more
Caused by: org.apache.axis2.AxisFault: Target fault type cannot be resolved:
null
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Uti
[jira] Updated: (TUSCANY-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Stucky updated TUSCANY-2056: --- Attachment: test.zip This is nearly the same eclipse project as in TUSCANY-2028. I only changed the composite to let some components use binding.ws and modified the Interface of Gamma slightly. > Conversation does not continue if a Service Reference is passed as a return > value (not as a parameter) when using binding.ws > > > Key: TUSCANY-2056 > URL: https://issues.apache.org/jira/browse/TUSCANY-2056 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk > 1.5.0_10 >Reporter: Daniel Stucky > Attachments: test.zip > > > This problem is related to TUSCANY-2028. It is exactly the same use case, but > instead of the default binding (sca) I now use binding.ws. > And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I > guess the fix that went into Tuscany 1.1 did only affect binding.sca and not > binding.ws. -- 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-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws Key: TUSCANY-2056 URL: https://issues.apache.org/jira/browse/TUSCANY-2056 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.1 Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk 1.5.0_10 Reporter: Daniel Stucky This problem is related to TUSCANY-2028. It is exactly the same use case, but instead of the default binding (sca) I now use binding.ws. And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I guess the fix that went into Tuscany 1.1 did only affect binding.sca and not binding.ws. -- 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-2028) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter)
[
https://issues.apache.org/jira/browse/TUSCANY-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569295#action_12569295
]
Daniel Stucky commented on TUSCANY-2028:
Yes, I tested it with version 1.1 the test now completes as expected..
> Conversation does not continue if a Service Reference is passed as a return
> value (not as a parameter)
> --
>
> Key: TUSCANY-2028
> URL: https://issues.apache.org/jira/browse/TUSCANY-2028
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
>Affects Versions: Java-SCA-1.0.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
>Reporter: Daniel Stucky
>Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
> Attachments: test.zip, test.zip
>
>
> I have 3 components: Alpha, Beta and Gamma, where Gamma's Interface is marked
> with @Conversational and @Scope("CONVERSATION"). I want Alpha to call a
> method on Beta that creates a conversation with Gamma and returns a reference
> to Gamma. Then I want to reuse that conversation to Gamma from Alpha.
> Therefore I let Alpha call method Beta.getRef(). Inside this method, a
> reference to Gamma is created via componentContext.getServiceReference() and
> the conversation is initialized by calling method Gamma.init(). Beta.getRef()
> returns a CallableReference. So far it works, but as soon as I call a
> method on that reference from within Alpha, a new Conversation is
> initialized, the Conversation created between Beta and Gamma is not reused.
> See the original post on the mailing list:
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200802.mbox/[EMAIL
> PROTECTED]
> And the answer by Simon Laws:
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200802.mbox/[EMAIL
> PROTECTED]
--
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-2028) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter)
[
https://issues.apache.org/jira/browse/TUSCANY-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stucky updated TUSCANY-2028:
---
Attachment: test.zip
Readded for test integration
> Conversation does not continue if a Service Reference is passed as a return
> value (not as a parameter)
> --
>
> Key: TUSCANY-2028
> URL: https://issues.apache.org/jira/browse/TUSCANY-2028
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
>Affects Versions: Java-SCA-1.0.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
>Reporter: Daniel Stucky
>Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
> Attachments: test.zip, test.zip
>
>
> I have 3 components: Alpha, Beta and Gamma, where Gamma's Interface is marked
> with @Conversational and @Scope("CONVERSATION"). I want Alpha to call a
> method on Beta that creates a conversation with Gamma and returns a reference
> to Gamma. Then I want to reuse that conversation to Gamma from Alpha.
> Therefore I let Alpha call method Beta.getRef(). Inside this method, a
> reference to Gamma is created via componentContext.getServiceReference() and
> the conversation is initialized by calling method Gamma.init(). Beta.getRef()
> returns a CallableReference. So far it works, but as soon as I call a
> method on that reference from within Alpha, a new Conversation is
> initialized, the Conversation created between Beta and Gamma is not reused.
> See the original post on the mailing list:
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200802.mbox/[EMAIL
> PROTECTED]
> And the answer by Simon Laws:
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200802.mbox/[EMAIL
> PROTECTED]
--
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-2028) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter)
[
https://issues.apache.org/jira/browse/TUSCANY-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stucky updated TUSCANY-2028:
---
Attachment: test.zip
This is a small eclipse project. Inside you find 3 Interfaces Alpha, Beta and
Gamma with their implementations and a Launcher.
Check the comments in AlphaImpl. They describe my expectations and the current
behaviour.
> Conversation does not continue if a Service Reference is passed as a return
> value (not as a parameter)
> --
>
> Key: TUSCANY-2028
> URL: https://issues.apache.org/jira/browse/TUSCANY-2028
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
>Affects Versions: Java-SCA-1.0.1
> Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
> 1.5.0_10
>Reporter: Daniel Stucky
> Attachments: test.zip
>
>
> I have 3 components: Alpha, Beta and Gamma, where Gamma's Interface is marked
> with @Conversational and @Scope("CONVERSATION"). I want Alpha to call a
> method on Beta that creates a conversation with Gamma and returns a reference
> to Gamma. Then I want to reuse that conversation to Gamma from Alpha.
> Therefore I let Alpha call method Beta.getRef(). Inside this method, a
> reference to Gamma is created via componentContext.getServiceReference() and
> the conversation is initialized by calling method Gamma.init(). Beta.getRef()
> returns a CallableReference. So far it works, but as soon as I call a
> method on that reference from within Alpha, a new Conversation is
> initialized, the Conversation created between Beta and Gamma is not reused.
> See the original post on the mailing list:
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200802.mbox/[EMAIL
> PROTECTED]
> And the answer by Simon Laws:
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200802.mbox/[EMAIL
> PROTECTED]
--
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-2028) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter)
Conversation does not continue if a Service Reference is passed as a return
value (not as a parameter)
--
Key: TUSCANY-2028
URL: https://issues.apache.org/jira/browse/TUSCANY-2028
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.0.1
Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk
1.5.0_10
Reporter: Daniel Stucky
I have 3 components: Alpha, Beta and Gamma, where Gamma's Interface is marked
with @Conversational and @Scope("CONVERSATION"). I want Alpha to call a method
on Beta that creates a conversation with Gamma and returns a reference to
Gamma. Then I want to reuse that conversation to Gamma from Alpha.
Therefore I let Alpha call method Beta.getRef(). Inside this method, a
reference to Gamma is created via componentContext.getServiceReference() and
the conversation is initialized by calling method Gamma.init(). Beta.getRef()
returns a CallableReference. So far it works, but as soon as I call a
method on that reference from within Alpha, a new Conversation is initialized,
the Conversation created between Beta and Gamma is not reused.
See the original post on the mailing list:
http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200802.mbox/[EMAIL
PROTECTED]
And the answer by Simon Laws:
http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200802.mbox/[EMAIL
PROTECTED]
--
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]
