DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| OASIS JIRA | Description | Tuscany TODO | Tuscany JIRA | Conformance |
|---|---|---|---|---|---|
| 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 |
|
| |
| Is interface.java specification normative in SCA-Assembly spec? | No action is required |
|
| |
| component type allows to specify wire targets on references | Push teh getTargets() method from Reference to ComponentReference |
|
| |
| usage of not promoted references | Make sure the reference resolution follows what's described by the assembly spec |
|
| |
| SCDL artifact resolution underspecified | Adjust the artifact resolution based on the proposal in this JIRA | TUSCANY-3079 |
| |
| 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 |
|
| |
| Component URI is not well described | Tuscany needs to support the structural URI based on this proposal |
|
| |
| 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 |
|
| |
| XSD definitions of Component Service and Component Referencehave unintended features |
|
|
| |
| WSDL extension should not be required for conversations | Make sure conversational intent is supported at interface and service |
|
| |
| SCA <anyAttribute.../> declarations should use namespace ##other rather than ##any | Update the xsd from OASIS, can we support OSOA and OASIS xsds? |
|
| |
| Can Implementation change property values after instantiaion | No action is required |
|
| |
| SCA Composite Visibility | This seems to be a clarification by the spec |
|
| |
| Missing XSD for contributions | Update the xsd from OASIS. Update the Import/Export model to |
|
| |
| 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 |
|
| |
| "SCA schema fixes requested for sca-core.xsd (based on OSOA site versions that may be copied to OASIS site)" |
|
|
| |
| Long-Running Request-Response Operations | Tuscany needs to support the proposal |
|
| |
| Confusing words in Section 5.3 relating to ConversationalIntent , Conversational support has gone |
|
|
| |
| Compatability of component type side files | Each implementation type has to decide how to support the componentType file |
|
| |
| Clarify whether a Default Value for a Property must appear inthe componentType of an implementation | No action is required |
|
| |
| Permit intents and PolicySets on <interface/> elements | The policy model needs to be changed so that interface can have intents/policySets attached. |
|
| |
| Autowire at the domain level | Tuscany needs to decide if/how it will support the domain-level autowiring |
|
| |
| Conflicting domain-level <wire> deployments | Tuscany needs to implement the proposal |
|
| |
| Autowire value for the logical domain composite | I think Tuscany is OK here as the autowire=false for the domain composite |
|
| |
| for implentations.*'s fix attributes that should show qnames as values |
|
|
| |
| Allow multiple definitions.xml files | Tuscany should allow META-INF/definitions.xml from SCA contributions. These definitions become visible to the SCA domain |
|
| |
| some smaller things we need to fix in the assembly specification |
|
|
| |
| Composite Completeness | Tuscany needs to add more validations to ensure the completeness of the composite for implementaiton.composite |
|
| |
| No schema or extension model definitions for contributions |
|
|
| |
| Need to clarify definition of Bidirectional Interfaces | Make sure Tuscany is consistent with the specified behavior |
|
| |
| Unresolved bindings on references | Add the support for "componentName/serviceName/bindingName" as the wire target |
|
| |
| Description elements in SCDL | Support documentation element in the model and processors |
|
| |
| What is the default value for many and mustSupply on Properties? | remove "mustSupply" from <component> |
|
| |
| Specification wording unclear on how local and remoteable interfaces are specified | Remotable is IDL specific |
|
| |
| Constraining Type talks about non-optional references but does not define what they are |
|
|
| |
| 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 |
|
|
| |
| ComponentType Properties should not have a source |
|
|
| |
| Language neutrality edits |
|
|
| |
| Implementation.composite pseudo-schema incorrect |
|
|
| |
| Do we need appendix A (pseudo-schema)? | No action is required |
|
| |
| Corrections to the contributions schema, sca-contribution.xml specify what is deployable We should use in our samples | See ASSEMLY-28 |
|
| |
| "Section on ""Wire"" in Appendix is Incorrect" | Tuscany already has the correct model, No action is required |
|
| |
| 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 |
|
| |
| Identifying wire format and operation selection | add "wireFormat" and "operationSelector" for bindings |
|
| |
| Duplicated atributes in sca-binding-sca.xsd and sca-implementation-composite.xsd | No action is required |
|
| |
| Need for a Callback annotation for WSDL interface files | Tuscany needs to handle sca:callback extensibility elements in WSDL |
|
| |
| Assembly Specification should not state what marks a Javainterface as Local |
|
|
| |
| Add a Section documenting naming conventions to the start ofthe SCA Assembly Specification | No action is required |
|
| |
| No @replace attribute for <wire> in OSOA spec | No action is required |
|
| |
| 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 |
|
| |
| Top level composite services/references are not included in the virtual domain composite | Adjust logic and tests |
|
|
...
| OASIS JIRA | Description | Tuscany TODO | Tuscany JIRA | Conformance |
|---|---|---|---|---|---|
| EJB remove method on EJBHome |
|
|
| |
| annotations on parameters | @Reference, @Property can only be used for constructor parameters. Tuscany |
|
| |
| Clarify Request Scope lifetime | Remove the Request scope |
|
| |
| Incorrect generated service name |
|
|
| |
| Inconsistent method description for @Init and @Destroy annotations | Tuscany already validates the pattern |
|
| |
| Incorrect examples of methods annotated @Init and @Destroy |
|
|
| |
| @Reference annotation can also be used on a constructor parameter. |
|
|
| |
| Missing description of what the @EagerInit annotation does |
|
|
| |
| @Callback annotation does not feature in section on Interfaces |
|
|
| |
| Version requirements for SDO, JAXB and JAX-WS |
|
|
| |
| 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 |
|
| |
| When more than one interface with the same unqualified name used in the @Service annotation |
|
|
| |
| SCA Spring Client and Implementation Specification uses an unacceptable namespace | Update the namespace based on the OASIS spec |
|
| |
| Describe the concurrency model for each scope |
|
|
| |
| SCA Spring C & I specification does not state the purpose of sca:composite element | Remove the sca:composite |
|
| |
| Incorrect code in section 6.7.2 example |
|
|
| |
| Should not say callback ID is passed in reference parameters |
|
|
| |
| Incorrect reference to "original request" |
|
|
| |
| Incorrect description of @Scope annotation default | Make sure the scope is default to "COMPOSITE" if there is an @Conversational |
|
| |
| Missing word "type" for "return type" in CAA spec - sec 3.1 |
|
|
| |
| Normative references to SCA Spec docs point to v1.00 docs |
|
|
| |
| Inconsistent use of a and an when referring to annotations |
|
|
| |
| Incorrect definition of the SCA JEE JSP Tag library |
|
|
| |
| Java CAA spec does not contain the interface.java schema |
|
|
| |
| Spurious cast() method definition in ComponentContext interface |
|
|
| |
| Constructor name information may not be available | Adjust the @Property/@Reference processor on CDI |
|
|
...