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

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

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

SCA Composite Visibility

This seems to be a clarification by the spec

ASSEMBLY-28

Missing XSD for contributions

Update the

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

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

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

"SCA schema fixes requested for sca-core.xsd (based on OSOA site versions that may be copied to OASIS site)" Confusing words in Section 5.3 relating to ConversationalIntent

ASSEMBLY-38

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

33

Long-Running Request-Response Operations

Tuscany needs to support the proposal No action is required

ASSEMBLY-39

Permit intents and PolicySets on <interface/> elements

35

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

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

ASSEMBLY-40

Autowire at the domain level

36

Compatability of component type side files

Each implementation type has to decide how to support the componentType file Tuscany needs to decide if/how it will support the domain-level autowiring

ASSEMBLY-42

Autowire value for the logical domain composite

38

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

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

ASSEMBLY-4339

Permit intents and PolicySets on <interface/> elements

The policy model needs to be changed so that interface can have intents/policySets attached. for implentations.*'s fix attributes that should show qnames as values

ASSEMBLY-57

Unresolved bindings on references

40

Autowire at the domain level

Tuscany needs to decide if/how it will support the domain-level autowiring Add the support for "componentName/serviceName/bindingName" as the wire target

ASSEMBLY-67

Component Type file name is too restrictive

41

Conflicting domain-level <wire> deployments

Tuscany needs to implement the proposal  

ASSEMBLY-68

ComponentType Properties should not have a source

42

Autowire value for the logical domain composite

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

ASSEMBLY-60

Description elements in SCDL

43

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

  Support documentation element in the model and processors

ASSEMBLY-53

No schema or extension model definitions for contributions

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-92 Assembly Specification should not state what marks a Javainterface as Local 45

some smaller things we need to fix in the assembly specification

ASSEMBLY-71 Implementation51

Composite Completeness

Tuscany needs to add more validations to ensure the completeness of the composite for implementaiton.composite .composite pseudo-schema incorrect

ASSEMBLY-2253

WSDL extension should not be required for conversations

No schema or extension model definitions for contributions

  Make sure conversational intent is supported at interface and service

ASSEMBLY-63

Specification wording unclear on how local and remoteable interfaces are specified

56

Need to clarify definition of Bidirectional Interfaces

Make sure Tuscany is consistent with the specified behavior Remotable is IDL specific

ASSEMBLY-65

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

57

Unresolved bindings on references

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

ASSEMBLY-77

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

60

Description elements in SCDL

Support documentation element in the model and processors Remove the wsdl2.0 specfics from sca namespace. Potentially add interface.wsdl2 under tuscany ns

ASSEMBLY-6962

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

Language neutrality edits

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

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

ASSEMBLY-56

Need to clarify definition of Bidirectional Interfaces

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

  Make sure Tuscany is consistent with the specified behavior

ASSEMBLY-41

Conflicting domain-level <wire> deployments

68

ComponentType Properties should not have a source

  Tuscany needs to implement the proposal

ASSEMBLY-79

Identifying wire format and operation selection

69

Language neutrality edits

  add "wireFormat" and "operationSelector" for bindings

ASSEMBLY-62

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

remove "mustSupply" from <component>

-71

Implementation.composite pseudo-schema incorrect

ASSEMBLY-26

SCA Composite Visibility

72

Do we need appendix A (pseudo-schema)?

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

74

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

See ASSEMLY-28

ASSEMBLY-36

Compatability of component type side files

75

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

Tuscany already has the correct model, No action is required Each implementation type has to decide how to support the componentType file

ASSEMBLY-44

Allow multiple definitions.xml files

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

79

Identifying wire format and operation selection

add "wireFormat" and "operationSelector" for bindings 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

81

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

ASSEMBLY-72

Do we need appendix A (pseudo-schema)?

No action is required

ASSEMBLY-74

Corrections to the contributions schema

89

Need for a Callback annotation for WSDL interface files

Tuscany needs to handle sca:callback extensibility elements in WSDL See ASSEMLY-28

ASSEMBLY-7592

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

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

Tuscany already has the correct model, No action is required

ASSEMBLY-81

N/A

No @replace attribute for <wire> in OSOA spec Duplicated atributes in sca-binding-sca.xsd and sca-implementation-composite.xsd

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

ASSEMBLY-89

Need for a Callback annotation for WSDL interface files

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

N/A

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

Adjust logic and tests No action is required

JAVAPOLICY-112 Spurious cast() method definition in ComponentContext interface 7

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

JAVAPOLICY-111

Constructor name information may not be available

8

Include definition on 'conversational' intent as mentioned in SCA Assembly Adjust the @Property/@Reference processor on CDI

POLICYJAVA-84 Java CAA spec does not contain the interface.java schema 15

External mechanism for attaching intents or policySets

JAVAPOLICY-8317

Need Transaction Policy Spec Incorrect definition of the SCA JEE JSP Tag library

JAVAPOLICY-8218

Should qualifiable intents have a default qualifier Inconsistent use of a and an when referring to annotations

JAVAPOLICY-81 Normative references to SCA Spec docs point to v1.00 docs 22

Profile intent extension - provides other intents

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

More direct, structural qualifier definition

JAVAPOLICY-75

Incorrect description of @Scope annotation default

26

Security implementation policy should be validate-able by schema

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

JAVAPOLICY-73 Incorrect reference to "original request" 29

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

JAVAPOLICY-7237

The URL for the location of the ws-policy.xsd is incorrect. Should not say callback ID is passed in reference parameters

JAVAPOLICY-7138

Improve description of the overides available to the two different hierarchies in SCA Incorrect code in section 6.7.2 example

JAVA-64

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

POLICY-39

Need Support for Mutually exclusive intents

  Remove the sca:composite

JAVAPOLICY-6140

Fix SCA Policy schema complex types for Qualifier and PolicySet Describe the concurrency model for each scope

POLICY-42

Infoset for policySet/@appliesTo

POLICY-44

Need a clear way to distinguish Implementation Intents from Interaction Intents

JAVA-57

SCA Spring Client and Implementation Specification uses an unacceptable namespace

Update the namespace based on the OASIS spec

JAVAPOLICY-5646

How to configure policySets When more than one interface with the same unqualified name used in the @Service annotation

JAVAPOLICY-55

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

52

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

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

JAVAPOLICY-49 Version requirements for SDO, JAXB and JAX-WS 53

How do we tell what a policySet @provides?

JAVAPOLICY-4854

Wire validation rules have changed @Callback annotation does not feature in section on Interfaces

JAVAPOLICY-4755

Clarify the handling of Intents Missing description of what the @EagerInit annotation does

JAVAPOLICY-4356

Intents which conflict with binding configuration @Reference annotation can also be used on a constructor parameter.

JAVAPOLICY-42 Incorrect examples of methods annotated @Init and @Destroy 58

Remove <operation/> elements from the specification

JAVAPOLICY-41

Inconsistent method description for @Init and @Destroy annotations

59

Limit policySet attachment to bindings

  Tuscany already validates the pattern

JAVAPOLICY-32

Incorrect generated service name

60

Clarify scope of ordered intent

Add "ordered" intent support  

JAVAPOLICY-21

Clarify Request Scope lifetime

61

How are mayProvide intents on bindings satisfied

  Remove the Request scope

JAVAPOLICY-20

annotations on parameters

63

intents names defined by SCA should be defined using camel case

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

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.

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

Add "ordered" intent support

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

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.