ASSEMBLY-43

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

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? Reference side is different now. When no bindings it dervies them from service
If service has binding.ws it doesn't have binding.sca

ASSEMBLY-3

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

No action is required

ASSEMBLY-65

component type allows to specify wire targets on references

Push teh getTargets() method from Reference to ComponentReference

ASSEMBLY-6

usage of not usage of not promoted references

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

ASSEMBLY-23

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

Update the xsd from OASIS

8

SCDL artifact resolution underspecified

Adjust the artifact resolution based on the proposal in this JIRA

TUSCANY-3079

ASSEMBLY-14

Conflicting Specification of Values for Many-Valued StringProperties

Adjust the property value processing to conform to the new syntax, Can't have multiple properties with the same name

ASSEMBLY-25

Can Implementation change property values after instantiaion

No action is required

ASSEMBLY-28

Missing XSD for contributions

16

Component URI is not well described

Tuscany needs to support the structural URI based on this proposal Update the xsd from OASIS. Update the Import/Export model to
be extensible as the XSD allows xsd:any and xsd:anyAttribute

ASSEMBLY-38

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

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 No action is required

ASSEMBLY-39

Permit intents and PolicySets on <interface/> elements

18

XSD definitions of Component Service and Component Referencehave unintended features

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

ASSEMBLY-40

Autowire at the domain level

22

WSDL extension should not be required for conversations

Make sure conversational intent is supported at interface and service Tuscany needs to decide if/how it will support the domain-level autowiring

ASSEMBLY-42

Autowire value for the logical domain composite

23

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

Update the xsd from OASIS, can we support OSOA and OASIS xsds? I think Tuscany is OK here as the autowire=false for the domain composite

ASSEMBLY-57

Unresolved bindings on references

25

Can Implementation change property values after instantiaion

No action is required Add the support for "componentName/serviceName/bindingName" as the wire target

ASSEMBLY-67 Component Type file name is too restrictive 26

SCA Composite Visibility

This seems to be a clarification by the spec

ASSEMBLY-68

ComponentType Properties should not have a source

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-35

Confusing words in Section 5.3 relating to ConversationalIntent

30

Incorrect description of <Operation/> child elements inAssembly

I see this conflicts with  http://www.osoa.org/jira/browse/POLICY-58 Policy-58 did win and operation elements are no longer required  

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

33

Long-Running Request-Response Operations

Tuscany needs to support the proposal Support documentation element in the model and processors

ASSEMBLY-53 No schema or extension model definitions for contributions 35

Confusing words in Section 5.3 relating to ConversationalIntent , Conversational support has gone

ASSEMBLY-536

Compatability of component type allows to specify wire targets on references

Push teh getTargets() method from Reference to ComponentReference

type side files

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

ASSEMBLY-92

Assembly Specification should not state what marks a Javainterface as Local

38

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

No action is required  

ASSEMBLY-71

Implementation.composite pseudo-schema incorrect

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-14

Conflicting Specification of Values for Many-Valued StringProperties

Adjust the property value processing to conform to the new syntax

ASSEMBLY-22

WSDL extension should not be required for conversations

41

Conflicting domain-level <wire> deployments

Tuscany needs to implement the proposal Make sure conversational intent is supported at interface and service

ASSEMBLY-18

XSD definitions of Component Service and Component Referencehave unintended features

42

Autowire value for the logical domain composite

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

ASSEMBLY-63

Specification wording unclear on how local and remoteable interfaces are specified

Remotable is IDL specific

43

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

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?

44

Allow multiple definitions.xml files

Tuscany should allow META-INF/definitions.xml from SCA contributions. These definitions become visible to the SCA domain Remove the wsdl2.0 specfics from sca namespace. Potentially add interface.wsdl2 under tuscany ns

ASSEMBLY-69

Language neutrality edits

45

some smaller things we need to fix in the assembly specification

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

Composite Completeness

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

ASSEMBLY-53

No schema or extension model definitions for contributions

ASSEMBLY-56

Need to clarify definition of Bidirectional Interfaces

Make sure Tuscany is consistent with the specified behavior

ASSEMBLY-41

Conflicting domain-level <wire> deployments

57

Unresolved bindings on references

Add the support for "componentName/serviceName/bindingName" as the wire target Tuscany needs to implement the proposal

ASSEMBLY-79

Identifying wire format and operation selection

60

Description elements in SCDL

Support documentation element in the model and processors add "wireFormat" and "operationSelector" for bindings

ASSEMBLY-62

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

remove "mustSupply" from <component>

ASSEMBLY-26

SCA Composite Visibility

63

Specification wording unclear on how local and remoteable interfaces are specified

Remotable is IDL specific This seems to be a clarification by the spec

ASSEMBLY-51

Composite Completeness

65

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

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

ASSEMBLY-36

Compatability of component type side files

67

Component Type file name is too restrictive Assembly has washed itself somewhat of ComponentType files Up to C&I to define what to do, BPEL has got rid of them, Tuscany should ignore for 2.x

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

ASSEMBLY-44

Allow multiple definitions.xml files

68

ComponentType Properties should not have a source

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

ASSEMBLY-89

Need for a Callback annotation for WSDL interface files

69

Language neutrality edits

  Tuscany needs to handle sca:callback extensibility elements in WSDL

ASSEMBLY-16

Component URI is not well described

71

Implementation.composite pseudo-schema incorrect

  Tuscany needs to support the structural URI based on this proposal

ASSEMBLY-8

SCDL artifact resolution underspecified

72

Do we need appendix A (pseudo-schema)?

No action is required Adjust the artifact resolution based on the proposal in this JIRA

ASSEMBLY-1774

Need to define Namespace handling for included Composites

Corrections to the contributions schema, sca-contribution.xml specify what is deployable We should use in our samples

See ASSEMLY-28 Tuscany needs to adjust how the composite include is aggregated based on the proposal in this JIRA

ASSEMBLY-30

Incorrect description of <Operation/> child elements inAssembly

75

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

Tuscany already has the correct model, No action is required 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-96

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

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 No action is required

ASSEMBLY-74

Corrections to the contributions schema

79

Identifying wire format and operation selection

add "wireFormat" and "operationSelector" for bindings See ASSEMLY-28

ASSEMBLY-81

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

No action is required

ASSEMBLY-75

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

89

Need for a Callback annotation for WSDL interface files

Tuscany needs to handle sca:callback extensibility elements in WSDL Tuscany already has the correct model, No action is required

ASSEMBLY-72 Do we need appendix A (pseudo-schema)? 92

Assembly Specification should not state what marks a Javainterface as Local

ASSEMBLY-96

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

No action is required

N/A

No @replace attribute for <wire> in OSOA spec

No action is required

N/A

No <value> subelement for property in OSOA spec, so ASM50028,ASM50029 in OASIS spec couldn't be tested for vtest code.

No action is required

N/A

Top level composite services/references are not included in the virtual domain composite

Adjust logic and tests

POLICY-7

Implicit addition of intents based on a service or reference's @requires list

POLICY-8

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

POLICY-15

External mechanism for attaching intents or policySets

POLICY-17

Need Transaction Policy Spec

POLICY-18

Should qualifiable intents have a default qualifier

POLICY-22

Profile intent extension - provides other intents

POLICY-24

More direct, structural qualifier definition

POLICY-26

Security implementation policy should be validate-able by schema

POLICY-29

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

POLICY-37

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

POLICY-38

Improve description of the overides available to the two different hierarchies in SCA

POLICY-39

Need Support for Mutually exclusive intents

POLICY-40

Fix SCA Policy schema complex types for Qualifier and PolicySet

POLICY-42

Infoset for policySet/@appliesTo

POLICY-44

Need a clear way to distinguish Implementation Intents from Interaction Intents

POLICY-46

How to configure policySets

POLICY-52

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

POLICY-53

How do we tell what a policySet @provides?

POLICY-54

Wire validation rules have changed

POLICY-55

Clarify the handling of Intents

POLICY-56

Intents which conflict with binding configuration

POLICY-58

Remove <operation/> elements from the specification

POLICY-59

Limit policySet attachment to bindings

POLICY-60

Clarify scope of ordered intent

Add "ordered" intent support

POLICY-61

How are mayProvide intents on bindings satisfied

POLICY-63

intents names defined by SCA should be defined using camel case

Constructor name information may not be available

Adjust the @Property/@Reference processor on CDI

JAVA-845

EJB remove method on EJBHome Java CAA spec does not contain the interface.java schema

JAVA-83 Incorrect definition of the SCA JEE JSP Tag library 20

annotations on parameters

@Reference, @Property can only be used for constructor parameters. Tuscany
may need to report violations
<lresende> ReferenceProcessorTestCase and PropertyProcessorTestCase already test proper violation reports as in the specs </lresende>

JAVA-82

Inconsistent use of a and an when referring to annotations

21

Clarify Request Scope lifetime

Remove the Request scope

TUSCANY-3280  

JAVA-8132

Incorrect generated service name Normative references to SCA Spec docs point to v1.00 docs

JAVA-79 Missing word "type" for "return type" in CAA spec - sec 3.1 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-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-56

When more than one interface with the same unqualified name used in the @Service annotation

61

Describe the concurrency model for each scope

JAVA-64

SCA Spring C & I specification does not state the purpose of sca:composite element

Remove the sca:composite  

JAVA-55

SCA Java Specifications do not Adequately Define the ComponentType of a Java implementation

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

Tuscany already validates the pattern

JAVA-32

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

JAVA-21

Clarify Request Scope lifetime

Remove the Request scope

83

Incorrect definition of the SCA JEE JSP Tag library

JAVA-20

annotations on parameters

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

JAVA-5 EJB remove method on EJBHome 84

Java CAA spec does not contain the interface.java schema

JAVA-112

Spurious cast() method definition in ComponentContext interface

JAVA-111

Constructor name information may not be available

Adjust the @Property/@Reference processor on CDI

POLICY-63

intents names defined by SCA should be defined using camel case

POLICY-61

How are mayProvide intents on bindings satisfied

N/A

Support for @Remote attribute in in <interface.java/>

TUSCANY-3290  

POLICY-60

Clarify scope of ordered intent

Add "ordered" intent support

N/A

Illegal annotations in a service interface class

TUSCANY-3289  

POLICY-59

Limit policySet attachment to bindings

N/A

Support JAX-WS Client Asynchronous API for a Synchronous Service as described in Java CAA

TUSCANY-3294  

POLICY-58

Remove <operation/> elements from the specification

N/A

Update SCA Annotation definitions in sca-api to match the OASIS 1.1 Java CAA Specification

TUSCANY-3293

N/A

Verify @Service compliance with latest OASIS Java 1.1 draft spec

TUSCANY-3300

N/A

Verify @Property compliance with latest OASIS Java 1.1 draft spec

TUSCANY-3301

BINDINGS-1

JMSDeliveryMode, JMSTimeToLive and JMSPriority defined as types different from what the JMS specification uses.

POLICY-56

Intents which conflict with binding configuration

POLICY-55

Clarify the handling of Intents

POLICY-54

Wire validation rules have changed

POLICY-53

How do we tell what a policySet @provides?

POLICY-52

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

POLICY-46

How to configure policySets

POLICYBINDINGS-44 Need a clear way to distinguish Implementation Intents from Interaction Intents 5

JMS bindingType and atLeastOne intent overlaps with setting JMSDeliveryMode

POLICYBINDINGS-426

JMS bindingType and conversation intent Infoset for policySet/@appliesTo

POLICYBINDINGS-408

JMS bindingType and ordered intent - clarification needed Fix SCA Policy schema complex types for Qualifier and PolicySet

POLICYBINDINGS-3912

Are JMS message selectors supported? Need Support for Mutually exclusive intents

POLICYBINDINGS-38 Improve description of the overides available to the two different hierarchies in SCA 13

What namespace(s) do we use for each binding?

POLICYBINDINGS-3717

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

POLICYBINDINGS-2918

Clarify the rules on which queues are used for responses and callbacks Need more precision on when policies in a policySet are in effect

POLICYBINDINGS-26 Security implementation policy should be validate-able by schema 20

JMS binding URI should follow JMS IRI scheme submitted to IETF

POLICYBINDINGS-24 More direct, structural qualifier definition 26

JMS binding pseudo-schemas inconsistent with assembly

POLICYBINDINGS-22 Profile intent extension - provides other intents 29

Properties on Bindings

POLICYBINDINGS-1830

Normative reference consistency Should qualifiable intents have a default qualifier

POLICY-17

BINDINGS-31

What is a "plain name" for a connection factories or activation specs, and how is one distinguished from a JNDI name? Need Transaction Policy Spec

POLICYBINDINGS-15 External mechanism for attaching intents or policySets 32

Document the attributes inherited from the base definition provided by SCA Assembly specification.

POLICYBINDINGS-8 Include definition on 'conversational' intent as mentioned in SCA Assembly 33

Correlation property names are odd, and the space of options is not extensible.

POLICYBINDINGS-7 Implicit addition of intents based on a service or reference's @requires list 34

Clarify default function selection and data binding behavior

BINDINGS-35

Allow topics anywhere that queues can be used

BINDINGS-38

Clarify use of URI vs. uri

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

Clarify rules around combination of destination, CF and AS elements

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

How are mayProvide intents on bindings satisfied

BINDINGS-3462

Conformance statement numbering

  Clarify default function selection and data binding behavior

BINDINGS-33

Correlation property names are odd, and the space of options is not extensible.

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

How should SCA callback semantics be carried over Web Services?

BINDINGS-203

portType referred to inconsistently throughout specification JMS binding URI should follow JMS IRI scheme submitted to IETF

BINDINGS-198

No bindingType for binding.ws Web Service binding should allow #wsdl.binding with reference targets

BINDINGS-18 Clarify the rules on which queues are used for responses and callbacks 9

Use of wsdli:wsdlLocation does not match WSDL 2.0 specification

BINDINGS-1710

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

BINDINGS-1613

What namespace(s) do we use for each binding? binding.ws reference to assembly spec for interface mapping is incorrect

BINDINGS-15

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

BINDINGS-1316

binding.ws reference to assembly spec for interface mapping is incorrect What namespace(s) do we use for each binding?

BINDINGS-1217

Rules for Binding compatibility Are JMS message selectors supported?

BINDINGS-1019

Web Service binding should allow #wsdl.binding with reference targets Rules for WSDL generation create invalid WSDL by using "/" where it is not allowed.

BINDINGS-923

@wsdlElement definition needs clarification on "equivalent" and use of Use of wsdli:wsdlLocation does not match WSDL 2.0 specification constructs

BINDINGS-829

Properties on Bindings No bindingType for binding.ws

BINDINGS-630

Normative reference consistency JMS bindingType and conversation intent

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

Document the attributes inherited from the base definition provided by SCA Assembly specification.

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.