Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Service Component Architecture (SCA) Tools » Validating SCA 1.1 namespaces(Any other way around this hack?)
Validating SCA 1.1 namespaces [message #544295] Fri, 02 July 2010 05:13 Go to next message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
I am preparing a tutorial and prototype of a composite application, build with SCA Tools (ergo SCA 1.0). I am able to deploy it to Tuscany 2.0M5, by manually changing the namespace declarations in the composite file:

From

<!--sca:composite xmlns:sca="http://www.osoa.org/xmlns/sca/1.0" xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0" name="Default"-->

To

<sca:composite targetNamespace="http://test" xmlns:sca="http://docs.oasis-open.org/ns/opencsa/sca/200912" xmlns:tuscany="http://http://tuscany.apache.org/xmlns/sca/1.1" name="Default">

However, this naturally breaks the meta-model validation done by the SCA Tools plugin. Is there any other way to acheive compatibility? What is the status of SCA 1.1 model validation? I had difficulties finding information on this subject.

Cheers,

Ken
Re: Validating SCA 1.1 namespaces [message #544643 is a reply to message #544295] Mon, 05 July 2010 03:48 Go to previous messageGo to next message
Stephane Drapeau is currently offline Stephane Drapeau
Messages: 198
Registered: July 2009
Senior Member
Hi Ken,

Which version of SCA Tools do you use?
The Helios version (SCA Tools 2.1.0) is supposed to work with SCA 1.1.
Can you give it a try?

Best regards,

Stephane Drapeau
Obeo

Ken Mc Neill a écrit :
> I am preparing a tutorial and prototype of a composite application,
> build with SCA Tools (ergo SCA 1.0). I am able to deploy it to Tuscany
> 2.0M5, by manually changing the namespace declarations in the composite
> file:
>
> From
>
> <!--sca:composite xmlns:sca="http://www.osoa.org/xmlns/sca/1.0"
> xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0" name="Default"-->
>
> To
>
> <sca:composite targetNamespace="http://test"
> xmlns:sca="http://docs.oasis-open.org/ns/opencsa/sca/200912"
> xmlns:tuscany="http://http://tuscany.apache.org/xmlns/sca/1.1"
> name="Default">
>
> However, this naturally breaks the meta-model validation done by the SCA
> Tools plugin. Is there any other way to acheive compatibility? What is
> the status of SCA 1.1 model validation? I had difficulties finding
> information on this subject.
> Cheers,
>
> Ken
Re: Validating SCA 1.1 namespaces [message #544757 is a reply to message #544643] Mon, 05 July 2010 08:46 Go to previous messageGo to next message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
Thanks for the tip.

I downloaded Helios and the latest SCA Tools 2.1.0.x from the update site. I have created a new 'fresh' SCA project, and I can build a composite diagram (using the New...Other...SCA-> OASIS/CSA Composite Diagram), and run it on Tuscany 2.0.

However, the validator refuses to validate the assembly; it says: "default.composite could not be loaded by the SCA meta-model (it might be an invalid XML document)." on the first line, showing the little red 'x'.

The associated diagram (default.composite_diagram) model builder also flags a problem: "One or several errors were found in the diagram. See default.composite for more details."

This does NOT stop me from modifying the diagram or redeploying the composite successfully. The builder seems not to like the namespace declaration that the plugin, itself created by default:

<?xml version="1.0" encoding="UTF-8" standalone="no"?><csa:composite xmlns:csa="http://docs.oasis-open.org/ns/opencsa/sca/200912" name="default" targetNamespace="http://eclipse.org/SCA3/src/test/default"/>

This seems like some sort of validation bug, which does NOT happen if I create a new OSOA SCA (older namespace) Composite and diagram. Should I file a bug?

A+,

Ken
Re: Validating SCA 1.1 namespaces [message #544824 is a reply to message #544757] Mon, 05 July 2010 11:56 Go to previous messageGo to next message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
There are other apparent kinks in the the SCA Tools 2.1 release when using SCA version 1.1. It looks like the new Schema isn't being properly manipulated. When creating a wire on the diagram between a reference and a service, the model outputs into the composite file:

<csa:wire source="SomeComponent/SomeReference" source2="#SomeComponent/SomeReference" target="AnotherComponent/AnotherService" target2="#AnotherComponent/AnotherService"/>

Elements 'source2' and 'target2' are not valid wire attributes--I believe they are probably EMF objects.

It seems to me that the SCA 1.1 model still needs some work before it output valid composites for Tuscany 2.0...

-K
Re: Validating SCA 1.1 namespaces [message #545015 is a reply to message #544757] Tue, 06 July 2010 07:28 Go to previous messageGo to next message
Vincent Zurczak is currently offline Vincent Zurczak
Messages: 140
Registered: July 2009
Senior Member
Hi Ken,

Indeed, this is a bug.
Validation for SCA 1.1 was supposed to be disabled (composite should
have been skipped). Only edition was added. Validation needs us to
reorganize most of our plug-ins and that could not be done for Helios.

Regards,

Vincent.



Le 05/07/2010 14:46, Ken Mc Neill a écrit :
> Thanks for the tip.
>
> I downloaded Helios and the latest SCA Tools 2.1.0.x from the update
> site. I have created a new 'fresh' SCA project, and I can build a
> composite diagram (using the New...Other...SCA-> OASIS/CSA Composite
> Diagram), and run it on Tuscany 2.0.
>
> However, the validator refuses to validate the assembly; it says:
> "default.composite could not be loaded by the SCA meta-model (it might
> be an invalid XML document)." on the first line, showing the little red
> 'x'.
>
> The associated diagram (default.composite_diagram) model builder also
> flags a problem: "One or several errors were found in the diagram. See
> default.composite for more details."
>
> This does NOT stop me from modifying the diagram or redeploying the
> composite successfully. The builder seems not to like the namespace
> declaration that the plugin, itself created by default:
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?><csa:composite
> xmlns:csa="http://docs.oasis-open.org/ns/opencsa/sca/200912"
> name="default" targetNamespace="http://eclipse.org/SCA3/src/test/default"/>
>
> This seems like some sort of validation bug, which does NOT happen if I
> create a new OSOA SCA (older namespace) Composite and diagram. Should I
> file a bug?
>
> A+,
>
> Ken
Re: Validating SCA 1.1 namespaces [message #545018 is a reply to message #544757] Tue, 06 July 2010 08:16 Go to previous messageGo to next message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
I have found a strange workaround to the problem of the SCA 1.1 composite and diagram files being flagged as invalid (see previous post).

If those files (in my case 'default.composite' and 'default.composite_diagram') are placed in the top-level project directory, the validation problem dissappears.

If I move them to 'src', or to a package under 'src', they are flagged as invalid (only happens for SCA 1.1 OASIS/CSA).

The problem of "source2" and "target2" attributes in the wire node of the composite file remains...

-K
Re: Validating SCA 1.1 namespaces [message #545064 is a reply to message #545018] Tue, 06 July 2010 10:12 Go to previous messageGo to next message
Vincent Zurczak is currently offline Vincent Zurczak
Messages: 140
Registered: July 2009
Senior Member
It is not a "real workaround".
Your composite being at the root of the project, it is not built anymore.
Neither by the SCA builder (which validates it), nor by the Java builder.

It means the composite being in your bin directory (and used by Tuscany,
I guess) is not the same that the one at the root of the project.


Vincent.


Le 06/07/2010 14:17, Ken Mc Neill a écrit :
> I have found a strange workaround to the problem of the SCA 1.1
> composite and diagram files being flagged as invalid (see previous post).
>
> If those files (in my case 'default.composite' and
> 'default.composite_diagram') are placed in the top-level project
> directory, the validation problem dissappears.
>
> If I move them to 'src', or to a package under 'src', they are flagged
> as invalid (only happens for SCA 1.1 OASIS/CSA).
>
> The problem of "source2" and "target2" attributes in the wire node of
> the composite file remains...
>
> -K
Re: Validating SCA 1.1 namespaces [message #545089 is a reply to message #545064] Tue, 06 July 2010 11:18 Go to previous messageGo to next message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
Ok, I understand.

On a positive note, it seems to me that there are very few things missing from the "OASIS / CSA" builder / validator with respect to the existing "OSOA SCA".

The tutorial I'm preparing aims to clarify some of the confusion surrounding the two specs. Is there a target timeframe for stabilizing the 1.1 plugin? Is it easy to get involved?

Ken
Re: Validating SCA 1.1 namespaces [message #545158 is a reply to message #545089] Tue, 06 July 2010 15:44 Go to previous message
Stephane Drapeau is currently offline Stephane Drapeau
Messages: 198
Registered: July 2009
Senior Member
Ken Mc Neill a écrit :
> Ok, I understand.
>
> On a positive note, it seems to me that there are very few things
> missing from the "OASIS / CSA" builder / validator with respect to the
> existing "OSOA SCA".
>
> The tutorial I'm preparing aims to clarify some of the confusion
> surrounding the two specs. Is there a target timeframe for stabilizing
> the 1.1 plugin?

We aim to fix a maximum of blocking bugs for Helios SR1 (end of
September) and the others for SR2.

Is it easy to get involved?

Yes, it's very easy. The two main ways to help us are:
- to open bugs in the bugzilla,
- to submit patches.

You're welcome ;-)

Stephane Drapeau
Obeo
Re: Validating SCA 1.1 namespaces [message #577466 is a reply to message #544643] Mon, 05 July 2010 08:46 Go to previous message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
Thanks for the tip.

I downloaded Helios and the latest SCA Tools 2.1.0.x from the update site. I have created a new 'fresh' SCA project, and I can build a composite diagram (using the New...Other...SCA-> OASIS/CSA Composite Diagram), and run it on Tuscany 2.0.

However, the validator refuses to validate the assembly; it says: "default.composite could not be loaded by the SCA meta-model (it might be an invalid XML document)." on the first line, showing the little red 'x'.

The associated diagram (default.composite_diagram) model builder also flags a problem: "One or several errors were found in the diagram. See default.composite for more details."

This does NOT stop me from modifying the diagram or redeploying the composite successfully. The builder seems not to like the namespace declaration that the plugin, itself created by default:

<?xml version="1.0" encoding="UTF-8" standalone="no"?><csa:composite xmlns:csa="http://docs.oasis-open.org/ns/opencsa/sca/200912" name="default" targetNamespace="http://eclipse.org/SCA3/src/test/default"/>

This seems like some sort of validation bug, which does NOT happen if I create a new OSOA SCA (older namespace) Composite and diagram. Should I file a bug?

A+,

Ken
Re: Validating SCA 1.1 namespaces [message #577486 is a reply to message #577466] Mon, 05 July 2010 11:56 Go to previous message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
There are other apparent kinks in the the SCA Tools 2.1 release when using SCA version 1.1. It looks like the new Schema isn't being properly manipulated. When creating a wire on the diagram between a reference and a service, the model outputs into the composite file:

<csa:wire source="SomeComponent/SomeReference" source2="#SomeComponent/SomeReference" target="AnotherComponent/AnotherService" target2="#AnotherComponent/AnotherService"/>

Elements 'source2' and 'target2' are not valid wire attributes--I believe they are probably EMF objects.

It seems to me that the SCA 1.1 model still needs some work before it output valid composites for Tuscany 2.0...

-K
Re: Validating SCA 1.1 namespaces [message #577508 is a reply to message #577466] Tue, 06 July 2010 07:28 Go to previous message
Vincent Zurczak is currently offline Vincent Zurczak
Messages: 140
Registered: July 2009
Senior Member
Hi Ken,

Indeed, this is a bug.
Validation for SCA 1.1 was supposed to be disabled (composite should
have been skipped). Only edition was added. Validation needs us to
reorganize most of our plug-ins and that could not be done for Helios.

Regards,

Vincent.



Le 05/07/2010 14:46, Ken Mc Neill a écrit :
> Thanks for the tip.
>
> I downloaded Helios and the latest SCA Tools 2.1.0.x from the update
> site. I have created a new 'fresh' SCA project, and I can build a
> composite diagram (using the New...Other...SCA-> OASIS/CSA Composite
> Diagram), and run it on Tuscany 2.0.
>
> However, the validator refuses to validate the assembly; it says:
> "default.composite could not be loaded by the SCA meta-model (it might
> be an invalid XML document)." on the first line, showing the little red
> 'x'.
>
> The associated diagram (default.composite_diagram) model builder also
> flags a problem: "One or several errors were found in the diagram. See
> default.composite for more details."
>
> This does NOT stop me from modifying the diagram or redeploying the
> composite successfully. The builder seems not to like the namespace
> declaration that the plugin, itself created by default:
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?><csa:composite
> xmlns:csa="http://docs.oasis-open.org/ns/opencsa/sca/200912"
> name="default" targetNamespace="http://eclipse.org/SCA3/src/test/default"/>
>
> This seems like some sort of validation bug, which does NOT happen if I
> create a new OSOA SCA (older namespace) Composite and diagram. Should I
> file a bug?
>
> A+,
>
> Ken
Re: Validating SCA 1.1 namespaces [message #577522 is a reply to message #577466] Tue, 06 July 2010 08:17 Go to previous message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
I have found a strange workaround to the problem of the SCA 1.1 composite and diagram files being flagged as invalid (see previous post).

If those files (in my case 'default.composite' and 'default.composite_diagram') are placed in the top-level project directory, the validation problem dissappears.

If I move them to 'src', or to a package under 'src', they are flagged as invalid (only happens for SCA 1.1 OASIS/CSA).

The problem of "source2" and "target2" attributes in the wire node of the composite file remains...

-K
Re: Validating SCA 1.1 namespaces [message #577538 is a reply to message #577522] Tue, 06 July 2010 10:12 Go to previous message
Vincent Zurczak is currently offline Vincent Zurczak
Messages: 140
Registered: July 2009
Senior Member
It is not a "real workaround".
Your composite being at the root of the project, it is not built anymore.
Neither by the SCA builder (which validates it), nor by the Java builder.

It means the composite being in your bin directory (and used by Tuscany,
I guess) is not the same that the one at the root of the project.


Vincent.


Le 06/07/2010 14:17, Ken Mc Neill a écrit :
> I have found a strange workaround to the problem of the SCA 1.1
> composite and diagram files being flagged as invalid (see previous post).
>
> If those files (in my case 'default.composite' and
> 'default.composite_diagram') are placed in the top-level project
> directory, the validation problem dissappears.
>
> If I move them to 'src', or to a package under 'src', they are flagged
> as invalid (only happens for SCA 1.1 OASIS/CSA).
>
> The problem of "source2" and "target2" attributes in the wire node of
> the composite file remains...
>
> -K
Re: Validating SCA 1.1 namespaces [message #577559 is a reply to message #545064] Tue, 06 July 2010 11:18 Go to previous message
Ken Mc Neill is currently offline Ken Mc Neill
Messages: 10
Registered: July 2009
Junior Member
Ok, I understand.

On a positive note, it seems to me that there are very few things missing from the "OASIS / CSA" builder / validator with respect to the existing "OSOA SCA".

The tutorial I'm preparing aims to clarify some of the confusion surrounding the two specs. Is there a target timeframe for stabilizing the 1.1 plugin? Is it easy to get involved?

Ken
Re: Validating SCA 1.1 namespaces [message #577579 is a reply to message #545089] Tue, 06 July 2010 15:44 Go to previous message
Stephane Drapeau is currently offline Stephane Drapeau
Messages: 198
Registered: July 2009
Senior Member
Ken Mc Neill a écrit :
> Ok, I understand.
>
> On a positive note, it seems to me that there are very few things
> missing from the "OASIS / CSA" builder / validator with respect to the
> existing "OSOA SCA".
>
> The tutorial I'm preparing aims to clarify some of the confusion
> surrounding the two specs. Is there a target timeframe for stabilizing
> the 1.1 plugin?

We aim to fix a maximum of blocking bugs for Helios SR1 (end of
September) and the others for SR2.

Is it easy to get involved?

Yes, it's very easy. The two main ways to help us are:
- to open bugs in the bugzilla,
- to submit patches.

You're welcome ;-)

Stephane Drapeau
Obeo
Previous Topic:Validating SCA 1.1 namespaces
Next Topic:STP headless build from Hudson CI server
Goto Forum:
  


Current Time: Mon Apr 21 00:51:51 EDT 2014

Powered by FUDForum. Page generated in 0.03208 seconds