Ayla,
Thank you for your feedback. I made these edits a little differently,
and passed them through several validating parser-generators. Can you
test the attached file?
Staurt
-----Original Message-----
From: Ayla Debora Dantas de Souza - Projeto Ourgrid
[mailto:ayla@dsc.ufcg.edu.br]
Sent: Tuesday, July 05, 2005 2:11 PM
To: Stuart Schaefer
Cc: cddlm-wg(a)ggf.org
Subject: Re: [cddlm] Doubts about Component Model
Hi Stuart,
sorry for the delay.
I still have some problems with the Component Model wsdl file that I'm
trying to solve, but I will let you know about some errors that I've
already changed here:
* The targetNamespace used in the wsdl file was the same of the
component-model.xsd. I've included the "/wsdl" at the end of the target
namespace, and I've also declared "xmlns:tns" with this namespace.
* The <wsdl:types> element of the wsdl is missing. In this part I
import the schemas used.
* The "taskActionResponse" message should be as follows instead of
refering to "taskActionRequest":
<wsdl:message name="taskActionResponse">
<wsdl:part name="taskActionResponse"
element="cmp:taskActionResponse"/>
</wsdl:message>
* The "StateActionFault" message was missing:
<wsdl:message name="StateActionFault">
<wsdl:part name="fault" element="cmp:StateActionFault"/>
</wsdl:message-->
* The "ComponentEndpoint" attribute wsrp:resourceProperties should be
"wsrp:ResourceProperties"
* The prefix of the messages referenced in the "GetResourceProperty",
"SetResourceProperty", "QueryResourceProperties" and
"GetMultipleResourceProperties" operations should be "wsrpw"(wsdl file)
instead of "wsrp" (which would be the schema).
* The prefix of the messages referenced in the "Destroy" operation
should be "wsrlw" instead of "wsrl"
* The prefix of the messages referenced in the "Initialize",
"Terminate", "Run" and "RunTask" operations should be "tns" instead of
"cmp".
* There is a typo in the "Run" operation: "StateActiontFault" should
be replaced by "StateActionFault"
* In the "RunTask" operation, the "taskActionResponsne" should be
"taskActionResponse"
* wsdl:binding and wsdl:service parts are missing in the wsdl
definition.
Best regards,
Ayla
Stuart Schaefer wrote:
>Ayla,
>
>The Component Model document was updated to clarify this. The "Last
>Call" version changed the examples. Internal elements are not allowed.
>Flow control elements can only be defined as children of a node in the
>property list. They cannot have child nodes.
>
>Please let me know about the wsdl errors. I will take a look as soon
as
>you forward the details.
>
>Stuart
>
>-----Original Message-----
>From: Ayla Debora Dantas de Souza - Projeto Ourgrid
>[mailto:ayla@dsc.ufcg.edu.br]
>Sent: Thursday, June 30, 2005 11:18 AM
>To: 'cddlm-wg(a)ggf.org'
>Subject: [cddlm] Doubts about Component Model
>
>Hi,
>
>we are having some problems in understanding the correct use of control
>flow elements from the component model. According to the schema, the
>cmp:sequence and cmp:flow elements, cannot have internal elements (like
>in the 'delegate' declaration), but according to some examples from the
>component model Word document, components can be defined inside these
>elements. Which option is the correct one?
>
>We also had some problems in the component-model.wsdl, specially
>regarding namespaces use, message definitions missing and some typos.
In
>
>another mail I will send more details about this.
>Best regards,
> Ayla
>
>
>
>
