[jira] Created: (TUSCANY-2258) Spring Implementation support of Services isn't compliant with the Specification
Spring Implementation support of Services isn't compliant with the Specification Key: TUSCANY-2258 URL: https://issues.apache.org/jira/browse/TUSCANY-2258 Project: Tuscany Issue Type: Bug Components: Java SCA Spring Implementation Extension Environment: Not Specific, but current environment is Windows Reporter: Kapish Aggarwal Based on the specification (verbatim from PDF below): Each service element used with implementation.spring should include the name of the Spring bean that is to be exposed as an SCA service in its name attribute. So, for Spring, the name attribute of a service plays two roles: it identifies a Spring bean, and it names the service for the component. The service element above has a name of X, so there should be a Spring bean with that name. This means in a component using implementation.spring, the name attribute of the service should be based on the value of the id attribute of the corresponding bean in the Spring context file. However, since Spring Implementation code piggybacks on the Java Introspection, it should the Java interface name instead. The SpringBeanIntrospector class's introspectBean method simply uses the Java implementation introspection and just copies the Services, References, and Properties directly over to the componentType object for the Spring Implementation. There needs to be some processing to ensure that the service is named based on the bean. I am unsure if the references and properties need have some extra processing involved either. Example below: Spring Context: bean id=testBean class=test.spring.HelloWorldBean /bean Component Element from Composite Should Be (This does not work): component name=SpringComponent implementation.spring location=META-INF/SpringHelloWorld-context.xml/ service name=testBean interface.java interface=test.spring.HelloWorld/ /service /component Component Element from Composite Actually Is (This works): component name=SpringComponent implementation.spring location=META-INF/SpringHelloWorld-context.xml/ service name=HelloWorld interface.java interface=test.spring.HelloWorld/ /service /component -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2073) The resolution to TUSCANY-2047 didn't clean up references to SCA Binding module
The resolution to TUSCANY-2047 didn't clean up references to SCA Binding module --- Key: TUSCANY-2073 URL: https://issues.apache.org/jira/browse/TUSCANY-2073 Project: Tuscany Issue Type: Sub-task Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: Not Environment specific Reporter: Kapish Aggarwal The resolution to TUSCANY-2047 left the import of org.apache.tuscany.sca.binding.sca.xml.SCABindingProcessor, which is no longer referenced. With this import removed, the Maven dependency on the binding-sca module can be removed from the host-embedded module. -- 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-2073) The resolution to TUSCANY-2047 didn't clean up references to SCA Binding module
[ https://issues.apache.org/jira/browse/TUSCANY-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577522#action_12577522 ] Kapish Aggarwal commented on TUSCANY-2073: -- The file containing the import is java\sca\modules\host-embedded\src\main\java\org\apache\tuscany\sca\host\embedded\impl\ReallySmallRuntimeBuilder.java The resolution to TUSCANY-2047 didn't clean up references to SCA Binding module --- Key: TUSCANY-2073 URL: https://issues.apache.org/jira/browse/TUSCANY-2073 Project: Tuscany Issue Type: Sub-task Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: Not Environment specific Reporter: Kapish Aggarwal The resolution to TUSCANY-2047 left the import of org.apache.tuscany.sca.binding.sca.xml.SCABindingProcessor, which is no longer referenced. With this import removed, the Maven dependency on the binding-sca module can be removed from the host-embedded module. -- 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-981) Capability to Remove / Undeploy Applications from Tuscany
[ http://issues.apache.org/jira/browse/TUSCANY-981?page=all ] Kapish Aggarwal updated TUSCANY-981: Attachment: JIRA981Patches.zip This zip contains a rough skeleton of implementing undeployment. This code has been used to remove applications and manage multiple applications in a single runtime. The five patches in the zip apply to the following classes/files: org.apache.tuscany.spi.component.CompositeComponent - java\sca\kernel\spi\src\main\java\org\apache\tuscany\spi\component\CompositeComponent.java org.apache.tuscany.spi.extension.CompositeComponentExtension - java\sca\kernel\spi\src\main\java\org\apache\tuscany\spi\extension\CompositeComponentExtension.java org.apache.tuscany.spi.deployer.Deployer- java\sca\kernel\spi\src\main\java\org\apache\tuscany\spi\deployer\Deployer.java org.apache.tuscany.core.deployer.DeployerImpl - java\sca\kernel\core\src\main\java\org\apache\tuscany\core\deployer\DeployerImpl.java org.apache.tuscany.core.launcher.LauncherImpl - java\sca\kernel\core\src\main\java\org\apache\tuscany\core\launcher\LauncherImpl.java Capability to Remove / Undeploy Applications from Tuscany - Key: TUSCANY-981 URL: http://issues.apache.org/jira/browse/TUSCANY-981 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Reporter: Kapish Aggarwal Attachments: JIRA981Patches.zip There is no capability to remove an application once it has been deployed into the Tuscany runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-983) Schema Definitions need to be unregistered from Registry
Schema Definitions need to be unregistered from Registry Key: TUSCANY-983 URL: http://issues.apache.org/jira/browse/TUSCANY-983 Project: Tuscany Issue Type: Sub-task Reporter: Kapish Aggarwal -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-678) Java XSD files cannot be used to validate SCA Model
Java XSD files cannot be used to validate SCA Model --- Key: TUSCANY-678 URL: http://issues.apache.org/jira/browse/TUSCANY-678 Project: Tuscany Issue Type: Task Reporter: Kapish Aggarwal Priority: Minor The XSD schema files that are packaged in the tuscany java project are out of date with the current SCA model and cannot be used to validate any SCDL files. It appears that the C++ is the one being worked on, but the dates of edit do not correspond with one C++ being more uptodate than Java. The two sets of XSD files need to be synchronized so that both sets reflect the current SCA Model. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
