DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
OASIS JIRA | Description | Action |
|---|---|---|
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 |
| |
"Section on ""Wire"" in Appendix is Incorrect" |
| |
Do we need appendix A (pseudo-schema)? |
|
General
Feature | OSOA Ref | OSOA Description | OASIS Ref | OASIS Description |
|---|---|---|---|---|
Schema namespace |
|
|
Assembly
OSOA - Tuscany 1.x (SCA_AssemblyModel_V100 +)
OASIS - sca-assembly-1.1-spec-cd01-rev3 + Current JIRA
Test | Feature | OASIS Ref | OASIS Change |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
| Properties | Specification of multi-value string properties | |
|
|
|
|
|
|
|
|
|
|
|
|
Java
OSOA - Tuscany 1.x (SCA_JavaAnnotationsAndAPIs_V100 +)
OASIS - sca-javacaa-1.1-spec-cd01
OASIS JIRA | Description | Action |
|---|---|---|
Spurious cast() method definition in ComponentContext interface | ||
Constructor name information may not be available | ||
Java CAA spec does not contain the interface.java schema | ||
Incorrect definition of the SCA JEE JSP Tag library | ||
Inconsistent use of a and an when referring to annotations | ||
Normative references to SCA Spec docs point to v1.00 docs | ||
Missing word "type" for "return type" in CAA spec - sec 3.1 | ||
Incorrect description of @Scope annotation default | ||
Incorrect reference to "original request" | ||
Should not say callback ID is passed in reference parameters | ||
Incorrect code in section 6.7.2 example | ||
SCA Spring C & I specification does not state the purpose of sca:composite element | ||
Describe the concurrency model for each scope | ||
SCA Spring Client and Implementation Specification uses an unacceptable namespace | ||
When more than one interface with the same unqualified name used in the @Service annotation | ||
SCA Java Specifications do not Adequately Define the ComponentType of a Java implementation | ||
Version requirements for SDO, JAXB and JAX-WS | ||
@Callback annotation does not feature in section on Interfaces | ||
Missing description of what the @EagerInit annotation does | ||
@Reference annotation can also be used on a constructor parameter. | ||
Incorrect examples of methods annotated @Init and @Destroy | ||
Inconsistent method description for @Init and @Destroy annotations | ||
Incorrect generated service name | ||
Clarify Request Scope lifetime | ||
annotations on parameters | ||
EJB remove method on EJBHome |
...
Policy
...
Feature
OSOA
...
OSOA Description
...
OASIS Ref
...
OASIS Description
...
Schema namespace
...
...
http://www.osoa.org/xmlns/sca/1.0
...
...
-
...
Assembly
OSOA - Tuscany 1.x (SCA_Policy_AssemblyModelFramework_V100 +)
OASIS - sca-assemblypolicy-11.1-spec-cd01-rev3 + Current wd-10
OASIS JIRA | Test Description | Feature | OASIS Ref | OASIS Change |
|---|---|---|---|---|
|
|
|
| |
|
|
|
| |
|
|
|
| |
| Properties | Specification of multi-value string properties | ||
|
|
|
| |
|
|
|
| |
|
|
|
|
Java Annotations and APIS
OSOA - Tuscany 1.x (SCA_JavaAnnotationsAndAPIs_V100 +)
OASIS - sca-javacaa-1.1-spec-cd01
Policy
...
Action | ||
|---|---|---|
intents names defined by SCA should be defined using camel case |
| |
How are mayProvide intents on bindings satisfied |
| |
Clarify scope of ordered intent |
| |
Limit policySet attachment to bindings |
| |
Remove <operation/> elements from the specification |
| |
Intents which conflict with binding configuration |
| |
Clarify the handling of Intents |
| |
Wire validation rules have changed |
| |
How do we tell what a policySet @provides? |
| |
Policy algorithm gets required intents from what interfaces definitions/declarations? |
| |
How to configure policySets |
| |
Need a clear way to distinguish Implementation Intents from Interaction Intents |
| |
Infoset for policySet/@appliesTo |
| |
Fix SCA Policy schema complex types for Qualifier and PolicySet |
| |
Need Support for Mutually exclusive intents |
| |
Improve description of the overides available to the two different hierarchies in SCA |
| |
The URL for the location of the ws-policy.xsd is incorrect. |
| |
Need more precision on when policies in a policySet are in effect |
| |
Security implementation policy should be validate-able by schema |
| |
More direct, structural qualifier definition |
| |
Profile intent extension - provides other intents |
| |
Should qualifiable intents have a default qualifier |
| |
Need Transaction Policy Spec |
| |
External mechanism for attaching intents or policySets |
| |
Include definition on 'conversational' intent as mentioned in SCA Assembly |
| |
Implicit addition of intents based on a service or reference's @requires list |
|