June 2005 - cddlm-wg - lists.ogf.org

Problems using Muse
by Ayla Debora Dantas de Souza - Projeto Ourgrid 22 Jun '05

22 Jun '05

Hi, when I've changed to the new released version (in fact a SNAPSHOT) of Muse and I try to compile the generated code for the portal and system services, even do not changing anything in the generated code, I get an error indicating that the "DeploymentFaultException" file is missing (it was not generated). I saw that the "ComponentFaultException" was generated. I think that maybe there is a problem with the deployment-api.wsdl, in the part: <wsdl:message name="DeploymentFault"> <wsdl:part name="fault" element="cmp:ComponentFault"/> </wsdl:message> When I look at the component-model.xsd file cmp:ComponentFault element, I see that its type is cmp:DeploymentFaultType. I'm trying to solve it in several ways, but with my changes I get other exceptions. Does someone have an idea? Thanks, Ayla

3 5

XML-CDL schema issue
by Stuart Schaefer 22 Jun '05

22 Jun '05

Jun and Steve, Microsoft was supposed to have fixed their XML parser issues with .NET 2.0. It appears that most issues that I have tested are resolved. However, the issue with ##local and ##other are still there. The XML-CDL schema defines the propertyListType and cdl elements to have an unlimited choice of either element. MSXML will not accept this. We will either need to allow for a .NET schema and Java schema or my proposal would be to eliminate ##local and force all elements to have namespace qualification. Thoughts? Stuart

2 1

RE: [cddlm] Problems using Muse
by Stuart Schaefer 22 Jun '05

22 Jun '05

Ayla, The "DeploymentFaultType" is the base of all CDDLM faults used by the component model and deployment API. The ComponentFault is a fault generated by a component implementing the component model. It adds no other elements to the DeploymentFaultType. The deployment api defines the DeploymentFault. It should not be of type ComponentFault unless a fault is generated by a component. Either way, the wsdl and xsd are valid. Not sure why Muse is upset. Stuart -----Original Message----- From: Ayla Debora Dantas de Souza - Projeto Ourgrid [mailto:ayla@dsc.ufcg.edu.br] Sent: Wednesday, June 22, 2005 1:59 PM To: Steve Loughran Cc: 'cddlm-wg(a)ggf.org' Subject: Re: [cddlm] Problems using Muse Hi, So, do you think Muse is a dead end? I created by hand the "DeploymentFaultException" based on the "ComponentFaultException" which was generated and the compilation and deployment with Muse worked out. It may be a problem with Muse, but I thought it was strange to see a message called "DeploymentFault" pointing to an element called "ComponentFault" which was of the type "DeploymentFaultType". That's why I'm not sure that this is not a problem with the specification. Does anyone see any problem in this part of the specification? Regarding Muse use, I really appreciate your opinion about it. This latest version seems to be better, but now I would have to learn how to communicate with the deployed services and insert code into the generated code which will actually be the deployment engine. Steve gave me the advice of looking at their source code, as Muse documentation is not complete. Ayla Steve Loughran wrote: > Ayla Debora Dantas de Souza - Projeto Ourgrid wrote: > >> Hi, >> >> when I've changed to the new released version (in fact a SNAPSHOT) of >> Muse and I try to compile the generated code for the portal and >> system services, even do not changing anything in the generated code, >> I get an error indicating that the "DeploymentFaultException" file is >> missing (it was not generated). I saw that the >> "ComponentFaultException" was generated. I think that maybe there is >> a problem with the deployment-api.wsdl, in the part: >> >> <wsdl:message name="DeploymentFault"> >> <wsdl:part name="fault" element="cmp:ComponentFault"/> >> </wsdl:message> >> >> When I look at the component-model.xsd file cmp:ComponentFault >> element, I see that its type is cmp:DeploymentFaultType. >> >> I'm trying to solve it in several ways, but with my changes I get >> other exceptions. Does someone have an idea? >> > > I think you are in the wonderful world of WSDL2Java generated stuff. > Ed and I wrote paper critiquing that very thing ( > http://www.hpl.hp.com/techreports/2005/HPL-2005-83.html ) > > the short term solution is to raise it with the muse mail list; point > them at the XSD/WSDL and see if it is a bug on their side. I suspect > they could do with more test WSDL/XSD and so to get ours in there > would be a good bit of integration. > > Long term (2 weeks plus), well, we need to do a new SOAP stack, dont we? >

2 1

Bad PDF for ggf-cddlm-deploy-api.pdf June 14 2005 file
by Ian Stokes-Rees 22 Jun '05

22 Jun '05

Hi, Last week an email was sent with these two files: ggf-cddlm-deploy-api.pdf ggf-cddlm-deploy-api.doc For me, the images in the PDF document were garbled -- the fonts didn't display properly. I have a pretty standard Windows 2000 installation, so perhaps others had the same result? It is not a big issue, since I can look at the Word version, but it would be nice to have a "good" PDF copy as well. Cheers, Ian -- Ian Stokes-Rees i.stokes-rees(a)physics.ox.ac.uk Particle Physics, Oxford http://www-pnp.physics.ox.ac.uk/~stokes

2 1

updated doc in CVS
by Steve Loughran 22 Jun '05

22 Jun '05

There is an updated document on CVS, for those with CVS access. I havent generated the PDF image as I had to turn off images to stop word crashing on image layout. I will send that later tonight. Changes -updated events -reported errors -consistent use of ResourceID -replace most of the inline pictures with (valid) non-normative examples of messages/responses. email/uploaded version to follow in a few hours, steve

1 0

Component Model Last Call
by Stuart Schaefer 20 Jun '05

20 Jun '05

Attached is the final draft of the CDDLM Component Model. This will be the Last Call for comments on this version of the specification. The document includes fixes for the events declared by the component model, causing XML validation errors. There is a new section clarifying the effect of scope on control flow operations, to ensure that spaghetti control flow does not occur. I have a proposal on how to address Jun's comments on component model element inheritance. It is not included in this draft. I will send it in a separate email, for discussion on Wednesday. Please take time to review this document. Any and all comments are welcome. Stuart

1 0

RE: [cddlm] updated deployment API
by Milojicic, Dejan S 20 Jun '05

20 Jun '05

Hi Steve, Please do so, put the documents on the site. I am in Seattle at the moment, but we'll continue to have our regular weekly meeting tomorrow, 6am, usual phone number. The agenda is update on two remaining specs, agenda at GGF, and daily business. Thanks, Dejan. > -----Original Message----- > From: owner-cddlm-wg(a)ggf.org [mailto:owner-cddlm-wg@ggf.org] > On Behalf Of Steve Loughran > Sent: Tuesday, June 14, 2005 7:29 AM > To: cddlm-wg(a)ggf.org > Subject: [cddlm] updated deployment API > > > Hello, > this is the final pre-GGF14 update. > 1. the .doc file shows the most recent changes 2. the .pdf is > the one for broad circulation. > > Dejan, shall I put this + the WSDL/XSD up on the documents > list on the site? >

3 2

OGSA-WG Proposed agenda for June 20th call
by Hiro Kishimoto 18 Jun '05

18 Jun '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 20th Monday from 5pm to 7pm (CDT). The upcoming call is for cross-WG discussion with CDDLM-WG and three documents (hopefully) final review. The dial-in number for Monday; Free: +1-866-639-4741 Toll: +1-574-935-6703 PIN: 8980700 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0620 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval (if available) Agenda bashing 2) GGF13 session schedule update (10 min) OGSA session schedule https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan/en… GGF on-line schedule page (not 100% up-to-date) http://tinyurl.com/ext3m 3) CDDLM-WG cross discussion (60 min) The intent of the meeting is to familiarize OGSA with CDDLM-WG's progress, to get OGSA-WG's feedback, and agree on the next steps. Most importantly to plan our meeting at GGF with the OGSA-EMS architecture team. (OGSA-WG #4 "EMS architecture" session, June 28 (Tues), 2:30-4pm at Wellington 1) Dejan, CDDLM-WG co-chair, comes up with a brief presentation on where CDDLM-WG are, where they are going, etc. and carrying it over to GGF14. 4) Three documents final review (40 min) OGSA roadmap 1.0 Jem has uploaded the revised version to the GridForge. - http://tinyurl.com/aez86 OGSA profile definition 1.0 Andreas will upload the revised version shortly. OGSA basic profile 1.0 Tom will upload the revised version shortly. 5) Wrap up (10 min) AOB June 22th (Wed) GGF14 preparation June 27-30 GGF14 ---- Hiro Kishimoto -- Hiro Kishimoto

1 0

CDL: extension and cdl:documentation
by Steve Loughran 17 Jun '05

17 Jun '05

I would presume that both of the following operations are illegal <?xml version="1.0"?> <cdl:cdl xmlns:cdl="http://www.gridforum.org/namespaces/2005/02/cddlm/CDL-1.0"> <cdl:documentation> Presumably, documentation cannot be extended. </cdl:documentation> <cdl:configuration> <cdl:documentation> do not expand these </cdl:documentation> </cdl:configuration> <cdl:system> <example cdl:extends="cdl:documentation"/> </cdl:system> </cdl:cdl> and <?xml version="1.0"?> <cdl:cdl xmlns:cdl="http://www.gridforum.org/namespaces/2005/02/cddlm/CDL-1.0"> <cdl:documentation> In which a documentation node extends something. We should reject this. </cdl:documentation> <cdl:configuration> <example /> </cdl:configuration> <cdl:system> <cdl:documentation cdl:extends="example"> </cdl:documentation> </cdl:system> </cdl:cdl> These are extensions to and from documentation elements. My implementation does not (currently) resolve these; more by accident than design, and it doesnt give a very good error message as a consequence. -steve

1 0

CDL: extension query
by Steve Loughran 16 Jun '05

16 Jun '05

Jun, I have one more query on extensions. What do you do with children of an element that are not eleements, but comments, text, etc. Specifically, what is the result of this extension. <?xml version="1.0"?> <cdl:cdl xmlns:cdl="http://www.gridforum.org/namespaces/2005/02/cddlm/CDL-1.0" > <cdl:configuration> <Component>  Component: Nested Text </Component> </cdl:configuration> <cdl:system> <Extension cdl:extends="Component">  Extension : Nested Text </Extension> </cdl:system> </cdl:cdl> Should it be parent retains stuff: <Extension cdl:extends="Component">  Extension : Nested Text </Extension> or merge in children <Extension cdl:extends="Component">  Extension : Nested Text  Component: Nested Text </Extension> I will file this on the tracker. -Steve

1 0