ASSEMBLY-1

Is binding.sca always present?

If a component service is configured with binding.ws, can be accessed by a component reference in the same composite with binding.sca?

ASSEMBLY-3

Is interface.java specification normative in SCA-Assembly spec?

No action is required

ASSEMBLY-5

component type allows to specify wire targets on references

Push teh getTargets() method from Reference to ComponentReference

ASSEMBLY-6

usage of not promoted references

Make sure the reference resolution follows what's described by the assembly spec

ASSEMBLY-8

SCDL artifact resolution underspecified

Adjust the artifact resolution based on the proposal in this JIRA

ASSEMBLY-14

Conflicting Specification of Values for Many-Valued StringProperties

Adjust the property value processing to conform to the new syntax

ASSEMBLY-16

Component URI is not well described

Tuscany needs to support the structural URI based on this proposal

ASSEMBLY-17

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

ASSEMBLY-18

XSD definitions of Component Service and Component Referencehave unintended features

ASSEMBLY-22

WSDL extension should not be required for conversations

Make sure conversational intent is supported at interface and service

ASSEMBLY-23

SCA <anyAttribute.../> declarations should use namespace ##other rather than ##any

Update the xsd from OASIS

ASSEMBLY-25

Can Implementation change property values after instantiaion

No action is required

ASSEMBLY-26

SCA Composite Visibility

This seems to be a clarification by the spec

ASSEMBLY-28

Missing XSD for contributions

Update the xsd from OASIS. Update the Import/Export model to
be extensible as the XSD allows xsd:any and xsd:anyAttribute

ASSEMBLY-3230

Incorrect description of <Operation/> child elements inAssembly

I see this conflicts with  http://www.osoa.org/jira/browse/POLICY-58

ASSEMBLY-32

" "SCA schema fixes requested for sca-core.xsd (based on OSOA site versions that may be copied to OASIS site)"

ASSEMBLY-3533

Long-Running Request-Response Operations

Tuscany needs to support the proposal

ASSEMBLY-35

Confusing words in Section 5.3 Confusing words in Section 5.3 relating to ConversationalIntent

ASSEMBLY-36

Compatability of component type side files

Each implementation type has to decide how to support the componentType file

ASSEMBLY-38

Clarify whether a Default Value for a Property must appear inthe componentType of an implementation

No action is required

ASSEMBLY-39

Permit intents and PolicySets on <interface/> elements

The policy model needs to be changed so that interface can have intents/policySets attached.

ASSEMBLY-40

Autowire at the domain level

Tuscany needs to decide if/how it will support the domain-level autowiring

ASSEMBLY-4241

Conflicting domain-level <wire> deployments

Tuscany needs to implement the proposal

ASSEMBLY-42

Autowire Autowire value for the logical domain composite

I think Tuscany is OK here as the autowire=false for the domain composite

ASSEMBLY-43

for implentations.*'s fix attributes that should show qnames as values

ASSEMBLY-57

Unresolved bindings on references

44

Allow multiple definitions.xml files

Tuscany should allow META-INF/definitions.xml from SCA contributions. These definitions become visible to the SCA domain Add the support for "componentName/serviceName/bindingName" as the wire target

ASSEMBLY-67 Component Type file name is too restrictive 45

some smaller things we need to fix in the assembly specification

ASSEMBLY-68

ComponentType Properties should not have a source

51

Composite Completeness

Tuscany needs to add more validations to ensure the completeness of the composite for implementaiton.composite  

ASSEMBLY-60

Description elements in SCDL

Support documentation element in the model and processors

ASSEMBLY-53

No schema or extension model definitions for contributions

ASSEMBLY-92

Assembly Specification should not state what marks a Javainterface as Local

56

Need to clarify definition of Bidirectional Interfaces

Make sure Tuscany is consistent with the specified behavior  

ASSEMBLY-71

Implementation.composite pseudo-schema incorrect

57

Unresolved bindings on references

Add the support for "componentName/serviceName/bindingName" as the wire target  

ASSEMBLY-22

WSDL extension should not be required for conversations

60

Description elements in SCDL

Support documentation element in the model and processors Make sure conversational intent is supported at interface and service

ASSEMBLY-6362

What is the default value for many and mustSupply on Properties?

remove "mustSupply" from <component>

ASSEMBLY-63

Specification wording unclear on how local and remoteable interfaces are specified

Remotable is IDL specific

ASSEMBLY-65

Constraining Type talks about non-optional references but does not define what they are

ASSEMBLY-7767

Component Type file name is too restrictive

ASSEMBLY-68

ComponentType Properties should not have a source

How to map WSDL 1.1. portType to WSDL 2.0 interface and vice versa?

Remove the wsdl2.0 specfics from sca namespace. Potentially add interface.wsdl2 under tuscany ns

ASSEMBLY-69

Language neutrality edits

ASSEMBLY-45 some smaller things we need to fix in the assembly specification 71

Implementation.composite pseudo-schema incorrect

ASSEMBLY-56

Need to clarify definition of Bidirectional Interfaces

72

Do we need appendix A (pseudo-schema)?

No action is required Make sure Tuscany is consistent with the specified behavior

ASSEMBLY-41

Conflicting domain-level <wire> deployments

74

Corrections to the contributions schema

See ASSEMLY-28 Tuscany needs to implement the proposal

ASSEMBLY-79

Identifying wire format and operation selection

75

"Section on ""Wire"" in Appendix is Incorrect"

Tuscany already has the correct model, No action is required add "wireFormat" and "operationSelector" for bindings

ASSEMBLY-62

What is the default value for many and mustSupply on Properties?

77

How to map WSDL 1.1. portType to WSDL 2.0 interface and vice versa?

Remove the wsdl2.0 specfics from sca namespace. Potentially add interface.wsdl2 under tuscany ns remove "mustSupply" from <component>

ASSEMBLY-26

SCA Composite Visibility

79

Identifying wire format and operation selection

add "wireFormat" and "operationSelector" for bindings This seems to be a clarification by the spec

ASSEMBLY-51

Composite Completeness

Tuscany needs to add more validations to ensure the completeness of the composite for implementaiton.composite

ASSEMBLY-36

Compatability of component type side files

Each implementation type has to decide how to support the componentType file

ASSEMBLY-44

Allow multiple definitions.xml files

Tuscany should allow META-INF/definitions.xml from SCA contributions. These definitions become visible to the SCA domain

ASSEMBLY-30

Incorrect description of <Operation/> child elements inAssembly

I see this conflicts with  http://www.osoa.org/jira/browse/POLICY-58

ASSEMBLY-33

Long-Running Request-Response Operations

Tuscany needs to support the proposal

ASSEMBLY-72

Do we need appendix A (pseudo-schema)?

No action is required

ASSEMBLY-74

Corrections to the contributions schema

See ASSEMLY-28

ASSEMBLY-75

"Section on ""Wire"" in Appendix is Incorrect"

Tuscany already has the correct model, No action is required

81

Duplicated atributes in

ASSEMBLY-81

Duplicated atributes in sca-binding-sca.xsd and sca-implementation-composite.xsd

No action is required

ASSEMBLY-89

Need for a Callback annotation for WSDL interface files for a Callback annotation for WSDL interface files

Tuscany needs to handle sca:callback extensibility elements in WSDL

ASSEMBLY-92

Assembly Specification should not state what marks a Javainterface as Local

  Tuscany needs to handle sca:callback extensibility elements in WSDL

ASSEMBLY-96

Add a Section documenting naming conventions to the start ofthe SCA Assembly Specification

No action is required

JAVA-112

Spurious cast() method definition in ComponentContext interface

5

EJB remove method on EJBHome

JAVA-111

Constructor name information may not be available

Adjust the @Property/@Reference processor on CDI

JAVA-84

Java CAA spec does not contain the interface.java schema

20

annotations on parameters

@Reference, @Property can only be used for constructor parameters. Tuscany
may need to report violations  

JAVA-83

Incorrect definition of the SCA JEE JSP Tag library

21

Clarify Request Scope lifetime

Remove the Request scope  

JAVA-8232

Incorrect generated service name Inconsistent use of a and an when referring to annotations

JAVA-81

Normative references to SCA Spec docs point to v1.00 docs

41

Inconsistent method description for @Init and @Destroy annotations

Tuscany already validates the pattern  

JAVA-42

Incorrect examples of methods annotated @Init and @Destroy

JAVA-79

Missing word "type" for "return type" in CAA spec - sec 3.1

JAVA-75

Incorrect description of @Scope annotation default

43

@Reference annotation can also be used on a constructor parameter.

  Make sure the scope is default to "COMPOSITE" if there is an @Conversational

JAVA-73 Incorrect reference to "original request" 47

Missing description of what the @EagerInit annotation does

JAVA-7248

Should not say callback ID is passed in reference parameters @Callback annotation does not feature in section on Interfaces

JAVA-71 Incorrect code in section 6.7.2 example 49

Version requirements for SDO, JAXB and JAX-WS

JAVA-6455

SCA Spring C & I specification does not state the purpose of sca:composite element Remove the sca:composite Java Specifications do not Adequately Define the ComponentType of a Java implementation

Check the compontType to see if it matches the rules defined by this proposal

JAVA-6156

When more than one interface with the same unqualified name used in the @Service annotation Describe the concurrency model for each scope

JAVA-57

SCA Spring Client and Implementation Specification uses an unacceptable namespace

Update the namespace based on the OASIS spec

JAVA-5661

Describe the concurrency model for each scope When more than one interface with the same unqualified name used in the @Service annotation

JAVA-5564

SCA Java Specifications do not Adequately Define the ComponentType of a Java implementation Spring C & I specification does not state the purpose of sca:composite element

Remove the sca:composite

JAVA-71

Incorrect code in section 6.7.2 example

  Check the compontType to see if it matches the rules defined by this proposal

JAVA-49 Version requirements for SDO, JAXB and JAX-WS 72

Should not say callback ID is passed in reference parameters

JAVA-48 @Callback annotation does not feature in section on Interfaces 73

Incorrect reference to "original request"

JAVA-4775

Missing Incorrect description of what the @EagerInit @Scope annotation does  default

Make sure the scope is default to "COMPOSITE" if there is an @Conversational

JAVA-4379

Missing word "type" for "return type" in CAA spec - sec 3.1 @Reference annotation can also be used on a constructor parameter.

JAVA-42 Incorrect examples of methods annotated @Init and @Destroy 81

Normative references to SCA Spec docs point to v1.00 docs

JAVA-4182

Inconsistent method description for @Init and @Destroy annotations use of a and an when referring to annotations

  Tuscany already validates the pattern

JAVA-3283

Incorrect generated service name definition of the SCA JEE JSP Tag library

JAVA-21

Clarify Request Scope lifetime

84

Java CAA spec does not contain the interface.java schema

  Remove the Request scope

JAVA-20

annotations on parameters

@Reference, @Property can only be used for constructor parameters. Tuscany
may need to report violations

112

Spurious cast() method definition in ComponentContext interface

JAVA-5

EJB remove method on EJBHome

111

Constructor name information may not be available

Adjust the @Property/@Reference processor on CDI  

intents names defined by SCA should be defined using camel case

POLICY-617

Implicit addition of intents based on a service or reference's @requires list How are mayProvide intents on bindings satisfied

POLICY-60

Clarify scope of ordered intent

8

Include definition on 'conversational' intent as mentioned in SCA Assembly

  Add "ordered" intent support

POLICY-59 Limit policySet attachment to bindings 15

External mechanism for attaching intents or policySets

POLICY-5817

Need Transaction Policy Spec Remove <operation/> elements from the specification

POLICY-56 Intents which conflict with binding configuration 18

Should qualifiable intents have a default qualifier

POLICY-55 Clarify the handling of Intents 22

Profile intent extension - provides other intents

POLICY-54 Wire validation rules have changed 24

More direct, structural qualifier definition

POLICY-53 How do we tell what a policySet @provides? 26

Security implementation policy should be validate-able by schema

POLICY-52 Policy algorithm gets required intents from what interfaces definitions/declarations? 29

Need more precision on when policies in a policySet are in effect

POLICY-46 How to configure policySets 37

The URL for the location of the ws-policy.xsd is incorrect.

POLICY-4438

Improve description of the overides available to the two different hierarchies in SCA Need a clear way to distinguish Implementation Intents from Interaction Intents

POLICY-4239

Infoset for policySet/@appliesTo Need Support for Mutually exclusive intents

POLICY-40

Fix SCA Policy schema complex types for Qualifier and PolicySet

POLICY-3942

Need Support for Mutually exclusive intents Infoset for policySet/@appliesTo

POLICY-3844

Need a clear way to distinguish Implementation Intents from Interaction Intents Improve description of the overides available to the two different hierarchies in SCA

POLICY-37 The URL for the location of the ws-policy.xsd is incorrect. 46

How to configure policySets

POLICY-52

Policy algorithm gets required intents from what interfaces definitions/declarations?

POLICY-2953

How do we tell what a policySet @provides? Need more precision on when policies in a policySet are in effect

POLICY-26 Security implementation policy should be validate-able by schema 54

Wire validation rules have changed

POLICY-2455

Clarify the handling of Intents More direct, structural qualifier definition

POLICY-22 Profile intent extension - provides other intents 56

Intents which conflict with binding configuration

POLICY-18 Should qualifiable intents have a default qualifier 58

Remove <operation/> elements from the specification

POLICY-1759

Limit policySet attachment to bindings Need Transaction Policy Spec

POLICY-15

External mechanism for attaching intents or policySets

60

Clarify scope of ordered intent

Add "ordered" intent support  

POLICY-861

How are mayProvide intents on bindings satisfied Include definition on 'conversational' intent as mentioned in SCA Assembly

POLICY-763

Implicit addition of intents based on a service or reference's @requires list intents names defined by SCA should be defined using camel case

BINDINGS-381

JMSDeliveryMode, JMSTimeToLive and JMSPriority defined as types different from what the JMS specification uses. Clarify use of URI vs. uri

BINDINGS-36 Does WSDL binding take precedend over policy intents 3

portType referred to inconsistently throughout specification

BINDINGS-35 Allow topics anywhere that queues can be used 5

JMS bindingType and atLeastOne intent overlaps with setting JMSDeliveryMode

BINDINGS-346

JMS bindingType and conversation intent Clarify default function selection and data binding behavior

BINDINGS-338

No bindingType for binding.ws Correlation property names are odd, and the space of options is not extensible.

BINDINGS-26 JMS binding pseudo-schemas inconsistent with assembly 9

Use of wsdli:wsdlLocation does not match WSDL 2.0 specification

BINDINGS-20 JMS binding URI should follow JMS IRI scheme submitted to IETF 10

Rules for WSDL generation create invalid WSDL by using "/" where it is not allowed.

BINDINGS-19 Web Service binding should allow #wsdl.binding with reference targets 12

Are JMS message selectors supported?

BINDINGS-1813

What namespace(s) do we use for each binding? Clarify the rules on which queues are used for responses and callbacks

BINDINGS-1715

Rules for Binding compatibility Namespace/location for WS-Addressing is incorrect in WebService binding spec/XSD

BINDINGS-16

binding.ws reference to assembly spec for interface mapping is incorrect

BINDINGS-1517 Namespace

/location for WS-Addressing is incorrect in WebService binding spec/XSD Rules for Binding compatibility

BINDINGS-1318

Clarify the rules on which queues are used for responses and callbacks What namespace(s) do we use for each binding?

BINDINGS-12 Are JMS message selectors supported? 19

Web Service binding should allow #wsdl.binding with reference targets

BINDINGS-10 Rules for WSDL generation create invalid WSDL by using "/" where it is not allowed. 20

JMS binding URI should follow JMS IRI scheme submitted to IETF

BINDINGS-9 Use of wsdli:wsdlLocation does not match WSDL 2.0 specification 26

JMS binding pseudo-schemas inconsistent with assembly

BINDINGS-833

Correlation property names are odd, and the space of options is not extensible. No bindingType for binding.ws

BINDINGS-634

Clarify default function selection and data binding behavior JMS bindingType and conversation intent

BINDINGS-5 JMS bindingType and atLeastOne intent overlaps with setting JMSDeliveryMode 35

Allow topics anywhere that queues can be used

BINDINGS-3 portType referred to inconsistently throughout specification 36

Does WSDL binding take precedend over policy intents

BINDINGS-138

Clarify use of URI vs. uri JMSDeliveryMode, JMSTimeToLive and JMSPriority defined as types different from what the JMS specification uses.