[jira] Assigned: (TUSCANY-2391) Tuscany SCA support in the Geronimo Admin Console
[ https://issues.apache.org/jira/browse/TUSCANY-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2391: -- Assignee: ant elder Tuscany SCA support in the Geronimo Admin Console - Key: TUSCANY-2391 URL: https://issues.apache.org/jira/browse/TUSCANY-2391 Project: Tuscany Issue Type: New Feature Components: Java SCA Tools Reporter: Thilina Buddhika Assignee: ant elder Attachments: geronimo_ACE.zip This is the primary implementation of this Admin Console Extension. It does not contain any functionality related to Tuscany. But it is intended to use this as the basis for developing the ACE. The patch contains the source, and provides a maven build file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2391) Tuscany SCA support in the Geronimo Admin Console
[ https://issues.apache.org/jira/browse/TUSCANY-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12605074#action_12605074 ] ant elder commented on TUSCANY-2391: Patch applied to your sandbos area at: https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/thilina/geronimo_ACE/ It tried building and deploying to Geronimo 2.1.1 and it appears in the admin console and runs. Cool! Tuscany SCA support in the Geronimo Admin Console - Key: TUSCANY-2391 URL: https://issues.apache.org/jira/browse/TUSCANY-2391 Project: Tuscany Issue Type: New Feature Components: Java SCA Tools Reporter: Thilina Buddhika Assignee: ant elder Attachments: geronimo_ACE.zip This is the primary implementation of this Admin Console Extension. It does not contain any functionality related to Tuscany. But it is intended to use this as the basis for developing the ACE. The patch contains the source, and provides a maven build file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2274) @Scope vTest failing intermittently
[ https://issues.apache.org/jira/browse/TUSCANY-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2274. -- Resolution: Fixed Fixed in r667046 and r667049 but adding some synchronization clauses @Scope vTest failing intermittently Key: TUSCANY-2274 URL: https://issues.apache.org/jira/browse/TUSCANY-2274 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Fix For: Java-SCA-Next The atScope1 vTest fails intermittently like this: --- T E S T S --- Running org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase Setting up Apr 26, 2008 5:00:57 PM org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime buildComposite WARNING: Can't find monitor extension on the classpath GService-initGService atScope1 Exception in thread Thread-5 java.lang.IllegalArgumentException: Invalid phase name: component.implementation at org.apache.tuscany.sca.core.invocation.InvocationChainImpl.addInvoker(InvocationChainImpl.java:106) at org.apache.tuscany.sca.core.invocation.InvocationChainImpl.addInvoker(InvocationChainImpl.java:70) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:316) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:188) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChain(RuntimeWireImpl.java:115) at org.apache.tuscany.sca.core.assembly.RuntimeComponentServiceImpl.getInvocationChain(RuntimeComponentServiceImpl.java:120) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:232) ThreadB1-BService2 ThreadB2-BService9 at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:245) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBindingInterceptor(RuntimeWireImpl.java:228) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:167) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:243) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:148) at $Proxy17.setCurrentState(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase$CThread.run(ScopeAnnotationTestCase.java:359) Exception in thread Thread-4 org.osoa.sca.ServiceUnavailableException: Service not found for component CComponent reference $self$.CService (bi ndingURI=/CComponent operation=getName). Ensure that the composite containing the service is loaded and started somewhere in the SCA domain and t hat if running in a remote node that the interface of the target service marked as @Remotable at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:247) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBindingInterceptor(RuntimeWireImpl.java:228) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:167) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:243) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:148) at $Proxy17.setCurrentState(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase$CThread.run(ScopeAnnotationTestCase.java:359) atScope2 --- Still not clear if this is a runtime r test setup issue. I have added Ignore annotation until this is resolved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2243) ServiceRuntimeException due to NPE with ComponentContext.getService()
[ https://issues.apache.org/jira/browse/TUSCANY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2243. -- Resolution: Fixed It looks like the problem reported in the subject of this jira is now fixed and the remaining ignored test was incorrectly reporting a failure so i've corrected that ServiceRuntimeException due to NPE with ComponentContext.getService() - Key: TUSCANY-2243 URL: https://issues.apache.org/jira/browse/TUSCANY-2243 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Reporter: Yee-Kang Chang Assignee: ant elder Fix For: Java-SCA-Next Attachments: ComponentContextUpdatesJIRA2243.patch ComponentContext.getService() did not return the expected service when invoked. It works with a @Reference field is defined for the service in the Impl class but it failed without the annotation. The reference is defined in the SCDL. Section 1.4.1.1 of the specification says, When a component implementation needs access to a service where the reference to the service is not known at compile time, the reference can be located using the component's ComponentContext. So, this should work without @Reference defined. org.osoa.sca.ServiceRuntimeException: java.lang.NullPointerException at org.apache.tuscany.sca.core.context.ComponentContextImpl.getServiceReference(ComponentContextImpl.java:228) at org.apache.tuscany.sca.core.context.ComponentContextImpl.getServiceReference(ComponentContextImpl.java:110) at org.apache.tuscany.sca.core.context.ComponentContextImpl.getService(ComponentContextImpl.java:102) at org.apache.tuscany.sca.vtest.javaapi.apis.componentcontext.impl.AComponentImpl.testServiceLookup(AComponentImpl.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) 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 $Proxy7.testServiceLookup(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.apis.componentcontext.ComponentContextTestCase.testServiceLookup(ComponentContextTestCase.java:170) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.lang.NullPointerException at
[jira] Commented: (TUSCANY-2274) @Scope vTest failing intermittently
[ https://issues.apache.org/jira/browse/TUSCANY-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602993#action_12602993 ] ant elder commented on TUSCANY-2274: One interesting part of this is it rarely happens to me when I build just the individual module but often happens when I'm building everything from the top sca folder. Doesn't make it easy to debug :-( @Scope vTest failing intermittently Key: TUSCANY-2274 URL: https://issues.apache.org/jira/browse/TUSCANY-2274 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Fix For: Java-SCA-Next The atScope1 vTest fails intermittently like this: --- T E S T S --- Running org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase Setting up Apr 26, 2008 5:00:57 PM org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime buildComposite WARNING: Can't find monitor extension on the classpath GService-initGService atScope1 Exception in thread Thread-5 java.lang.IllegalArgumentException: Invalid phase name: component.implementation at org.apache.tuscany.sca.core.invocation.InvocationChainImpl.addInvoker(InvocationChainImpl.java:106) at org.apache.tuscany.sca.core.invocation.InvocationChainImpl.addInvoker(InvocationChainImpl.java:70) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:316) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:188) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChain(RuntimeWireImpl.java:115) at org.apache.tuscany.sca.core.assembly.RuntimeComponentServiceImpl.getInvocationChain(RuntimeComponentServiceImpl.java:120) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:232) ThreadB1-BService2 ThreadB2-BService9 at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:245) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBindingInterceptor(RuntimeWireImpl.java:228) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:167) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:243) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:148) at $Proxy17.setCurrentState(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase$CThread.run(ScopeAnnotationTestCase.java:359) Exception in thread Thread-4 org.osoa.sca.ServiceUnavailableException: Service not found for component CComponent reference $self$.CService (bi ndingURI=/CComponent operation=getName). Ensure that the composite containing the service is loaded and started somewhere in the SCA domain and t hat if running in a remote node that the interface of the target service marked as @Remotable at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:247) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addReferenceBindingInterceptor(RuntimeWireImpl.java:228) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:167) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:243) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:148) at $Proxy17.setCurrentState(Unknown Source) at org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase$CThread.run(ScopeAnnotationTestCase.java:359) atScope2 --- Still not clear if this is a runtime r test setup issue. I have added Ignore annotation until this is resolved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2369) sample-calculator-ws-webapp fails to deploy
[ https://issues.apache.org/jira/browse/TUSCANY-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2369. -- Resolution: Fixed Works fine today now when i try to debug it with a fresh build sample-calculator-ws-webapp fails to deploy --- Key: TUSCANY-2369 URL: https://issues.apache.org/jira/browse/TUSCANY-2369 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next sample-calculator-ws-webapp fails to deploy on Tomcat with the following: org.osoa.sca.ServiceRuntimeException: java.lang.reflect.InvocationTargetException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:276) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:83) at org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:218) at org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:52) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4356) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) 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.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 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.host.embedded.SCADomain.createNewInstance(SCADomain.java:258) ... 30 more Caused by: java.lang.NoSuchMethodError: org.apache.tuscany.sca.databinding.DataBinding.getXMLTypeHelperClass()Ljava/lang/Class; at org.apache.tuscany.sca.interfacedef.wsdl.interface2wsdl.Interface2WSDLGenerator.getElementInfo(Interface2WSDLGenerator.java:515) at org.apache.tuscany.sca.interfacedef.wsdl.interface2wsdl.Interface2WSDLGenerator.generateWrapperPart(Interface2WSDLGenerator.java:487) at org.apache.tuscany.sca.interfacedef.wsdl.interface2wsdl.Interface2WSDLGenerator.generateOperation(Interface2WSDLGenerator.java:383) at org.apache.tuscany.sca.interfacedef.wsdl.interface2wsdl.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:159) at org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl.Java2WSDLHelper.createWSDLInterfaceContract(Java2WSDLHelper.java:193) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ReferenceBindingProvider.init(Axis2ReferenceBindingProvider.java:68) at
[jira] Created: (TUSCANY-2369) sample-calculator-ws-webapp fails to deploy
sample-calculator-ws-webapp fails to deploy --- Key: TUSCANY-2369 URL: https://issues.apache.org/jira/browse/TUSCANY-2369 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next sample-calculator-ws-webapp fails to deploy on Tomcat with the following: org.osoa.sca.ServiceRuntimeException: java.lang.reflect.InvocationTargetException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:276) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:83) at org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:218) at org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:52) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4356) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:829) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:718) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) 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.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 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.host.embedded.SCADomain.createNewInstance(SCADomain.java:258) ... 30 more Caused by: java.lang.NoSuchMethodError: org.apache.tuscany.sca.databinding.DataBinding.getXMLTypeHelperClass()Ljava/lang/Class; at org.apache.tuscany.sca.interfacedef.wsdl.interface2wsdl.Interface2WSDLGenerator.getElementInfo(Interface2WSDLGenerator.java:515) at org.apache.tuscany.sca.interfacedef.wsdl.interface2wsdl.Interface2WSDLGenerator.generateWrapperPart(Interface2WSDLGenerator.java:487) at org.apache.tuscany.sca.interfacedef.wsdl.interface2wsdl.Interface2WSDLGenerator.generateOperation(Interface2WSDLGenerator.java:383) at org.apache.tuscany.sca.interfacedef.wsdl.interface2wsdl.Interface2WSDLGenerator.generate(Interface2WSDLGenerator.java:159) at org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl.Java2WSDLHelper.createWSDLInterfaceContract(Java2WSDLHelper.java:193) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ReferenceBindingProvider.init(Axis2ReferenceBindingProvider.java:68) at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:70) at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createReferenceBindingProvider(Axis2BindingProviderFactory.java:47)
[jira] Commented: (TUSCANY-2357) CORBA objects invocation mechanism
[ https://issues.apache.org/jira/browse/TUSCANY-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602249#action_12602249 ] ant elder commented on TUSCANY-2357: Applied license header patch in r663066, thanks for the patch! CORBA objects invocation mechanism -- Key: TUSCANY-2357 URL: https://issues.apache.org/jira/browse/TUSCANY-2357 Project: Tuscany Issue Type: New Feature Reporter: Wojtek Janiszewski Attachments: add-license-headers.patch.tar.gz, corba-operation-invoker.patch.tar.gz Implementation of generic mechanism for remote operation invocation: passing CORBA structures, sequences, primitives as arguments, retrieving return values (also structs, seq, prims.). There is no exception handling yet. It's not connected to CORBA binding extension yet - it won't be hard, and I think it's now more important to complete this generic mechanism. Some tests are provided - you need to have tnameserv in your PATH to run tests correctly! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2359) Rationalize the SCA runtime use of cglib and asm dependencies
Rationalize the SCA runtime use of cglib and asm dependencies - Key: TUSCANY-2359 URL: https://issues.apache.org/jira/browse/TUSCANY-2359 Project: Tuscany Issue Type: Improvement Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next The Tuscany runtime now has dependencies on both asm-all and cglib-nodep, these both do the same type of thing, and the -nodep version of cglib includes asm, so it would be nice to rationalize the use of these to just one dependency. Asm is used by interface-java-jaxws, cglib-nodep is used by CglibProxyFactory.java in the core module. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2357) CORBA objects invocation mechanism
[ https://issues.apache.org/jira/browse/TUSCANY-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601596#action_12601596 ] ant elder commented on TUSCANY-2357: Thanks Wojtek, patch applied. One comment, where possible the files in SVN should have the ASF license header you can see the format from existing files, eg its the following for Java files: /* * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership. The ASF licenses this file * to you under the Apache License, Version 2.0 (the * License); you may not use this file except in compliance * with the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, * software distributed under the License is distributed on an * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY * KIND, either express or implied. See the License for the * specific language governing permissions and limitations * under the License. */ CORBA objects invocation mechanism -- Key: TUSCANY-2357 URL: https://issues.apache.org/jira/browse/TUSCANY-2357 Project: Tuscany Issue Type: New Feature Reporter: Wojtek Janiszewski Attachments: corba-operation-invoker.patch.tar.gz Implementation of generic mechanism for remote operation invocation: passing CORBA structures, sequences, primitives as arguments, retrieving return values (also structs, seq, prims.). There is no exception handling yet. It's not connected to CORBA binding extension yet - it won't be hard, and I think it's now more important to complete this generic mechanism. Some tests are provided - you need to have tnameserv in your PATH to run tests correctly! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2291) Runtime does not detect illegal mix of local and remoteable on bidirectional interface
[ https://issues.apache.org/jira/browse/TUSCANY-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601556#action_12601556 ] ant elder commented on TUSCANY-2291: Fixed in r662367 but the vtest is still commented out because as an exception is thrown when this problem is detected that breaks all the other tests in this vtest module. The vtest could be changed to work like vtest-java-api-annotations-destroy to use SCANode2Factory to start individual composites but there's also work on going to use monitors and trapping exceptions so a validation error doesn't stop the domain startup so maybe thats the better fix Runtime does not detect illegal mix of local and remoteable on bidirectional interface -- Key: TUSCANY-2291 URL: https://issues.apache.org/jira/browse/TUSCANY-2291 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Priority: Minor Fix For: Java-SCA-Next From Lines 534, 535 of the Java API/Annotaitons spec: Callbacks may be used for both remotable and local services. Either both interfaces of a bidirectional service must be remotable, or both must be local. It is illegal to mix the two. The test org.apache.tuscany.sca.vtest.javaapi.conversation.callback.statefulCallback3 demonstrates this error and is currently @Ignore(d) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2296) SCADomain.newInstance() processes all composites in the contribution irrespective of the parameter passed
[ https://issues.apache.org/jira/browse/TUSCANY-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599081#action_12599081 ] ant elder commented on TUSCANY-2296: FYI, additional comments on the dev list: http://apache.markmail.org/message/dj72oxzhfdofouae SCADomain.newInstance() processes all composites in the contribution irrespective of the parameter passed - Key: TUSCANY-2296 URL: https://issues.apache.org/jira/browse/TUSCANY-2296 Project: Tuscany Issue Type: Bug Components: Java SCA Embedded Runtime Affects Versions: Java-SCA-1.2 Reporter: Vamsavardhana Reddy Fix For: Java-SCA-Next Attachments: TUSCANY-2296-recreate.patch I have two composites, namely proper.composite and error.composite, in my test project. proper.composite is used to test proper contribution without any errors whereas error.composite is used to test a problematic contribution. But when I initialize a domain using SCADomain. newInstance(proper.composite), I am getting an exception due to error.composite. Though it looks as if the call SCADomain. newInstance(proper.composite) processes only proper.composite, in reality it is processing all the .composite files present in the project irrespective of the parameter passed to SCADomain.newInstance(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2304) SCA client Hang Forver after getting handled exception from service
[ https://issues.apache.org/jira/browse/TUSCANY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-2304: --- Fix Version/s: (was: Java-SCA-Next) Java-SCA-1.2.1 SCA client Hang Forver after getting handled exception from service --- Key: TUSCANY-2304 URL: https://issues.apache.org/jira/browse/TUSCANY-2304 Project: Tuscany Issue Type: Bug Components: Java SCA Embedded Runtime Affects Versions: Java-SCA-1.2 Environment: Tuscnay SCA 1.2 Reporter: Nishant Joshi Priority: Blocker Fix For: Java-SCA-1.2.1 Attachments: Client_Service.zip, tuscany-binding-ws-axis2-1.2-incubating.jar, tuscany-sca-all-1.2-incubating.jar Hi there, The problem here from SCA client is blocking me to go further. Here i m also attaching my client and service to give you idea. Here from service i m throwing exception and handled them into my exception class. Now on client side after getting two exception from service it was hang and not proceed further. I have also tested with diff. sequence of call and behavior i noticed is after getting total 2 exception from service my SCA client hangs forever. Its a very interesting scenario for me. please let me know if any body has faced same. By investigating my sample i guess many of us may face same problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2320) The contextPath init parameter for TuscanyServletFilter.
[ https://issues.apache.org/jira/browse/TUSCANY-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597712#action_12597712 ] ant elder commented on TUSCANY-2320: Sure okhow about a patch to fix it too :-) The contextPath init parameter for TuscanyServletFilter. Key: TUSCANY-2320 URL: https://issues.apache.org/jira/browse/TUSCANY-2320 Project: Tuscany Issue Type: Bug Components: Java SCA Web App Integration Affects Versions: Java-SCA-1.2 Reporter: Ilya Kanonirov Assignee: ant elder Attachments: tuscany-host-webapp-1.2-TUSCANY-2320.jar Current version of the component requires the contextPath initialization parameter to be specified in the Servlet Context, i.e. we need the following context-param in web.xml: web-app ... context-param param-namecontextPath/param-name param-value/ctx/param-value /context-param ... /webapp while the previous Java SCA 1.1 required that parameter at the filter description level: web-app ... filter filter-nametuscany/filter-name filter-classorg.apache.tuscany.sca.host.webapp.TuscanyServletFilter/filter-class init-param param-namecontextPath/param-name param-value/ctx/param-value /init-param /filter ... /webapp Is that parameter supposed to be there, defined at the Servlet Context level? If yes, I would suggest renaming the parameter to avoid confusing. For example, adding a package prefix might be enough. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2320) The contextPath init parameter for TuscanyServletFilter.
[ https://issues.apache.org/jira/browse/TUSCANY-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-2320: --- Fix Version/s: Java-SCA-1.2.1 The contextPath init parameter for TuscanyServletFilter. Key: TUSCANY-2320 URL: https://issues.apache.org/jira/browse/TUSCANY-2320 Project: Tuscany Issue Type: Bug Components: Java SCA Web App Integration Affects Versions: Java-SCA-1.2 Reporter: Ilya Kanonirov Assignee: ant elder Fix For: Java-SCA-1.2.1 Attachments: tuscany-host-webapp-1.2-TUSCANY-2320.jar Current version of the component requires the contextPath initialization parameter to be specified in the Servlet Context, i.e. we need the following context-param in web.xml: web-app ... context-param param-namecontextPath/param-name param-value/ctx/param-value /context-param ... /webapp while the previous Java SCA 1.1 required that parameter at the filter description level: web-app ... filter filter-nametuscany/filter-name filter-classorg.apache.tuscany.sca.host.webapp.TuscanyServletFilter/filter-class init-param param-namecontextPath/param-name param-value/ctx/param-value /init-param /filter ... /webapp Is that parameter supposed to be there, defined at the Servlet Context level? If yes, I would suggest renaming the parameter to avoid confusing. For example, adding a package prefix might be enough. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-1867) @OneWay with String return type causes NullPointerException
[ https://issues.apache.org/jira/browse/TUSCANY-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-1867. -- Resolution: Fixed Patch 2 applied, thanks for the fix! @OneWay with String return type causes NullPointerException --- Key: TUSCANY-1867 URL: https://issues.apache.org/jira/browse/TUSCANY-1867 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.0 Environment: Windows XP Reporter: Simon Nash Assignee: ant elder Fix For: Java-SCA-Next Attachments: TUSCANY-1867-2.patch, TUSCANY-1867.patch I tried using @OneWay on a method with a String return type and I got a NullPointerException, like this: Exception in thread Axis2 Task java.lang.NullPointerException at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:444) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) We should produce a better exception to tell the user what he/she has done wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2252) Remove exception declaration from SCANodeManagerService Interface
[ https://issues.apache.org/jira/browse/TUSCANY-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2252. -- Resolution: Fixed Superseded and fixed by TUSCANY-1867 Remove exception declaration from SCANodeManagerService Interface - Key: TUSCANY-2252 URL: https://issues.apache.org/jira/browse/TUSCANY-2252 Project: Tuscany Issue Type: Bug Components: Java SCA Domain Management Affects Versions: Java-SCA-Next Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2252.patch org.apache.tuscany.sca.node.NodeException: org.apache.tuscany.sca.interfacedef.InvalidOperationException: Method should not declare exceptions with an @OneWay annotation. at org.apache.tuscany.sca.node.impl.SCANodeImpl.init(SCANodeImpl.java:222) at org.apache.tuscany.sca.node.impl.SCANodeImpl.init(SCANodeImpl.java:128) at org.apache.tuscany.sca.node.impl.SCANodeFactoryImpl.createSCANode(SCANodeFactoryImpl.java:54) at org.apache.tuscany.sca.node.impl.NodeDrivenTestCase.init(NodeDrivenTestCase.java:72) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod(BeforeAndAfterRunner.java:74) at org.junit.internal.runners.BeforeAndAfterRunner.runBefores(BeforeAndAfterRunner.java:50) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:33) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) DomainDrivenTestCase fails with the above exception as we have a destroyNode() method in org.apache.tuscany.sca.node.management.SCANodeManagerService.java interface with @OneWay annotation, but declared to throw NodeException. As per the specs, Any method that returns void and has no declared exceptions may be marked with an @OneWay annotation. I am raising this JIRA to fix this issue by making the destroyNode() method not to throw any exception. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2320) The contextPath init parameter for TuscanyServletFilter.
[ https://issues.apache.org/jira/browse/TUSCANY-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2320: -- Assignee: ant elder The contextPath init parameter for TuscanyServletFilter. Key: TUSCANY-2320 URL: https://issues.apache.org/jira/browse/TUSCANY-2320 Project: Tuscany Issue Type: Improvement Components: Java SCA Web App Integration Affects Versions: Java-SCA-1.2 Reporter: Ilya Kanonirov Assignee: ant elder Current version of the component requires the contextPath initialization parameter to be specified in the Servlet Context, i.e. we need the following context-param in web.xml: web-app ... context-param param-namecontextPath/param-name param-value/ctx/param-value /context-param ... /webapp while the previous Java SCA 1.1 required that parameter at the filter description level: web-app ... filter filter-nametuscany/filter-name filter-classorg.apache.tuscany.sca.host.webapp.TuscanyServletFilter/filter-class init-param param-namecontextPath/param-name param-value/ctx/param-value /init-param /filter ... /webapp Is that parameter supposed to be there, defined at the Servlet Context level? If yes, I would suggest renaming the parameter to avoid confusing. For example, adding a package prefix might be enough. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2320) The contextPath init parameter for TuscanyServletFilter.
[
https://issues.apache.org/jira/browse/TUSCANY-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-2320:
---
Attachment: tuscany-host-webapp-1.2-TUSCANY-2320.jar
Thanks for finding this, it looks like a couple of conflicting changes combined
to lead to the change in behaviour. I've attached a patched jar -
tuscany-host-webapp-1.2-TUSCANY-2320.jar - to this JIRA, which restores the
behaviour to how it worked in 1.1. Could you try this out to see if it resolves
the problem ok for you?
The diff for the changes in that jar are:
Index: src/main/java/org/apache/tuscany/sca/host/webapp/WebAppServletHost.java
===
--- src/main/java/org/apache/tuscany/sca/host/webapp/WebAppServletHost.java
(revision 656535)
+++ src/main/java/org/apache/tuscany/sca/host/webapp/WebAppServletHost.java
(working copy)
@@ -26,6 +26,7 @@
import java.net.URI;
import java.net.URL;
import java.net.UnknownHostException;
+import java.util.Collections;
import java.util.HashMap;
import java.util.Map;
import java.util.logging.Logger;
@@ -206,7 +207,7 @@
public void init(ServletConfig config) throws ServletException {
ServletContext servletContext = config.getServletContext();
-initContextPath(servletContext);
+initContextPath(config);
if (servletContext.getAttribute(SCA_DOMAIN_ATTRIBUTE) == null) {
String domainURI = http://localhost/; + contextPath;
@@ -266,19 +267,20 @@
* containers use an init parameter.
*/
@SuppressWarnings(unchecked)
-public void initContextPath(ServletContext context) {
-// The getContextPath() is introduced since Servlet 2.5
-Method m;
-try {
-// Try to get the method anyway since some ServletContext impl has
this method even before 2.5
-m = context.getClass().getMethod(getContextPath, new Class[] {});
-contextPath = (String)m.invoke(context, new Object[] {});
-} catch (Exception e) {
-contextPath = context.getInitParameter(contextPath);
-if (contextPath == null) {
+public void initContextPath(ServletConfig config) {
+
+if
(Collections.list(config.getInitParameterNames()).contains(contextPath)) {
+contextPath = config.getInitParameter(contextPath);
+} else {
+// The getContextPath() is introduced since Servlet 2.5
+ServletContext context = config.getServletContext();
+try {
+// Try to get the method anyway since some ServletContext impl
has this method even before 2.5
+Method m = context.getClass().getMethod(getContextPath, new
Class[] {});
+contextPath = (String)m.invoke(context, new Object[] {});
+} catch (Exception e) {
logger.warning(Servlet level is: +
context.getMajorVersion() + . + context.getMinorVersion());
-throw new IllegalStateException(
-'contextPath' init parameter
must be set for pre-2.5 servlet container);
+throw new IllegalStateException('contextPath' init parameter
must be set for pre-2.5 servlet container);
}
}
The contextPath init parameter for TuscanyServletFilter.
Key: TUSCANY-2320
URL: https://issues.apache.org/jira/browse/TUSCANY-2320
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Web App Integration
Affects Versions: Java-SCA-1.2
Reporter: Ilya Kanonirov
Assignee: ant elder
Attachments: tuscany-host-webapp-1.2-TUSCANY-2320.jar
Current version of the component requires the contextPath initialization
parameter to be specified in the Servlet Context, i.e. we need the following
context-param in web.xml:
web-app
...
context-param
param-namecontextPath/param-name
param-value/ctx/param-value
/context-param
...
/webapp
while the previous Java SCA 1.1 required that parameter at the filter
description level:
web-app
...
filter
filter-nametuscany/filter-name
filter-classorg.apache.tuscany.sca.host.webapp.TuscanyServletFilter/filter-class
init-param
param-namecontextPath/param-name
param-value/ctx/param-value
/init-param
/filter
...
/webapp
Is that parameter supposed to be there, defined at the Servlet Context level?
If yes, I would suggest renaming the parameter to avoid confusing. For
example, adding a package prefix might be enough.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2129) Rename DistributedSCABinding.setSCABinging() to setSCABinding()
[ https://issues.apache.org/jira/browse/TUSCANY-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2129: -- Assignee: ant elder Rename DistributedSCABinding.setSCABinging() to setSCABinding() --- Key: TUSCANY-2129 URL: https://issues.apache.org/jira/browse/TUSCANY-2129 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Vamsavardhana Reddy Assignee: ant elder Priority: Trivial Fix For: Java-SCA-Next Attachments: TUSCANY-2129.patch Rename setSCABinging() to setSCABinding() in DistributedSCABinding. It is no big deal, but, still!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-1867) @OneWay with String return type causes NullPointerException
[ https://issues.apache.org/jira/browse/TUSCANY-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-1867. -- Resolution: Fixed Patch applied in r656190, thanks for the fix @OneWay with String return type causes NullPointerException --- Key: TUSCANY-1867 URL: https://issues.apache.org/jira/browse/TUSCANY-1867 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.0 Environment: Windows XP Reporter: Simon Nash Assignee: ant elder Fix For: Java-SCA-Next Attachments: TUSCANY-1867.patch I tried using @OneWay on a method with a String return type and I got a NullPointerException, like this: Exception in thread Axis2 Task java.lang.NullPointerException at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:444) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) We should produce a better exception to tell the user what he/she has done wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2279) itest/osgi-tuscany broken (policy-ws missing)
[ https://issues.apache.org/jira/browse/TUSCANY-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2279. -- Resolution: Fixed Was applied a while back now, thanks for the fix itest/osgi-tuscany broken (policy-ws missing) - Key: TUSCANY-2279 URL: https://issues.apache.org/jira/browse/TUSCANY-2279 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Affects Versions: Java-SCA-Next Environment: All Reporter: Graham Charters Priority: Minor Fix For: Java-SCA-Next Attachments: Jira-2279-policy-ws-missing.patch Original Estimate: 0.5h Remaining Estimate: 0.5h Looks like there's a new policy-ws module which has not been added to itest/osgi-tuscany so the dependency is missing, which results in the package not being available. I have a fix which I will attach shortly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-1867) @OneWay with String return type causes NullPointerException
[ https://issues.apache.org/jira/browse/TUSCANY-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-1867: -- Assignee: ant elder (was: Ramkumar Ramalingam) @OneWay with String return type causes NullPointerException --- Key: TUSCANY-1867 URL: https://issues.apache.org/jira/browse/TUSCANY-1867 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.0 Environment: Windows XP Reporter: Simon Nash Assignee: ant elder Fix For: Java-SCA-Next Attachments: TUSCANY-1867.patch I tried using @OneWay on a method with a String return type and I got a NullPointerException, like this: Exception in thread Axis2 Task java.lang.NullPointerException at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:444) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) We should produce a better exception to tell the user what he/she has done wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2285) Make sca-api automatically build as an OSGi bundle
[ https://issues.apache.org/jira/browse/TUSCANY-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2285. -- Resolution: Fixed Closing as this has been done now Make sca-api automatically build as an OSGi bundle -- Key: TUSCANY-2285 URL: https://issues.apache.org/jira/browse/TUSCANY-2285 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime, Java SCA OSGi Integration Affects Versions: Java-SCA-Next Environment: All Reporter: Graham Charters Priority: Minor Fix For: Java-SCA-Next Attachments: sca-api-bundle-2.patch, sca-api-bundle.patch Original Estimate: 0.5h Remaining Estimate: 0.5h Itest/osgi-tuscany creates an OSGi bundle for the sca-api module. As a step towards providing better support for OSGi, it has been suggested on the dev-list that we simply make sca-api automatically build as an OSGi bundle. This does not preclude it being used as a normal jar. I have a patch which I will attached shortly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2093) Hangs in osgi itests
[ https://issues.apache.org/jira/browse/TUSCANY-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2093. -- Resolution: Fixed closing as all resolved now Hangs in osgi itests Key: TUSCANY-2093 URL: https://issues.apache.org/jira/browse/TUSCANY-2093 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next I get hangs running various of the osgi itests, the test run part way through then just appear to hang for ever, no IO or CPU activity on the process. Eg, the output on the console for some hangs are: Running org.apache.tuscany.sca.test.osgi.tuscany.OSGiSupplyChainTestCase - Run tests from : ../../../samples/osgi-supplychain Loaded Tuscany, time taken = 31625 ms Running test null(supplychain.SupplyChainClientTestCase) Started OSGi bundle with activator OSGiCustomerImpl Started OSGi bundle with activator OSGiShipperImpl another: [INFO] Building Apache Tuscany OSGi Contribution tests [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 1 source file to C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 4 source files to C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\surefire-reports --- T E S T S --- Running org.apache.tuscany.sca.contribution.osgi.test.OSGiResolverTestCase - Created supplychain.customer.JavaCustomerComponentImpl using classloader 6.0 Created supplychain.retailer.JavaRetailerComponentImpl using classloader 7.0 Created supplychain.warehouse.JavaWarehouseComponentImpl using classloader 8.0 Created supplychain.shipper.JavaShipperComponentImpl using classloader 9.0 another: Running supplychain.wiring.DSWiring1TestCase - Main thread Thread[main,5,main] Created OSGiCustomerComponentImpl [EMAIL PROTECTED] Activated OSGiCustomerComponentImpl bundle OSGiCustomerComponentImpl.purchaseBooks, retailer1 is [Proxy - [EMAIL PROTECTED] Activated OSGiRetailerComponentImpl bundle Activated OSGiRetailerComponentImpl bundle OSGiRetailerComponentImpl.submitOrder , warehouse is [Proxy - [EMAIL PROTECTED] JavaWarehouseComponentImpl.fulfillOrder : shipper is [Proxy - [EMAIL PROTECTED] Activated OSGiShipperComponentImpl bundle Activated OSGiShipperComponentImpl bundle OSGiShipperComponentImpl.processShipment, customer is [Proxy - [EMAIL PROTECTED] This is easily recreateable so i can help debug, just right now i'm not sure where to look. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2097) Build errors in itest/osgi-tuscany
[ https://issues.apache.org/jira/browse/TUSCANY-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2097. -- Resolution: Fixed Closing as this is all resolved now Build errors in itest/osgi-tuscany -- Key: TUSCANY-2097 URL: https://issues.apache.org/jira/browse/TUSCANY-2097 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Affects Versions: Java-SCA-Next Environment: Windows, Sun JDK 1.5.0_14 Reporter: Simon Nash Fix For: Java-SCA-Next Attachments: jira2097.log Here is a summary of the build errors I am seeing. I will attach my full build log to this JIRA. 1. revision.location error creating archive. This seems to show up on every test, and it does not seem to cause a hard failure in the test. java.io.FileNotFoundException: F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany- test\.felix.test\bundle1\version0.0\revision.location (The system cannot find th e file specified) ERROR: org.apache.felix.framework.cache.BundleCache: Error creating archive. (ja va.io.FileNotFoundException: F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany-te st\.felix.test\bundle1\version0.0\revision.location (The system cannot find the file specified)) 2. InvocationTargetException in CalculatorRMIReferencetestCase. java.lang.reflect.InvocationTargetException . Caused by: java.rmi.server.ExportException: Port already in use: 8099; nested ex ception is: java.net.BindException: Address already in use: JVM_Bind 3. Various errors in testOSGiTuscany_BindingWS - ERROR: org.apache.felix.framework.cache.BundleArchive: Unable to delete archi ve directory - F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany-test\.felix.test \bundle5 java.util.zip.ZipException: The system cannot find the file specified org.osgi.framework.BundleException: Could not create bundle object. . Caused by: java.util.zip.ZipException: The system cannot find the file specified -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2129) Rename DistributedSCABinding.setSCABinging() to setSCABinding()
[ https://issues.apache.org/jira/browse/TUSCANY-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2129. -- Resolution: Fixed Applied in r656171 Rename DistributedSCABinding.setSCABinging() to setSCABinding() --- Key: TUSCANY-2129 URL: https://issues.apache.org/jira/browse/TUSCANY-2129 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Vamsavardhana Reddy Assignee: ant elder Priority: Trivial Fix For: Java-SCA-Next Attachments: TUSCANY-2129.patch Rename setSCABinging() to setSCABinding() in DistributedSCABinding. It is no big deal, but, still!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2304) SCA client Hang Forver after getting handled exception from service
[ https://issues.apache.org/jira/browse/TUSCANY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596029#action_12596029 ] ant elder commented on TUSCANY-2304: The problem is that when the Axis2BindingInvoker.invokeTarget receives an exception response from the remote service it does not call operationClient.complete so the outgoing connection is not freed up and as we have HttpClient setDefaultMaxConnectionsPerHost set to 2 after two exceptions are received all the connections are used up so subsequent requests hang. SCA client Hang Forver after getting handled exception from service --- Key: TUSCANY-2304 URL: https://issues.apache.org/jira/browse/TUSCANY-2304 Project: Tuscany Issue Type: Bug Components: Java SCA Embedded Runtime Affects Versions: Java-SCA-1.2 Environment: Tuscnay SCA 1.2 Reporter: Nishant Joshi Priority: Blocker Fix For: Java-SCA-Next Attachments: Client_Service.zip Hi there, The problem here from SCA client is blocking me to go further. Here i m also attaching my client and service to give you idea. Here from service i m throwing exception and handled them into my exception class. Now on client side after getting two exception from service it was hang and not proceed further. I have also tested with diff. sequence of call and behavior i noticed is after getting total 2 exception from service my SCA client hangs forever. Its a very interesting scenario for me. please let me know if any body has faced same. By investigating my sample i guess many of us may face same problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2304) SCA client Hang Forver after getting handled exception from service
[ https://issues.apache.org/jira/browse/TUSCANY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596031#action_12596031 ] ant elder commented on TUSCANY-2304: I've committed a fix for this in r655464, can you try this out on the trunk code or can I give you a built jar to try out to check it fixes the issue for you? SCA client Hang Forver after getting handled exception from service --- Key: TUSCANY-2304 URL: https://issues.apache.org/jira/browse/TUSCANY-2304 Project: Tuscany Issue Type: Bug Components: Java SCA Embedded Runtime Affects Versions: Java-SCA-1.2 Environment: Tuscnay SCA 1.2 Reporter: Nishant Joshi Priority: Blocker Fix For: Java-SCA-Next Attachments: Client_Service.zip Hi there, The problem here from SCA client is blocking me to go further. Here i m also attaching my client and service to give you idea. Here from service i m throwing exception and handled them into my exception class. Now on client side after getting two exception from service it was hang and not proceed further. I have also tested with diff. sequence of call and behavior i noticed is after getting total 2 exception from service my SCA client hangs forever. Its a very interesting scenario for me. please let me know if any body has faced same. By investigating my sample i guess many of us may face same problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2304) SCA client Hang Forver after getting handled exception from service
[ https://issues.apache.org/jira/browse/TUSCANY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596035#action_12596035 ] ant elder commented on TUSCANY-2304: Ok, which release do you need the jar to be based on and do you use the tuscany-sca-all jar or the tuscany-binding-ws-axis2 jar? SCA client Hang Forver after getting handled exception from service --- Key: TUSCANY-2304 URL: https://issues.apache.org/jira/browse/TUSCANY-2304 Project: Tuscany Issue Type: Bug Components: Java SCA Embedded Runtime Affects Versions: Java-SCA-1.2 Environment: Tuscnay SCA 1.2 Reporter: Nishant Joshi Priority: Blocker Fix For: Java-SCA-Next Attachments: Client_Service.zip Hi there, The problem here from SCA client is blocking me to go further. Here i m also attaching my client and service to give you idea. Here from service i m throwing exception and handled them into my exception class. Now on client side after getting two exception from service it was hang and not proceed further. I have also tested with diff. sequence of call and behavior i noticed is after getting total 2 exception from service my SCA client hangs forever. Its a very interesting scenario for me. please let me know if any body has faced same. By investigating my sample i guess many of us may face same problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2304) SCA client Hang Forver after getting handled exception from service
[
https://issues.apache.org/jira/browse/TUSCANY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-2304:
---
Attachment: tuscany-binding-ws-axis2-1.2-incubating.jar
I've attached a patch binding-ws-axis2 jar to the JIRA, the change in there is
the following:
Index:
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
===
---
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
(revision 655474)
+++
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
(working copy)
@@ -109,9 +109,10 @@
protected Object invokeTarget(Message msg) throws AxisFault {
OperationClient operationClient = createOperationClient(msg);
-
// ensure connections are tracked so that they can be closed by the
reference binding
MessageContext requestMC =
operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
+try {
+
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
requestMC.getOptions().setTimeOutInMilliSeconds(12L);
@@ -128,9 +129,11 @@
response.build();
}
+return response;
+
+} finally {
operationClient.complete(requestMC);
-
-return response;
+}
}
@SuppressWarnings(deprecation)
SCA client Hang Forver after getting handled exception from service
---
Key: TUSCANY-2304
URL: https://issues.apache.org/jira/browse/TUSCANY-2304
Project: Tuscany
Issue Type: Bug
Components: Java SCA Embedded Runtime
Affects Versions: Java-SCA-1.2
Environment: Tuscnay SCA 1.2
Reporter: Nishant Joshi
Priority: Blocker
Fix For: Java-SCA-Next
Attachments: Client_Service.zip,
tuscany-binding-ws-axis2-1.2-incubating.jar
Hi there,
The problem here from SCA client is blocking me to go further.
Here i m also attaching my client and service to give you idea.
Here from service i m throwing exception and handled them into my exception
class.
Now on client side after getting two exception from service it was hang and
not proceed further.
I have also tested with diff. sequence of call and behavior i noticed is
after getting total 2 exception from service my SCA client hangs forever.
Its a very interesting scenario for me. please let me know if any body has
faced same.
By investigating my sample i guess many of us may face same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2304) SCA client Hang Forver after getting handled exception from service
[ https://issues.apache.org/jira/browse/TUSCANY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-2304: --- Attachment: tuscany-sca-all-1.2-incubating.jar Its the client side that needs this fix and it sounds like you are using the tuscany-sca-all jar on the client side so here's a patched version of that atached to the jira SCA client Hang Forver after getting handled exception from service --- Key: TUSCANY-2304 URL: https://issues.apache.org/jira/browse/TUSCANY-2304 Project: Tuscany Issue Type: Bug Components: Java SCA Embedded Runtime Affects Versions: Java-SCA-1.2 Environment: Tuscnay SCA 1.2 Reporter: Nishant Joshi Priority: Blocker Fix For: Java-SCA-Next Attachments: Client_Service.zip, tuscany-binding-ws-axis2-1.2-incubating.jar, tuscany-sca-all-1.2-incubating.jar Hi there, The problem here from SCA client is blocking me to go further. Here i m also attaching my client and service to give you idea. Here from service i m throwing exception and handled them into my exception class. Now on client side after getting two exception from service it was hang and not proceed further. I have also tested with diff. sequence of call and behavior i noticed is after getting total 2 exception from service my SCA client hangs forever. Its a very interesting scenario for me. please let me know if any body has faced same. By investigating my sample i guess many of us may face same problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2310) Incorrect Endpoint URI Resoultion in binding.ws when relative URIs are specified in wsa:Address in EndpointReference
[ https://issues.apache.org/jira/browse/TUSCANY-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2310. -- Resolution: Fixed Applied in r655286 Incorrect Endpoint URI Resoultion in binding.ws when relative URIs are specified in wsa:Address in EndpointReference Key: TUSCANY-2310 URL: https://issues.apache.org/jira/browse/TUSCANY-2310 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.2 Reporter: Vamsavardhana Reddy Assignee: ant elder Fix For: Java-SCA-Next Attachments: TUSCANY-2310.patch Web Service Binding Specification v1.00 - Sec 2.1.1 - Lines 70 to 85: 70 2.1.1 Endpoint URI resolution 71 The rules for resolving the URI at which an SCA service is hosted, or SCA reference targets, 72 when used with binding.ws (in precedence order) are: 73 1. The URIs in the endpoint(s) of the referenced WSDL 74 or 75 The URI specified by the wsa:Address element of the wsa:EndpointReference, 76 2. The explicitly stated URI in the uri attribute of the binding.ws element, which may be 77 relative, 78 3. The implicit URI as defined by the Assembly specification 79 The URI in the WSDL endpoint or in the wsa:Address of an EPR may be a relative URI, in which 80 case it is relative to the URI defined in (2) or (3). The wsa:Address element can be the empty 81 relative URI, in which case it uses the URI defined in (2) or (3) directly. This allows the EPR 82 writer to specify reference parameters, metadata and other EPR contents while allowing the URI 83 to be chosen by the deployer. -- I am using a URI http://localhost:8080/AService; on binding.ws element. With this in place, Issue 1: When I use an empty wsa:Address element, the Endpoint URI resolved should be http://localhost:8080/AService; whereas it is resolved to http://localhost:8080/;. Issue 2: When I use a relative uri of inAddress in wsa:Address element, the Endpoint URI resolved should be http://localhost:8080/AService/inAddress; whereas it is resolved to http://localhost:8080/inAddress;. The bottom line is that the Endpoint URI resolution is not correct when relative URI's is used in wsa:Address of an EPR. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2310) Incorrect Endpoint URI Resoultion in binding.ws when relative URIs are specified in wsa:Address in EndpointReference
[ https://issues.apache.org/jira/browse/TUSCANY-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2310: -- Assignee: ant elder Incorrect Endpoint URI Resoultion in binding.ws when relative URIs are specified in wsa:Address in EndpointReference Key: TUSCANY-2310 URL: https://issues.apache.org/jira/browse/TUSCANY-2310 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.2 Reporter: Vamsavardhana Reddy Assignee: ant elder Fix For: Java-SCA-Next Attachments: TUSCANY-2310.patch Web Service Binding Specification v1.00 - Sec 2.1.1 - Lines 70 to 85: 70 2.1.1 Endpoint URI resolution 71 The rules for resolving the URI at which an SCA service is hosted, or SCA reference targets, 72 when used with binding.ws (in precedence order) are: 73 1. The URIs in the endpoint(s) of the referenced WSDL 74 or 75 The URI specified by the wsa:Address element of the wsa:EndpointReference, 76 2. The explicitly stated URI in the uri attribute of the binding.ws element, which may be 77 relative, 78 3. The implicit URI as defined by the Assembly specification 79 The URI in the WSDL endpoint or in the wsa:Address of an EPR may be a relative URI, in which 80 case it is relative to the URI defined in (2) or (3). The wsa:Address element can be the empty 81 relative URI, in which case it uses the URI defined in (2) or (3) directly. This allows the EPR 82 writer to specify reference parameters, metadata and other EPR contents while allowing the URI 83 to be chosen by the deployer. -- I am using a URI http://localhost:8080/AService; on binding.ws element. With this in place, Issue 1: When I use an empty wsa:Address element, the Endpoint URI resolved should be http://localhost:8080/AService; whereas it is resolved to http://localhost:8080/;. Issue 2: When I use a relative uri of inAddress in wsa:Address element, the Endpoint URI resolved should be http://localhost:8080/AService/inAddress; whereas it is resolved to http://localhost:8080/inAddress;. The bottom line is that the Endpoint URI resolution is not correct when relative URI's is used in wsa:Address of an EPR. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2309) vtest for Endpoint URI resolution in binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2309. -- Resolution: Fixed Applied in 655288 vtest for Endpoint URI resolution in binding.ws - Key: TUSCANY-2309 URL: https://issues.apache.org/jira/browse/TUSCANY-2309 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-1.2 Reporter: Vamsavardhana Reddy Assignee: ant elder Fix For: Java-SCA-Next Attachments: TUSCANY-2309-new.patch, TUSCANY-2309.patch Web Service Binding Specification v1.00 - Section 2.1.1 - Lines 70 to 85: 70 2.1.1 Endpoint URI resolution 71 The rules for resolving the URI at which an SCA service is hosted, or SCA reference targets, 72 when used with binding.ws (in precedence order) are: 73 1. The URIs in the endpoint(s) of the referenced WSDL 74 or 75 The URI specified by the wsa:Address element of the wsa:EndpointReference, 76 2. The explicitly stated URI in the uri attribute of the binding.ws element, which may be 77 relative, 78 3. The implicit URI as defined by the Assembly specification 79 The URI in the WSDL endpoint or in the wsa:Address of an EPR may be a relative URI, in which 80 case it is relative to the URI defined in (2) or (3). The wsa:Address element can be the empty 81 relative URI, in which case it uses the URI defined in (2) or (3) directly. This allows the EPR 82 writer to specify reference parameters, metadata and other EPR contents while allowing the URI 83 to be chosen by the deployer. 84 To reference a WSDL document and also specify an EPR, the wsdlElement attribute must refer to 85 a binding element in the WSDL and not an endpoint or service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2309) vtest for Endpoint URI resolution in binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2309: -- Assignee: ant elder vtest for Endpoint URI resolution in binding.ws - Key: TUSCANY-2309 URL: https://issues.apache.org/jira/browse/TUSCANY-2309 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-1.2 Reporter: Vamsavardhana Reddy Assignee: ant elder Fix For: Java-SCA-Next Attachments: TUSCANY-2309-new.patch, TUSCANY-2309.patch Web Service Binding Specification v1.00 - Section 2.1.1 - Lines 70 to 85: 70 2.1.1 Endpoint URI resolution 71 The rules for resolving the URI at which an SCA service is hosted, or SCA reference targets, 72 when used with binding.ws (in precedence order) are: 73 1. The URIs in the endpoint(s) of the referenced WSDL 74 or 75 The URI specified by the wsa:Address element of the wsa:EndpointReference, 76 2. The explicitly stated URI in the uri attribute of the binding.ws element, which may be 77 relative, 78 3. The implicit URI as defined by the Assembly specification 79 The URI in the WSDL endpoint or in the wsa:Address of an EPR may be a relative URI, in which 80 case it is relative to the URI defined in (2) or (3). The wsa:Address element can be the empty 81 relative URI, in which case it uses the URI defined in (2) or (3) directly. This allows the EPR 82 writer to specify reference parameters, metadata and other EPR contents while allowing the URI 83 to be chosen by the deployer. 84 To reference a WSDL document and also specify an EPR, the wsdlElement attribute must refer to 85 a binding element in the WSDL and not an endpoint or service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2308) Reference annotation vtest for required=false
[ https://issues.apache.org/jira/browse/TUSCANY-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2308. -- Resolution: Fixed Applied in r655019, thanks for the code. Reference annotation vtest for required=false - Key: TUSCANY-2308 URL: https://issues.apache.org/jira/browse/TUSCANY-2308 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Priority: Minor Attachments: T2308.vtest.patch @Reference(required=false) and component does not define reference for it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2282) Poor warning issued when annotating private field with @Callback
[ https://issues.apache.org/jira/browse/TUSCANY-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2282: -- Assignee: ant elder Poor warning issued when annotating private field with @Callback Key: TUSCANY-2282 URL: https://issues.apache.org/jira/browse/TUSCANY-2282 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Assignee: ant elder Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2282.patch I inadvertently marked a private field with @Callback and received the following warning: WARNING: Invalid annotation @org.osoa.sca.annotations.Callback(value=class java.lang.Void) is found on private org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.AServiceCallback org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.impl.BServiceImpl.callback I should have realized sooner what the real problem was (private fields cannot be annotated) but a message like: WARNING: Invalid annotation @org.osoa.sca.annotations.Callback(value=class java.lang.Void) is found on private org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.AServiceCallback org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.impl.BServiceImpl.callback. You must not annotate private fields and if you do then the runtime will ignore them and only give you this warning. I think an exception would be even better since the application will not work without the requested injection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2282) Poor warning issued when annotating private field with @Callback
[ https://issues.apache.org/jira/browse/TUSCANY-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2282. -- Resolution: Fixed Applied in r654698. Thanks for the fix. Poor warning issued when annotating private field with @Callback Key: TUSCANY-2282 URL: https://issues.apache.org/jira/browse/TUSCANY-2282 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Assignee: ant elder Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2282.patch I inadvertently marked a private field with @Callback and received the following warning: WARNING: Invalid annotation @org.osoa.sca.annotations.Callback(value=class java.lang.Void) is found on private org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.AServiceCallback org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.impl.BServiceImpl.callback I should have realized sooner what the real problem was (private fields cannot be annotated) but a message like: WARNING: Invalid annotation @org.osoa.sca.annotations.Callback(value=class java.lang.Void) is found on private org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.AServiceCallback org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.impl.BServiceImpl.callback. You must not annotate private fields and if you do then the runtime will ignore them and only give you this warning. I think an exception would be even better since the application will not work without the requested injection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2302) Exception thrown during SimpleTypeMapperExtensionTestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595481#action_12595481 ] ant elder commented on TUSCANY-2302: See related ML thread: http://apache.markmail.org/message/ppwz3sx3woxp64ju Exception thrown during SimpleTypeMapperExtensionTestCase - Key: TUSCANY-2302 URL: https://issues.apache.org/jira/browse/TUSCANY-2302 Project: Tuscany Issue Type: Bug Components: Java SCA Data Binding Runtime Environment: Mac OS 10.5.2, JVM 1.5.0_13, MacBook Pro Reporter: Chris Trezzo I have attempted a build of the Tuscany trunk code using revision 653996. I encountered an IllegalArgumentException during the SimpleTypeMapperExtensionTestCase in the DataBinding module. Using the mvn -fae clean install command, no other issues were encountered. Below is the trace that I received for the failure: Running org.apache.tuscany.sca.databinding.extension.SimpleTypeMapperExtensionTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.014 sec FAILURE! testMap(org.apache.tuscany.sca.databinding.extension.SimpleTypeMapperExtensionTestCase) Time elapsed: 0.011 sec ERROR! java.lang.IllegalArgumentException: --02 at com.sun.org.apache.xerces.internal.jaxp.datatype.XMLGregorianCalendarImpl$Parser.read(XMLGregorianCalendarImpl.java:2810) at com.sun.org.apache.xerces.internal.jaxp.datatype.XMLGregorianCalendarImpl$Parser.skip(XMLGregorianCalendarImpl.java:2816) at com.sun.org.apache.xerces.internal.jaxp.datatype.XMLGregorianCalendarImpl$Parser.parse(XMLGregorianCalendarImpl.java:2740) at com.sun.org.apache.xerces.internal.jaxp.datatype.XMLGregorianCalendarImpl.init(XMLGregorianCalendarImpl.java:440) at com.sun.org.apache.xerces.internal.jaxp.datatype.DatatypeFactoryImpl.newXMLGregorianCalendar(DatatypeFactoryImpl.java:224) at org.apache.tuscany.sca.databinding.impl.SimpleTypeMapperImpl.toJavaObject(SimpleTypeMapperImpl.java:330) at org.apache.tuscany.sca.databinding.extension.SimpleTypeMapperExtensionTestCase.testMap(SimpleTypeMapperExtensionTestCase.java:113) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) Results : Tests in error: testMap(org.apache.tuscany.sca.databinding.extension.SimpleTypeMapperExtensionTestCase) Tests run: 30, Failures: 0, Errors: 1, Skipped: 0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2296) SCADomain.newInstance() processes all composites in the contribution irrespective of the parameter passed
[ https://issues.apache.org/jira/browse/TUSCANY-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595492#action_12595492 ] ant elder commented on TUSCANY-2296: I'm thinking about closing this as Working-As-Designed, but I'll just say this now and leave the JIRA open for a while to see if there are other comments. It does work as you've described and I agree that can seem unintuitive, but thats the way org.apache.tuscany.host.embedded.SCADomain works - the entire thing is treated as a contribution and all composites in that contribution get processed, the composite passed in on the newInstance call is the _deployable_ composite not the sole composite to be processed. There is a SCADomain newInstance method that takes both a contribution location and list of deployable composites and I think there IS a bug in that which means the contribution location often gets ignored, but really to clean all this up properly requires sorting out what to do with all the new domain/node/node2 etc stuff. SCADomain.newInstance() processes all composites in the contribution irrespective of the parameter passed - Key: TUSCANY-2296 URL: https://issues.apache.org/jira/browse/TUSCANY-2296 Project: Tuscany Issue Type: Bug Components: Java SCA Embedded Runtime Affects Versions: Java-SCA-1.2 Reporter: Vamsavardhana Reddy Fix For: Java-SCA-Next Attachments: TUSCANY-2296-recreate.patch I have two composites, namely proper.composite and error.composite, in my test project. proper.composite is used to test proper contribution without any errors whereas error.composite is used to test a problematic contribution. But when I initialize a domain using SCADomain. newInstance(proper.composite), I am getting an exception due to error.composite. Though it looks as if the call SCADomain. newInstance(proper.composite) processes only proper.composite, in reality it is processing all the .composite files present in the project irrespective of the parameter passed to SCADomain.newInstance(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (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 ] ant elder closed TUSCANY-2209. -- Resolution: Fixed 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.
[jira] Closed: (TUSCANY-2173) Add style formatter and template information to website Coding Guidelines
[ https://issues.apache.org/jira/browse/TUSCANY-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2173. -- Resolution: Fixed Done Add style formatter and template information to website Coding Guidelines --- Key: TUSCANY-2173 URL: https://issues.apache.org/jira/browse/TUSCANY-2173 Project: Tuscany Issue Type: Improvement Components: Website Environment: All browsers Reporter: Dan Becker Priority: Minor Incorporate more specific Eclipse style formatter and template notes to the external web site. The external web site at http://cwiki.apache.org/TUSCANY/sca-java-development-guide.html#SCAJavaDevelopmentGuide-CodingGuidelines contains useful coding guidelines. There are additional Eclipse-specific guidelines on the internal wiki at http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Code+Style+Formatters+and+Templates It would be useful if the Eclipse Style Formatter and Eclipse Templates (which are in the Tuscany build/repository) be mentioned in the external site. In other words, append the information from the second link above to the first link above. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2305) vtests for service binding.ws
[
https://issues.apache.org/jira/browse/TUSCANY-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder reassigned TUSCANY-2305:
--
Assignee: ant elder
vtests for service binding.ws
-
Key: TUSCANY-2305
URL: https://issues.apache.org/jira/browse/TUSCANY-2305
Project: Tuscany
Issue Type: Bug
Components: Java SCA Verification Tests
Reporter: Vamsavardhana Reddy
Assignee: ant elder
Fix For: Java-SCA-Next
Attachments: TUSCANY-2305-2.patch, TUSCANY-2305.patch
Create vtests for service webservice binding as per Web Service Binding
Specification Spec v1.00 - Sec 2.1 and 2.1.1 - lines 26 to 85:
-
26 2.1 Web Service Binding Schema
27 The Web Service binding element is defined by the following pseudo-schema.
28 binding.ws wsdlElement=xs:anyURI?
29 wsdli:wsdlLocation=list of xs:anyURI?
30 ...
31 wsa:EndpointReference.../wsa:EndpointReference*
32 ...
33 /binding.ws
34
35 • /binding.ws/@wsdlElement - optional attribute that specifies the URI of
a WSDL element.
36 The use of this attribute indicates that the SCA binding points to the
specified element in an
37 existing WSDL document. The URI can have the following forms:
38 o Service:
39 WSDL-namespace-URI#wsdl.service(service-name)
40 In this case, all the endpoints in the WSDL Service that have equivalent
PortTypes with
41 the SCA service or reference must be available to the SCA service or
reference.
42 o Port (WSDL 1.1):
43 WSDL-namespace-URI#wsdl.port(service-name/port-name)
44 In this case, the identified port in the WSDL 1.1 Service must have an
equivalent
45 PortType with the SCA service or reference.
46 o Endpoint (WSDL 2.0):
47 WSDL-namespace-URI#wsdl.endpoint(service-name/endpoint-name)
48 In this case, the identified endpoint in the WSDL 2.0 Service must have an
equivalent
49 PortType with the SCA service or reference.
50 o Binding:
51 WSDL-namespace-URI#wsdl.binding(binding-name)
52 In this case, the identified WSDL binding must have an equivalent PortType
with the SCA
53 service or reference. In this case the endpoint address URI for the SCA
service or
54 reference must be provided via the URI attribute on the binding.
55 • /binding.ws/@wsdli:wsdlLocation - optional attribute that specifies the
location of the
56 WSDL document. This attribute can be specified in the event that the
WSDL-namespace-
57 URI in the 'endpoint' attribute is not dereferencable, or when the
intended WSDL document
58 is to be found at a different location than the one pointed to by the
WSDL-namespace-
59 URI. The use of this attribute indicates that the WSDL binding points to
an existing WSDL
60 document.
61 • /binding.ws/wsa:EndpointReference - optional WS-Addressing [6]
EndpointReference
62 that specifies the endpoint for the service or reference. When this
element is present along
63 with the wsdlElement attribute on the parent element, the wsdlElement
attribute value MUST
64 be of the 'Binding' form as specified above, i.e. WSDL-namespace-
65 URI#wsdl.binding(binding-name).
66 • /binding.ws/@{any} - this is an extensibility mechanism to allow
extensibility via
67 attributes.
SCA Service Component Architecture
WS Binding Specification V1.00 March 2 3 007
68 • /binding.ws/any - this is an extensibility mechanism to allow
extensibility via elements.
69
70 2.1.1 Endpoint URI resolution
71 The rules for resolving the URI at which an SCA service is hosted, or SCA
reference targets,
72 when used with binding.ws (in precedence order) are:
73 1. The URIs in the endpoint(s) of the referenced WSDL
74 or
75 The URI specified by the wsa:Address element of the wsa:EndpointReference,
76 2. The explicitly stated URI in the uri attribute of the binding.ws
element, which may be
77 relative,
78 3. The implicit URI as defined by the Assembly specification
79 The URI in the WSDL endpoint or in the wsa:Address of an EPR may be a
relative URI, in which
80 case it is relative to the URI defined in (2) or (3). The wsa:Address
element can be the empty
81 relative URI, in which case it uses the URI defined in (2) or (3)
directly. This allows the EPR
82 writer to specify reference parameters, metadata and other EPR contents
while allowing the URI
83 to be chosen by the deployer.
84 To reference a WSDL document and also specify an EPR, the wsdlElement
attribute must refer to
85 a binding element in the WSDL and not an endpoint or service.
-
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2305) vtests for service binding.ws
[
https://issues.apache.org/jira/browse/TUSCANY-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-2305.
--
Resolution: Fixed
Applied in r654855
vtests for service binding.ws
-
Key: TUSCANY-2305
URL: https://issues.apache.org/jira/browse/TUSCANY-2305
Project: Tuscany
Issue Type: Bug
Components: Java SCA Verification Tests
Reporter: Vamsavardhana Reddy
Assignee: ant elder
Fix For: Java-SCA-Next
Attachments: TUSCANY-2305-2.patch, TUSCANY-2305.patch
Create vtests for service webservice binding as per Web Service Binding
Specification Spec v1.00 - Sec 2.1 and 2.1.1 - lines 26 to 85:
-
26 2.1 Web Service Binding Schema
27 The Web Service binding element is defined by the following pseudo-schema.
28 binding.ws wsdlElement=xs:anyURI?
29 wsdli:wsdlLocation=list of xs:anyURI?
30 ...
31 wsa:EndpointReference.../wsa:EndpointReference*
32 ...
33 /binding.ws
34
35 • /binding.ws/@wsdlElement - optional attribute that specifies the URI of
a WSDL element.
36 The use of this attribute indicates that the SCA binding points to the
specified element in an
37 existing WSDL document. The URI can have the following forms:
38 o Service:
39 WSDL-namespace-URI#wsdl.service(service-name)
40 In this case, all the endpoints in the WSDL Service that have equivalent
PortTypes with
41 the SCA service or reference must be available to the SCA service or
reference.
42 o Port (WSDL 1.1):
43 WSDL-namespace-URI#wsdl.port(service-name/port-name)
44 In this case, the identified port in the WSDL 1.1 Service must have an
equivalent
45 PortType with the SCA service or reference.
46 o Endpoint (WSDL 2.0):
47 WSDL-namespace-URI#wsdl.endpoint(service-name/endpoint-name)
48 In this case, the identified endpoint in the WSDL 2.0 Service must have an
equivalent
49 PortType with the SCA service or reference.
50 o Binding:
51 WSDL-namespace-URI#wsdl.binding(binding-name)
52 In this case, the identified WSDL binding must have an equivalent PortType
with the SCA
53 service or reference. In this case the endpoint address URI for the SCA
service or
54 reference must be provided via the URI attribute on the binding.
55 • /binding.ws/@wsdli:wsdlLocation - optional attribute that specifies the
location of the
56 WSDL document. This attribute can be specified in the event that the
WSDL-namespace-
57 URI in the 'endpoint' attribute is not dereferencable, or when the
intended WSDL document
58 is to be found at a different location than the one pointed to by the
WSDL-namespace-
59 URI. The use of this attribute indicates that the WSDL binding points to
an existing WSDL
60 document.
61 • /binding.ws/wsa:EndpointReference - optional WS-Addressing [6]
EndpointReference
62 that specifies the endpoint for the service or reference. When this
element is present along
63 with the wsdlElement attribute on the parent element, the wsdlElement
attribute value MUST
64 be of the 'Binding' form as specified above, i.e. WSDL-namespace-
65 URI#wsdl.binding(binding-name).
66 • /binding.ws/@{any} - this is an extensibility mechanism to allow
extensibility via
67 attributes.
SCA Service Component Architecture
WS Binding Specification V1.00 March 2 3 007
68 • /binding.ws/any - this is an extensibility mechanism to allow
extensibility via elements.
69
70 2.1.1 Endpoint URI resolution
71 The rules for resolving the URI at which an SCA service is hosted, or SCA
reference targets,
72 when used with binding.ws (in precedence order) are:
73 1. The URIs in the endpoint(s) of the referenced WSDL
74 or
75 The URI specified by the wsa:Address element of the wsa:EndpointReference,
76 2. The explicitly stated URI in the uri attribute of the binding.ws
element, which may be
77 relative,
78 3. The implicit URI as defined by the Assembly specification
79 The URI in the WSDL endpoint or in the wsa:Address of an EPR may be a
relative URI, in which
80 case it is relative to the URI defined in (2) or (3). The wsa:Address
element can be the empty
81 relative URI, in which case it uses the URI defined in (2) or (3)
directly. This allows the EPR
82 writer to specify reference parameters, metadata and other EPR contents
while allowing the URI
83 to be chosen by the deployer.
84 To reference a WSDL document and also specify an EPR, the wsdlElement
attribute must refer to
85 a binding element in the WSDL and not an endpoint or service.
-
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2268) Exceptions errors on binding to external web services
[ https://issues.apache.org/jira/browse/TUSCANY-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591978#action_12591978 ] ant elder commented on TUSCANY-2268: There's two problems I've noticed so far: - the interface HelloWorld has the @Remotable commented out with the comment utile ?, you need this. Without it when everything else is configured ok you'll get the following: [java] Exception in thread main java.lang.IllegalArgumentException: Can't handle mixed payloads betweem OMElements and other types. - in the .composite files the binding.ws has an incorrect port name of HelloWorldSoapPort instead of HelloWorldSoap as defined in the helloworld.wsdl. Changing those two things gets the client running for me though i can't test it fully as I don't have any service running for it. If you still have trouble invoking the service post the service code so i can help debug that. Apologies that the error messages given for those two problems are so unhelpful, more meaningfull messages would have made that much easier to debug. Exceptions errors on binding to external web services - Key: TUSCANY-2268 URL: https://issues.apache.org/jira/browse/TUSCANY-2268 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: Windows XP, Eclipse 3.3.0 , tuscany incubating 1.1 , java 6 Reporter: Marina Deslaugiers Attachments: ws-webhelloworld.zip Hi, I am considering web services that seems to be doc literal encoded. I began to try the direct connection to them but I did not succeed. As these web services are not public ones, I have done a try on a simple (helloworrd) public one without success. Depending, on the binding way (uri, wsdlElement and promoted or not promoted reference) I get different exceptions (some are indicated - within a comment - in the composite files). So, what is wrong ? I attach the code I wrote; please, would you mind to verify (and correct if necessary) it or send me an equivalent example that works because I need to make it work rapidly now. Thanks, Marina. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2241) EndpointReference in binding.ws when wsdlElement is not of 'Binding' form
[ https://issues.apache.org/jira/browse/TUSCANY-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2241. -- Resolution: Fixed Patch applied, thanks for the fix! EndpointReference in binding.ws when wsdlElement is not of 'Binding' form - Key: TUSCANY-2241 URL: https://issues.apache.org/jira/browse/TUSCANY-2241 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-1.2, Java-SCA-Next Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: Java-SCA-Next Attachments: TUSCANY-2241.patch Web Service Binding Specification v1.0 - Sec 2.1 - Lines 61 to 65: 61 • /binding.ws/wsa:EndpointReference - optional WS-Addressing [6] EndpointReference 62 that specifies the endpoint for the service or reference. When this element is present along 63 with the wsdlElement attribute on the parent element, the wsdlElement attribute value MUST 64 be of the 'Binding' form as specified above, i.e. WSDL-namespace- 65 URI#wsdl.binding(binding-name). I notice that when an EndpointReference is specified inside binding.ws along with a wsdlElement which is not of 'Binding' form, no warning or error is generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2249) Updates to ComponentContext's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591239#action_12591239 ] ant elder commented on TUSCANY-2249: Applied in r650408. Note though that the testGetRequestContext method is failing for me so I've added @Ignore to that. Is there some associated change that needs to be made? Updates to ComponentContext's vtest --- Key: TUSCANY-2249 URL: https://issues.apache.org/jira/browse/TUSCANY-2249 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: ComponentContextUpdatesJIRA2249.patch More vtest test cases for ComponentContext API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2241) EndpointReference in binding.ws when wsdlElement is not of 'Binding' form
[ https://issues.apache.org/jira/browse/TUSCANY-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2241. -- Resolution: Fixed Applied in r650504 EndpointReference in binding.ws when wsdlElement is not of 'Binding' form - Key: TUSCANY-2241 URL: https://issues.apache.org/jira/browse/TUSCANY-2241 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-1.2, Java-SCA-Next Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: Java-SCA-Next Attachments: TUSCANY-2241-test.patch, TUSCANY-2241.patch Web Service Binding Specification v1.0 - Sec 2.1 - Lines 61 to 65: 61 • /binding.ws/wsa:EndpointReference - optional WS-Addressing [6] EndpointReference 62 that specifies the endpoint for the service or reference. When this element is present along 63 with the wsdlElement attribute on the parent element, the wsdlElement attribute value MUST 64 be of the 'Binding' form as specified above, i.e. WSDL-namespace- 65 URI#wsdl.binding(binding-name). I notice that when an EndpointReference is specified inside binding.ws along with a wsdlElement which is not of 'Binding' form, no warning or error is generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2241) EndpointReference in binding.ws when wsdlElement is not of 'Binding' form
[ https://issues.apache.org/jira/browse/TUSCANY-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590878#action_12590878 ] ant elder commented on TUSCANY-2241: Many thanks for the fix, it looks ok to me but some of our existing tests have EndpointReferences where its actually invalid so with this fix applied there are test failures (try building binding-ws-axis2 with this fix applied to find them). Could you also supply a patch to fix those? EndpointReference in binding.ws when wsdlElement is not of 'Binding' form - Key: TUSCANY-2241 URL: https://issues.apache.org/jira/browse/TUSCANY-2241 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-1.2, Java-SCA-Next Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: Java-SCA-Next Attachments: TUSCANY-2241.patch Web Service Binding Specification v1.0 - Sec 2.1 - Lines 61 to 65: 61 • /binding.ws/wsa:EndpointReference - optional WS-Addressing [6] EndpointReference 62 that specifies the endpoint for the service or reference. When this element is present along 63 with the wsdlElement attribute on the parent element, the wsdlElement attribute value MUST 64 be of the 'Binding' form as specified above, i.e. WSDL-namespace- 65 URI#wsdl.binding(binding-name). I notice that when an EndpointReference is specified inside binding.ws along with a wsdlElement which is not of 'Binding' form, no warning or error is generated. -- 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] Closed: (TUSCANY-2246) Update DefaultContextFactoryExtensionPoint to use ServiceDiscovery
[ https://issues.apache.org/jira/browse/TUSCANY-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2246. -- Resolution: Fixed Applied in r650101, thanks for the code Greg. Update DefaultContextFactoryExtensionPoint to use ServiceDiscovery -- Key: TUSCANY-2246 URL: https://issues.apache.org/jira/browse/TUSCANY-2246 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Reporter: Greg Dritschler Attachments: tuscany-2246.patch Change DefaultContextFactoryExtensionPoint to use ServiceDiscovery to find implementation of context factory. -- 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-1997) Axis binding does not allow external configuration to increase the number of the maximum connections opened.
[
https://issues.apache.org/jira/browse/TUSCANY-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1997:
---
Attachment: tuscany-binding-ws-axis2-1.0-T1997-T1893.jar
Attached tuscany-binding-ws-axis2-1.0-T1997-T1893.jar which contains the
changes for TUSCANY-1997 and TUSCANY-1893 back-ported to the 1.0 code. The diff
to the base 1.0 code is the following:
Index:
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
===
---
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
(revision 630862)
+++
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
(working copy)
@@ -61,6 +61,7 @@
public static final QName CALLBACK_REFERENCE_REFPARM_QN = new
QName(Constants.SCA10_TUSCANY_NS, CallbackReference);
public static final QName CALLBACK_ID_REFPARM_QN = new
QName(Constants.SCA10_TUSCANY_NS, CallbackID);
public static final QName CONVERSATION_ID_REFPARM_QN = new
QName(Constants.SCA10_TUSCANY_NS, ConversationID);
+public static long GLOBAL_AXIS_TIMEOUT = 12L;
public Axis2BindingInvoker(ServiceClient serviceClient,
QName wsdlOperationName,
@@ -97,7 +98,7 @@
// ensure connections are tracked so that they can be closed by the
reference binding
MessageContext requestMC =
operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
-requestMC.getOptions().setTimeOutInMilliSeconds(12L);
+requestMC.getOptions().setTimeOutInMilliSeconds(GLOBAL_AXIS_TIMEOUT);
operationClient.execute(true);
Index:
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2OneWayBindingInvoker.java
===
---
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2OneWayBindingInvoker.java
(revision 630862)
+++
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2OneWayBindingInvoker.java
(working copy)
@@ -48,7 +48,11 @@
// ensure connections are tracked so that they can be closed by the
reference binding
MessageContext requestMC =
operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
-requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
+//requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
+Options opt = requestMC.getOptions();
+opt.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE);
+opt.setUseSeparateListener(true);
+opt.setProperty(HTTPConstants.AUTO_RELEASE_CONNECTION,Boolean.TRUE);
operationClient.execute(false);
Index:
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2ServiceClient.java
===
---
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2ServiceClient.java
(revision 630862)
+++
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2ServiceClient.java
(working copy)
@@ -52,8 +52,10 @@
import org.apache.axis2.description.WSDL11ToAxisServiceBuilder;
import org.apache.axis2.description.WSDL2Constants;
import org.apache.axis2.transport.http.HTTPConstants;
+import org.apache.axis2.util.threadpool.ThreadPool;
import org.apache.commons.httpclient.HttpClient;
import org.apache.commons.httpclient.MultiThreadedHttpConnectionManager;
+import org.apache.commons.httpclient.params.HttpConnectionManagerParams;
import org.apache.tuscany.sca.assembly.AbstractContract;
import org.apache.tuscany.sca.binding.ws.WebServiceBinding;
import org.apache.tuscany.sca.contribution.Contribution;
@@ -78,6 +80,8 @@
private ServiceClient serviceClient;
private static final QName SOAP12_INTENT = new
QName(http://www.osoa.org/xmlns/sca/1.0;, soap12);
+public static int httpMaxConnections = 2;
+
public Axis2ServiceClient(RuntimeComponent component,
AbstractContract contract,
WebServiceBinding wsBinding,
@@ -108,7 +112,26 @@
AxisService axisService =
createClientSideAxisService(wsdlDefinition, serviceQName,
portName, new Options());
+HttpClient httpClient = (HttpClient)
configContext.getProperty(HTTPConstants.CACHED_HTTP_CLIENT);
+if (httpClient == null)
+{
+MultiThreadedHttpConnectionManager connectionManager = new
MultiThreadedHttpConnectionManager();
+HttpConnectionManagerParams connectionManagerParams = new
HttpConnectionManagerParams();
+
connectionManagerParams.setDefaultMaxConnectionsPerHost(httpMaxConnections);
+
[jira] Reopened: (TUSCANY-88) Support invoking simple RPC/encoded Web services
[ https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reopened TUSCANY-88: -- Reopened see user list thread - http://apache.markmail.org/message/25in5vox5if6xbw2 Support invoking simple RPC/encoded Web services Key: TUSCANY-88 URL: https://issues.apache.org/jira/browse/TUSCANY-88 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Reporter: ant elder Priority: Minor Fix For: Java-SCA-M2 Currently externalServices using the WS binding don't support invoking RPC encoded services. To support RPC/encoded properly would be a lot of work and as its not WS-I compliant probably isn't a high priority, however as there are a lot of existing RPC/encoded services out there it would be good if we had some limitted support for the subset of RPC/encoded thats easy to do. It would great if at least it worked for trivial services like xmethods stockquote. Thats WS 101 and a lot of people will likely try using that when they first look at Tuscany. It would create a much better first impression if that works rather than giving the obscure exception you get if you try it today. -- 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-88) Support invoking simple RPC/encoded Web services
[ https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-88: - Attachment: translate.zip Example of using xml component to invoke an rpc-encoded WS Support invoking simple RPC/encoded Web services Key: TUSCANY-88 URL: https://issues.apache.org/jira/browse/TUSCANY-88 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Reporter: ant elder Priority: Minor Fix For: Java-SCA-M2 Attachments: translate.zip Currently externalServices using the WS binding don't support invoking RPC encoded services. To support RPC/encoded properly would be a lot of work and as its not WS-I compliant probably isn't a high priority, however as there are a lot of existing RPC/encoded services out there it would be good if we had some limitted support for the subset of RPC/encoded thats easy to do. It would great if at least it worked for trivial services like xmethods stockquote. Thats WS 101 and a lot of people will likely try using that when they first look at Tuscany. It would create a much better first impression if that works rather than giving the obscure exception you get if you try it today. -- 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-88) Support invoking simple RPC/encoded Web services
[ https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-88: - Fix Version/s: (was: Java-SCA-M2) Java-SCA-Next Support invoking simple RPC/encoded Web services Key: TUSCANY-88 URL: https://issues.apache.org/jira/browse/TUSCANY-88 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Reporter: ant elder Priority: Minor Fix For: Java-SCA-Next Attachments: translate.zip Currently externalServices using the WS binding don't support invoking RPC encoded services. To support RPC/encoded properly would be a lot of work and as its not WS-I compliant probably isn't a high priority, however as there are a lot of existing RPC/encoded services out there it would be good if we had some limitted support for the subset of RPC/encoded thats easy to do. It would great if at least it worked for trivial services like xmethods stockquote. Thats WS 101 and a lot of people will likely try using that when they first look at Tuscany. It would create a much better first impression if that works rather than giving the obscure exception you get if you try it today. -- 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-88) Support invoking simple RPC/encoded Web services
[
https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590361#action_12590361
]
ant elder commented on TUSCANY-88:
--
As a start we can support RPC-encoded by using XML components, but doing that
raises some issues:
- Axis2 no longer supports creating a ServiceClient from RPC-encoded WSDL
throwing an exception when it finds use=encoded. Could try to get that
changed in Axis2 as its only the Axis2 data bindings that should care.
- we've no facility to set the SOAP Action header other than from WSDL. Could
add a Tuscany specific attribute to binding.ws and/or support the jaxws
@Action attribute
- Tuscany script components no longer support WS references. Did work at one
point, i'd really like to be able to do (yes yes, i know inline scripts make
some people scowl):
component name=TranslationComponent
tuscany:implementation.script language=js![CDATA[
function translate(from, to, text) {
var resp = translator.translate(
tem:Translate xmlns:tem=http://tempuri.org/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
lang xsi:type=xsd:string { from }_{ to } /lang
text xsi:type=xsd:string{ text } /text
/tem:Translate;
return resp..TranslateResult
}
]]/tuscany:implementation.script
reference name=translator
binding.ws
wsdlElement=http://tempuri.org/#wsdl.port(Translator/TranslatorSoap) /
/reference
/component
Support invoking simple RPC/encoded Web services
Key: TUSCANY-88
URL: https://issues.apache.org/jira/browse/TUSCANY-88
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Axis Binding Extension
Reporter: ant elder
Priority: Minor
Fix For: Java-SCA-M2
Currently externalServices using the WS binding don't support invoking RPC
encoded services. To support RPC/encoded properly would be a lot of work and
as its not WS-I compliant probably isn't a high priority, however as there
are a lot of existing RPC/encoded services out there it would be good if we
had some limitted support for the subset of RPC/encoded thats easy to do. It
would great if at least it worked for trivial services like xmethods
stockquote. Thats WS 101 and a lot of people will likely try using that when
they first look at Tuscany. It would create a much better first impression if
that works rather than giving the obscure exception you get if you try it
today.
--
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-88) Support invoking simple RPC/encoded Web services
[ https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590363#action_12590363 ] ant elder commented on TUSCANY-88: -- - also Tuscany wsdl parsing code was complaining about the wsdl message parts type using http://www.w3.org/2001/XMLSchema, i've not investigated what that was about Support invoking simple RPC/encoded Web services Key: TUSCANY-88 URL: https://issues.apache.org/jira/browse/TUSCANY-88 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Reporter: ant elder Priority: Minor Fix For: Java-SCA-M2 Currently externalServices using the WS binding don't support invoking RPC encoded services. To support RPC/encoded properly would be a lot of work and as its not WS-I compliant probably isn't a high priority, however as there are a lot of existing RPC/encoded services out there it would be good if we had some limitted support for the subset of RPC/encoded thats easy to do. It would great if at least it worked for trivial services like xmethods stockquote. Thats WS 101 and a lot of people will likely try using that when they first look at Tuscany. It would create a much better first impression if that works rather than giving the obscure exception you get if you try it today. -- 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] Closed: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2165. -- Resolution: Fixed Patches applied, thanks for the fix! Java runtime should inject service references to field with common name in absence of @Reference - Key: TUSCANY-2165 URL: https://issues.apache.org/jira/browse/TUSCANY-2165 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Priority: Minor Attachments: TUSCANY-2165-revised-test.patch, TUSCANY-2165.patch The Java AnnotationsAPIs specification Lines 1407, 1408, 1409, 1410 ... * References may also be injected via public setter methods even when the * @Reference annotation is not present. However, the @Reference * annotation must be used in order to inject a reference onto a non public * field. In the case where there is no @Reference annotation, the name of * the reference is the same as the name of the field or setter. The vTest: org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 demonstrates this issue -- 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] Closed: (TUSCANY-2218) Endpoint URI resolution precedence for binding.ws reference is incorrect
[
https://issues.apache.org/jira/browse/TUSCANY-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-2218.
--
Resolution: Fixed
Applied, thanks for the fixes!
Endpoint URI resolution precedence for binding.ws reference is incorrect
Key: TUSCANY-2218
URL: https://issues.apache.org/jira/browse/TUSCANY-2218
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-1.0
Reporter: Lou Amodeo
Fix For: Java-SCA-Next
Attachments: TUSCANY-2218-testcase.patch, TUSCANY-2218.patch
I believe the order of Endpoint URI resolution precedence is incorrect for
binding.ws references. What I am seeing is that the uri attribute is taking
precedence over the location specified in the WSDL. The spec indicates that
the endpoint in the WSDL should take highest precedence.
Web Service Binding Spec
2.1.1 Endpoint URI resolution
71 The rules for resolving the URI at which an SCA service is hosted, or SCA
reference targets,
72 when used with binding.ws (in precedence order) are:
73 1. The URIs in the endpoint(s) of the referenced WSDL
74 or
75 The URI specified by the wsa:Address element of the wsa:EndpointReference,
76 2. The explicitly stated URI in the uri attribute of the binding.ws
element, which may be
77 relative,
78 3. The implicit URI as defined by the Assembly specification
In Axis2ServiceClient getPortLocation looks for uri first and returns it
ahead of wsdl location if present.
protected EndpointReference getPortLocationEPR(WebServiceBinding binding) {
String ep = binding.getURI(); WAS specific
if (ep == null binding.getPort() != null) {
List? wsdlPortExtensions =
binding.getPort().getExtensibilityElements();
for (final Object extension : wsdlPortExtensions) {
if (extension instanceof SOAPAddress) {
ep = ((SOAPAddress)extension).getLocationURI();
break;
}
if (extension instanceof SOAP12Address) {
SOAP12Address address = (SOAP12Address)extension;
ep = address.getLocationURI();
break;
}
}
}
return ep == null || .equals(ep) ? null : new EndpointReference(ep);
}
--
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-2199) Tests for @Reference annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589077#action_12589077 ] ant elder commented on TUSCANY-2199: Thanks for the patch Gilbert. Unfortunately it wont apply correctly for me complaining that some characters in the patch can't be mapped to Cp1252 encoding. I suspect an SVN config mismatch, could you check your SVN client config matches whats used by Tuscany and reattach a patch based on that? There's been some email on the dev list recently about how to do this, see: http://apache.markmail.org/message/kydc2535whfhass3 Tests for @Reference annotation --- Key: TUSCANY-2199 URL: https://issues.apache.org/jira/browse/TUSCANY-2199 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Attachments: TUSCANY-2199.multiplicity.test.patch Placeholder for tracking additions to the @Reference vtests -- 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-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589106#action_12589106 ] ant elder commented on TUSCANY-2165: Thanks for the lates patch, I've applied it locally but now running the test i get a failure: Tests run: 7, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 1.546 sec FAILURE! atReference2(org.apache.tuscany.sca.vtest.javaapi.annotations.reference.ReferenceAnnotationTestCase) Time elapsed: 0 sec FAILURE! java.lang.AssertionError: getB5Name expected to fail with NPE at org.junit.Assert.fail(Assert.java:69) at org.apache.tuscany.sca.vtest.javaapi.annotations.reference.ReferenceAnnotationTestCase.atReference2(ReferenceAnnotationTestCase.java:122) Is that expected? Java runtime should inject service references to field with common name in absence of @Reference - Key: TUSCANY-2165 URL: https://issues.apache.org/jira/browse/TUSCANY-2165 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Priority: Minor Attachments: TUSCANY-2165-revised-test.patch, TUSCANY-2165.patch The Java AnnotationsAPIs specification Lines 1407, 1408, 1409, 1410 ... * References may also be injected via public setter methods even when the * @Reference annotation is not present. However, the @Reference * annotation must be used in order to inject a reference onto a non public * field. In the case where there is no @Reference annotation, the name of * the reference is the same as the name of the field or setter. The vTest: org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 demonstrates this issue -- 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] Closed: (TUSCANY-2195) Test cases for ComponentContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2195. -- Resolution: Fixed Applied, many thanks for the code Test cases for ComponentContext API --- Key: TUSCANY-2195 URL: https://issues.apache.org/jira/browse/TUSCANY-2195 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Attachments: ComponentContext.zip, ComponentContext20080404.zip, ComponentContextJira2195.patch Contributions for ComponentContext API testing can be attached here -- 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] Closed: (TUSCANY-2199) Tests for @Reference annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2199. -- Resolution: Fixed So it is, in r644938. Tests for @Reference annotation --- Key: TUSCANY-2199 URL: https://issues.apache.org/jira/browse/TUSCANY-2199 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Attachments: TUSCANY-2199.multiplicity.test.patch Placeholder for tracking additions to the @Reference vtests -- 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-2145) SCADomain.getService () should throw exception when bogus component name is passed
[
https://issues.apache.org/jira/browse/TUSCANY-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587513#action_12587513
]
ant elder commented on TUSCANY-2145:
This behaviour was introduced in r570929 -
http://svn.apache.org/viewvc?view=revrevision=570929 so it looks like it is
intentional. I'll bring it up on the dev list but right now looks like this
will be closed as Working-As-Designed.
SCADomain.getService () should throw exception when bogus component name is
passed
--
Key: TUSCANY-2145
URL: https://issues.apache.org/jira/browse/TUSCANY-2145
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Kevin Williams
Priority: Minor
SCADomain.getService() currently returns a proxy even when the component name
passed is not in the domain.
I have created a test (currently ignored) in the new vTest suite to
demonstrate.
@Test
@Ignore
public void bogusComponentName() throws Exception {
--
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] Closed: (TUSCANY-2207) First steps towards Axis MTOM Support
[ https://issues.apache.org/jira/browse/TUSCANY-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2207. -- Resolution: Fixed Applied. Thanks Giorgio. First steps towards Axis MTOM Support -- Key: TUSCANY-2207 URL: https://issues.apache.org/jira/browse/TUSCANY-2207 Project: Tuscany Issue Type: New Feature Affects Versions: Java-SCA-1.2 Reporter: Giorgio Zoppi Priority: Minor Fix For: Java-SCA-Next Attachments: value.diff This is my first steps towards MTOM support in Tuscany using intent, as it was debated in http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg26726.html. Currently it supports only client generated communication. I opened this jira for tracking. -- 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-2195) Test cases for ComponentContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587070#action_12587070 ] ant elder commented on TUSCANY-2195: I'm a bit confused about the difference between the three patches - is it just the ComponentContextJira2195.patch from the 7th that needs applying or are the other two still relevant as well? Test cases for ComponentContext API --- Key: TUSCANY-2195 URL: https://issues.apache.org/jira/browse/TUSCANY-2195 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Attachments: ComponentContext.zip, ComponentContext20080404.zip, ComponentContextJira2195.patch Contributions for ComponentContext API testing can be attached here -- 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-2162) Spring SCA specification should accomodate common beans/aspects used by different composites/components
[ https://issues.apache.org/jira/browse/TUSCANY-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587085#action_12587085 ] ant elder commented on TUSCANY-2162: We (as in Apache Tuscany) can not enhance the actual specification, for that you'd need to send feed back to the OASIS committee, you can do that through the comments mailing lists - see http://www.oasis-opencsa.org/mailing-lists. What we can do in Tuscany is implement additional functionality thats not described in a spec and this sounds like it could help with what you want, and if we get something working we can then feed that back to OASIS to get the specs enhanced. Could you give a little more detail about what you're proposing, maybe with some snippets of code and/or SCDL to demonstrate what you mean? Spring SCA specification should accomodate common beans/aspects used by different composites/components --- Key: TUSCANY-2162 URL: https://issues.apache.org/jira/browse/TUSCANY-2162 Project: Tuscany Issue Type: New Feature Components: Java SCA Spring Implementation Extension Reporter: Catalin Boloaja The use case : service composites using components or composites as Spring beans. Those beans rely on other injected common beans or applied aspects. We should not instantiate a new bean or aspect for every Spring component or composite if the beans and aspects are shared . The Spring way would be to declare a parent context to accommodate the common beans / aspects. The Spring SCA implementation specification says a new Spring context will be created for each composite. Unclear for component. Can we enhance the specification in the sense of a parent application context ? -- 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-2212) SCA Java builds are getting very large
SCA Java builds are getting very large -- Key: TUSCANY-2212 URL: https://issues.apache.org/jira/browse/TUSCANY-2212 Project: Tuscany Issue Type: Improvement Components: Build System Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next As discussed on the ML SCA Java builds are getting very large. See http://apache.markmail.org/message/u7ebawcoicyqi55a Current size for me is 1.5GB so this jira is to track fixes to reduce that. Looking at the build and repo there's here's some things OTTOMH to start with: - the distribution build copies the distros to the target-last-successful folder. this is only needed for the continuum build and adds 120MB - where ever JMS is used the ActiveMQ default is persistence=true which adds about 50MB for the dbs, changing to persistence=false avoids that - a large amount of the mvn repository size is webapp samples but we don't need these installed into the mvn repo, is there a way to prevent that happening? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2092: -- Assignee: ant elder (was: Ramkumar Ramalingam) ConcurrentModificationException in ExtensibleContributionListener - Key: TUSCANY-2092 URL: https://issues.apache.org/jira/browse/TUSCANY-2092 Project: Tuscany Issue Type: Bug Reporter: Greg Dritschler Assignee: ant elder Attachments: JIRA-2092.patch java.util.ConcurrentModificationException at java.util.AbstractList$SimpleListIterator.next(Unknown Source) at org.apache.tuscany.sca.contribution.service.ExtensibleContributionListener.contributionAdded(ExtensibleContributionListener.java:40) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:389) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:202) The problem occurs if two threads try to add a contribution simultaneously. DefaultContributionListenerExtensionPoint does not synchronize the list of listeners. In particular loadListeners does not prevent multiple threads from trying to load the list of listeners. One thread completes first while the other is still loading. This leads to the exception shown above when a thread tries to iterate the listener list. -- 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] Closed: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2092. -- Resolution: Fixed Fix Version/s: Java-SCA-Next Applied in r646335, thanks for the fix Ramkumar! ConcurrentModificationException in ExtensibleContributionListener - Key: TUSCANY-2092 URL: https://issues.apache.org/jira/browse/TUSCANY-2092 Project: Tuscany Issue Type: Bug Reporter: Greg Dritschler Assignee: ant elder Fix For: Java-SCA-Next Attachments: JIRA-2092.patch java.util.ConcurrentModificationException at java.util.AbstractList$SimpleListIterator.next(Unknown Source) at org.apache.tuscany.sca.contribution.service.ExtensibleContributionListener.contributionAdded(ExtensibleContributionListener.java:40) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:389) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:202) The problem occurs if two threads try to add a contribution simultaneously. DefaultContributionListenerExtensionPoint does not synchronize the list of listeners. In particular loadListeners does not prevent multiple threads from trying to load the list of listeners. One thread completes first while the other is still loading. This leads to the exception shown above when a thread tries to iterate the listener list. -- 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-2212) SCA Java builds are getting very large
[ https://issues.apache.org/jira/browse/TUSCANY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587192#action_12587192 ] ant elder commented on TUSCANY-2212: - clean up use of multiple releases of dependencies by different modules some of the dependencies are several meg and we use several diff releases - jaxb-xjc, derby, xerces, saxon, cleaning this up would reduce the size and speed up builds from an empty repo SCA Java builds are getting very large -- Key: TUSCANY-2212 URL: https://issues.apache.org/jira/browse/TUSCANY-2212 Project: Tuscany Issue Type: Improvement Components: Build System Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next As discussed on the ML SCA Java builds are getting very large. See http://apache.markmail.org/message/u7ebawcoicyqi55a Current size for me is 1.5GB so this jira is to track fixes to reduce that. Looking at the build and repo there's here's some things OTTOMH to start with: - the distribution build copies the distros to the target-last-successful folder. this is only needed for the continuum build and adds 120MB - where ever JMS is used the ActiveMQ default is persistence=true which adds about 50MB for the dbs, changing to persistence=false avoids that - a large amount of the mvn repository size is webapp samples but we don't need these installed into the mvn repo, is there a way to prevent that happening? -- 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-1948) ?wsdl NPE working out base uri
[ https://issues.apache.org/jira/browse/TUSCANY-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-1948: --- Fix Version/s: (was: Java-SCA-Next) Java-SCA-1.2 ?wsdl NPE working out base uri -- Key: TUSCANY-1948 URL: https://issues.apache.org/jira/browse/TUSCANY-1948 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Reporter: ant elder Fix For: Java-SCA-1.2 ?wsdl no longer works properly, varies depending on the environment, sometimes returning wsdl with the wrong endpoint or sometimes failing with an NPE. To recreate use the sample-helloworld-ws-service-webapp sample and from a browser enter: http://localhost:8080/sample-helloworld-ws-service-webapp/SCA/HelloWorldService?wsdl -- 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] Closed: (TUSCANY-1974) Chat webapp sample misses chat messages
[ https://issues.apache.org/jira/browse/TUSCANY-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-1974. -- Resolution: Fixed Fixed in r643023 Chat webapp sample misses chat messages --- Key: TUSCANY-1974 URL: https://issues.apache.org/jira/browse/TUSCANY-1974 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.1 Environment: Tuscany 1.1 RC1 RHEL5 IBM JDK 1.5 Tested Firefox 2.0.0.11 and 3.0 beta2 Reporter: Jean-Sebastien Delfino Assignee: ant elder Fix For: Java-SCA-1.2 To reproduce the issue: Deploy the Chat webapp to Tomcat and open it in Firefox enter nickname: test1, text: 1 nothing is logged, the message seems to be lost enter text: 2, then 2 is logged Another weird issue: open another window enter nickname: test2, text: a again 'a' is lost enter text b, this time b is logged Go back to the first window enter several text messages they are logged in the first window but none of them is logged in the second window The chat application does not seem to really work. -- 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] Closed: (TUSCANY-1948) ?wsdl NPE working out base uri
[ https://issues.apache.org/jira/browse/TUSCANY-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-1948. -- Resolution: Fixed Fixed in r643024 ?wsdl NPE working out base uri -- Key: TUSCANY-1948 URL: https://issues.apache.org/jira/browse/TUSCANY-1948 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Reporter: ant elder Fix For: Java-SCA-1.2 ?wsdl no longer works properly, varies depending on the environment, sometimes returning wsdl with the wrong endpoint or sometimes failing with an NPE. To recreate use the sample-helloworld-ws-service-webapp sample and from a browser enter: http://localhost:8080/sample-helloworld-ws-service-webapp/SCA/HelloWorldService?wsdl -- 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-2184) HelloWorld DOJO Sample WebApp build fails when using alternate local maven repository location
HelloWorld DOJO Sample WebApp build fails when using alternate local maven repository location -- Key: TUSCANY-2184 URL: https://issues.apache.org/jira/browse/TUSCANY-2184 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Reporter: ant elder Priority: Minor Fix For: Java-SCA-1.2 Building the helloworld dojo webapp sample with -Dmaven.repo.local= parameter fails as it cant find the dojo files: [INFO] Error for project: Apache Tuscany SCA HelloWorld DOJO Sample WebApp (during install) [INFO] [INFO] Error executing ant tasks Embedded error: The following error occurred while executing this line: C:\Tuscany\SVN\1.2-BRN\samples\helloworld-dojo-webapp\build-dojo.xml:69: dojo zip file not installed in local repository: \Tuscany\Repos\1.2-brn -- 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-2185) Compile errors in the HelloWorld Web Service JMS and HelloWorld Service JMS samples
Compile errors in the HelloWorld Web Service JMS and HelloWorld Service JMS samples --- Key: TUSCANY-2185 URL: https://issues.apache.org/jira/browse/TUSCANY-2185 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Reporter: ant elder Priority: Blocker Fix For: Java-SCA-1.2 I get the following compile errors when building the samples in the 1.2 branch: [INFO] [INFO] Error for project: Apache Tuscany SCA HelloWorld Web Service JMS Sample (during install) [INFO] [INFO] Compilation failure C:\Tuscany\SVN\1.2-BRN\samples\helloworld-ws-service-jms\src\main\java\helloworld\HelloWorldServer.java:[23,34] package org.apache.activemq. broker does not exist C:\Tuscany\SVN\1.2-BRN\samples\helloworld-ws-service-jms\src\main\java\helloworld\HelloWorldServer.java:[32,21] cannot find symbol symbol : class BrokerService location: class helloworld.HelloWorldServer C:\Tuscany\SVN\1.2-BRN\samples\helloworld-ws-service-jms\src\main\java\helloworld\HelloWorldServer.java:[33,8] cannot find symbol symbol : class BrokerService location: class helloworld.HelloWorldServer C:\Tuscany\SVN\1.2-BRN\samples\helloworld-ws-service-jms\src\main\java\helloworld\HelloWorldServer.java:[33,38] cannot find symbol symbol : class BrokerService location: class helloworld.HelloWorldServer C:\Tuscany\SVN\1.2-BRN\samples\helloworld-ws-service-jms\src\main\java\helloworld\HelloWorldServer.java:[43,8] cannot find symbol symbol : class BrokerService location: class helloworld.HelloWorldServer [INFO] [INFO] Error for project: Apache Tuscany SCA HelloWorld Service JMS Sample (during install) [INFO] [INFO] Compilation failure C:\Tuscany\SVN\1.2-BRN\samples\helloworld-service-jms\src\main\java\helloworld\HelloWorldServer.java:[23,34] package org.apache.activemq.bro ker does not exist C:\Tuscany\SVN\1.2-BRN\samples\helloworld-service-jms\src\main\java\helloworld\HelloWorldServer.java:[24,44] package org.apache.tuscany.sca. host.embedded does not exist C:\Tuscany\SVN\1.2-BRN\samples\helloworld-service-jms\src\main\java\helloworld\HelloWorldServer.java:[33,8] cannot find symbol symbol : class SCADomain location: class helloworld.HelloWorldServer C:\Tuscany\SVN\1.2-BRN\samples\helloworld-service-jms\src\main\java\helloworld\HelloWorldServer.java:[35,24] cannot find symbol symbol : class BrokerService location: class helloworld.HelloWorldServer C:\Tuscany\SVN\1.2-BRN\samples\helloworld-service-jms\src\main\java\helloworld\HelloWorldServer.java:[35,51] cannot find symbol symbol : class BrokerService location: class helloworld.HelloWorldServer C:\Tuscany\SVN\1.2-BRN\samples\helloworld-service-jms\src\main\java\helloworld\HelloWorldServer.java:[42,36] cannot find symbol symbol : variable SCADomain location: class helloworld.HelloWorldServer -- 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-1974) Chat webapp sample misses chat messages
[
https://issues.apache.org/jira/browse/TUSCANY-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582937#action_12582937
]
ant elder commented on TUSCANY-1974:
The following two changes fix this problem for me. The problem is caused by a
bug in WebAppRequestDispatcher including the webapp context path in its
servletPath, this change strips out the context path so the
WebAppRequestDispatcher servlet path really is just the servlet path.
I'm just adding the fix to the jira as this late in the 1.2 release I'm a bit
worried there may be samples that have come to rely on the old behaviour and i
don't have time to test them all sorry.
Index:
modules/host-webapp/src/main/java/org/apache/tuscany/sca/host/webapp/WebAppServletHost.java
===
---
modules/host-webapp/src/main/java/org/apache/tuscany/sca/host/webapp/WebAppServletHost.java
(revision 639228)
+++
modules/host-webapp/src/main/java/org/apache/tuscany/sca/host/webapp/WebAppServletHost.java
(working copy)
@@ -185,7 +185,7 @@
if (servletPath.endsWith(*)) {
servletPath = servletPath.substring(0, servletPath.length() -
1);
if (suri.startsWith(servletPath)) {
-return new WebAppRequestDispatcher(entry.getKey(),
entry.getValue());
+return new
WebAppRequestDispatcher(entry.getKey().substring(contextPath.length()),
entry.getValue());
} else {
if ((suri + /).startsWith(servletPath)) {
return new WebAppRequestDispatcher(entry.getKey(),
entry.getValue());
C:\Tuscany\SVN\LATESTsvn diff
modules\binding-dwr\src\main\java\org\apache\tuscany\sca\binding\dwr\DWRServlet.java
Index:
modules/binding-dwr/src/main/java/org/apache/tuscany/sca/binding/dwr/DWRServlet.java
===
---
modules/binding-dwr/src/main/java/org/apache/tuscany/sca/binding/dwr/DWRServlet.java
(revision 639228)
+++
modules/binding-dwr/src/main/java/org/apache/tuscany/sca/binding/dwr/DWRServlet.java
(working copy)
@@ -146,7 +146,7 @@
// Use the DWR remoter to generate the JavaScipt function for each SCA
service
Remoter remoter =
(Remoter)getContainer().getBean(Remoter.class.getName());
-String path = request.getServletPath();
+String path = request.getContextPath() + request.getServletPath();
for (String serviceName : services.keySet()) {
String serviceScript =
remoter.generateInterfaceScript(serviceName, path);
Chat webapp sample misses chat messages
---
Key: TUSCANY-1974
URL: https://issues.apache.org/jira/browse/TUSCANY-1974
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects Versions: Java-SCA-1.1
Environment: Tuscany 1.1 RC1
RHEL5
IBM JDK 1.5
Tested Firefox 2.0.0.11 and 3.0 beta2
Reporter: Jean-Sebastien Delfino
Assignee: ant elder
Fix For: Java-SCA-1.2
To reproduce the issue:
Deploy the Chat webapp to Tomcat and open it in Firefox
enter nickname: test1, text: 1
nothing is logged, the message seems to be lost
enter text: 2, then 2 is logged
Another weird issue:
open another window
enter nickname: test2, text: a
again 'a' is lost
enter text b, this time b is logged
Go back to the first window
enter several text messages
they are logged in the first window but none of them is logged in the second
window
The chat application does not seem to really work.
--
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-2097) Build errors in itest/osgi-tuscany
[ https://issues.apache.org/jira/browse/TUSCANY-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580759#action_12580759 ] ant elder commented on TUSCANY-2097: The cachedir folder will be coming from the Jython script engine. I don't think we can control the name but the location can be controlled by setting a system property, python.cachedir, see http://www.jython.org/Project/userguide.html#registry-properties. we don't get that when running standalone as the default that gets used isn't writable so it fails to be created. Build errors in itest/osgi-tuscany -- Key: TUSCANY-2097 URL: https://issues.apache.org/jira/browse/TUSCANY-2097 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Affects Versions: Java-SCA-Next Environment: Windows, Sun JDK 1.5.0_14 Reporter: Simon Nash Fix For: Java-SCA-Next Attachments: jira2097.log Here is a summary of the build errors I am seeing. I will attach my full build log to this JIRA. 1. revision.location error creating archive. This seems to show up on every test, and it does not seem to cause a hard failure in the test. java.io.FileNotFoundException: F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany- test\.felix.test\bundle1\version0.0\revision.location (The system cannot find th e file specified) ERROR: org.apache.felix.framework.cache.BundleCache: Error creating archive. (ja va.io.FileNotFoundException: F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany-te st\.felix.test\bundle1\version0.0\revision.location (The system cannot find the file specified)) 2. InvocationTargetException in CalculatorRMIReferencetestCase. java.lang.reflect.InvocationTargetException . Caused by: java.rmi.server.ExportException: Port already in use: 8099; nested ex ception is: java.net.BindException: Address already in use: JVM_Bind 3. Various errors in testOSGiTuscany_BindingWS - ERROR: org.apache.felix.framework.cache.BundleArchive: Unable to delete archi ve directory - F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany-test\.felix.test \bundle5 java.util.zip.ZipException: The system cannot find the file specified org.osgi.framework.BundleException: Could not create bundle object. . Caused by: java.util.zip.ZipException: The system cannot find the file specified -- 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-2074) Component Service not coming up.
[ https://issues.apache.org/jira/browse/TUSCANY-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580290#action_12580290 ] ant elder commented on TUSCANY-2074: The attached zip has the Java src but not the rest of the files any more, could you attach a zip of the complete application including all the files - src, .composite, web.zml etc? Looking in the src for the RunTimeServlet.java I dont understand why it needs to have the SCADomain.newInstance call, if the web.xml defines the Tuscany servlet filter the SCADomain shoul dget started automatically. Component Service not coming up. Key: TUSCANY-2074 URL: https://issues.apache.org/jira/browse/TUSCANY-2074 Project: Tuscany Issue Type: Test Components: Java SCA Tomcat Integration Affects Versions: Java-SCA-1.1 Environment: Windows , Tomcat 5.5 , Apache tuscany 1.1 , Java 5.0 Reporter: Sandeep Raman Priority: Critical Fix For: Java-SCA-Next Attachments: java.zip Original Estimate: 72h Remaining Estimate: 72h summary of the Issue: I have an issue with the component service not coming up. below mentioned is my scenario. I have a JSP (default.jsp) which does the following: %@ page import=org.apache.tuscany.sca.host.embedded.SCADomain% %@ page contentType=text/html;charset=UTF-8 language=java % % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % and the Runtime.composite is as follows: component name=TwoWSService implementation.java class=eai.Compose / service name=Compose interface=http://eai#wsdl.interface(TwoWSService) / binding.ws uri=http://localhost:8080/TwoWSService; / /service /component Now I create a war of all my Java classes , wsdl , composite files and with the default.jsp as the default run target. This war gets deployed in tomcat and the jsp page comes up. It creates a new instance of Runtime.composite too , but it doesnt seem to be starting the component service which i have mentioned in the composite file : binding.ws uri=http://localhost:8080/TwoWSService; /. -- Following Mails explain the scenario:: I see everything in console, like INFO: initContextPath: /TwoWS INFO: Added Servlet mapping: /TwoWSService Even if i try to Run my low lying services which i am composing it Runs fine and can see the output in the console.. The issue is the wsdl url which i need to publish and not able to find it anywhere. As per the samples , in my case http://localhost:8080/TwoWS/TwoWSService?wsdl should point to my wsdl, but tht doesnt seem to exist Regards Sandeep ant elder [EMAIL PROTECTED] wrote on 03/11/2008 05:03:44 PM: A difference between this and the calculator sample is the way the jsp gets the SCADomain object, the Tuscany jsp samples do: % SCADomain scaDomain = (SCADomain) application.getAttribute( org.apache.tuscany.sca.SCADomain); CalculatorService calculatorService = (CalculatorService)scaDomain.getService(CalculatorService.class, CalculatorServiceComponent); % whereas this code does: % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % I've never tried that so i don't know if it will work. If Tuscany is activating the WS endpoint you should see the messages on the tomcat console about it, for example, with the calculator ws sample you see: INFO: ContextPath: /sample-calculator-ws-webapp and INFO: Added Servlet mapping: /AddServiceComponent so you can add those and you tomcat host and port to get http://localhost:8080//sample-calculator-ws-webapp/AddServiceComponent You can test thats working by appending ?wsdl to that and url and entering it in a browser which should return the wsdl document for the service. If you don't see the above messages then something is going wrong and the WS endpoint is not being registered correctly. ...ant On Tue, Mar 11, 2008 at 11:07 AM, Sandeep Raman [EMAIL PROTECTED] wrote: Hi, I have done pretty much in the same way as the sample. i need to see my wsdl , my component service which is running . I am not able to figure out the URL for the wsdl file. I am stuck up there, since all my external requests need this wsdl URL to process, any help or suggestion will be highly appreciated Regards Sandeep Raman ant elder [EMAIL PROTECTED] wrote on 03/11/2008
[jira] Commented: (TUSCANY-2093) Hangs in osgi itests
[ https://issues.apache.org/jira/browse/TUSCANY-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579771#action_12579771 ] ant elder commented on TUSCANY-2093: That gives: Running supplychain.wiring.DSWiring1TestCase - Main thread Thread[main,5,main] Created OSGiCustomerComponentImpl [EMAIL PROTECTED] Activated OSGiCustomerComponentImpl bundle OSGiCustomerComponentImpl.purchaseBooks, retailer1 is [Proxy - [EMAIL PROTECTED] Activated OSGiRetailerComponentImpl bundle Activated OSGiRetailerComponentImpl bundle OSGiRetailerComponentImpl.submitOrder , warehouse is [Proxy - [EMAIL PROTECTED] JavaWarehouseComponentImpl.fulfillOrder : shipper is [Proxy - [EMAIL PROTECTED] Activated OSGiShipperComponentImpl bundle Activated OSGiShipperComponentImpl bundle OSGiShipperComponentImpl.processShipment, customer is [Proxy - [EMAIL PROTECTED] Full thread dump Java HotSpot(TM) Client VM (1.5.0_10-b03 mixed mode): Thread-1 prio=6 tid=0x48ee1008 nid=0x1eb0 runnable [0x4929f000..0x4929f9e8] at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:194) at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411) at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453) at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183) - locked 0x02ad2a40 (a java.io.InputStreamReader) at java.io.InputStreamReader.read(InputStreamReader.java:167) at java.io.BufferedReader.fill(BufferedReader.java:136) at java.io.BufferedReader.readLine(BufferedReader.java:299) - locked 0x02ad2a40 (a java.io.InputStreamReader) at java.io.BufferedReader.readLine(BufferedReader.java:362) at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:139) Thread-0 prio=6 tid=0x48ee9ba0 nid=0x1fac runnable [0x4925f000..0x4925fd68] at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:194) at java.io.BufferedInputStream.read1(BufferedInputStream.java:254) at java.io.BufferedInputStream.read(BufferedInputStream.java:313) - locked 0x02ce0058 (a java.io.BufferedInputStream) at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411) at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453) at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183) - locked 0x02ce0078 (a java.io.InputStreamReader) at java.io.InputStreamReader.read(InputStreamReader.java:167) at java.io.BufferedReader.fill(BufferedReader.java:136) at java.io.BufferedReader.readLine(BufferedReader.java:299) - locked 0x02ce0078 (a java.io.InputStreamReader) at java.io.BufferedReader.readLine(BufferedReader.java:362) at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:152) Low Memory Detector daemon prio=6 tid=0x00a952f8 nid=0xecc runnable [0x..0x] CompilerThread0 daemon prio=10 tid=0x00a94028 nid=0x1d30 waiting on condition [0x..0x48b9f848] Signal Dispatcher daemon prio=10 tid=0x00a93308 nid=0x1a7c waiting on condition [0x..0x] Finalizer daemon prio=8 tid=0x00a8a230 nid=0x161c in Object.wait() [0x48b1f000..0x48b1fc68] at java.lang.Object.wait(Native Method) - waiting on 0x079a2d28 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116) - locked 0x079a2d28 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) Reference Handler daemon prio=10 tid=0x00a88dc0 nid=0x1e9c in Object.wait() [0x0099f000..0x0099fce8] at java.lang.Object.wait(Native Method) - waiting on 0x079a2da8 (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:474) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116) - locked 0x079a2da8 (a java.lang.ref.Reference$Lock) main prio=6 tid=0x00036c30 nid=0x1e5c runnable [0x0007f000..0x0007fc3c] at java.lang.ProcessImpl.waitFor(Native Method) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:98) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:60) at org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:588) at org.apache.maven.surefire.booter.SurefireBooter.forkSuites(SurefireBooter.java:431) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkOnce(SurefireBooter.java:331) at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:217) at
[jira] Commented: (TUSCANY-2093) Hangs in osgi itests
[ https://issues.apache.org/jira/browse/TUSCANY-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579801#action_12579801 ] ant elder commented on TUSCANY-2093: It looks like two java.exe processes get started up and that previous thread dump is only from one, i've tried using the JSE6 jstack utility which gives the following dump for the other java.exe process. Note jstack hangs when i ask for a dump of that process and doesn't produce the dump until i kill the other java.exe process, i don't know if that changes the dump in a significant way. Full thread dump Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode): Configuration Updater daemon prio=6 tid=0x1787c400 nid=0x142c in Object.wait() [0x17e6f000..0x17e6fd14] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0x04090670 (a java.util.LinkedList) at java.lang.Object.wait(Object.java:485) at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:69) - locked 0x04090670 (a java.util.LinkedList) SCR Component Actor daemon prio=6 tid=0x17868800 nid=0x73c in Object.wait() [0x17e1f000..0x17e1fd94] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0x040906f8 (a java.util.LinkedList) at java.lang.Object.wait(Object.java:485) at org.apache.felix.scr.impl.ComponentActorThread.run(ComponentActorThread.java:63) - locked 0x040906f8 (a java.util.LinkedList) Felix Shell TUI daemon prio=6 tid=0x1784a000 nid=0xa74 runnable [0x17dcf000..0x17dcfa14] java.lang.Thread.State: RUNNABLE at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:260) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:109) - locked 0x03d7a338 (a java.io.BufferedOutputStream) at java.io.PrintStream.write(PrintStream.java:430) - locked 0x03d710a0 (a java.io.PrintStream) at java.io.PrintStream.write(PrintStream.java:430) - locked 0x03df4598 (a org.apache.maven.surefire.util.TeeStream) at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202) at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272) at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:85) - locked 0x03df7998 (a java.io.OutputStreamWriter) at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:168) at java.io.PrintStream.write(PrintStream.java:477) - locked 0x03df4598 (a org.apache.maven.surefire.util.TeeStream) at java.io.PrintStream.print(PrintStream.java:619) at org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java:133) at java.lang.Thread.run(Thread.java:619) FelixPackageAdmin daemon prio=6 tid=0x17872800 nid=0x1634 in Object.wait() [0x17d7f000..0x17d7fa94] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0x0406ce10 (a org.apache.felix.framework.PackageAdminImpl) at java.lang.Object.wait(Object.java:485) at org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:247) - locked 0x0406ce10 (a org.apache.felix.framework.PackageAdminImpl) at java.lang.Thread.run(Thread.java:619) FelixStartLevel daemon prio=6 tid=0x17827c00 nid=0x168 in Object.wait() [0x17d2f000..0x17d2fb14] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0x0406db30 (a java.util.ArrayList) at java.lang.Object.wait(Object.java:485) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:239) - locked 0x0406db30 (a java.util.ArrayList) at java.lang.Thread.run(Thread.java:619) FelixDispatchQueue prio=6 tid=0x17827400 nid=0xd98 in Object.wait() [0x17cdf000..0x17cdfb94] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0x0406cf28 (a java.util.ArrayList) at java.lang.Object.wait(Object.java:485) at org.apache.felix.framework.util.EventDispatcher.run(EventDispatcher.java:794) - locked 0x0406cf28 (a java.util.ArrayList) at org.apache.felix.framework.util.EventDispatcher.access$000(EventDispatcher.java:42) at org.apache.felix.framework.util.EventDispatcher$1.run(EventDispatcher.java:94) at java.lang.Thread.run(Thread.java:619) Low Memory Detector daemon prio=6 tid=0x16b7e800 nid=0x1c98 runnable [0x..0x] java.lang.Thread.State: RUNNABLE CompilerThread0 daemon prio=10
[jira] Commented: (TUSCANY-2097) Build errors in itest/osgi-tuscany
[ https://issues.apache.org/jira/browse/TUSCANY-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579816#action_12579816 ] ant elder commented on TUSCANY-2097: Do you have any orphaned java processes still running from a previous run? I've seen errors similar to this when thats happened, using the task monitor and killing any left over java.exe processes has fixed it. Build errors in itest/osgi-tuscany -- Key: TUSCANY-2097 URL: https://issues.apache.org/jira/browse/TUSCANY-2097 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Affects Versions: Java-SCA-Next Environment: Windows, Sun JDK 1.5.0_14 Reporter: Simon Nash Fix For: Java-SCA-Next Attachments: jira2097.log Here is a summary of the build errors I am seeing. I will attach my full build log to this JIRA. 1. revision.location error creating archive. This seems to show up on every test, and it does not seem to cause a hard failure in the test. java.io.FileNotFoundException: F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany- test\.felix.test\bundle1\version0.0\revision.location (The system cannot find th e file specified) ERROR: org.apache.felix.framework.cache.BundleCache: Error creating archive. (ja va.io.FileNotFoundException: F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany-te st\.felix.test\bundle1\version0.0\revision.location (The system cannot find the file specified)) 2. InvocationTargetException in CalculatorRMIReferencetestCase. java.lang.reflect.InvocationTargetException . Caused by: java.rmi.server.ExportException: Port already in use: 8099; nested ex ception is: java.net.BindException: Address already in use: JVM_Bind 3. Various errors in testOSGiTuscany_BindingWS - ERROR: org.apache.felix.framework.cache.BundleArchive: Unable to delete archi ve directory - F:\tuscany63\sca\itest\osgi-tuscany\osgi-tuscany-test\.felix.test \bundle5 java.util.zip.ZipException: The system cannot find the file specified org.osgi.framework.BundleException: Could not create bundle object. . Caused by: java.util.zip.ZipException: The system cannot find the file specified -- 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-2093) Hangs in osgi itests
[ https://issues.apache.org/jira/browse/TUSCANY-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579847#action_12579847 ] ant elder commented on TUSCANY-2093: As an fyi with the latest IBM 1.6 JDK the tests work ok for me, with the Sun 1.6 or any 1.5 JDK i get the hangs. Hangs in osgi itests Key: TUSCANY-2093 URL: https://issues.apache.org/jira/browse/TUSCANY-2093 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next I get hangs running various of the osgi itests, the test run part way through then just appear to hang for ever, no IO or CPU activity on the process. Eg, the output on the console for some hangs are: Running org.apache.tuscany.sca.test.osgi.tuscany.OSGiSupplyChainTestCase - Run tests from : ../../../samples/osgi-supplychain Loaded Tuscany, time taken = 31625 ms Running test null(supplychain.SupplyChainClientTestCase) Started OSGi bundle with activator OSGiCustomerImpl Started OSGi bundle with activator OSGiShipperImpl another: [INFO] Building Apache Tuscany OSGi Contribution tests [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 1 source file to C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 4 source files to C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\surefire-reports --- T E S T S --- Running org.apache.tuscany.sca.contribution.osgi.test.OSGiResolverTestCase - Created supplychain.customer.JavaCustomerComponentImpl using classloader 6.0 Created supplychain.retailer.JavaRetailerComponentImpl using classloader 7.0 Created supplychain.warehouse.JavaWarehouseComponentImpl using classloader 8.0 Created supplychain.shipper.JavaShipperComponentImpl using classloader 9.0 another: Running supplychain.wiring.DSWiring1TestCase - Main thread Thread[main,5,main] Created OSGiCustomerComponentImpl [EMAIL PROTECTED] Activated OSGiCustomerComponentImpl bundle OSGiCustomerComponentImpl.purchaseBooks, retailer1 is [Proxy - [EMAIL PROTECTED] Activated OSGiRetailerComponentImpl bundle Activated OSGiRetailerComponentImpl bundle OSGiRetailerComponentImpl.submitOrder , warehouse is [Proxy - [EMAIL PROTECTED] JavaWarehouseComponentImpl.fulfillOrder : shipper is [Proxy - [EMAIL PROTECTED] Activated OSGiShipperComponentImpl bundle Activated OSGiShipperComponentImpl bundle OSGiShipperComponentImpl.processShipment, customer is [Proxy - [EMAIL PROTECTED] This is easily recreateable so i can help debug, just right now i'm not sure where to look. -- 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-1974) Chat webapp sample misses chat messages
[ https://issues.apache.org/jira/browse/TUSCANY-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-1974: --- Fix Version/s: (was: Java-SCA-Next) Java-SCA-1.2 Chat webapp sample misses chat messages --- Key: TUSCANY-1974 URL: https://issues.apache.org/jira/browse/TUSCANY-1974 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.1 Environment: Tuscany 1.1 RC1 RHEL5 IBM JDK 1.5 Tested Firefox 2.0.0.11 and 3.0 beta2 Reporter: Jean-Sebastien Delfino Assignee: ant elder Fix For: Java-SCA-1.2 To reproduce the issue: Deploy the Chat webapp to Tomcat and open it in Firefox enter nickname: test1, text: 1 nothing is logged, the message seems to be lost enter text: 2, then 2 is logged Another weird issue: open another window enter nickname: test2, text: a again 'a' is lost enter text b, this time b is logged Go back to the first window enter several text messages they are logged in the first window but none of them is logged in the second window The chat application does not seem to really work. -- 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-2093) Hangs in osgi itests
Hangs in osgi itests Key: TUSCANY-2093 URL: https://issues.apache.org/jira/browse/TUSCANY-2093 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next I get hangs running various of the osgi itests, the test run part way through then just appear to hang for ever, no IO or CPU activity on the process. Eg, the output on the console for some hangs are: Running org.apache.tuscany.sca.test.osgi.tuscany.OSGiSupplyChainTestCase - Run tests from : ../../../samples/osgi-supplychain Loaded Tuscany, time taken = 31625 ms Running test null(supplychain.SupplyChainClientTestCase) Started OSGi bundle with activator OSGiCustomerImpl Started OSGi bundle with activator OSGiShipperImpl another: [INFO] Building Apache Tuscany OSGi Contribution tests [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 1 source file to C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Compiling 4 source files to C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\Tuscany\SVN\LATEST\itest\osgi-contribution\contribution-test\target\surefire-reports --- T E S T S --- Running org.apache.tuscany.sca.contribution.osgi.test.OSGiResolverTestCase - Created supplychain.customer.JavaCustomerComponentImpl using classloader 6.0 Created supplychain.retailer.JavaRetailerComponentImpl using classloader 7.0 Created supplychain.warehouse.JavaWarehouseComponentImpl using classloader 8.0 Created supplychain.shipper.JavaShipperComponentImpl using classloader 9.0 another: Running supplychain.wiring.DSWiring1TestCase - Main thread Thread[main,5,main] Created OSGiCustomerComponentImpl [EMAIL PROTECTED] Activated OSGiCustomerComponentImpl bundle OSGiCustomerComponentImpl.purchaseBooks, retailer1 is [Proxy - [EMAIL PROTECTED] Activated OSGiRetailerComponentImpl bundle Activated OSGiRetailerComponentImpl bundle OSGiRetailerComponentImpl.submitOrder , warehouse is [Proxy - [EMAIL PROTECTED] JavaWarehouseComponentImpl.fulfillOrder : shipper is [Proxy - [EMAIL PROTECTED] Activated OSGiShipperComponentImpl bundle Activated OSGiShipperComponentImpl bundle OSGiShipperComponentImpl.processShipment, customer is [Proxy - [EMAIL PROTECTED] This is easily recreateable so i can help debug, just right now i'm not sure where to look. -- 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] Closed: (TUSCANY-1950) Calculator-script produces etrenuous *sys-package-mgr* output.
[ https://issues.apache.org/jira/browse/TUSCANY-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-1950. -- Resolution: Fixed r637375 has a work around fix for this by setting the cachedir to a temporary folder if the Jython system properties are not set. This actually makes even more *sys-package-mgr* messages the first time a jython script is run as the cachedir gets initialized, but subsequent runs then don't get any messages. Calculator-script produces etrenuous *sys-package-mgr* output. --- Key: TUSCANY-1950 URL: https://issues.apache.org/jira/browse/TUSCANY-1950 Project: Tuscany Issue Type: Improvement Affects Versions: Java-SCA-1.1 Environment: All Reporter: Simon Laws Priority: Minor Fix For: Java-SCA-1.2 s\calculator-scriptant run Buildfile: build.xml run: [java] 3 + 2=5.0 [java] 3 - 2=1.0 [java] *sys-package-mgr*: can't create package cache dir, 'C:\simon\tuscany \release\sca-r1.1-rc0\tuscany-sca-1.1-incubating-SNAPSHOT\lib\jython-2.2.jar\cac hedir\packages' [java] 3 * 2=6.0 [java] 3 / 2=1.5 Mail from ant on this subject during R1.1 release... Is thats the *sys-package-mgr* messages? If so they've been there in all the past releases and i think we should just ignore them for now (unless someone wants to try?). Jython works fine like this, just runs a little slower. You can fix it by setting the python.home system property, ideally we'd do that in the script extension and set it up so it only has the application classes visable in the classloader that jython uses to create the package cache. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2068) itest/osgi-implementation is broken due to recent changes
[ https://issues.apache.org/jira/browse/TUSCANY-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2068: -- Assignee: ant elder (was: Rajini Sivaram) itest/osgi-implementation is broken due to recent changes - Key: TUSCANY-2068 URL: https://issues.apache.org/jira/browse/TUSCANY-2068 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Reporter: Rajini Sivaram Assignee: ant elder Fix For: Java-SCA-1.2 Attachments: implementation.osgi.txt Recent changes related to Pass-by-value and callbacks have broken many of the itest/osgi-implementationt tests. The tests need to be added back to the itest pom to ensure that breakages are caught earlier. -- 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] Closed: (TUSCANY-2068) itest/osgi-implementation is broken due to recent changes
[ https://issues.apache.org/jira/browse/TUSCANY-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2068. -- Resolution: Fixed Patch applied in r637134, thanks for the fix Graham. Note, i still get a a hang when i run the itest/osgi-implementation tests, this happens everytime and with or without this fix applied. itest/osgi-implementation is broken due to recent changes - Key: TUSCANY-2068 URL: https://issues.apache.org/jira/browse/TUSCANY-2068 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Reporter: Rajini Sivaram Assignee: ant elder Fix For: Java-SCA-1.2 Attachments: implementation.osgi.txt Recent changes related to Pass-by-value and callbacks have broken many of the itest/osgi-implementationt tests. The tests need to be added back to the itest pom to ensure that breakages are caught earlier. -- 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-2074) Component Service not coming up.
[
https://issues.apache.org/jira/browse/TUSCANY-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578197#action_12578197
]
ant elder commented on TUSCANY-2074:
When i try deploying that war I get the following errors on the Tomcat log, do
you see these?
I ask becuase previously you've said you do see the Tuscany IinitContextPath
and Added Servlet mapping which indicates success so i wonder if thats not
exactly the same war that I have?
13-Mar-2008 09:23:01 org.apache.tuscany.sca.contribution.processor.ValidatingXML
StreamReader$1 error
WARNING: XMLSchema validation problem in: file:/C:/Tomcat/apache-tomcat-6.0.10/w
ebapps/TwoWS/WEB-INF/classes/RunTime.composite, line: 14, column: 9
cvc-complex-type.2.3: Element '{http://www.osoa.org/xmlns/sca/1.0}service' canno
t have character [children], because the type's content type is element-only.
13-Mar-2008 09:23:01 org.apache.tuscany.sca.contribution.processor.ValidatingXML
StreamReader$1 error
WARNING: XMLSchema validation problem in: file:/C:/Tomcat/apache-tomcat-6.0.10/w
ebapps/TwoWS/WEB-INF/classes/TwoWS.composite, line: 47, column: 5
cvc-complex-type.4: Attribute 'promote' must appear on element 'reference'.
Component Service not coming up.
Key: TUSCANY-2074
URL: https://issues.apache.org/jira/browse/TUSCANY-2074
Project: Tuscany
Issue Type: Test
Components: Java SCA Tomcat Integration
Affects Versions: Java-SCA-1.1
Environment: Windows , Tomcat 5.5 , Apache tuscany 1.1 , Java 5.0
Reporter: Sandeep Raman
Priority: Critical
Fix For: Java-SCA-1.1
Attachments: TwoWS.war
Original Estimate: 72h
Remaining Estimate: 72h
summary of the Issue:
I have an issue with the component service not coming up. below mentioned
is my scenario.
I have a JSP (default.jsp) which does the following:
%@ page import=org.apache.tuscany.sca.host.embedded.SCADomain%
%@ page contentType=text/html;charset=UTF-8 language=java %
%
SCADomain scaDomain = SCADomain.newInstance(RunTime.composite);
System.out.println(RunTime Composite Started);
%
and the Runtime.composite is as follows:
component name=TwoWSService
implementation.java class=eai.Compose /
service name=Compose
interface=http://eai#wsdl.interface(TwoWSService) /
binding.ws uri=http://localhost:8080/TwoWSService; /
/service
/component
Now I create a war of all my Java classes , wsdl , composite files and
with the default.jsp as the default run target.
This war gets deployed in tomcat and the jsp page comes up. It creates a
new instance of Runtime.composite too , but it doesnt seem to be starting
the
component service which i have mentioned in the composite file :
binding.ws uri=http://localhost:8080/TwoWSService; /.
--
Following Mails explain the scenario::
I see everything in console, like
INFO: initContextPath: /TwoWS
INFO: Added Servlet mapping: /TwoWSService
Even if i try to Run my low lying services which i am composing it Runs
fine and can see the output in the console..
The issue is the wsdl url which i need to publish and not able to find it
anywhere.
As per the samples , in my case
http://localhost:8080/TwoWS/TwoWSService?wsdl should point to my wsdl, but
tht doesnt seem to exist
Regards
Sandeep
ant elder [EMAIL PROTECTED] wrote on 03/11/2008 05:03:44 PM:
A difference between this and the calculator sample is the way the jsp
gets
the SCADomain object, the Tuscany jsp samples do:
%
SCADomain scaDomain = (SCADomain) application.getAttribute(
org.apache.tuscany.sca.SCADomain);
CalculatorService calculatorService =
(CalculatorService)scaDomain.getService(CalculatorService.class,
CalculatorServiceComponent);
%
whereas this code does:
%
SCADomain scaDomain = SCADomain.newInstance(RunTime.composite);
System.out.println(RunTime Composite Started);
%
I've never tried that so i don't know if it will work.
If Tuscany is activating the WS endpoint you should see the messages on
the
tomcat console about it, for example, with the calculator ws sample you
see:
INFO: ContextPath: /sample-calculator-ws-webapp
and
INFO: Added Servlet mapping: /AddServiceComponent
so you can add those and you tomcat host and port to get
http://localhost:8080//sample-calculator-ws-webapp/AddServiceComponent
You can test thats working by appending ?wsdl to that and url and
entering
it in a browser which should return the wsdl document for the service.
If you don't see the above messages then
[jira] Closed: (TUSCANY-2075) Test for setting a property value of a complex type within a component
[ https://issues.apache.org/jira/browse/TUSCANY-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2075. -- Resolution: Fixed Fix Version/s: (was: Java-SCA-1.2) Java-SCA-Next Patch applied, thanks very much for the code Vamsavardhana! Test for setting a property value of a complex type within a component -- Key: TUSCANY-2075 URL: https://issues.apache.org/jira/browse/TUSCANY-2075 Project: Tuscany Issue Type: Test Components: Java SCA Integration Tests Affects Versions: Java-SCA-1.2 Reporter: Vamsavardhana Reddy Assignee: ant elder Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2075.patch The properties tests do not include an explicit test for setting a property value of a complex type within a component. Ref section 1.6.1.1 of Assembly spec. property name=complexBar source=$complexFoo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2075) Test for setting a property value of a complex type within a component
[ https://issues.apache.org/jira/browse/TUSCANY-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2075: -- Assignee: ant elder Test for setting a property value of a complex type within a component -- Key: TUSCANY-2075 URL: https://issues.apache.org/jira/browse/TUSCANY-2075 Project: Tuscany Issue Type: Test Components: Java SCA Integration Tests Affects Versions: Java-SCA-1.2 Reporter: Vamsavardhana Reddy Assignee: ant elder Priority: Minor Fix For: Java-SCA-1.2 Attachments: TUSCANY-2075.patch The properties tests do not include an explicit test for setting a property value of a complex type within a component. Ref section 1.6.1.1 of Assembly spec. property name=complexBar source=$complexFoo -- 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-2074) Component Service not coming up.
[ https://issues.apache.org/jira/browse/TUSCANY-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578244#action_12578244 ] ant elder commented on TUSCANY-2074: Lets first fix some of those error messages: - deleting servlet-api-2.5.jar from the web-inf/lib folder fixes the first - in RunTime.composite there's an XML syntax error on line 12: interface= should be interface.wsdl interface= - in TwoWS.composite the reference at the bottom (line 47) is missing the promote attribute and should be: reference name=StockQuoteService promote=StockServiceComponent/StockQuoteService requires =authentication (guessing StockQuoteService is the service name as i don't have the source code) With those changes the application starts up with no errors. Going to the url http://localhost:8080/TwoWS/ now gives: org.osoa.sca.ServiceRuntimeException: java.lang.ClassCastException: org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLInterfaceImpl 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 helloworld.RunTimeServlet.doGet(RunTimeServlet.java:25) That looks like it could be due to the way the application is using several different SCADomain instances, i'll debug it a bit futher but could you comment on if there's a specific reason that the jsp and RunTimeServlet are creating new SCADomain instances? Component Service not coming up. Key: TUSCANY-2074 URL: https://issues.apache.org/jira/browse/TUSCANY-2074 Project: Tuscany Issue Type: Test Components: Java SCA Tomcat Integration Affects Versions: Java-SCA-1.1 Environment: Windows , Tomcat 5.5 , Apache tuscany 1.1 , Java 5.0 Reporter: Sandeep Raman Priority: Critical Fix For: Java-SCA-1.1 Attachments: TwoWS.war Original Estimate: 72h Remaining Estimate: 72h summary of the Issue: I have an issue with the component service not coming up. below mentioned is my scenario. I have a JSP (default.jsp) which does the following: %@ page import=org.apache.tuscany.sca.host.embedded.SCADomain% %@ page contentType=text/html;charset=UTF-8 language=java % % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % and the Runtime.composite is as follows: component name=TwoWSService implementation.java class=eai.Compose / service name=Compose interface=http://eai#wsdl.interface(TwoWSService) / binding.ws uri=http://localhost:8080/TwoWSService; / /service /component Now I create a war of all my Java classes , wsdl , composite files and with the default.jsp as the default run target. This war gets deployed in tomcat and the jsp page comes up. It creates a new instance of Runtime.composite too , but it doesnt seem to be starting the component service which i have mentioned in the composite file : binding.ws uri=http://localhost:8080/TwoWSService; /. -- Following Mails explain the scenario:: I see everything in console, like INFO: initContextPath: /TwoWS INFO: Added Servlet mapping: /TwoWSService Even if i try to Run my low lying services which i am composing it Runs fine and can see the output in the console.. The issue is the wsdl url which i need to publish and not able to find it anywhere. As per the samples , in my case http://localhost:8080/TwoWS/TwoWSService?wsdl should point to my wsdl, but tht doesnt seem to exist Regards Sandeep ant elder [EMAIL PROTECTED] wrote on 03/11/2008 05:03:44 PM: A difference between this and the calculator sample is the way the jsp gets the SCADomain object, the Tuscany jsp samples do: % SCADomain scaDomain = (SCADomain) application.getAttribute( org.apache.tuscany.sca.SCADomain); CalculatorService calculatorService = (CalculatorService)scaDomain.getService(CalculatorService.class, CalculatorServiceComponent); % whereas this code does: % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % I've never tried that so i don't know if it will work. If Tuscany is activating the WS endpoint you should see the messages on the tomcat console about it, for example, with the calculator ws sample you see: INFO: ContextPath: /sample-calculator-ws-webapp and INFO: Added Servlet mapping: /AddServiceComponent so you can add those and you tomcat host and port to
[jira] Commented: (TUSCANY-2074) Component Service not coming up.
[ https://issues.apache.org/jira/browse/TUSCANY-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578254#action_12578254 ] ant elder commented on TUSCANY-2074: Two other fixes: - the meta-inf/sca-contribution.xml should be using the namespace http://helloworld; instead of http://sample; to match trhe .composite file - in RunTime.composite the interface.wsdl element points to a non-existent wsdl portType, i've just deleted the interface.wsdl element Fixing those and going to http://localhost:8080/TwoWS/RunTimeServlet (should i be usingthe jsp or servlet url?) gives this warning: WARNING: Promoted component reference not found: StockServiceComponent/StockQuoteService I don't have the src code to see what the service name should be? Component Service not coming up. Key: TUSCANY-2074 URL: https://issues.apache.org/jira/browse/TUSCANY-2074 Project: Tuscany Issue Type: Test Components: Java SCA Tomcat Integration Affects Versions: Java-SCA-1.1 Environment: Windows , Tomcat 5.5 , Apache tuscany 1.1 , Java 5.0 Reporter: Sandeep Raman Priority: Critical Fix For: Java-SCA-1.1 Attachments: TwoWS.war Original Estimate: 72h Remaining Estimate: 72h summary of the Issue: I have an issue with the component service not coming up. below mentioned is my scenario. I have a JSP (default.jsp) which does the following: %@ page import=org.apache.tuscany.sca.host.embedded.SCADomain% %@ page contentType=text/html;charset=UTF-8 language=java % % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % and the Runtime.composite is as follows: component name=TwoWSService implementation.java class=eai.Compose / service name=Compose interface=http://eai#wsdl.interface(TwoWSService) / binding.ws uri=http://localhost:8080/TwoWSService; / /service /component Now I create a war of all my Java classes , wsdl , composite files and with the default.jsp as the default run target. This war gets deployed in tomcat and the jsp page comes up. It creates a new instance of Runtime.composite too , but it doesnt seem to be starting the component service which i have mentioned in the composite file : binding.ws uri=http://localhost:8080/TwoWSService; /. -- Following Mails explain the scenario:: I see everything in console, like INFO: initContextPath: /TwoWS INFO: Added Servlet mapping: /TwoWSService Even if i try to Run my low lying services which i am composing it Runs fine and can see the output in the console.. The issue is the wsdl url which i need to publish and not able to find it anywhere. As per the samples , in my case http://localhost:8080/TwoWS/TwoWSService?wsdl should point to my wsdl, but tht doesnt seem to exist Regards Sandeep ant elder [EMAIL PROTECTED] wrote on 03/11/2008 05:03:44 PM: A difference between this and the calculator sample is the way the jsp gets the SCADomain object, the Tuscany jsp samples do: % SCADomain scaDomain = (SCADomain) application.getAttribute( org.apache.tuscany.sca.SCADomain); CalculatorService calculatorService = (CalculatorService)scaDomain.getService(CalculatorService.class, CalculatorServiceComponent); % whereas this code does: % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % I've never tried that so i don't know if it will work. If Tuscany is activating the WS endpoint you should see the messages on the tomcat console about it, for example, with the calculator ws sample you see: INFO: ContextPath: /sample-calculator-ws-webapp and INFO: Added Servlet mapping: /AddServiceComponent so you can add those and you tomcat host and port to get http://localhost:8080//sample-calculator-ws-webapp/AddServiceComponent You can test thats working by appending ?wsdl to that and url and entering it in a browser which should return the wsdl document for the service. If you don't see the above messages then something is going wrong and the WS endpoint is not being registered correctly. ...ant On Tue, Mar 11, 2008 at 11:07 AM, Sandeep Raman [EMAIL PROTECTED] wrote: Hi, I have done pretty much in the same way as the sample. i need to see my wsdl , my component service which is running . I am not able to figure out the URL for the wsdl file. I am stuck up there, since all my
[jira] Closed: (TUSCANY-1829) Maven Clean from SVN repository failing
[ https://issues.apache.org/jira/browse/TUSCANY-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-1829. -- Resolution: Fixed I've just tried this with the current trunk code and a complete build with an empty local repository worked ok so I'm going to close this as fixed. Maven Clean from SVN repository failing --- Key: TUSCANY-1829 URL: https://issues.apache.org/jira/browse/TUSCANY-1829 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.1 Environment: Windows XP SP2, JDK 1.5.0_13, Maven 2.0.7 Reporter: Shane Blake Fix For: Java-SCA-Next svn co https://svn.apache.org/repos/asf/incubator/tuscany/java/; mvn clean; [INFO] [INFO] Building Apache Tuscany SCA BPEL Implementation Extension [INFO]task-segment: [clean] [INFO] Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/tuscany/sca/tuscany-maven-wsdl2java/1.1-incubating-SNAPSHOT/tuscany-maven-wsdl2java-1.1-incubating-SNAPSHOT.jar Downloading: http://snapshots.repository.codehaus.org/org/apache/tuscany/sca/tuscany-maven-wsdl2java/1.1-incubating-SNAPSHOT/tuscany-maven-wsdl2java-1.1-incubating-SNAPSHOT.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download t he artifact from any repository -- 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] Closed: (TUSCANY-2051) JMS binding: Exception while sending a FaultReply
[
https://issues.apache.org/jira/browse/TUSCANY-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-2051.
--
Resolution: Fixed
There was some more discussion about this on the ML:
http://apache.markmail.org/message/kmdzotqlosermrve?q=TUSCANY-2051
The JMS binding has been updated so exceptions get sent back in a JMS object
message with a property set to indicate its a fault response, and while not
completly perfect that fixes the reported problem so I'll close this JIRA.
JMS binding: Exception while sending a FaultReply
-
Key: TUSCANY-2051
URL: https://issues.apache.org/jira/browse/TUSCANY-2051
Project: Tuscany
Issue Type: Bug
Components: Java SCA JMS Binding Extension
Affects Versions: Java-SCA-1.1
Environment: Win XP
Reporter: Ph.Konradi
Fix For: Java-SCA-Next
Class: JMSBindingListener.java
Method: public void onMessage(Message requestJMSMsg)
calling sendFaultReply(requestJMSMsg, e) fails
with the following exception:
Exception while processing message: java.lang.ClassCastException:
org.apache.tuscany.sca.binding.jms.impl.JMSBindingException
java.lang.ClassCastException:
org.apache.tuscany.sca.binding.jms.impl.JMSBindingException
at
org.apache.tuscany.sca.binding.jms.provider.JMSMessageProcessorImpl.createXMLJMSMessage(JMSMessageProcessorImpl.java:140)
at
org.apache.tuscany.sca.binding.jms.provider.JMSMessageProcessorImpl.insertPayloadIntoJMSMessage(JMSMessageProcessorImpl.java:85)
at
org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.sendReply(JMSBindingListener.java:125)
at
org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.sendFaultReply(JMSBindingListener.java:152)
at
org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.onMessage(JMSBindingListener.java:65)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:854)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:99)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:166)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:117)
at
org.apache.activemq.thread.PooledTaskRunner.access$100(PooledTaskRunner.java:26)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:44)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
A quick, but not optimal, resolution would be:
change: sendFaultReply(requestJMSMsg, e)
to: sendFaultReply(requestJMSMsg, new Object[]{e})
--
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] Closed: (TUSCANY-2054) sample-chat does not currentl send messages in Tomcat
[ https://issues.apache.org/jira/browse/TUSCANY-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2054. -- Resolution: Duplicate Duplicate of TUSCANY-1974 and as thats where more details are I'll close this one as DUP. sample-chat does not currentl send messages in Tomcat - Key: TUSCANY-2054 URL: https://issues.apache.org/jira/browse/TUSCANY-2054 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-Next Reporter: Luciano Resende Fix For: Java-SCA-1.2, Java-SCA-Next -- 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] Closed: (TUSCANY-1389) published DTD for composite XML Schema needed/useful
[ https://issues.apache.org/jira/browse/TUSCANY-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-1389. -- Resolution: Fixed Its been about 9 months so I'll assume the above did solve the problem and close this. Feel free to re-open if necessary. published DTD for composite XML Schema needed/useful Key: TUSCANY-1389 URL: https://issues.apache.org/jira/browse/TUSCANY-1389 Project: Tuscany Issue Type: Improvement Components: Java SCA BigBank Sample, Java SCA Core Runtime, Java SCA Samples Affects Versions: Java-SCA-0.90 Environment: java Reporter: James Tomkinson Assignee: Luciano Resende Priority: Minor Fix For: Java-SCA-Next Attachments: addattributes_knownfromDTD.jpg, addchild_knownfromDTD.jpg, openwithxmleditor.jpg Samples should supply a DOCTYPE in *.composite xml files, that points to a stored DTD, so that XML editing tools can be used to create/edit/validate XML schema. This will enhance productivity/accuracy. Example for Hibernate: !DOCTYPE hibernate-configuration PUBLIC -//Hibernate/Hibernate Configuration DTD 3.0//EN http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd; -- 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-2074) Component Service not coming up.
[ https://issues.apache.org/jira/browse/TUSCANY-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-2074: --- Fix Version/s: (was: Java-SCA-1.1) Java-SCA-Next Component Service not coming up. Key: TUSCANY-2074 URL: https://issues.apache.org/jira/browse/TUSCANY-2074 Project: Tuscany Issue Type: Test Components: Java SCA Tomcat Integration Affects Versions: Java-SCA-1.1 Environment: Windows , Tomcat 5.5 , Apache tuscany 1.1 , Java 5.0 Reporter: Sandeep Raman Priority: Critical Fix For: Java-SCA-Next Attachments: TwoWS.war Original Estimate: 72h Remaining Estimate: 72h summary of the Issue: I have an issue with the component service not coming up. below mentioned is my scenario. I have a JSP (default.jsp) which does the following: %@ page import=org.apache.tuscany.sca.host.embedded.SCADomain% %@ page contentType=text/html;charset=UTF-8 language=java % % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % and the Runtime.composite is as follows: component name=TwoWSService implementation.java class=eai.Compose / service name=Compose interface=http://eai#wsdl.interface(TwoWSService) / binding.ws uri=http://localhost:8080/TwoWSService; / /service /component Now I create a war of all my Java classes , wsdl , composite files and with the default.jsp as the default run target. This war gets deployed in tomcat and the jsp page comes up. It creates a new instance of Runtime.composite too , but it doesnt seem to be starting the component service which i have mentioned in the composite file : binding.ws uri=http://localhost:8080/TwoWSService; /. -- Following Mails explain the scenario:: I see everything in console, like INFO: initContextPath: /TwoWS INFO: Added Servlet mapping: /TwoWSService Even if i try to Run my low lying services which i am composing it Runs fine and can see the output in the console.. The issue is the wsdl url which i need to publish and not able to find it anywhere. As per the samples , in my case http://localhost:8080/TwoWS/TwoWSService?wsdl should point to my wsdl, but tht doesnt seem to exist Regards Sandeep ant elder [EMAIL PROTECTED] wrote on 03/11/2008 05:03:44 PM: A difference between this and the calculator sample is the way the jsp gets the SCADomain object, the Tuscany jsp samples do: % SCADomain scaDomain = (SCADomain) application.getAttribute( org.apache.tuscany.sca.SCADomain); CalculatorService calculatorService = (CalculatorService)scaDomain.getService(CalculatorService.class, CalculatorServiceComponent); % whereas this code does: % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % I've never tried that so i don't know if it will work. If Tuscany is activating the WS endpoint you should see the messages on the tomcat console about it, for example, with the calculator ws sample you see: INFO: ContextPath: /sample-calculator-ws-webapp and INFO: Added Servlet mapping: /AddServiceComponent so you can add those and you tomcat host and port to get http://localhost:8080//sample-calculator-ws-webapp/AddServiceComponent You can test thats working by appending ?wsdl to that and url and entering it in a browser which should return the wsdl document for the service. If you don't see the above messages then something is going wrong and the WS endpoint is not being registered correctly. ...ant On Tue, Mar 11, 2008 at 11:07 AM, Sandeep Raman [EMAIL PROTECTED] wrote: Hi, I have done pretty much in the same way as the sample. i need to see my wsdl , my component service which is running . I am not able to figure out the URL for the wsdl file. I am stuck up there, since all my external requests need this wsdl URL to process, any help or suggestion will be highly appreciated Regards Sandeep Raman ant elder [EMAIL PROTECTED] wrote on 03/11/2008 02:28:13 PM: On Tue, Mar 11, 2008 at 3:38 AM, Sandeep Raman [EMAIL PROTECTED] wrote: Hi, I have an issue with the component service not coming up. below mentioned is my scenario. I have a JSP (default.jsp) which does the following: %@ page import=org.apache.tuscany.sca.host.embedded.SCADomain% %@ page
[jira] Closed: (TUSCANY-2079) workspace-admin tests fail with IOException
[ https://issues.apache.org/jira/browse/TUSCANY-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2079. -- Resolution: Fixed Fix Version/s: (was: Java-SCA-1.2) Java-SCA-Next Patch applied in r636811, thaks for the fix Jürgen. workspace-admin tests fail with IOException --- Key: TUSCANY-2079 URL: https://issues.apache.org/jira/browse/TUSCANY-2079 Project: Tuscany Issue Type: Test Affects Versions: Java-SCA-1.2 Environment: Windows XP, Sun Java 1.5 Reporter: Jürgen Schumacher Priority: Minor Fix For: Java-SCA-Next Attachments: tuscany-workspace-admin.patch org.apache.tuscany.sca.workspace.admin.impl.AdminTestCase fails with an IOException: org.osoa.sca.ServiceRuntimeException: java.io.FileNotFoundException: D:\Works\Ja va\Tuscany\java\sca\modules\workspace-admin\target\test-classes\workspace.xml (D er Vorgang ist bei einer Datei mit einem geöffneten Bereich, der einem Benutzer zugeordnet ist, nicht anwendbar) at org.apache.tuscany.sca.workspace.admin.impl.ContributionCollectionImp l.writeWorkspace(ContributionCollectionImpl.java:423) at org.apache.tuscany.sca.workspace.admin.impl.ContributionCollectionImp l.post(ContributionCollectionImpl.java:210) at org.apache.tuscany.sca.workspace.admin.impl.AdminTestCase.setUp(Admin TestCase.java:75) The geman message means something like This process is not applicable on a file with a open part associated to a user (actually, it does not make too much sense in german ...) There are two places in the code where writers/streams are not explicitly close. Closing them seems to help. See attached patch file. -- 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-1974) Chat webapp sample misses chat messages
[ https://issues.apache.org/jira/browse/TUSCANY-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578432#action_12578432 ] ant elder commented on TUSCANY-1974: fyi, the change in r636817 fixes an issue related to this problem. The remaining problem here is that Tuscany is getting the context path and servlet path incorrect so the urls used by the scaDomain.js script are incorrect. Chat webapp sample misses chat messages --- Key: TUSCANY-1974 URL: https://issues.apache.org/jira/browse/TUSCANY-1974 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.1 Environment: Tuscany 1.1 RC1 RHEL5 IBM JDK 1.5 Tested Firefox 2.0.0.11 and 3.0 beta2 Reporter: Jean-Sebastien Delfino Assignee: ant elder Fix For: Java-SCA-Next To reproduce the issue: Deploy the Chat webapp to Tomcat and open it in Firefox enter nickname: test1, text: 1 nothing is logged, the message seems to be lost enter text: 2, then 2 is logged Another weird issue: open another window enter nickname: test2, text: a again 'a' is lost enter text b, this time b is logged Go back to the first window enter several text messages they are logged in the first window but none of them is logged in the second window The chat application does not seem to really work. -- 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]
