[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-j] [JAVA-77] - Updated proposal: A remotable service SHOULD be translatable into a generally accepted standard for a service, such as WSDL 1.1 or WSDL 2.0
Hi, It looks as though we maybe discussing JAVA-77 in today's
call. There have been previous email discussions on a proposal in January. The main point of the proposal is that since ASSEMBLY-77 [2]
specifies that a WSDL interface is WSDL 1.1 and not WSDL 2.0, the SCA-J
specification only needs to support WSDL 1.1 To simplify the work on the call, I've updated the proposal and
changed the line numbers to reflect the latest PDF version (CD02 Rev 01 PDF
version) which can be obtained from [1]. Updated Proposal The updated proposal is to specify that a @Remotable
interface must be translatable to a WSDL 1.1 portType. The original text reads in CAA: 1180 The
@Remotable annotation is used to specify a Java service interface as remotable.
A remotable 1181 service can be
published externally as a service and must be translatable into a WSDL
portType. This should be updated to specify a WSDL 1.1 portType
(yellow highlight added to identify change but should not be committed to specification) 1180 The
@Remotable annotation is used to specify a Java service interface as remotable.
A remotable 1181 service can be
published externally as a service and must be translatable into a WSDL 1.1 portType. Also, the reference to WSDL 2.0 should be removed from
section 1.2 Normative References. Change from: 39 [WSDL] WSDL
Specification, 40 WSDL 1.1: http://www.w3.org/TR/wsdl, 41 WSDL
2.0: http://www.w3.org/TR/wsdl20/ To: 39 [WSDL] WSDL
Specification, 40 WSDL 1.1: http://www.w3.org/TR/wsdl, Thanks, Mark [2] http://www.osoa.org/jira/browse/ASSEMBLY-77 Mark
Combellack| Software Developer|
Avaya | > -----Original Message----- > From: Simon Nash [mailto:oasis@cjnash.com] > Sent: 12 January 2009 12:59 > To: OASIS Java > Subject: Re: [sca-j] [JAVA-77] - Updated proposal: A remotable service > SHOULD be translatable into a generally accepted standard for a service, > such as WSDL 1.1 or WSDL 2.0 > > Mark Combellack wrote: > > Hi, > > > > > > > > JAVA-77 [1] talks about remotable services being translatable into WSDL > > 1.1 and WSDL 2.0. > > > > > > > > Recently, the Assembly TC has decided not to require WSDL 2.0 support at > > this time (see ASSEMBLY-77 [2]) > > > > > > > > > > > > I would like to propose that we Close No Action JAVA-77 since this would > > be in line with the decision of the Assembly TC. > > > > > > > > > > > > What do people think to this proposal? > > > > > I think it would be better to be explicit and say > "A remotable service can be published externally as a service and must > be translatable into a WSDL 1.1 portType" > > The only change is the addition of "1.1". > > Simon > > > > > > > > > Thanks, > > > > > > > > Mark > > > > > > > > [1] http://www.osoa.org/jira/browse/JAVA-77 > > > > [2] http://www.osoa.org/jira/browse/ASSEMBLY-77 > > > > Mark Combellack| Software Developer| Avaya | Eastern > > Mellons | > > mcombellack@avaya.com <mailto:|mcombellack@avaya.com> > > > > > > > > > > --------------------------------------------------------------------- > 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 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]