sca-j message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-j] ISSUE 192: JAX-WS annotations imply a WSDL based binding (binding.ws) -proposal
- From: Mike Edwards <mike_edwards@uk.ibm.com>
- To: "OASIS Java" <sca-j@lists.oasis-open.org>
- Date: Fri, 8 Jan 2010 16:45:44 +0000
Folks,
I've prepared an update to Dave's proposal,
which
a) Wordsmiths the paragraphs
b) Adds a statement about <reference/>
elements in the component type
Yours, Mike.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email: mike_edwards@uk.ibm.com
From:
| David Booz <booz@us.ibm.com>
|
To:
| sca-j@lists.oasis-open.org
|
Date:
| 06/01/2010 17:27
|
Subject:
| [sca-j] ISSUE 192: JAX-WS annotations
imply a WSDL based binding (binding.ws) - proposal |
Attached is a proposal for the subject issue [1].
The underlying issues are non-trivial so please take some time to review.
Please keep in mind a few things:
1) This resolution is heavily related to JAVA-184 [2] which was resolved
back on Nov 9,2009. 184 introduced quite a few rules for the effects of
JAX-WS annotations on interfaces and the effective componentType. Since
there is no spec revision with 184 in it, I based my proposal on a copy
of
rev2 which contains the 184 resolution. I accepted all changes BEFORE
adding text for 192 so you will not see the 184 changes highlighted.
2) Unlike 184, this issue only affects the effective componentType so only
the Java POJO spec had to be modified.
3) The assembly spec does support binding instances in the effective
componentType and defines rules for how to override them in
components/composites.
4) JAVA-184 introduces the SOAP intent into the effective componentType
in
some cases, but that in itself doesn't necessarily cause the right JAX-WS
compliant WSDL binding to be used.
5) Since componentType bindings can be overridden in components/composites,
there is still value in retaining the SOAP intent attachment rules defined
by 184.
If we can do the word-smithing in email the telecon will go more smoothly.
(See attached file: sca-javaci-1.1-spec-cd01-rev2 Issue 192.doc)
[1] http://www.osoa.org/jira/browse/JAVA-192
[2] http://www.osoa.org/jira/browse/JAVA-184
Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com[attachment "sca-javaci-1.1-spec-cd01-rev2 Issue
192.doc" deleted by Mike Edwards/UK/IBM] ---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
sca-javaci-1.1-spec-cd01-rev2 Issue 192_mje.doc
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]