Eclipse Community Forums: Service Component Architecture (SCA) Tools » Using the SCA Designer as an abstract modeling tool

Help

Home

Home » Archived » Service Component Architecture (SCA) Tools » Using the SCA Designer as an abstract modeling tool

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

Using the SCA Designer as an abstract modeling tool [message #6265]

Mon, 02 March 2009 13:44

Mischa

Messages: 14
Registered: July 2009

Junior Member

Hi all,

I want to use the SCA Designer as a kind of abstract modeling tool. This way
I don't want to have any dependencies to SCA implementations like the
"Apache Tuscany".
The SCA Designer generates a interface description like the following one as
default:

<tuscany:interface.wsdl
xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0"
interface="http://www.itemis.com/BLABLUB#wsdl.interface(BLUB)"/>

Why I'm forced to use tusacany? Is there a way to remove this impl-specific
namespace (or to change to it to a spring specific one) in the designer?

regards,
Mischa

Report message to a moderator

Re: Using the SCA Designer as an abstract modeling tool [message #6295 is a reply to message #6265]

Mon, 02 March 2009 14:21

Stephane Drapeau

Messages: 199
Registered: July 2009

Senior Member

Mischa a écrit :
> Hi all,
>
> I want to use the SCA Designer as a kind of abstract modeling tool. This
> way I don't want to have any dependencies to SCA implementations like
> the "Apache Tuscany".
> The SCA Designer generates a interface description like the following
> one as default:
>
> <tuscany:interface.wsdl
> xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0"
> interface="http://www.itemis.com/BLABLUB#wsdl.interface(BLUB)"/>
>
> Why I'm forced to use tusacany? Is there a way to remove this
> impl-specific namespace (or to change to it to a spring specific one) in
> the designer?
>
> regards,
> Mischa
>
>

Hi Mischa,

Currently the WSDL interface element is defined in the Open SOA
namespace and not in the Tuscany one. It was a bug that we fixed in the
last build [0]. Can you try the last version of the designer?

The following bindings (WebService, EJB, JMS), interfaces (Java, WSDL,
C++, BPEL Partner Link), and implementations (Java, SCA, BPEL, C++, EJB,
Spring, Web) are defined in the OSOA namespace, because they are defined
by the Open SOA consortium.
The others bindings, implementations and interfaces are defined in the
namespace of the SCA runtime that defines them. It's conceivable to have
the same SCA element (for example the RMI binding) defined in a way by
Tuscany and in another way by Frascati. So, the namespace is important.

If the namespace information isn't useful for you in your assembly file
you can use an XSLT transformation that remove this information when you
save the assembly file and an other transformation that add this
information when you load the assembly file. Because, the SCA tools (xml
editor, designer, tree viewer) need this information to work correctly.

In the plugin org.eclipse.stp.sca, in the directory xslt, you have two
samples of XSLT transformations, one for the transformation sca to
tuscany and an other for tuscany to sca. These transformations are not
maintenained.

Regards,

Stephane Drapeau
Obeo

[0]: http://download.eclipse.org/stp/updates/galileo/site.xml

Report message to a moderator

Re: Using the SCA Designer as an abstract modeling tool [message #7566 is a reply to message #6295]

Mon, 02 March 2009 15:03

Mischa

Messages: 14
Registered: July 2009

Junior Member

Hi Stephane,

thanks a lot for this detailed explanation. Since I'm not going to use any
"not Open SOA conform" elements I should be able to work with the Open SOA
namespaces only, which was my initial intention. (At least after updating to
the lasted build:-)).

Regrads,
Mischa

"Stephane Drapeau" <Stephane.Drapeau@obeo.fr> schrieb im Newsbeitrag
news:49ABEB7C.5010701@obeo.fr...
> Mischa a écrit :
>> Hi all,
>>
>> I want to use the SCA Designer as a kind of abstract modeling tool. This
>> way I don't want to have any dependencies to SCA implementations like the
>> "Apache Tuscany".
>> The SCA Designer generates a interface description like the following one
>> as default:
>>
>> <tuscany:interface.wsdl
>> xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0"
>> interface="http://www.itemis.com/BLABLUB#wsdl.interface(BLUB)"/>
>>
>> Why I'm forced to use tusacany? Is there a way to remove this
>> impl-specific namespace (or to change to it to a spring specific one) in
>> the designer?
>>
>> regards,
>> Mischa
>>
>>
>
> Hi Mischa,
>
> Currently the WSDL interface element is defined in the Open SOA namespace
> and not in the Tuscany one. It was a bug that we fixed in the last build
> [0]. Can you try the last version of the designer?
>
> The following bindings (WebService, EJB, JMS), interfaces (Java, WSDL,
> C++, BPEL Partner Link), and implementations (Java, SCA, BPEL, C++, EJB,
> Spring, Web) are defined in the OSOA namespace, because they are defined
> by the Open SOA consortium.
> The others bindings, implementations and interfaces are defined in the
> namespace of the SCA runtime that defines them. It's conceivable to have
> the same SCA element (for example the RMI binding) defined in a way by
> Tuscany and in another way by Frascati. So, the namespace is important.
>
> If the namespace information isn't useful for you in your assembly file
> you can use an XSLT transformation that remove this information when you
> save the assembly file and an other transformation that add this
> information when you load the assembly file. Because, the SCA tools (xml
> editor, designer, tree viewer) need this information to work correctly.
>
> In the plugin org.eclipse.stp.sca, in the directory xslt, you have two
> samples of XSLT transformations, one for the transformation sca to tuscany
> and an other for tuscany to sca. These transformations are not
> maintenained.
>
> Regards,
>
> Stephane Drapeau
> Obeo
>
> [0]: http://download.eclipse.org/stp/updates/galileo/site.xml
>

Report message to a moderator