|
|
|
|
| Re: Validating SCA 1.1 namespaces [message #545015 is a reply to message #544757] |
Tue, 06 July 2010 11:28   |
|
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 #545064 is a reply to message #545018] |
Tue, 06 July 2010 14:12 |
|
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 #577508 is a reply to message #577466] |
Tue, 06 July 2010 11:28 |
|
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 #577538 is a reply to message #577522] |
Tue, 06 July 2010 14:12 |
|
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
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02780 seconds
] 
Search
Help
Register
Login
Home
