This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • OSOA SCA vs OASIS SCA
Skip to end of metadata
Go to start of metadata

The intention of this page is to document the differences between the Tuscany(OSOA) and OASIS versions of SCA on a spec by spec basis. I intend initially just to highlight those features that differ and have an impact on Tuscany without confirming those features that remain the same but we'll see how it goes.

(warning) This page is under construction so please feel invited to add any differences that you are aware of

http://www.osoa.org/jira/secure/BrowseProjects.jspa

General

Feature

OSOA Ref

OSOA Description

OASIS Ref

OASIS Description

Schema namespace

 

http://www.osoa.org/xmlns/sca/1.0

 

http://docs.oasis-open.org/ns/opencsa/sca/200712

Assembly

OSOA - Tuscany 1.x (SCA_AssemblyModel_V100 +)
OASIS - sca-assembly-1.1-spec-cd01-rev3 + Current JIRA

http://www.osoa.org/jira/browse/ASSEMBLY

 

OASIS JIRA

Description

Tuscany TODO

Tuscany JIRA

Conformance

(question)

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

 

 

(tick)

ASSEMBLY-3

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

No action is required

 

 

(question)

ASSEMBLY-5

component type allows to specify wire targets on references

Push teh getTargets() method from Reference to ComponentReference

 

 

(question)

ASSEMBLY-6

usage of not promoted references

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

 

 

(question)

ASSEMBLY-8

SCDL artifact resolution underspecified

Adjust the artifact resolution based on the proposal in this JIRA

TUSCANY-3079

 

(question)

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

 

 

(question)

ASSEMBLY-16

Component URI is not well described

Tuscany needs to support the structural URI based on this proposal

 

 

(question)

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

 

 

(tick)

ASSEMBLY-18

XSD definitions of Component Service and Component Referencehave unintended features

 

 

 

(question)

ASSEMBLY-22

WSDL extension should not be required for conversations

Make sure conversational intent is supported at interface and service

 

 

(tick)

ASSEMBLY-23

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

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

 

 

(tick)

ASSEMBLY-25

Can Implementation change property values after instantiaion

No action is required

 

 

(tick)

ASSEMBLY-26

SCA Composite Visibility

This seems to be a clarification by the spec

 

 

(question)

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

 

 

(minus)

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

 

 

(tick)

ASSEMBLY-32

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

 

 

 

(question)

ASSEMBLY-33

Long-Running Request-Response Operations

Tuscany needs to support the proposal

 

 

(tick)

ASSEMBLY-35

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

 

 

 

(question)

ASSEMBLY-36

Compatability of component type side files

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

 

 

(tick)

ASSEMBLY-38

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

No action is required

 

 

(question)

ASSEMBLY-39

Permit intents and PolicySets on <interface/> elements

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

 

 

(question)

ASSEMBLY-40

Autowire at the domain level

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

 

 

(question)

ASSEMBLY-41

Conflicting domain-level <wire> deployments

Tuscany needs to implement the proposal

 

 

(tick)

ASSEMBLY-42

Autowire value for the logical domain composite

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

 

 

(tick)

ASSEMBLY-43

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

 

 

 

(question)

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

 

 

(tick)

ASSEMBLY-45

some smaller things we need to fix in the assembly specification

 

 

 

(question)

ASSEMBLY-51

Composite Completeness

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

 

 

(tick)

ASSEMBLY-53

No schema or extension model definitions for contributions

 

 

 

(question)

ASSEMBLY-56

Need to clarify definition of Bidirectional Interfaces

Make sure Tuscany is consistent with the specified behavior

 

 

(question)

ASSEMBLY-57

Unresolved bindings on references

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

 

 

(question)

ASSEMBLY-60

Description elements in SCDL

Support documentation element in the model and processors

 

 

(question)

ASSEMBLY-62

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

remove "mustSupply" from <component>

 

 

(tick)

ASSEMBLY-63

Specification wording unclear on how local and remoteable interfaces are specified

Remotable is IDL specific

 

 

(tick)

ASSEMBLY-65

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

 

 

 

(tick)

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

 

 

 

(tick)

ASSEMBLY-68

ComponentType Properties should not have a source

 

 

 

(tick)

ASSEMBLY-69

Language neutrality edits

 

 

 

(tick)

ASSEMBLY-71

Implementation.composite pseudo-schema incorrect

 

 

 

(tick)

ASSEMBLY-72

Do we need appendix A (pseudo-schema)?

No action is required

 

 

(tick)

ASSEMBLY-74

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

See ASSEMLY-28

 

 

(tick)

ASSEMBLY-75

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

Tuscany already has the correct model, No action is required

 

 

(question)

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

 

 

(question)

ASSEMBLY-79

Identifying wire format and operation selection

add "wireFormat" and "operationSelector" for bindings

 

 

(tick)

ASSEMBLY-81

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

No action is required

 

 

(question)

ASSEMBLY-89

Need for a Callback annotation for WSDL interface files

Tuscany needs to handle sca:callback extensibility elements in WSDL

 

 

(tick)

ASSEMBLY-92

Assembly Specification should not state what marks a Javainterface as Local

 

 

 

(tick)

ASSEMBLY-96

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

No action is required

 

 

(tick)

N/A

No @replace attribute for <wire> in OSOA spec

No action is required

 

 

(tick)

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

 

 

(tick)

N/A

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

Adjust logic and tests

 

 

Policy

OSOA - Tuscany 1.x (SCA_Policy_Framework_V100 +)
OASIS - sca-policy-11.1-spec-wd-10

http://www.osoa.org/jira/browse/POLICY

 

OASIS JIRA

Description

Tuscany TODO

Tuscany JIRA

Conformance

 

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

 

 

 

(question)

POLICY-58

Remove <operation/> elements from the specification

 

 

 

(question)

POLICY-59

Limit policySet attachment to bindings

 

 

 

(question)

POLICY-60

Clarify scope of ordered intent

Add "ordered" intent support

 

 

(tick)

POLICY-61

How are mayProvide intents on bindings satisfied

 

 

 

(tick)

POLICY-63

intents names defined by SCA should be defined using camel case

 

 

 

Implementations

Implementation-java

OSOA - Tuscany 1.x (SCA_JavaAnnotationsAndAPIs_V100 +)
OASIS - sca-javacaa-1.1-spec-cd01

http://www.osoa.org/jira/browse/JAVA

 

OASIS JIRA

Description

Tuscany TODO

Tuscany JIRA

Conformance

(tick)

JAVA-5

EJB remove method on EJBHome

 

 

 

(tick)

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>

 

 

(question)

JAVA-21

Clarify Request Scope lifetime

Remove the Request scope

TUSCANY-3280

 

(tick)

JAVA-32

Incorrect generated service name

 

 

 

(tick)

JAVA-41

Inconsistent method description for @Init and @Destroy annotations

Tuscany already validates the pattern

 

 

(tick)

JAVA-42

Incorrect examples of methods annotated @Init and @Destroy

 

 

 

(tick)

JAVA-43

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

 

 

 

(tick)

JAVA-47

Missing description of what the @EagerInit annotation does

 

 

 

(tick)

JAVA-48

@Callback annotation does not feature in section on Interfaces

 

 

 

(tick)

JAVA-49

Version requirements for SDO, JAXB and JAX-WS

 

 

 

(question)

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

 

 

(tick)

JAVA-56

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

 

 

 

(question)

JAVA-57

SCA Spring Client and Implementation Specification uses an unacceptable namespace

Update the namespace based on the OASIS spec

 

 

(tick)

JAVA-61

Describe the concurrency model for each scope

 

 

 

(question)

JAVA-64

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

Remove the sca:composite

 

 

(tick)

JAVA-71

Incorrect code in section 6.7.2 example

 

 

 

(tick)

JAVA-72

Should not say callback ID is passed in reference parameters

 

 

 

(tick)

JAVA-73

Incorrect reference to "original request"

 

 

 

(tick)

JAVA-75

Incorrect description of @Scope annotation default

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

 

 

(tick)

JAVA-79

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

 

 

 

(tick)

JAVA-81

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

 

 

 

(tick)

JAVA-82

Inconsistent use of a and an when referring to annotations

 

 

 

(tick)

JAVA-83

Incorrect definition of the SCA JEE JSP Tag library

 

 

 

(tick)

JAVA-84

Java CAA spec does not contain the interface.java schema

 

 

 

(tick)

JAVA-112

Spurious cast() method definition in ComponentContext interface

 

 

 

(question)

JAVA-111

Constructor name information may not be available

Adjust the @Property/@Reference processor on CDI

 

 

(question)

N/A

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

 

TUSCANY-3290

 

(question)

N/A

Illegal annotations in a service interface class

 

TUSCANY-3289

 

(question)

N/A

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

 

TUSCANY-3294

 

(question)

N/A

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

 

TUSCANY-3293

 

(question)

N/A

Verify @Service compliance with latest OASIS Java 1.1 draft spec

 

TUSCANY-3300

 

(question)

N/A

Verify @Property compliance with latest OASIS Java 1.1 draft spec

 

TUSCANY-3301

 

Bindings

http://www.osoa.org/jira/browse/BINDINGS

Binding-jms

 

OASIS JIRA

Description

Tuscany TODO

Tuscany JIRA

Conformance

 

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

 

 

 

(question)

BINDINGS-20

JMS binding URI should follow JMS IRI scheme submitted to IETF

 

 

 

(question)

BINDINGS-26

JMS binding pseudo-schemas inconsistent with assembly

 

 

 

 

BINDINGS-29

Properties on Bindings

 

 

 

(tick)

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

 

 

 

(tick)

BINDINGS-62

Conformance statement numbering

 

 

 

Binding-ws

 

OASIS JIRA

Description

Tuscany TODO

Tuscany JIRA

Conformance

 

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

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

 

 

 

 

BINDINGS-23

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

 

 

 

 

BINDINGS-29

Properties on Bindings

 

 

 

 

BINDINGS-30

Normative reference consistency

 

 

 

 

BINDINGS-32

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

 

 

 

 

BINDINGS-36

Does WSDL binding take precedend over policy intents

 

 

 

 

BINDINGS-38

Clarify use of URI vs. uri

 

 

 

BPEL

http://www.osoa.org/jira/browse/BPEL

 

OASIS JIRA

Description

Tuscany TODO

Tuscany JIRA

Conformance

 

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

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

 

 

 

 

BPEL-17

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

 

 

 

 

BPEL-19

SCA-BPEL XML Schema

 

 

 

 

BPEL-20

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