[cddlm] Doubts about ComandPath

[Stuart Schaefer]

Iury,

I think you missed a bit of the documentation.  The example you are
looking at does not include the <cmp:CodeBase> element.

<WebApplication>
  <cmp:CodeBase>http://server/file.jar</cmp:CodeBase>
  <cmp:CommandPath>com.exns.ApacheDeployer</cmp:CommandPath>
  <port>80</port>
  <hostname>www.example.org</hostname>
</WebApplication>

The command path is supposed to be used to locate the actual executable
instance, class file, etc...  The command path is declared normatively
in the schema as mixed content, which allows inline content.  This is
done in lieu of an <xs:any> element, which could cause problems with
inheritance.

I will look in the Component Model document, and see if this can be
clarified.

Regards,

Stuart

-----Original Message-----
From: Marcelo Iury Oliveira / Projeto Ourgrid - Prof. Walfredo
[mailto:iury at lsd.ufcg.edu.br] 
Sent: Tuesday, July 05, 2005 2:33 PM
To: cddlm-wg at ggf.org
Subject: [cddlm] Doubts about ComandPath

Hello all!

I'm developing a cddlm engine with Ayla, and now we are writing a 
factory that deploys and instantiates a given deployment component, 
using a CodeBase and a CommpandPath.
Looking at the component model specification, I got a little bit 
confused about the CommandPath, specially considering the given example,

which is in the following:
...
<cmp:CommandPath>
   <cmp:path>http://server.com/app.jar</cmp:path>
   <cmp:args>...</cmp:args> *
</cmp:CommandPath>
...

As we have arguments, I think we need a "command" element (that can be 
optional) to pass these arguments. As we do not have the "command" 
element, we thought it could be in the "path" element, or we could have 
there executable files, but in the example presented  we  have a  .jar 
file,  which is not  executable by itself.


Can anyone help us in making this more clear?

   Iury