Eclipse Community Forums: Service Component Architecture (SCA) Tools

Help

Home

Home » Archived » Service Component Architecture (SCA) Tools » WS binding vs. propagated WS binding

Show: Today's Messages :: Show Polls :: Message Navigator

WS binding vs. propagated WS binding [message #499840]

Tue, 24 November 2009 11:00

Eclipse User

Originally posted by: michael.gebhart.googlemail.com

Hi,

assuming, I have one SCA assembly with one component. Now, I wanna
expose the functionality of the component as web service. I have two
ways to do this:

1. Creating a WS binding for the component
2. Creating a WS binding for the component and propgating it as service
for the entire SCA assembly.

What is the difference between these two possibiliites? In both cases
the component functionality can be accessed via a web service interface.

Usually, interfaces that should be accessible from external, the service
should be propagated to the SCA assembly. But when using a WS binding,
this is not necessary. So, what is the difference at a logical level?

Best regards

Michael

Report message to a moderator

Re: WS binding vs. propagated WS binding [message #500198 is a reply to message #499840]

Wed, 25 November 2009 10:37

Vincent Zurczak

Messages: 149
Registered: July 2009

Senior Member

Hi Mickael,

Michael Gebhart a écrit :
> Hi,
>
> assuming, I have one SCA assembly with one component. Now, I wanna
> expose the functionality of the component as web service. I have two
> ways to do this:
>
> 1. Creating a WS binding for the component
> 2. Creating a WS binding for the component and propgating it as service
> for the entire SCA assembly.
>
> What is the difference between these two possibiliites? In both cases
> the component functionality can be accessed via a web service interface.

In SCA, what is inside the composite is not visible from the outside.
So, if you component service is not promoted, no matter which binding
you attached on it, it is not accessible from the outside of the composite.

So your first assumption (1.) is wrong.
The only exception is if the component is in fact a composite (a
component with a composite implementation) with the same service
available as a web service. Which brings you to 2.

Regards,

Vincent.

Report message to a moderator

Re: WS binding vs. propagated WS binding [message #500206 is a reply to message #500198]

Wed, 25 November 2009 11:35

Eclipse User

Originally posted by: michael.gebhart.googlemail.com

Hi Vincent,

thanks for your answer. Helped me pretty much!

Michael

> Hi Mickael,
>
>
> Michael Gebhart a écrit :
>> Hi,
>>
>> assuming, I have one SCA assembly with one component. Now, I wanna
>> expose the functionality of the component as web service. I have two
>> ways to do this:
>>
>> 1. Creating a WS binding for the component
>> 2. Creating a WS binding for the component and propgating it as
>> service for the entire SCA assembly.
>>
>> What is the difference between these two possibiliites? In both cases
>> the component functionality can be accessed via a web service interface.
>
>
> In SCA, what is inside the composite is not visible from the outside.
> So, if you component service is not promoted, no matter which binding
> you attached on it, it is not accessible from the outside of the composite.
>
> So your first assumption (1.) is wrong.
> The only exception is if the component is in fact a composite (a
> component with a composite implementation) with the same service
> available as a web service. Which brings you to 2.
>
>
> Regards,
>
> Vincent.
>
>

Report message to a moderator