DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
http://www.osoa.org/jira/secure/BrowseProjects.jspa![]()
ASSEMBLY-43 | for implentations.*'s fix attributes that should show qnames as values | |
ASSEMBLY-1 | Is binding.sca always present? | |
ASSEMBLY-3 | Is interface.java specification normative in SCA-Assembly spec? | |
ASSEMBLY-6 | usage of not promoted references | |
ASSEMBLY-23 | SCA <anyAttribute.../> declarations should use namespace ##other rather than ##any | |
ASSEMBLY-25 | Can Implementation change property values after instantiaion | |
ASSEMBLY-28 | Missing XSD for contributions | |
ASSEMBLY-38 | Clarify whether a Default Value for a Property must appear inthe componentType of an implementation | |
ASSEMBLY-39 | Permit intents and PolicySets on <interface/> elements | |
ASSEMBLY-40 | Autowire at the domain level | |
ASSEMBLY-42 | Autowire value for the logical domain composite | |
ASSEMBLY-57 | Unresolved bindings on references | |
ASSEMBLY-67 | Component Type file name is too restrictive | |
ASSEMBLY-68 | ComponentType Properties should not have a source | |
ASSEMBLY-35 | Confusing words in Section 5.3 relating to ConversationalIntent | |
ASSEMBLY-32 | "SCA schema fixes requested for sca-core.xsd (based on OSOA site versions | that may be copied to OASIS site)" |
ASSEMBLY-60 | Description elements in SCDL | |
ASSEMBLY-53 | No schema or extension model definitions for contributions | |
ASSEMBLY-5 | component type allows to specify wire targets on references | |
ASSEMBLY-92 | Assembly Specification should not state what marks a Javainterface as Local | |
ASSEMBLY-71 | Implementation.composite pseudo-schema incorrect | |
ASSEMBLY-14 | Conflicting Specification of Values for Many-Valued StringProperties | |
ASSEMBLY-22 | WSDL extension should not be required for conversations | |
ASSEMBLY-18 | XSD definitions of Component Service and Component Referencehave unintended features | |
ASSEMBLY-63 | Specification wording unclear on how local and remoteable interfaces are specified | |
ASSEMBLY-65 | Constraining Type talks about non-optional references but does not define what they are | |
ASSEMBLY-77 | How to map WSDL 1.1. portType to WSDL 2.0 interface and vice versa? | |
ASSEMBLY-69 | Language neutrality edits | |
ASSEMBLY-45 | some smaller things we need to fix in the assembly specification | |
ASSEMBLY-56 | Need to clarify definition of Bidirectional Interfaces | |
ASSEMBLY-41 | Conflicting domain-level <wire> deployments | |
ASSEMBLY-79 | Identifying wire format and operation selection | |
ASSEMBLY-62 | What is the default value for many and mustSupply on Properties? | |
ASSEMBLY-26 | SCA Composite Visibility | |
ASSEMBLY-51 | Composite Completeness | |
ASSEMBLY-36 | Compatability of component type side files | |
ASSEMBLY-44 | Allow multiple definitions.xml files | |
ASSEMBLY-89 | Need for a Callback annotation for WSDL interface files | |
ASSEMBLY-16 | Component URI is not well described | |
ASSEMBLY-8 | SCDL artifact resolution underspecified | |
ASSEMBLY-17 | Need to define Namespace handling for included Composites | |
ASSEMBLY-30 | Incorrect description of <Operation/> child elements inAssembly | |
ASSEMBLY-33 | Long-Running Request-Response Operations | |
ASSEMBLY-96 | Add a Section documenting naming conventions to the start ofthe SCA Assembly Specification | |
ASSEMBLY-74 | Corrections to the contributions schema | |
ASSEMBLY-81 | Duplicated atributes in sca-binding-sca.xsd and sca-implementation-composite.xsd | |
ASSEMBLY-75 | "Section on ""Wire"" in Appendix is Incorrect" | |
ASSEMBLY-72 | Do we need appendix A (pseudo-schema)? |
General
Feature | OSOA Ref | OSOA Description | OASIS Ref | OASIS Description |
|---|---|---|---|---|
Schema namespace |
|
|
...