DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| OASIS JIRA | Description | Tuscany TODO | |
|---|---|---|---|---|
| for implentations.*'s fix attributes that should show qnames as values |
| ||
| Is binding.sca always present? |
| ||
| Is interface.java specification normative in SCA-Assembly spec? | No action is required | ||
| usage of not promoted references | Make sure the reference resolution follows what's described by the assembly spec | ||
| SCA <anyAttribute.../> declarations should use namespace ##other rather than ##any | Update the xsd from OASIS | ||
| Can Implementation change property values after instantiaion | No action is required | ||
| Missing XSD for contributions | Update the xsd from OASIS. Update the Import/Export model to | ||
| Clarify whether a Default Value for a Property must appear inthe componentType of an implementation | No action is required | ||
| Permit intents and PolicySets on <interface/> elements | The policy model needs to be changed so that interface can have intents/policySets attached. | ||
| Autowire at the domain level | Tuscany needs to decide if/how it will support the domain-level autowiring | ||
| Autowire value for the logical domain composite | I think Tuscany is OK here as the autowire=false for the domain composite | ||
| Unresolved bindings on references |
| ||
| Component Type file name is too restrictive |
| ||
| ComponentType Properties should not have a source |
| ||
| Confusing words in Section 5.3 relating to ConversationalIntent |
| ||
| "SCA schema fixes requested for sca-core.xsd (based on OSOA site versions that may be copied to OASIS site)" |
| ||
| Description elements in SCDL |
| ||
| No schema or extension model definitions for contributions |
| ||
| component type allows to specify wire targets on references |
| ||
| Assembly Specification should not state what marks a Javainterface as Local |
| ||
| Implementation.composite pseudo-schema incorrect |
| ||
| Conflicting Specification of Values for Many-Valued StringProperties |
| ||
| WSDL extension should not be required for conversations |
| ||
| XSD definitions of Component Service and Component Referencehave unintended features |
| ||
| Specification wording unclear on how local and remoteable interfaces are specified |
| ||
| Constraining Type talks about non-optional references but does not define what they are |
| ||
| How to map WSDL 1.1. portType to WSDL 2.0 interface and vice versa? |
| ||
| Language neutrality edits |
| ||
| some smaller things we need to fix in the assembly specification |
| ||
| Need to clarify definition of Bidirectional Interfaces |
| Make sure Tuscany is consistent with the specified behavior | |
| Conflicting domain-level <wire> deployments |
| Tuscany needs to implement the proposal | |
| Identifying wire format and operation selection |
| add "wireFormat" and "operationSelector" for bindings | |
| What is the default value for many and mustSupply on Properties? |
| remove "mustSupply" from <component> | |
| SCA Composite Visibility |
| This seems to be a clarification by the spec | |
| Composite Completeness |
| Tuscany needs to add more validations to ensure the completeness of the composite for implementaiton.composite | |
| Compatability of component type side files |
| Each implementation type has to decide how to support the componentType file | |
| Allow multiple definitions.xml files |
| Tuscany should allow META-INF/definitions.xml from SCA contributions. These definitions become visible to the SCA domain | |
| Need for a Callback annotation for WSDL interface files | Tuscany needs to handle sca:callback extensibility elements in WSDL | ||
| Component URI is not well described | Tuscany needs to support the structural URI based on this proposal | ||
| SCDL artifact resolution underspecified | Adjust the artifact resolution based on the proposal in this JIRA | ||
| Need to define Namespace handling for included Composites | Tuscany needs to adjust how the composite include is aggregated based on the proposal in this JIRA | ||
| Incorrect description of <Operation/> child elements inAssembly | I see this conflicts with http://www.osoa.org/jira/browse/POLICY-58  | ||
| Long-Running Request-Response Operations | Tuscany needs to support the proposal | ||
| Add a Section documenting naming conventions to the start ofthe SCA Assembly Specification | No action is required | ||
| Corrections to the contributions schema | See ASSEMLY-28 | ||
| Duplicated atributes in sca-binding-sca.xsd and sca-implementation-composite.xsd | No action is required | ||
| "Section on ""Wire"" in Appendix is Incorrect" | Tuscany already has the correct model, No action is required | ||
| Do we need appendix A (pseudo-schema)? | No action is required |
...