OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-j] JAVA-153: Proposed resolution rev3


Hi Simon,

Two points:

(1)

So then based on your proposal, is the following example correct?

Implementation class:

package services.hello;

@Remotable
@Service(HelloServiceImpl.class)
public class HelloServiceImpl {

public String hello(String message) {

In this case the introspected component type for the implementation uses the @remotable attribute of the <interface.java/> element, as shown in the following snippet:

<?xml version="1.0" encoding="UTF-8"?>
<componentType xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200903">
<service name="HelloServiceImpl">

</service>


(2)
I looked back at the resolution for JAVA-125 and noticed that it did not address a question that arises from line 277-278 (from sca-javacaa-1.1-spec-cd03+issue125-rev2.doc) which has the following statement:

The @remotable attribute is intended as an alternative to using the @Remotable annotation.


That's quite a strong statement and it implies semantics which allow the ability for a component definition to assert remotability onto a service interface. Remember that <interface.java/> is used on both componentTypes and component definitions. I quite like the ability to assert remotability in this way, but I suspect there are also dissenting opinions. I want to make sure we have a consistent story across the specs.


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

Inactive hide details for Simon Nash ---06/15/2009 07:40:03 AM---I am attaching a revised proposed resolution for JAVA-153, as Simon Nash ---06/15/2009 07:40:03 AM---I am attaching a revised proposed resolution for JAVA-153, as discussed on last Monday's call.


From:

Simon Nash <oasis@cjnash.com>

To:

OASIS Java <sca-j@lists.oasis-open.org>

Date:

06/15/2009 07:40 AM

Subject:

[sca-j] JAVA-153: Proposed resolution rev3





I am attaching a revised proposed resolution for JAVA-153,
as discussed on last Monday's call.

  Simon
(See attached file: sca-javaci-1.1-spec-cd01+issue153-rev3.doc)---------------------------------------------------------------------
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 

sca-javaci-1.1-spec-cd01+issue153-rev3.doc



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]