You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Scott Kurz <sc...@gmail.com> on 2009/06/25 16:23:33 UTC

Re: issue with binding.jms: interface.wsdl with either obj, bytes, text wireFormat

Picking this thread up again, I wonder if a starting point might be to
define a new SPI that a binding could use to obtain a Java
InterfaceContract in the cases where we expect/require the
componentType IC to be Java.

E.g. in org.apache.tuscany.sca.binding.jms.wireformat.jmsobject.runtime.WireFormatJMSObjectServiceProvider
we have:

            List<Operation> opList =
service.getService().getInterfaceContract().getInterface().getOperations();

what if:

  service.getService().getInterfaceContract()

were replaced by:

  service.getJavaInterfaceContract()

I realize that's not exactly a giant leap forward in the
discussion....just didn't want to let the idea die as I've noticed
this is a very important step required to implement certain Tuscany
bindings correctly, but you just have to know this "trick" rather than
using a potentially clearer SPI.

Scott

Re: issue with binding.jms: interface.wsdl with either obj, bytes, text wireFormat

Posted by Simon Laws <si...@googlemail.com>.
On Thu, Jun 25, 2009 at 4:55 PM, Scott Kurz<sc...@gmail.com> wrote:
> I'm not suggesting generating one from WSDL yet, until we understand
> the use case(s) we'd need this in more detail.    It might be nice to
> throw an error if a Java interface is unavailable however.
>
> Obviously we have a lot of bindings today and people have figured out
> the trick... just seemed nicer to have a method clearly intended for
> this purpose.
>
> Scott
>

Hi Scott

Ok, I understand. I guess we could add it as a helper so if the
extension developer were really expecting a Java interface then we
could test that a Java interface is available.

Simon

Re: issue with binding.jms: interface.wsdl with either obj, bytes, text wireFormat

Posted by Scott Kurz <sc...@gmail.com>.
I'm not suggesting generating one from WSDL yet, until we understand
the use case(s) we'd need this in more detail.    It might be nice to
throw an error if a Java interface is unavailable however.

Obviously we have a lot of bindings today and people have figured out
the trick... just seemed nicer to have a method clearly intended for
this purpose.

Scott

Re: issue with binding.jms: interface.wsdl with either obj, bytes, text wireFormat

Posted by Simon Laws <si...@googlemail.com>.
On Thu, Jun 25, 2009 at 3:23 PM, Scott Kurz<sc...@gmail.com> wrote:
> Picking this thread up again, I wonder if a starting point might be to
> define a new SPI that a binding could use to obtain a Java
> InterfaceContract in the cases where we expect/require the
> componentType IC to be Java.
>
> E.g. in org.apache.tuscany.sca.binding.jms.wireformat.jmsobject.runtime.WireFormatJMSObjectServiceProvider
> we have:
>
>            List<Operation> opList =
> service.getService().getInterfaceContract().getInterface().getOperations();
>
> what if:
>
>  service.getService().getInterfaceContract()
>
> were replaced by:
>
>  service.getJavaInterfaceContract()
>
> I realize that's not exactly a giant leap forward in the
> discussion....just didn't want to let the idea die as I've noticed
> this is a very important step required to implement certain Tuscany
> bindings correctly, but you just have to know this "trick" rather than
> using a potentially clearer SPI.
>
> Scott
>

Hi Scott

And is the suggestion here to test, inside
service.getJavaInterfaceContract(), that there is a Java interface
contract available? We either throw an error if there isn't or
generate one from WSDL (we don't have this generated code in the
runtime now).

Simon