[jira] [Assigned] (TUSCANY-3988) Cloned component shares same policy provider list as original component causing duplicated policy providers
[ https://issues.apache.org/jira/browse/TUSCANY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-3988: --- Assignee: Simon Laws > Cloned component shares same policy provider list as original component > causing duplicated policy providers > --- > > Key: TUSCANY-3988 > URL: https://issues.apache.org/jira/browse/TUSCANY-3988 > Project: Tuscany > Issue Type: Bug >Affects Versions: Java-SCA-2.0 >Reporter: Greg Dritschler >Assignee: Simon Laws >Priority: Minor > > Scenario: A composite "X" has multiple implementation.composite components > that point to the same composite Y. > Problem: Components in Y have duplicated implementation policy providers. > Detailed explanation: CompositeCloneBuilderImpl clones each occurrence of Y > which clones the components under it. However RuntimeComponentImpl does not > have a clone method, so its policy provider list is simply copied to the > clone. When CompositeActivatorImpl creates implementation policy providers > for each component in Y, it is not updating a unique list, but rather a list > that is shared with the other clones, causing the duplication. > Proposed solution: Add a clone method to RuntimeComponentImpl that > initializes a new policy provider list. > @Override > public Object clone() throws CloneNotSupportedException { > RuntimeComponentImpl clone = (RuntimeComponentImpl)super.clone(); > clone.policyProviders = new ArrayList(); > return clone; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TUSCANY-3989) JMS binding schema is back level
JMS binding schema is back level - Key: TUSCANY-3989 URL: https://issues.apache.org/jira/browse/TUSCANY-3989 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-2.x Environment: All Reporter: Simon Laws Fix For: Java-SCA-2.x In svn we have the jms binding schema sca-binding-jms-1.1-cd04-rev2.xsd. OASIS is showing cd05 (see http://docs.oasis-open.org/ns/opencsa/sca/200912) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TUSCANY-3974) IntentNotSatisfiedAtBuild error occurs when using an intent provided by implementation
[ https://issues.apache.org/jira/browse/TUSCANY-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-3974: -- Assignee: ant elder > IntentNotSatisfiedAtBuild error occurs when using an intent provided by > implementation > -- > > Key: TUSCANY-3974 > URL: https://issues.apache.org/jira/browse/TUSCANY-3974 > Project: Tuscany > Issue Type: Bug >Affects Versions: Java-SCA-2.0 >Reporter: Greg Dritschler >Assignee: ant elder >Priority: Minor > Attachments: TUSCANY-3974.patch > > > ComponentPolicyBuilderImpl.checkIntentsResolved() isn't finding the > mayProvides/alwaysProvides intent list for an implementation type. I've > attached a fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TUSCANY-3974) IntentNotSatisfiedAtBuild error occurs when using an intent provided by implementation
[ https://issues.apache.org/jira/browse/TUSCANY-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder resolved TUSCANY-3974. Resolution: Fixed Patch applied, thanks for the fix Greg. > IntentNotSatisfiedAtBuild error occurs when using an intent provided by > implementation > -- > > Key: TUSCANY-3974 > URL: https://issues.apache.org/jira/browse/TUSCANY-3974 > Project: Tuscany > Issue Type: Bug >Affects Versions: Java-SCA-2.0 >Reporter: Greg Dritschler >Assignee: ant elder >Priority: Minor > Attachments: TUSCANY-3974.patch > > > ComponentPolicyBuilderImpl.checkIntentsResolved() isn't finding the > mayProvides/alwaysProvides intent list for an implementation type. I've > attached a fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TUSCANY-3916) When we pass interface descriptions via the registry is must be complete or the target node must be provided with a mechanism for retrieving the interface
[ https://issues.apache.org/jira/browse/TUSCANY-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-3916. --- Resolution: Fixed A while back at 1167202 the WSDL representation was changed for an internal representation that serializes the internal Tuscany model to XML which looks like: http://tuscany.apache.org/xmlns/sca/1.1";> class org.apache.tuscany.sca.itest.interfaces.ParameterObject NoType org.apache.tuscany.sca.itest.interfaces.ParameterObject class java.lang.String {http://www.w3.org/2001/XMLSchema}string java.lang.String class java.lang.String {http://www.w3.org/2001/XMLSchema}string java.lang.String etc. I'll close this issue now as this format doesn't depend on imports or any resolution in remote nodes. > When we pass interface descriptions via the registry is must be complete or > the target node must be provided with a mechanism for retrieving the interface > -- > > Key: TUSCANY-3916 > URL: https://issues.apache.org/jira/browse/TUSCANY-3916 > Project: Tuscany > Issue Type: Bug > Components: SCA Java Runtime >Affects Versions: Java-SCA-2.0 > Environment: All >Reporter: Simon Laws > Fix For: Java-SCA-2.0 > > > We are currently add function to serializing WSDL documents via the registry > but those WSDL serializations can have includes/imports that the remote node > won't be able to satisfy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TUSCANY-3986) Missing null check in JAXWSBindingInvoker for non blocking operation
[ https://issues.apache.org/jira/browse/TUSCANY-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz resolved TUSCANY-3986. - Resolution: Fixed > Missing null check in JAXWSBindingInvoker for non blocking operation > > > Key: TUSCANY-3986 > URL: https://issues.apache.org/jira/browse/TUSCANY-3986 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Axis Binding Extension >Reporter: Rashmi Hunt >Assignee: Scott Kurz > Fix For: Java-SCA-2.x > > Attachments: TUSCANY-3986.patch > > > invokeTarget() returns soap reponse as null if operation is nonBlocking. > invokeTarget() is called from invoke() method which doesn not check for > 'null' response and goes ahead to get the soap body from null response > which throws NullPointerException. > I have attached a patch which checks for null response. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira