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

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

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.

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

Autowire at the domain level

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

ASSEMBLY-42

Autowire value for the logical domain composite

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

ASSEMBLY-57

Unresolved bindings on references

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

23

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

Update the xsd from OASIS, can we support OSOA and OASIS xsds?

ASSEMBLY-25

Can Implementation change property values after instantiaion

No action is required

ASSEMBLY-67

Component Type file name is too restrictive

ASSEMBLY-6826

SCA Composite Visibility

This seems to be a clarification by the spec ComponentType Properties should not have a source

ASSEMBLY-3528

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 Confusing words in Section 5.3 relating to ConversationalIntent

ASSEMBLY-3230

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 "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-5335

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

  No schema or extension model definitions for contributions

ASSEMBLY-536

component type allows to specify wire targets on references

Compatability of component type side files

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

  Push teh getTargets() method from Reference to ComponentReference

ASSEMBLY-9238

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

No action is required Assembly Specification should not state what marks a Javainterface as Local

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

Conflicting Specification of Values for Many-Valued StringProperties

40

Autowire at the domain level

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

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

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

45

some smaller things we need to fix in the assembly specification

ASSEMBLY-51

Composite Completeness

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

ASSEMBLY-69

Language neutrality edits

ASSEMBLY-4553

No schema or extension model definitions for contributions

  some smaller things we need to fix in the assembly specification

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

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

Need for a Callback annotation for WSDL interface files

Tuscany needs to handle sca:callback extensibility elements in WSDL

ASSEMBLY-16

Component URI is not well described

Tuscany needs to support the structural URI based on this proposal

ASSEMBLY-8

SCDL artifact resolution underspecified

Adjust the artifact resolution based on the proposal in this JIRA

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

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

ASSEMBLY-68

ComponentType Properties should not have a source

ASSEMBLY-69

Language neutrality edits

ASSEMBLY-71

Implementation.composite pseudo-schema incorrect

ASSEMBLY-72

Do we need appendix A (pseudo-schema)?

No action is required

ASSEMBLY-74

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

See ASSEMLY-28

ASSEMBLY-75

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

Tuscany already has the correct model, No action is required

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

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

No action is required

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

ASSEMBLY-79

Identifying wire format and operation selection

add "wireFormat" and "operationSelector" for bindings

ASSEMBLY-74

Corrections to the contributions schema

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)?

No action is required

JAVA-112

Spurious cast() method definition in ComponentContext interface

JAVA-111

Constructor name information may not be available

JAVA-84

Java CAA spec does not contain the interface.java schema

JAVA-83

Incorrect definition of the SCA JEE JSP Tag library

JAVA-82

Inconsistent use of a and an when referring to annotations

JAVA-81

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

JAVA-75

Incorrect description of @Scope annotation default

JAVA-73

Incorrect reference to "original request"

JAVA-72

Should not say callback ID is passed in reference parameters

JAVA-71

Incorrect code in section 6.7.2 example

JAVA-64

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

JAVA-61

Describe the concurrency model for each scope

JAVA-57

SCA Spring Client and Implementation Specification uses an unacceptable namespace

JAVA-56

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

JAVA-55

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

JAVA-49

Version requirements for SDO, JAXB and JAX-WS

JAVA-48

@Callback annotation does not feature in section on Interfaces

JAVA-47

Missing description of what the @EagerInit annotation does

JAVA-43

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

JAVA-42

Incorrect examples of methods annotated @Init and @Destroy

JAVA-41

Inconsistent method description for @Init and @Destroy annotations

JAVA-32

Incorrect generated service name

JAVA-21

Clarify Request Scope lifetime

JAVA-20

annotations on parameters

JAVA-5

EJB remove method on EJBHome

POLICY-63

intents names defined by SCA should be defined using camel case

POLICY-61

How are mayProvide intents on bindings satisfied

POLICY-60

Clarify scope of ordered intent

POLICY-59

Limit policySet attachment to bindings

POLICY-58

Remove <operation/> elements from the specification

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

POLICY-44

Need a clear way to distinguish Implementation Intents from Interaction Intents

POLICY-42

Infoset for policySet/@appliesTo

POLICY-40

Fix SCA Policy schema complex types for Qualifier and PolicySet

POLICY-39

Need Support for Mutually exclusive intents

POLICY-38

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.

POLICY-29

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

POLICY-26

Security implementation policy should be validate-able by schema

POLICY-24

More direct, structural qualifier definition

POLICY-22

Profile intent extension - provides other intents

POLICY-18

Should qualifiable intents have a default qualifier

POLICY-17

Need Transaction Policy Spec

POLICY-15

External mechanism for attaching intents or policySets

POLICY-8

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

POLICY-7

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

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

JAVA-5

EJB remove method on EJBHome

JAVA-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-21

Clarify Request Scope lifetime

Remove the Request scope

TUSCANY-3280

JAVA-32

Incorrect generated service name

JAVA-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-43

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

JAVA-47

Missing description of what the @EagerInit annotation does

JAVA-48

@Callback annotation does not feature in section on Interfaces

JAVA-49

Version requirements for SDO, JAXB and JAX-WS

JAVA-55

SCA 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-56

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

JAVA-57

SCA Spring Client and Implementation Specification uses an unacceptable namespace

Update the namespace based on the OASIS spec

JAVA-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-71

Incorrect code in section 6.7.2 example

JAVA-72

Should not say callback ID is passed in reference parameters

JAVA-73

Incorrect reference to "original request"

JAVA-75

Incorrect description of @Scope annotation default

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

JAVA-79

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

JAVA-81

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

JAVA-82

Inconsistent use of a and an when referring to annotations

JAVA-83

Incorrect definition of the SCA JEE JSP Tag library

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

N/A

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

TUSCANY-3290

N/A

Illegal annotations in a service interface class

TUSCANY-3289

N/A

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

TUSCANY-3294

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.

BINDINGS-5

JMS bindingType and atLeastOne intent overlaps with setting JMSDeliveryMode

BINDINGS-6

JMS bindingType and conversation intent

BINDINGS-8

JMS bindingType and ordered intent - clarification needed

BINDINGS-12

Are JMS message selectors supported?

BINDINGS-13

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

BINDINGS-17

Rules for Binding compatibility

BINDINGS-18

Clarify the rules on which queues are used for responses and callbacks

BINDINGS-20

JMS binding URI should follow JMS IRI scheme submitted to IETF

BINDINGS-26

JMS binding pseudo-schemas inconsistent with assembly

BINDINGS-29

Properties on Bindings

BINDINGS-30

Normative reference consistency

BINDINGS-31

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

BINDINGS-32

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

BINDINGS-33

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

BINDINGS-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-40

Clarify rules around combination of destination, CF and AS elements

BINDINGS-48

How are mayProvide intents on bindings satisfied

BINDINGS-62

Conformance statement numbering

BINDINGS-2

How should SCA callback semantics be carried over Web Services?

BINDINGS-3

portType referred to inconsistently throughout specification

BINDINGS-8

No bindingType for binding.ws

BINDINGS-9

Use of wsdli:wsdlLocation does not match WSDL 2.0 specification

BINDINGS-10

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

BINDINGS-13

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

BINDINGS-15

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

Rules for Binding compatibility

BINDINGS-38

Clarify use of URI vs. uri

BINDINGS-36

Does WSDL binding take precedend over policy intents

BINDINGS-35

Allow topics anywhere that queues can be used

BINDINGS-34

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

BINDINGS-20

JMS binding URI should follow JMS IRI scheme submitted to IETF

BINDINGS-19

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

BINDINGS-18

Clarify the rules on which queues are used for responses and callbacks

BINDINGS-23

@wsdlElement definition needs clarification on "equivalent" and use of WSDL 2.0 constructs

BINDINGS-29

Properties on Bindings

BINDINGS-17

Rules for Binding compatibility

BINDINGS-1630

Normative reference consistency

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

BINDINGS-1532

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

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

BINDINGS-1336

Does WSDL binding take precedend over policy intents What namespace(s) do we use for each binding?

BINDINGS-12

  Are JMS message selectors supported?

BINDINGS-10

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

BINDINGS-9

Use of wsdli:wsdlLocation does not match WSDL 2.0 specification

BINDINGS-8

No bindingType for binding.ws

BINDINGS-6

JMS bindingType and conversation intent

BINDINGS-5

JMS bindingType and atLeastOne intent overlaps with setting JMSDeliveryMode

BINDINGS-3

portType referred to inconsistently throughout specification

BINDINGS-1

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

38

Clarify use of URI vs. uri

BPEL-1

support for BPEL4WS 1.1

BPEL-2

Does the spec allow a componentType side file

BPEL-3

Correlation disagreement between SCA and BPEL

BPEL-9

SCA-BPEL XML Namespaces

BPEL-10

test issue please ignore

BPEL-13

ComponentType should not contain implementation.bpel

BPEL-20

SCA-BPEL spec can not require bpel:mustUnderstand to be true

BPEL-19

SCA-BPEL XML Schema

BPEL-17

Allow Component Type side file to override defaults for service/reference

BPEL-14

Allow sca-aware processes to specify everything that can be specified in a CT side file

BPEL-13 ComponentType should not contain implementation.bpel 17

Allow Component Type side file to override defaults for service/reference

BPEL-10

  test issue please ignore

BPEL-919

SCA-BPEL XML Namespaces Schema

BPEL-3

  Correlation disagreement between SCA and BPEL

BPEL-2

Does the spec allow a componentType side file

20

SCA-BPEL spec can not require bpel:mustUnderstand to be true

BPEL-1

support for BPEL4WS 1.1