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? |
| |
| usage of not promoted references |
| |
| SCA <anyAttribute.../> declarations should use namespace ##other rather than ##any |
| |
| Can Implementation change property values after instantiaion |
| |
| Missing XSD for contributions |
| |
| Clarify whether a Default Value for a Property must appear inthe componentType of an implementation |
| |
| Permit intents and PolicySets on <interface/> elements |
| |
| Autowire at the domain level |
| |
| Autowire value for the logical 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 |
| |
| Conflicting domain-level <wire> deployments |
| |
| Identifying wire format and operation selection |
| |
| What is the default value for many and mustSupply on Properties? |
| |
| SCA Composite Visibility |
| |
| Composite Completeness |
| |
| Compatability of component type side files |
| |
| Allow multiple definitions.xml files |
| |
| Need for a Callback annotation for WSDL interface files |
| |
| Component URI is not well described |
| |
| SCDL artifact resolution underspecified |
| |
| Need to define Namespace handling for included Composites |
| |
| Incorrect description of <Operation/> child elements inAssembly |
| |
| Long-Running Request-Response Operations |
| |
| Add a Section documenting naming conventions to the start ofthe SCA Assembly Specification |
| |
| Corrections to the contributions schema |
| |
| 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 |
...