[Smartfrog-developer] Enhancement idea: an execution context for deployment

[Steve L. <ste...@hp...>]

I have discussed this with Julio in the context of #include 
interpretation, but I have had a further thought.

1. For dynamic support of #include terms, we need to be able to 
dynamically extend the list of jars that get searched for #include 
resolution. This is critical when doing dynamic addition of new files 
via a Web Service interface.

proposed idea: we have a context that contains extra information used 
when reading the sf file; the core of the context would be a properties 
file providing overrides of System.properties(). The initial property 
declaring the path to JAR files to search could be overridden in this 
context.

2. I'd like to more easily override attributes from a build file. 
Example, I have  a TouchFile component

sfConfig extends Prim {
  sfClass "org.smartfrog.test.TouchFile";
  file "c:\\some-file";
}

If I want to deploy that configuration on multiple boxes, I can do it 
with the ant inline stuff, but why not just allow me to override some 
attributes when invoking the file

e.g.

<sf-deploy securityref="mysecurity" >
   <application name="touch" url="/org/ex/touch.sf">
    <attribute name="sfConfig:file" file="../somefile.txt"/>
    <attribute name="sfProcessHost" value="${server}"/>
   </application>
</sf-deploy>

Essentially the build file provides an extra layer of customisation 
round the deployment descriptor, setting parameters like platform 
specific file paths, hostnames, other things. Its essentially a more 
structured mechanism for integrating with ant.

I think the context could also be used for this, though it integrates 
more tightly with the resolution process.

Thoughts?

-steve