[jira] Updated: (TUSCANY-2384) Message Conversion for Contribution Builders
[ https://issues.apache.org/jira/browse/TUSCANY-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2384: - Attachment: TUSCANY-2384-NEW.patch Message Conversion for Contribution Builders Key: TUSCANY-2384 URL: https://issues.apache.org/jira/browse/TUSCANY-2384 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Win XP SP2, JDK 1.5 Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2384-NEW.patch, TUSCANY-2384.patch Message Conversion were required for the Contribution Builders, where few instance of messages was found without using the messageID and resourcebundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2362) Fix for test failure in TUSCANY-2344 5 validation message
[ https://issues.apache.org/jira/browse/TUSCANY-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam closed TUSCANY-2362. Fix for test failure in TUSCANY-2344 5 validation message --- Key: TUSCANY-2362 URL: https://issues.apache.org/jira/browse/TUSCANY-2362 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2362-New.patch, TUSCANY-2362.patch Problems with the widget and resource validation testing were noticed. CouldNotResolveLocation doesn't seem to be raised. Noticed that the reason for the failure in CouldNotResolveLocation for implementation.resource and implementation.widget validation is due to the missed code while applying the patch for TUSCANY-2344 and 2345. The changes suggested in the patch does not seem to appear in the committed code. Raising this defect to apply the missed code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2345) NPE from implementation.resource for missing location attribute
[ https://issues.apache.org/jira/browse/TUSCANY-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam closed TUSCANY-2345. NPE from implementation.resource for missing location attribute --- Key: TUSCANY-2345 URL: https://issues.apache.org/jira/browse/TUSCANY-2345 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2345.patch java.lang.NullPointerException at org.apache.tuscany.sca.implementation.resource.provider.ResourceImplementationProvider.createInvoker(ResourceImplementationProvider.java:49) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:315) 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:125) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:182) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:195) 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 $Proxy0.get(Unknown Source) NPE is thrown from ResourceImplementationProvider, when the composite is provided with missing location attribute. Need to catch this exception and throw a meaningful message for the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2344) NPE from implementation.widget for missing location attribute
[ https://issues.apache.org/jira/browse/TUSCANY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam closed TUSCANY-2344. NPE from implementation.widget for missing location attribute - Key: TUSCANY-2344 URL: https://issues.apache.org/jira/browse/TUSCANY-2344 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2344.patch Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProvider.init(WidgetImplementationProvider.java:45) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:41) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:1) at org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyImplementationProviderFactory.createImplementationProvider(DefaultProviderFactoryExtensionPoint.java:292) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addImplementationProvider(CompositeActivatorImpl.java:463) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:973) ... 19 more NPE is thrown for missing location attribute We need a fix to catch this exception much before it reaches WidgetImplementationProvider. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2242: - Attachment: TUSCANY-2242.patch Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2242.patch Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://helloworld; xmlns:hw=http://helloworld; name=helloworldwsclient !-- A component with an embedded reference definition connecting to an external webservice The wsdl interface for the reference is derived from the information specified by the 'wsdlElement' -- component name=HelloTuscanyServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ reference name=helloWorldService binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)/ /reference /component !-- A component with a reference promoted as a composite reference -- component name=HelloWorldServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ /component reference name=HelloWorldService promote=HelloWorldServiceComponent/helloWorldService interface.java interface=helloworld.HelloWorldService / binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)/ /reference /composite Notice the NonExistentPort port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2242: - Patch Info: [Patch Available] Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2242.patch Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://helloworld; xmlns:hw=http://helloworld; name=helloworldwsclient !-- A component with an embedded reference definition connecting to an external webservice The wsdl interface for the reference is derived from the information specified by the 'wsdlElement' -- component name=HelloTuscanyServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ reference name=helloWorldService binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)/ /reference /component !-- A component with a reference promoted as a composite reference -- component name=HelloWorldServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ /component reference name=HelloWorldService promote=HelloWorldServiceComponent/helloWorldService interface.java interface=helloworld.HelloWorldService / binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)/ /reference /composite Notice the NonExistentPort port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part8.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5-NEW.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6-NEW.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7-NEW.patch, TUSCANY-2347-Part7.patch, TUSCANY-2347-Part8.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2242: - Attachment: (was: TUSCANY-2242.patch) Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://helloworld; xmlns:hw=http://helloworld; name=helloworldwsclient !-- A component with an embedded reference definition connecting to an external webservice The wsdl interface for the reference is derived from the information specified by the 'wsdlElement' -- component name=HelloTuscanyServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ reference name=helloWorldService binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)/ /reference /component !-- A component with a reference promoted as a composite reference -- component name=HelloWorldServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ /component reference name=HelloWorldService promote=HelloWorldServiceComponent/helloWorldService interface.java interface=helloworld.HelloWorldService / binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)/ /reference /composite Notice the NonExistentPort port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2242: - Patch Info: (was: [Patch Available]) I have removed the patch just to ensure that the complete build does not throw any issue. I had a bad experience recently with TUSCANY-2347 because of the same. Will be submitting the patch once i am sure that everything goes fine. Thanks, Ramkumar R Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://helloworld; xmlns:hw=http://helloworld; name=helloworldwsclient !-- A component with an embedded reference definition connecting to an external webservice The wsdl interface for the reference is derived from the information specified by the 'wsdlElement' -- component name=HelloTuscanyServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ reference name=helloWorldService binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)/ /reference /component !-- A component with a reference promoted as a composite reference -- component name=HelloWorldServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ /component reference name=HelloWorldService promote=HelloWorldServiceComponent/helloWorldService interface.java interface=helloworld.HelloWorldService / binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)/ /reference /composite Notice the NonExistentPort port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part9.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5-NEW.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6-NEW.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7-NEW.patch, TUSCANY-2347-Part7.patch, TUSCANY-2347-Part8.patch, TUSCANY-2347-Part9.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2242: - Attachment: TUSCANY-2242.patch Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2242.patch Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://helloworld; xmlns:hw=http://helloworld; name=helloworldwsclient !-- A component with an embedded reference definition connecting to an external webservice The wsdl interface for the reference is derived from the information specified by the 'wsdlElement' -- component name=HelloTuscanyServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ reference name=helloWorldService binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)/ /reference /component !-- A component with a reference promoted as a composite reference -- component name=HelloWorldServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ /component reference name=HelloWorldService promote=HelloWorldServiceComponent/helloWorldService interface.java interface=helloworld.HelloWorldService / binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)/ /reference /composite Notice the NonExistentPort port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2379) CompositeProcessor.java is calling promotedService.getService() instead of promotedService.getName() when writing out a composite file.
[
https://issues.apache.org/jira/browse/TUSCANY-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam updated TUSCANY-2379:
-
Attachment: TUSCANY-2379.patch
NOTE: Please apply the provided patch after the fixes for TUSCANY-2347 is
committed.
CompositeProcessor.java is calling promotedService.getService() instead of
promotedService.getName() when writing out a composite file.
---
Key: TUSCANY-2379
URL: https://issues.apache.org/jira/browse/TUSCANY-2379
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.2
Reporter: Richard Mah
Assignee: Ramkumar Ramalingam
Attachments: TUSCANY-2379.patch
CompositeProcessor.java is calling promotedService.getService() instead of
promotedService.getName() when writing out the promoted service to file.
Here is the snippet of code starting from line 546 (Revision 665831):
String promote;
if (promotedService != null) {
if (promotedService.getName() != null) {
promote = promotedComponent.getName() + '/' +
promotedService.getService();-Here is the
promotedService.getService() call
} else {
promote = promotedComponent.getName();
}
promotedService.getService() looks like it should be
promotedService.getName() instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2379) CompositeProcessor.java is calling promotedService.getService() instead of promotedService.getName() when writing out a composite file.
[
https://issues.apache.org/jira/browse/TUSCANY-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam updated TUSCANY-2379:
-
Patch Info: [Patch Available]
CompositeProcessor.java is calling promotedService.getService() instead of
promotedService.getName() when writing out a composite file.
---
Key: TUSCANY-2379
URL: https://issues.apache.org/jira/browse/TUSCANY-2379
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.2
Reporter: Richard Mah
Assignee: Ramkumar Ramalingam
Attachments: TUSCANY-2379.patch
CompositeProcessor.java is calling promotedService.getService() instead of
promotedService.getName() when writing out the promoted service to file.
Here is the snippet of code starting from line 546 (Revision 665831):
String promote;
if (promotedService != null) {
if (promotedService.getName() != null) {
promote = promotedComponent.getName() + '/' +
promotedService.getService();-Here is the
promotedService.getService() call
} else {
promote = promotedComponent.getName();
}
promotedService.getService() looks like it should be
promotedService.getName() instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2242: - Patch Info: [Patch Available] NOTE: Please apply the provided patch after the fixes for TUSCANY-2347 is committed. Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2242.patch Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://helloworld; xmlns:hw=http://helloworld; name=helloworldwsclient !-- A component with an embedded reference definition connecting to an external webservice The wsdl interface for the reference is derived from the information specified by the 'wsdlElement' -- component name=HelloTuscanyServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ reference name=helloWorldService binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)/ /reference /component !-- A component with a reference promoted as a composite reference -- component name=HelloWorldServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ /component reference name=HelloWorldService promote=HelloWorldServiceComponent/helloWorldService interface.java interface=helloworld.HelloWorldService / binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)/ /reference /composite Notice the NonExistentPort port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2384) Message Conversion for Contribution Builders
[ https://issues.apache.org/jira/browse/TUSCANY-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2384: - Attachment: TUSCANY-2384.patch Message Conversion for Contribution Builders Key: TUSCANY-2384 URL: https://issues.apache.org/jira/browse/TUSCANY-2384 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Win XP SP2, JDK 1.5 Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2384.patch Message Conversion were required for the Contribution Builders, where few instance of messages was found without using the messageID and resourcebundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2384) Message Conversion for Contribution Builders
Message Conversion for Contribution Builders Key: TUSCANY-2384 URL: https://issues.apache.org/jira/browse/TUSCANY-2384 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Win XP SP2, JDK 1.5 Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2384.patch Message Conversion were required for the Contribution Builders, where few instance of messages was found without using the messageID and resourcebundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part4-NEW.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part6-NEW.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5-NEW.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6-NEW.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7-NEW.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part7-NEW.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5-NEW.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6-NEW.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7-NEW.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part5-NEW.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5-NEW.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6-NEW.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7-NEW.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-2242: Assignee: Ramkumar Ramalingam Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://helloworld; xmlns:hw=http://helloworld; name=helloworldwsclient !-- A component with an embedded reference definition connecting to an external webservice The wsdl interface for the reference is derived from the information specified by the 'wsdlElement' -- component name=HelloTuscanyServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ reference name=helloWorldService binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)/ /reference /component !-- A component with a reference promoted as a composite reference -- component name=HelloWorldServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ /component reference name=HelloWorldService promote=HelloWorldServiceComponent/helloWorldService interface.java interface=helloworld.HelloWorldService / binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)/ /reference /composite Notice the NonExistentPort port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603793#action_12603793 ] Ramkumar Ramalingam commented on TUSCANY-2242: -- Hi Simon, I have a fix for this issue, this one looks similar to the issue reported in TUSCANY-2319. This fix would stop the NPE being thrown from WebServiceBindingProcessor.java and show a warning message saying that the #wsdl.port does not match with the WSDL Definitions. I would be submitting a patch to this JIRA, once the patches for TUSCANY-2347 is applied. Thanks, Ramkumar R Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://helloworld; xmlns:hw=http://helloworld; name=helloworldwsclient !-- A component with an embedded reference definition connecting to an external webservice The wsdl interface for the reference is derived from the information specified by the 'wsdlElement' -- component name=HelloTuscanyServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ reference name=helloWorldService binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)/ /reference /component !-- A component with a reference promoted as a composite reference -- component name=HelloWorldServiceComponent implementation.java class=helloworld.HelloWorldServiceComponent/ /component reference name=HelloWorldService promote=HelloWorldServiceComponent/helloWorldService interface.java interface=helloworld.HelloWorldService / binding.ws wsdlElement=http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)/ /reference /composite Notice the NonExistentPort port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2267) Raise a warning if both reference target and binding URI are specified
[ https://issues.apache.org/jira/browse/TUSCANY-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-2267: Assignee: Ramkumar Ramalingam Raise a warning if both reference target and binding URI are specified -- Key: TUSCANY-2267 URL: https://issues.apache.org/jira/browse/TUSCANY-2267 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: All Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next The assembly spec says around line 1380 that A reference must not mix the use of endpoints specified via binding elements with target endpoints specified via the target attribute. We should raise a warning if this is detected in a composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2267) Raise a warning if both reference target and binding URI are specified
[ https://issues.apache.org/jira/browse/TUSCANY-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603797#action_12603797 ] Ramkumar Ramalingam commented on TUSCANY-2267: -- Hi Simon, I just wanted to confirm that only binding-ws and binding-notifications are the once which need a fix here. Please let me know if i have missed something. Thanks, Ramkumar R Raise a warning if both reference target and binding URI are specified -- Key: TUSCANY-2267 URL: https://issues.apache.org/jira/browse/TUSCANY-2267 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: All Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next The assembly spec says around line 1380 that A reference must not mix the use of endpoints specified via binding elements with target endpoints specified via the target attribute. We should raise a warning if this is detected in a composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2267) Raise a warning if both reference target and binding URI are specified
[ https://issues.apache.org/jira/browse/TUSCANY-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2267: - Attachment: TUSCANY-2267.patch Raise a warning if both reference target and binding URI are specified -- Key: TUSCANY-2267 URL: https://issues.apache.org/jira/browse/TUSCANY-2267 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: All Reporter: Simon Laws Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2267.patch The assembly spec says around line 1380 that A reference must not mix the use of endpoints specified via binding elements with target endpoints specified via the target attribute. We should raise a warning if this is detected in a composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2379) CompositeProcessor.java is calling promotedService.getService() instead of promotedService.getName() when writing out a composite file.
[
https://issues.apache.org/jira/browse/TUSCANY-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam reassigned TUSCANY-2379:
Assignee: Ramkumar Ramalingam
CompositeProcessor.java is calling promotedService.getService() instead of
promotedService.getName() when writing out a composite file.
---
Key: TUSCANY-2379
URL: https://issues.apache.org/jira/browse/TUSCANY-2379
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.2
Reporter: Richard Mah
Assignee: Ramkumar Ramalingam
CompositeProcessor.java is calling promotedService.getService() instead of
promotedService.getName() when writing out the promoted service to file.
Here is the snippet of code starting from line 546 (Revision 665831):
String promote;
if (promotedService != null) {
if (promotedService.getName() != null) {
promote = promotedComponent.getName() + '/' +
promotedService.getService();-Here is the
promotedService.getService() call
} else {
promote = promotedComponent.getName();
}
promotedService.getService() looks like it should be
promotedService.getName() instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part6.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part7.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: (was: TUSCANY-2347-Part5.patch) Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Patch Info: [Patch Available] Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part5.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part4.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part5.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part3.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2347: - Attachment: TUSCANY-2347-Part2.patch Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, TUSCANY-2347-Part3.patch After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2365) ExtensibleStAXArtifactProcessor should register an error when a unrecognized element is found
[ https://issues.apache.org/jira/browse/TUSCANY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602251#action_12602251 ] Ramkumar Ramalingam commented on TUSCANY-2365: -- Hi Hasan, The ideal place to catch these exceptions seems to be in the ExtensibleStAXArtifactProcessor read method, i think it would not be possible to categorize the exception based on implementation and binding at this stage. I believe it would be possible to throw a generic exception saying that this element is not supported by the runtime as it does not have a suitable processor to proceed. Let me know your say on this. Thanks. ExtensibleStAXArtifactProcessor should register an error when a unrecognized element is found - Key: TUSCANY-2365 URL: https://issues.apache.org/jira/browse/TUSCANY-2365 Project: Tuscany Issue Type: Improvement Environment: All Reporter: Hasan Muhammad Assignee: Ramkumar Ramalingam Priority: Critical ExtensibleStAXArtifactProcessor should register an error instead of a warning when unrecognized elements such as unsupported implementation types and binding types are found. Currently it registers a warning. If possible, it is better to isolate unsupported implementation and binding types as separate error messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2365) ExtensibleStAXArtifactProcessor should register an error when a unrecognized element is found
[ https://issues.apache.org/jira/browse/TUSCANY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-2365: Assignee: Ramkumar Ramalingam ExtensibleStAXArtifactProcessor should register an error when a unrecognized element is found - Key: TUSCANY-2365 URL: https://issues.apache.org/jira/browse/TUSCANY-2365 Project: Tuscany Issue Type: Improvement Environment: All Reporter: Hasan Muhammad Assignee: Ramkumar Ramalingam Priority: Critical ExtensibleStAXArtifactProcessor should register an error instead of a warning when unrecognized elements such as unsupported implementation types and binding types are found. Currently it registers a warning. If possible, it is better to isolate unsupported implementation and binding types as separate error messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2362) Fix for test failure in TUSCANY-2344 5 validation message
Fix for test failure in TUSCANY-2344 5 validation message --- Key: TUSCANY-2362 URL: https://issues.apache.org/jira/browse/TUSCANY-2362 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Problems with the widget and resource validation testing were noticed. CouldNotResolveLocation doesn't seem to be raised. Noticed that the reason for the failure in CouldNotResolveLocation for implementation.resource and implementation.widget validation is due to the missed code while applying the patch for TUSCANY-2344 and 2345. The changes suggested in the patch does not seem to appear in the committed code. Raising this defect to apply the missed code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2362) Fix for test failure in TUSCANY-2344 5 validation message
[ https://issues.apache.org/jira/browse/TUSCANY-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2362: - Attachment: TUSCANY-2362.patch Fix for test failure in TUSCANY-2344 5 validation message --- Key: TUSCANY-2362 URL: https://issues.apache.org/jira/browse/TUSCANY-2362 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2362.patch Problems with the widget and resource validation testing were noticed. CouldNotResolveLocation doesn't seem to be raised. Noticed that the reason for the failure in CouldNotResolveLocation for implementation.resource and implementation.widget validation is due to the missed code while applying the patch for TUSCANY-2344 and 2345. The changes suggested in the patch does not seem to appear in the committed code. Raising this defect to apply the missed code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2362) Fix for test failure in TUSCANY-2344 5 validation message
[ https://issues.apache.org/jira/browse/TUSCANY-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2362: - Attachment: TUSCANY-2362-New.patch NOTE: Please note that this new patch is just a replacement for the older ones and the older patch has some confusing local paths. Fix for test failure in TUSCANY-2344 5 validation message --- Key: TUSCANY-2362 URL: https://issues.apache.org/jira/browse/TUSCANY-2362 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2362-New.patch, TUSCANY-2362.patch Problems with the widget and resource validation testing were noticed. CouldNotResolveLocation doesn't seem to be raised. Noticed that the reason for the failure in CouldNotResolveLocation for implementation.resource and implementation.widget validation is due to the missed code while applying the patch for TUSCANY-2344 and 2345. The changes suggested in the patch does not seem to appear in the committed code. Raising this defect to apply the missed code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2362) Fix for test failure in TUSCANY-2344 5 validation message
[ https://issues.apache.org/jira/browse/TUSCANY-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2362: - Patch Info: [Patch Available] Fix for test failure in TUSCANY-2344 5 validation message --- Key: TUSCANY-2362 URL: https://issues.apache.org/jira/browse/TUSCANY-2362 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2362-New.patch, TUSCANY-2362.patch Problems with the widget and resource validation testing were noticed. CouldNotResolveLocation doesn't seem to be raised. Noticed that the reason for the failure in CouldNotResolveLocation for implementation.resource and implementation.widget validation is due to the missed code while applying the patch for TUSCANY-2344 and 2345. The changes suggested in the patch does not seem to appear in the committed code. Raising this defect to apply the missed code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2354) Fix required for the unreachable code in policy processors
Fix required for the unreachable code in policy processors
--
Key: TUSCANY-2354
URL: https://issues.apache.org/jira/browse/TUSCANY-2354
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Environment: Windows XP,
Reporter: Ramkumar Ramalingam
Assignee: Ramkumar Ramalingam
Fix For: Java-SCA-Next
For creating an itests for the validation messages, it was a requirement to
reproduce all kind of exceptions thrown from various processors in the runtime.
I came across this issue of unreachable code in the policy processors
(especially in PolicyIntentProcessor.java and PolicySetProcessor.java). Here is
the piece of code from resolveProfileIntent method of
PolicyIntentProcessor.java to explain.
for (Intent requiredIntent : policyIntent.getRequiredIntents()) {
if (requiredIntent.isUnresolved()) {
Intent resolvedRequiredIntent = resolver.resolveModel(Intent.class,
requiredIntent);
if (resolvedRequiredIntent != null) {
requiredIntents.add(resolvedRequiredIntent);
} else {
error(RequiredIntentNotFound, resolver, requiredIntent,
policyIntent);
throw new ContributionResolveException(Required Intent - +
requiredIntent
+ not found for ProfileIntent
+ policyIntent);
}
} else {
requiredIntents.add(requiredIntent);
}
}
Here the resolver.resolveModel does not seem to return null in any case, what
happens is if the resolver is unable to resolve the model it just returns the
unresolved model. So the if condition checking for resolvedRequiredIntent for
null never fails and the later part of the code in the else condition is never
reached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2338) Part 2 - itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2338: - Attachment: TUSCANY-2338-Part5.patch Note: TUSCANY-2338-Part5.patch is an additional fix for ReallySmallRuntime.java code. Few changes are also available for the same code as part of TUSCANY-2338-Part3.patch. So Please take only the additional line of code into consideration for checking in. Thanks. Part 2 - itests for validation messages --- Key: TUSCANY-2338 URL: https://issues.apache.org/jira/browse/TUSCANY-2338 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2338-Part1.patch, TUSCANY-2338-Part2.patch, TUSCANY-2338-Part3.patch, TUSCANY-2338-Part4.patch, TUSCANY-2338-Part5.patch The remaining fixes on itest for validation messages. Part1 fixes are available from TUSCANY-2329. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2344) NPE from implementation.widget for missing location attribute
[ https://issues.apache.org/jira/browse/TUSCANY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-2344: Assignee: Ramkumar Ramalingam NPE from implementation.widget for missing location attribute - Key: TUSCANY-2344 URL: https://issues.apache.org/jira/browse/TUSCANY-2344 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProvider.init(WidgetImplementationProvider.java:45) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:41) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:1) at org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyImplementationProviderFactory.createImplementationProvider(DefaultProviderFactoryExtensionPoint.java:292) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addImplementationProvider(CompositeActivatorImpl.java:463) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:973) ... 19 more NPE is thrown for missing location attribute We need a fix to catch this exception much before it reaches WidgetImplementationProvider. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2344) NPE from implementation.widget for missing location attribute
NPE from implementation.widget for missing location attribute - Key: TUSCANY-2344 URL: https://issues.apache.org/jira/browse/TUSCANY-2344 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Fix For: Java-SCA-Next Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProvider.init(WidgetImplementationProvider.java:45) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:41) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:1) at org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyImplementationProviderFactory.createImplementationProvider(DefaultProviderFactoryExtensionPoint.java:292) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addImplementationProvider(CompositeActivatorImpl.java:463) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:973) ... 19 more NPE is thrown for missing location attribute We need a fix to catch this exception much before it reaches WidgetImplementationProvider. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2345) NPE from implementation.resource for missing location attribute
NPE from implementation.resource for missing location attribute --- Key: TUSCANY-2345 URL: https://issues.apache.org/jira/browse/TUSCANY-2345 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Fix For: Java-SCA-Next java.lang.NullPointerException at org.apache.tuscany.sca.implementation.resource.provider.ResourceImplementationProvider.createInvoker(ResourceImplementationProvider.java:49) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:315) 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:125) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:182) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:195) 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 $Proxy0.get(Unknown Source) NPE is thrown from ResourceImplementationProvider, when the composite is provided with missing location attribute. Need to catch this exception and throw a meaningful message for the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2345) NPE from implementation.resource for missing location attribute
[ https://issues.apache.org/jira/browse/TUSCANY-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-2345: Assignee: Ramkumar Ramalingam NPE from implementation.resource for missing location attribute --- Key: TUSCANY-2345 URL: https://issues.apache.org/jira/browse/TUSCANY-2345 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next java.lang.NullPointerException at org.apache.tuscany.sca.implementation.resource.provider.ResourceImplementationProvider.createInvoker(ResourceImplementationProvider.java:49) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:315) 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:125) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:182) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:195) 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 $Proxy0.get(Unknown Source) NPE is thrown from ResourceImplementationProvider, when the composite is provided with missing location attribute. Need to catch this exception and throw a meaningful message for the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2347) Removing the exception throws from the processors
Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Fix For: Java-SCA-Next After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-2347: Assignee: Ramkumar Ramalingam Removing the exception throws from the processors - Key: TUSCANY-2347 URL: https://issues.apache.org/jira/browse/TUSCANY-2347 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: Windows XP, Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next After introducing the monitors in various part of the code (especially in the processors), while the runtime reads and resolves the contribution. Now we are trying to remove the exception that are being thrown from these modules. As a first step we are removing the exceptions that are safe to remove, by leaving the critical exceptions like a) IOException b) XMLStreamException c) PriviledegedActionException d) and ParseConfigurationExceptions As a second step, we will also be dealing with the above said exception once we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2344) NPE from implementation.widget for missing location attribute
[ https://issues.apache.org/jira/browse/TUSCANY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2344: - Attachment: TUSCANY-2344.patch NPE from implementation.widget for missing location attribute - Key: TUSCANY-2344 URL: https://issues.apache.org/jira/browse/TUSCANY-2344 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2344.patch Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProvider.init(WidgetImplementationProvider.java:45) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:41) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:1) at org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyImplementationProviderFactory.createImplementationProvider(DefaultProviderFactoryExtensionPoint.java:292) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addImplementationProvider(CompositeActivatorImpl.java:463) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:973) ... 19 more NPE is thrown for missing location attribute We need a fix to catch this exception much before it reaches WidgetImplementationProvider. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2345) NPE from implementation.resource for missing location attribute
[ https://issues.apache.org/jira/browse/TUSCANY-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2345: - Attachment: TUSCANY-2345.patch NPE from implementation.resource for missing location attribute --- Key: TUSCANY-2345 URL: https://issues.apache.org/jira/browse/TUSCANY-2345 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2345.patch java.lang.NullPointerException at org.apache.tuscany.sca.implementation.resource.provider.ResourceImplementationProvider.createInvoker(ResourceImplementationProvider.java:49) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:315) 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:125) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:182) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:195) 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 $Proxy0.get(Unknown Source) NPE is thrown from ResourceImplementationProvider, when the composite is provided with missing location attribute. Need to catch this exception and throw a meaningful message for the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2344) NPE from implementation.widget for missing location attribute
[ https://issues.apache.org/jira/browse/TUSCANY-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12600408#action_12600408 ] Ramkumar Ramalingam commented on TUSCANY-2344: -- Please Note: Need to add this as dependency in the itest-validation/pom.xml file dependency groupIdorg.apache.tuscany.sca/groupId artifactIdtuscany-implementation-widget/artifactId version2.0-incubating-SNAPSHOT/version /dependency Thanks, Ramkumar R NPE from implementation.widget for missing location attribute - Key: TUSCANY-2344 URL: https://issues.apache.org/jira/browse/TUSCANY-2344 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2344.patch Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProvider.init(WidgetImplementationProvider.java:45) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:41) at org.apache.tuscany.sca.implementation.widget.provider.WidgetImplementationProviderFactory.createImplementationProvider(WidgetImplementationProviderFactory.java:1) at org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyImplementationProviderFactory.createImplementationProvider(DefaultProviderFactoryExtensionPoint.java:292) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addImplementationProvider(CompositeActivatorImpl.java:463) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:973) ... 19 more NPE is thrown for missing location attribute We need a fix to catch this exception much before it reaches WidgetImplementationProvider. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2345) NPE from implementation.resource for missing location attribute
[ https://issues.apache.org/jira/browse/TUSCANY-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12600410#action_12600410 ] Ramkumar Ramalingam commented on TUSCANY-2345: -- Please Note: Need to add this as dependency to the itest-validation/pom.xml file i could not provide them as patch due to some mismatch in my file dependency groupIdorg.apache.tuscany.sca/groupId artifactIdtuscany-implementation-resource/artifactId version2.0-incubating-SNAPSHOT/version /dependency Thanks, Ramkumar R NPE from implementation.resource for missing location attribute --- Key: TUSCANY-2345 URL: https://issues.apache.org/jira/browse/TUSCANY-2345 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Implementation Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2345.patch java.lang.NullPointerException at org.apache.tuscany.sca.implementation.resource.provider.ResourceImplementationProvider.createInvoker(ResourceImplementationProvider.java:49) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addImplementationInterceptor(RuntimeWireImpl.java:315) 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:125) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.getInvoker(RuntimeSCAReferenceBindingProvider.java:182) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:195) 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 $Proxy0.get(Unknown Source) NPE is thrown from ResourceImplementationProvider, when the composite is provided with missing location attribute. Need to catch this exception and throw a meaningful message for the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2338) Part 2 - itests for validation messages
Part 2 - itests for validation messages --- Key: TUSCANY-2338 URL: https://issues.apache.org/jira/browse/TUSCANY-2338 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next The remaining fixes on itest for validation messages. Part1 fixes are available from TUSCANY-2329. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2338) Part 2 - itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2338: - Attachment: TUSCANY-2338-Part2.patch Part 2 - itests for validation messages --- Key: TUSCANY-2338 URL: https://issues.apache.org/jira/browse/TUSCANY-2338 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2338-Part1.patch, TUSCANY-2338-Part2.patch The remaining fixes on itest for validation messages. Part1 fixes are available from TUSCANY-2329. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2338) Part 2 - itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2338: - Attachment: TUSCANY-2338-Part1.patch Part 2 - itests for validation messages --- Key: TUSCANY-2338 URL: https://issues.apache.org/jira/browse/TUSCANY-2338 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2338-Part1.patch, TUSCANY-2338-Part2.patch The remaining fixes on itest for validation messages. Part1 fixes are available from TUSCANY-2329. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2338) Part 2 - itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2338: - Attachment: TUSCANY-2338-Part3.patch Part 2 - itests for validation messages --- Key: TUSCANY-2338 URL: https://issues.apache.org/jira/browse/TUSCANY-2338 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2338-Part1.patch, TUSCANY-2338-Part2.patch, TUSCANY-2338-Part3.patch The remaining fixes on itest for validation messages. Part1 fixes are available from TUSCANY-2329. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2329) itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2329: - Attachment: TUSCANY-2329-Part1.patch itests for validation messages -- Key: TUSCANY-2329 URL: https://issues.apache.org/jira/browse/TUSCANY-2329 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2329-Part1.patch itests for validation messages introduced through monitors (with TUSCANY-2277) for various processors during read and resolve phase of the composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2329) itests for validation messages
itests for validation messages -- Key: TUSCANY-2329 URL: https://issues.apache.org/jira/browse/TUSCANY-2329 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next itests for validation messages introduced through monitors (with TUSCANY-2277) for various processors during read and resolve phase of the composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597544#action_12597544 ] Ramkumar Ramalingam commented on TUSCANY-2277: -- Hi Simon, The issue seems to be due to subeclipse. I did not realize that such characters would crop up due to subeclipse. I apologies for the inconvenience. I am just uploading a new set of patch for the same fixes. Thanks, Ramkumar R Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: TUSCANY-2277-Part1-New.rtf Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: (was: TUSCANY-2277-Part1-New.rtf) Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: TUSCANY-2277-Part1-New.patch Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1-New.patch, TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: (was: TUSCANY-2277-Part1-New.patch) Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: TUSCANY-2277-Part2-New.patch Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1-New.patch, TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2-New.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3-New.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: TUSCANY-2277-Part3-New.patch Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1-New.patch, TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2-New.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3-New.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-1867) @OneWay with String return type causes NullPointerException
[ https://issues.apache.org/jira/browse/TUSCANY-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597020#action_12597020 ] Ramkumar Ramalingam commented on TUSCANY-1867: -- Hi Vamsi, FYI... Fixes for SCANodeManagerService.destroyNode() is also available from TUSCANY-2252. Since you have also included a fix for @OneWay annotation exception in your patch TUSCANY-1867-2.patch. We could probably ignore the patch for TUSCANY-2252, and apply the ones available in this JIRA. @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] Created: (TUSCANY-2318) Need a meaningful exception message from binding.ws
Need a meaningful exception message from binding.ws --- Key: TUSCANY-2318 URL: https://issues.apache.org/jira/browse/TUSCANY-2318 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Binding Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next In Sample helloworld-ws-reference-jms, when the helloworldwsjms.composite is modified to look like this: binding.ws wsdlElement=http://helloworld#wsdl.binding(HelloWorldSoapJmsBinding) uri=jjms:/queue.sample?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryamp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactoryamp;java.naming.provider.url=tcp://localhost:61619/ here the jms: is replace with jjms:. The runtime seems to throw (MalformedURLException) exception from the JettyServer, during the Composite Activation phase. I feel it would be good we can catch this exception much before and show a meaniful message to the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2319) binding.ws throws NullPointerException
binding.ws throws NullPointerException -- Key: TUSCANY-2319 URL: https://issues.apache.org/jira/browse/TUSCANY-2319 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Binding Extensions Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next In helloworld-ws-reference-jms sample, when the helloworldwsjms.composite is modified to look like this: interface.wsdl interface=http://helloworld#wsdl.interface(HelloWorld2) / binding.ws wsdlElement=http://helloworld#wsdl.binding(HelloWorldSoapJmsBinding2) uri=jms:/queue.sample?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryamp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactoryamp;java.naming.provider.url=tcp://localhost:61619/ Here the wsdl.interface HelloWorld is replace with HelloWorld2 and the wsdl.binding HelloWorldSoapJmsBinding is replaced with HelloWorldSoapJmsBinding2. Here a NullPointerException is thrown while running the sample, instead of showing a meaningful message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: (was: TUSCANY-2277-Part1.patch) Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: TUSCANY-2277-Part1.patch Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: (was: TUSCANY-2277-Part1.patch) Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: TUSCANY-2277-Part3.patch TUSCANY-2277-Part2.patch TUSCANY-2277-Part1.patch Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch, TUSCANY-2277-Part3.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2277: - Attachment: TUSCANY-2277-Part1.patch As the changes seems to be huge for this issue, i am providing with a incremental patch... more patches are in the pipe-line. Here I have attached Part1 of the changes. Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2277-Part1.patch Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2277) Standardization of registering msg with monitor
Standardization of registering msg with monitor --- Key: TUSCANY-2277 URL: https://issues.apache.org/jira/browse/TUSCANY-2277 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Lokking at the monitors that are being hooked up with different parts of the code, found that we have some inconsistency interms of raising warning errors. In some places we throw exceptions and in other places we raise a warning. Here are some examples for the inconsistency... BaseConfigurationBuilderImpl.java Here we raise only a warning for URISyntaxException, should we not throw an exception too? BaseWireBuilderImpl.java Here we throw exceptions for IncompatibleInterfaceContractException, don't you think we also need to register this message in our monitor? In the same class, we raise a warning message for the PolicyRelated Exceptions, should we also throw an exception here? CompositeProcessor.java There are instances where we throw new ContributionReadException, i believe registering this msg with a monitor is also required as this is caused by incorrect user input. From Simon's comments on how we can go ahead with handling such instance, we will fix the issue as discussed http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.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-2261) Default monitor failure if bundle for local not found
[ https://issues.apache.org/jira/browse/TUSCANY-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam closed TUSCANY-2261. Default monitor failure if bundle for local not found - Key: TUSCANY-2261 URL: https://issues.apache.org/jira/browse/TUSCANY-2261 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Would like the default logging monitor to use a default resource bundle if it can't find the one it requires for the locale, i.e. it would be good if it didn't fail trying to write out a warning for people where we haven't translated the messages. This may be as easy as just providing a default bundle with no locale or may be a few code changes. haven't had chance to look at it yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2261) Default monitor failure if bundle for local not found
[ https://issues.apache.org/jira/browse/TUSCANY-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12592342#action_12592342 ] Ramkumar Ramalingam commented on TUSCANY-2261: -- By default the default resource bundle is being by the JDK logger, it means we just need to have the .properties file without any _en (locale) mentioned in it. This way whatever locale is used, we will get some english messages displayed. So we don't require any patch here what we only need is a non_locale property file. Default monitor failure if bundle for local not found - Key: TUSCANY-2261 URL: https://issues.apache.org/jira/browse/TUSCANY-2261 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Would like the default logging monitor to use a default resource bundle if it can't find the one it requires for the locale, i.e. it would be good if it didn't fail trying to write out a warning for people where we haven't translated the messages. This may be as easy as just providing a default bundle with no locale or may be a few code changes. haven't had chance to look at it yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2262) Flow XSD schema validation errors through the monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2262: - Attachment: TUSCANY-2262.txt Flow XSD schema validation errors through the monitor - Key: TUSCANY-2262 URL: https://issues.apache.org/jira/browse/TUSCANY-2262 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, JDK1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: TUSCANY-2262.txt The Monitor to date is only integrated into the builders. There are other places that raise validation warnings, i.e. warning to the user that there is something wrong with the input that they have provided. The first one to look at would be the XSD schema validation. This happens within the contribution processing so we need to. Make the monitor available to the part of the processing Get warnings from the schema processor Create a contribution resource bundle to hold any messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2262) Flow XSD schema validation errors through the monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-2262: Assignee: Ramkumar Ramalingam Flow XSD schema validation errors through the monitor - Key: TUSCANY-2262 URL: https://issues.apache.org/jira/browse/TUSCANY-2262 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, JDK1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next The Monitor to date is only integrated into the builders. There are other places that raise validation warnings, i.e. warning to the user that there is something wrong with the input that they have provided. The first one to look at would be the XSD schema validation. This happens within the contribution processing so we need to. Make the monitor available to the part of the processing Get warnings from the schema processor Create a contribution resource bundle to hold any messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2269) Import package could not be resolved in CalculateBindingURITestCase
Import package could not be resolved in CalculateBindingURITestCase --- Key: TUSCANY-2269 URL: https://issues.apache.org/jira/browse/TUSCANY-2269 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next The import com.sun.org.apache.xerces.internal.impl.xs.opti.DefaultNode could not be resolved in org.apache.tuscany.sca.implementation.node.builder.impl.CalculateBindingURITestCase. Solution: Need to remove the import statement as this class is not used anywhere in the code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2269) Import package could not be resolved in CalculateBindingURITestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2269: - Attachment: TUSCANY-2269.patch Import package could not be resolved in CalculateBindingURITestCase --- Key: TUSCANY-2269 URL: https://issues.apache.org/jira/browse/TUSCANY-2269 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Environment: Windows XP Reporter: Ramkumar Ramalingam Assignee: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2269.patch The import com.sun.org.apache.xerces.internal.impl.xs.opti.DefaultNode could not be resolved in org.apache.tuscany.sca.implementation.node.builder.impl.CalculateBindingURITestCase. Solution: Need to remove the import statement as this class is not used anywhere in the code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2261) Default monitor failure if bundle for local not found
[ https://issues.apache.org/jira/browse/TUSCANY-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-2261: Assignee: Ramkumar Ramalingam Default monitor failure if bundle for local not found - Key: TUSCANY-2261 URL: https://issues.apache.org/jira/browse/TUSCANY-2261 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Would like the default logging monitor to use a default resource bundle if it can't find the one it requires for the locale, i.e. it would be good if it didn't fail trying to write out a warning for people where we haven't translated the messages. This may be as easy as just providing a default bundle with no locale or may be a few code changes. haven't had chance to look at it yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2252) Remove exception declaration from SCANodeManagerService Interface
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 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] Commented: (TUSCANY-2252) Remove exception declaration from SCANodeManagerService Interface
[ https://issues.apache.org/jira/browse/TUSCANY-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591242#action_12591242 ] Ramkumar Ramalingam commented on TUSCANY-2252: -- By removing the declared exception from destroyNode() method in org.apache.tuscany.sca.node.management.SCANodeManagerService.java interface with @OneWay annotation, we might also need to reflect the same change in org.apache.tuscany.sca.node.management.impl.SCANodeManagerServiceImpl.java 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 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] Updated: (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 ] Ramkumar Ramalingam updated TUSCANY-2252: - Attachment: TUSCANY-2252.patch 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] Updated: (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 ] Ramkumar Ramalingam updated TUSCANY-1867: - Attachment: TUSCANY-1867.patch @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: Ramkumar Ramalingam 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 ] Ramkumar Ramalingam reassigned TUSCANY-1867: Assignee: 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: Ramkumar Ramalingam Fix For: Java-SCA-Next 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1867) @OneWay with String return type causes NullPointerException
[
https://issues.apache.org/jira/browse/TUSCANY-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589541#action_12589541
]
Ramkumar Ramalingam commented on TUSCANY-1867:
--
This JIRA talks about producing better exception message for those methods with
@OneWay annotations, when these method does not have void return type. The
best place to throw this exception would be in the
org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl
code as shown below, instead of allowing them to crop-up in the axis2 code.
boolean nonBlocking = method.isAnnotationPresent(OneWay.class);
if (nonBlocking) {
if (!(returnType == void.class)) {
throw new InvalidOperationException(
Method should return 'void' when declared with an
@OneWay annotation.,
method);
}
if (!(faultTypes.length == 0)) {
throw new InvalidOperationException(
Method should not declare exceptions with an
@OneWay annotation.,
method);
}
}
I'll attach a patch with this 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: Ramkumar Ramalingam
Fix For: Java-SCA-Next
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.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-1881) Remote bidings attached to non-remotable services not reported as a warning in some cases
[ https://issues.apache.org/jira/browse/TUSCANY-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-1881: Assignee: Ramkumar Ramalingam (was: Simon Laws) Remote bidings attached to non-remotable services not reported as a warning in some cases - Key: TUSCANY-1881 URL: https://issues.apache.org/jira/browse/TUSCANY-1881 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model, Java SCA Problem Determination Affects Versions: Java-SCA-1.0 Environment: All Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next I seem to remember in the past that adding remote bindings to services with interfaces not marked as remotable used to cause and error or a warning. This cropped up in the domain manager app which defines the following component. component name=DomainManagerComponent implementation.java class=org.apache.tuscany.sca.domain.impl.DomainManagerServiceImpl/ service name=DomainManagerInitService interface.java interface=org.apache.tuscany.sca.domain.DomainManagerInitService/ binding.sca/ /service service name=DomainManagerNodeEventService interface.java interface=org.apache.tuscany.sca.domain.DomainManagerNodeEventService/ binding.ws/ /service service name=DomainManagementService interface.java interface=org.apache.tuscany.sca.domain.management.DomainManagementService/ t:binding.jsonrpc / /service /component Where the DomainManagementService interface was not marked as remotable when it should have been (my mistake) but the interesting effect is that everything works except that no databindings are applied to the wires so parameters/return types are messed up. -- 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-1881) Remote bidings attached to non-remotable services not reported as a warning in some cases
[ https://issues.apache.org/jira/browse/TUSCANY-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589562#action_12589562 ] Ramkumar Ramalingam commented on TUSCANY-1881: -- This JIRA talks about fixing the databinding issue that crops-up while the interfaces not marked as remotable in case of remote bindings to services. After discussing with Venkat, I understood that the datatransformation interceptor will not be inserted in the invocation chain if the target interface is not marked as remotable. Not having this interceptor will end up with binding specific data transformations not being done.. for example transformation of java object to OMElements in the case of axis2 binding. So if the json-rpc binding does have trouble with the arguments and returntypes because of the absence of transformations... that seems to the expected behaviour in this case. As a fix we will provide a warning in such scenarios. I'II attach a patch with a fix. Remote bidings attached to non-remotable services not reported as a warning in some cases - Key: TUSCANY-1881 URL: https://issues.apache.org/jira/browse/TUSCANY-1881 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model, Java SCA Problem Determination Affects Versions: Java-SCA-1.0 Environment: All Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next I seem to remember in the past that adding remote bindings to services with interfaces not marked as remotable used to cause and error or a warning. This cropped up in the domain manager app which defines the following component. component name=DomainManagerComponent implementation.java class=org.apache.tuscany.sca.domain.impl.DomainManagerServiceImpl/ service name=DomainManagerInitService interface.java interface=org.apache.tuscany.sca.domain.DomainManagerInitService/ binding.sca/ /service service name=DomainManagerNodeEventService interface.java interface=org.apache.tuscany.sca.domain.DomainManagerNodeEventService/ binding.ws/ /service service name=DomainManagementService interface.java interface=org.apache.tuscany.sca.domain.management.DomainManagementService/ t:binding.jsonrpc / /service /component Where the DomainManagementService interface was not marked as remotable when it should have been (my mistake) but the interesting effect is that everything works except that no databindings are applied to the wires so parameters/return types are messed up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reopened TUSCANY-2092: -- Assignee: Ramkumar Ramalingam (was: ant elder) As per the recommendation made by Simon Laws in the mailing list (http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200804.mbox/[EMAIL PROTECTED]), we need a fix to synchronize the access to loadListeners() method. I'll attach a patch for the same. ConcurrentModificationException in ExtensibleContributionListener - Key: TUSCANY-2092 URL: https://issues.apache.org/jira/browse/TUSCANY-2092 Project: Tuscany Issue Type: Bug Reporter: Greg Dritschler Assignee: Ramkumar Ramalingam 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] Updated: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2092: - Attachment: TUSCANY-2092.patch Latest patch for the re-opened issue. ConcurrentModificationException in ExtensibleContributionListener - Key: TUSCANY-2092 URL: https://issues.apache.org/jira/browse/TUSCANY-2092 Project: Tuscany Issue Type: Bug Reporter: Greg Dritschler Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next Attachments: JIRA-2092.patch, TUSCANY-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-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587149#action_12587149 ] Ramkumar Ramalingam commented on TUSCANY-2092: -- Using Vectors OR Collections.synchronizedList for listeners synchronizes your list object. However, the iterators implemented in the java.util Collections classes are fail-fast, which means that if one thread changes a collection while another thread is traversing it through an Iterator, the next Iterator.hasNext() or Iterator.next() call will throw ConcurrentModificationException. If we have to prevent ConcurrentModificationException, we must lock the entire List while you are iterating by wrapping it with a synchronized block, which inturn is costly. A better solution to the above problem seems to be, the CopyOnWriteArrayList class from util.concurrent (which will also appear in the java.util.concurrent package in JDK 1.5) is a thread-safe implementation of ArrayList that offers far better concurrency. Multiple reads can almost always execute concurrently, simultaneous reads and writes can usually execute concurrently, and multiple simultaneous writes can often execute concurrently. Also CopyOnWriteArrayList contains a mutable reference to an immutable array, so as long as that reference is held fixed, you get all the thread-safety benefits of immutability without the need for locking. I have attached a patch using the above solution to this issue. ConcurrentModificationException in ExtensibleContributionListener - Key: TUSCANY-2092 URL: https://issues.apache.org/jira/browse/TUSCANY-2092 Project: Tuscany Issue Type: Bug Reporter: Greg Dritschler Assignee: Ramkumar Ramalingam 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] Updated: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2092: - Attachment: JIRA-2092.patch ConcurrentModificationException in ExtensibleContributionListener - Key: TUSCANY-2092 URL: https://issues.apache.org/jira/browse/TUSCANY-2092 Project: Tuscany Issue Type: Bug Reporter: Greg Dritschler Assignee: Ramkumar Ramalingam 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-2085) ConcurentModExc in DefaultDataBindingExtensionPoint
[
https://issues.apache.org/jira/browse/TUSCANY-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587156#action_12587156
]
Ramkumar Ramalingam commented on TUSCANY-2085:
--
To prevent ConcurrentModificationException, one way is to lock the entire List
while you are iterating by wrapping it with a synchronized block, which inturn
looks costly as the this would block the other thread to access the list for
reading.
A better solution i would consider for the above problem would be, using
CopyOnWriteArrayList class from util.concurrent (which will also appear in the
java.util.concurrent package in JDK 1.5) is a thread-safe implementation of
ArrayList that offers far better concurrency. Multiple reads can almost always
execute concurrently, simultaneous reads and writes can usually execute
concurrently, and multiple simultaneous writes can often execute concurrently.
Also CopyOnWriteArrayList contains a mutable reference to an immutable array,
so as long as that reference is held fixed, you get all the thread-safety
benefits of immutability without the need for locking.
The code change required would be just to replace the ArrayList with
CopyOnWriteArrayList:
private final ListDataBinding databindings = new
CopyOnWriteArrayListDataBinding();
ConcurentModExc in DefaultDataBindingExtensionPoint
Key: TUSCANY-2085
URL: https://issues.apache.org/jira/browse/TUSCANY-2085
Project: Tuscany
Issue Type: Bug
Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.1
Reporter: Scott Kurz
Priority: Minor
Fix For: Java-SCA-Next
Attachments: 2085.patch
Get an exception like the following,
java.util.ConcurrentModificationException
at java.util.AbstractList$SimpleListIterator.next(Unknown Source)at
org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:223)
at
org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSFaultExceptionMapper.introspectFaultDataType(JAXWSFaultExceptionMapper.java:214)
at
org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.introspectFaultTypes(JAXWSJavaInterfaceProcessor.java:178)
at
org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.visitInterface(JAXWSJavaInterfaceProcessor.java:90)
at
org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl.introspectInterface(JavaInterfaceIntrospectorImpl.java:91)
as this thread, A, is in a for-loop looping through 'databindings'
public boolean introspectType(DataType dataType, Annotation[] annotations,
boolean isException) {
loadDataBindings();
for (DataBinding binding : databindings) {
while another thread, B, is still in loadDataBindings() and is still adding
to the databindings ArrayList.
I'm working around this by putting a lock around the whole body of
loadDataBindings()
private final byte[] loadingLock = new byte[0];
...
private void loadDataBindings() {
synchronized (loadingLock) {
if (loadedDataBindings)
return;
...
}
}
Another option might be to change addDataBinding() to look at the 'bindings'
Map before adding to 'databindings'.
I'll attach a patch and leave it for a second opinion.
--
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 ] Ramkumar Ramalingam reassigned TUSCANY-2092: Assignee: 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: Ramkumar Ramalingam 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] Updated: (TUSCANY-2170) Synchronizing the access to SCADefinitions
[ https://issues.apache.org/jira/browse/TUSCANY-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam updated TUSCANY-2170: - Attachment: SCADefinitionsImpl-JIRA-2170.patch Synchronizing the access to SCADefinitions -- Key: TUSCANY-2170 URL: https://issues.apache.org/jira/browse/TUSCANY-2170 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: SVN revision 642920 - Windows Reporter: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next Attachments: SCADefinitionsImpl-JIRA-2170.patch http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg29138.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2170) Synchronizing the access to SCADefinitions
[ https://issues.apache.org/jira/browse/TUSCANY-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584098#action_12584098 ] Ramkumar Ramalingam commented on TUSCANY-2170: -- Learnt that using Vectors OR Collections.synchronizedList synchronizes your list object. However, the iterators implemented in the java.util Collections classes are fail-fast, which means that if one thread changes a collection while another thread is traversing it through an Iterator, the next Iterator.hasNext() or Iterator.next() call will throw ConcurrentModificationException. If we have to prevent ConcurrentModificationException, we must lock the entire List while you are iterating by wrapping it with a synchronized block, which inturn is costly. As a solution to the above problem, the CopyOnWriteArrayList class from util.concurrent (which will also appear in the java.util.concurrent package in JDK 1.5) is a thread-safe implementation of ArrayList that offers far better concurrency. Multiple reads can almost always execute concurrently, simultaneous reads and writes can usually execute concurrently, and multiple simultaneous writes can often execute concurrently. Also CopyOnWriteArrayList contains a mutable reference to an immutable array, so as long as that reference is held fixed, you get all the thread-safety benefits of immutability without the need for locking. Hence i believe the best solution would be to go with CopyOnWriteArrayList instead of the current ArrayList used to store the list of policy sets, intents, binding types etc. Please suggest me if this one is the right approach. Thanks. Synchronizing the access to SCADefinitions -- Key: TUSCANY-2170 URL: https://issues.apache.org/jira/browse/TUSCANY-2170 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: SVN revision 642920 - Windows Reporter: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg29138.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2170) Synchronizing the access to SCADefinitions
Synchronizing the access to SCADefinitions -- Key: TUSCANY-2170 URL: https://issues.apache.org/jira/browse/TUSCANY-2170 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: SVN revision 642920 - Windows Reporter: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg29138.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2170) Synchronizing the access to SCADefinitions
[ https://issues.apache.org/jira/browse/TUSCANY-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12583638#action_12583638 ] Ramkumar Ramalingam commented on TUSCANY-2170: -- The current implementation SCADefinitionsImpl.java uses java ArrayList to store the list of policy sets, intents, binding types etc. I believe Instead of synchronizing the methods that does the operations like clear/addAll. I believe the best solution would be to replace the ArrayList with a Vector. Please suggest me if this one is the right approach. Thanks. Synchronizing the access to SCADefinitions -- Key: TUSCANY-2170 URL: https://issues.apache.org/jira/browse/TUSCANY-2170 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Environment: SVN revision 642920 - Windows Reporter: Ramkumar Ramalingam Priority: Minor Fix For: Java-SCA-Next http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg29138.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
