Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

http://www.osoa.org/jira/browse/ASSEMBLYImage Added

OASIS JIRA

Description

Action

ASSEMBLY-43

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

 

ASSEMBLY-1

Is binding.sca always present?

 

ASSEMBLY-3

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

 

ASSEMBLY-6

usage of not promoted references

 

ASSEMBLY-23

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

 

ASSEMBLY-25

Can Implementation change property values after instantiaion

 

ASSEMBLY-28

Missing XSD for contributions

 

ASSEMBLY-38

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

 

ASSEMBLY-39

Permit intents and PolicySets on <interface/> elements

 

ASSEMBLY-40

Autowire at the domain level

 

ASSEMBLY-42

Autowire value for the logical domain composite

 

ASSEMBLY-57

Unresolved bindings on references

 

ASSEMBLY-67

Component Type file name is too restrictive

 

ASSEMBLY-68

ComponentType Properties should not have a source

 

ASSEMBLY-35

Confusing words in Section 5.3 relating to ConversationalIntent

 

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

 

ASSEMBLY-53

No schema or extension model definitions for contributions

 

ASSEMBLY-5

component type allows to specify wire targets on references

 

ASSEMBLY-92

Assembly Specification should not state what marks a Javainterface as Local

 

ASSEMBLY-71

Implementation.composite pseudo-schema incorrect

 

ASSEMBLY-14

Conflicting Specification of Values for Many-Valued StringProperties

 

ASSEMBLY-22

WSDL extension should not be required for conversations

 

ASSEMBLY-18

XSD definitions of Component Service and Component Referencehave unintended features

 

ASSEMBLY-63

Specification wording unclear on how local and remoteable interfaces are specified

 

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?

 

ASSEMBLY-69

Language neutrality edits

 

ASSEMBLY-45

some smaller things we need to fix in the assembly specification

 

ASSEMBLY-56

Need to clarify definition of Bidirectional Interfaces

 

ASSEMBLY-41

Conflicting domain-level <wire> deployments

 

ASSEMBLY-79

Identifying wire format and operation selection

 

ASSEMBLY-62

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

 

ASSEMBLY-26

SCA Composite Visibility

 

ASSEMBLY-51

Composite Completeness

 

ASSEMBLY-36

Compatability of component type side files

 

ASSEMBLY-44

Allow multiple definitions.xml files

 

ASSEMBLY-89

Need for a Callback annotation for WSDL interface files

 

ASSEMBLY-16

Component URI is not well described

 

ASSEMBLY-8

SCDL artifact resolution underspecified

 

ASSEMBLY-17

Need to define Namespace handling for included Composites

 

ASSEMBLY-30

Incorrect description of <Operation/> child elements inAssembly

 

ASSEMBLY-33

Long-Running Request-Response Operations

 

ASSEMBLY-96

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

 

ASSEMBLY-74

Corrections to the contributions schema

 

ASSEMBLY-81

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

 

ASSEMBLY-75

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

 

ASSEMBLY-72

Do we need appendix A (pseudo-schema)?

 

...

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

http://www.osoa.org/jira/browse/JAVAImage Added

OASIS JIRA

Description

Action

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

 

...

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

http://www.osoa.org/jira/browse/POLICYImage Added

OASIS JIRA

Description

Action

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

 

Bindings

http://www.osoa.org/jira/browse/BINDINGSImage Added

OASIS JIRA

Description

Action

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

Rules for Binding compatibility

 

BINDINGS-16

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

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.

 

BPEL

http://www.osoa.org/jira/browse/BPELImage Added

OASIS JIRA

Description

Action

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

 

BPEL-10

test issue please ignore

 

BPEL-9

SCA-BPEL XML Namespaces

 

BPEL-3

Correlation disagreement between SCA and BPEL

 

BPEL-2

Does the spec allow a componentType side file

 

BPEL-1

support for BPEL4WS 1.1