Re: [winery-dev] Problem about “export CSAR”

[Oliver Kopp <kopp.dev@xxxxxxxxx>]

Dear Yao Chen,

Which Moodle.csar are you referring to? Could you provide a URL? :)

Winery's exported CSAR is standards compliant. The difference to other
CSARs is that we export one Definitions file per "component". A
"component" is something that may be nested directly in a
<Definitions>-XML-tag. To "read" the Definitions manually, go to
TOSCA-Metadata and then "TOSCA.meta". In that file,
"Entry-Definitions" is defined. It points to the "root" Definitoins
file. For instance, "Definitions/ns7__Moodle.tosca". If you open that
file you'll see many "Import" statements. For instance:
--cut--
<tosca:Import namespace="http://www.example.org";
location="ns3__MySQLConnection.tosca"
importType="http://docs.oasis-open.org/tosca/ns/2011/12"/>
--end--
If you open ns3__MySQLConnection.tosca, you'll see the Definitions for
the MySQLConnection type.

We don't have a real user guide. We recommend following the TOSCA
Primer - http://docs.oasis-open.org/tosca/tosca-primer/v1.0/tosca-primer-v1.0.html

Hope that helps.

Cheers,

Oliver

2014-08-08 5:24 GMT+02:00 Yao Chen <tracyaoer@xxxxxxxxx>:
>       I have applied the “export CSAR” function to generate our own CSAR
> package, and the file/directory structure is quite different from the
> Moodle.csar provided as a showcase. In our package, there is only one
> directory called “definitions”. I am quite confused about our steps and a
> user guide can be very helpful.