Re: [sca-j] Raw chat log for April 3 SCA-J TC call

[Bryan Aupperle <aupperle@us.ibm.com>]

You are correct  about it being
impossible for a Java implementation to have an interface defined using
WSDL, so my concern there is invalid.  But a component can still use
a WSDL interface so there must be a way to represent any intent that can
be specified on a Java interface in the corresponding WSDL. This leads
to my comments about interface.wsdl.

The first is pretty mechanical.  Section
7.5 of the Assembly spec normatively defines interface.wsdl but does not
include @requires or @policySets in the pseudo-schema or attribute descriptions.

The second problem is not a concern
with interface.wsdl itself, but the @requires WSDL extension defined in
section 7.4 of the assembly spec.  The text in section 7.4 states
that the extension can be applied to portTypes.  It needs to be applicable
to operations as well given the recent discussion we have had about intents
on Java methods.

I'll raise issues in Assembly for both
of these.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

Simon Nash <oasis@cjnash.com>

04/06/2009 06:24 AM

To	OASIS Java <sca-j@lists.oasis-open.org>
cc
Subject	Re: [sca-j] Raw chat log for April 3 SCA-J TC call

Bryan Aupperle wrote:
> 
> Anish,
> 
> Excellent point.  This also impacts Simon's "synthetic"
interface idea. 
>  If the interface is defined via WSDL (with or without attached
intents) 
> and the implementation is annotated with intents (interaction or 
> implementation) then the "synthetic" interface should still
be defined 
> via WSDL with the intents from the implementation added.
> 
For a Java implementation, it isn't possible for a service or reference
interface in a component type to be defined using WSDL.  These interfaces
are introspected and therefore they will always be interface.java.

> I think this leads to some deficiencies with the text in Assembly
about 
> interface.wsdl, but I'll need to look a bit more closely.
> 
Could you elaborate more?

   Simon

> Bryan Aupperle, Ph.D.
> STSM, WebSphere Enterprise Platform Software Solution Architect
> 
> Research Triangle Park,  NC
> +1 919-254-7508 (T/L 444-7508)
> Internet Address: aupperle@us.ibm.com
> 
> 
> *Anish Karmarkar <Anish.Karmarkar@oracle.com>*
> 
> 04/03/2009 02:39 PM
> 
>                  
> To
>                  Bryan
Aupperle/Raleigh/IBM@IBMUS
> cc
>                  OASIS
Java <sca-j@lists.oasis-open.org>
> Subject
>                  Re:
[sca-j] Raw chat log for April 3 SCA-J TC call
> 
> 
>                  
> 
> 
> 
> 
> 
> Bryan,
> 
> I have been thinking about this issue of intents and independence
of
> interface language. Unless I missed an issue resolution, section 11
of
> CAA spec relegates the wsdl->java and java->wsdl mapping to
JAX-WS. I
> don't think this is sufficient. We'll have to specify that for intents
> specified using @Requires, @Authentication etc annotations get mapped
to
> @requires WSDL attribute (in both directions).
> 
> -Anish
> --
> 
> Bryan Aupperle wrote:
>  >
>  > This is not a comment about the minutes but some additional
thoughts on
>  > Anish's comment that impl methods should be required to
have the same
>  > interaction intents as the interfaces that they implement.
>  >
>  > This should be true independent of the interface language
and needs to
>  > be applied to the other implementation languages as well.
>  >
>  > Bryan Aupperle, Ph.D.
>  > STSM, WebSphere Enterprise Platform Software Solution Architect
>  >
>  > Research Triangle Park,  NC
>  > +1 919-254-7508 (T/L 444-7508)
>  > Internet Address: aupperle@us.ibm.com
>  >
>  >
>  > *Simon Nash <oasis@cjnash.com>*
>  >
>  > 04/03/2009 11:28 AM
>  >
>  >                
 
>  > To
>  >                
 OASIS Java <sca-j@lists.oasis-open.org>
>  > cc
>  >                
 
>  > Subject
>  >                
 [sca-j] Raw chat log for April 3 SCA-J TC call
>  >
>  >
>  >                
 
>  >
>  >
>  >
>  >
>  >
>  > ---------------------------------------------------------------------
>  > 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
>  >
>  >
>  > ------------------------------------------------------------------------
>  >
>  > ---------------------------------------------------------------------
>  > 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
> 
> ---------------------------------------------------------------------
> 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
> 
> 



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