Hi,
would it make sense to create a service that will contain all the deployment
required functions ? And just load this in the "Deployer" default component.
My need would be have a deployer by component group. In this way I could
have the deployment function, scheduling, outside interface in the same
Component.
I could spend time doing this if it is usefull and just "copy paste" work
deployment methods as a Service ?
On Monday 10 October 2011 21:49:26 Willy Lambert wrote:
> Hi,
>
> would it make sense to create a service that will contain all the
> deployment required functions ? And just load this in the "Deployer"
> default component. My need would be have a deployer by component group. In
> this way I could have the deployment function, scheduling, outside
> interface in the same Component.
> I could spend time doing this if it is usefull and just "copy paste" work
The easiest way (might be) to allow the initial deployer create additional
deployment components. Ie, add two lines to loadComponent that intercept
a creation for OCL::DeploymentComponent, and return a new instance.
If you have it as a service, how would you cause that service to be loaded in
a component, given that the loadService function is part of the deployment
component ? Or would you suggest that loadService becomes a 'default'
TaskContext operation ? That would solve the bootstrap problem.
Peter
deployment methods as a Service ?
On Tue, 11 Oct 2011, Peter Soetens wrote:
> On Monday 10 October 2011 21:49:26 Willy Lambert wrote:
>> Hi,
>>
>> would it make sense to create a service that will contain all the
>> deployment required functions ? And just load this in the "Deployer"
>> default component. My need would be have a deployer by component group. In
>> this way I could have the deployment function, scheduling, outside
>> interface in the same Component.
>> I could spend time doing this if it is usefull and just "copy paste" work
>
> The easiest way (might be) to allow the initial deployer create additional
> deployment components. Ie, add two lines to loadComponent that intercept
> a creation for OCL::DeploymentComponent, and return a new instance.
>
> If you have it as a service, how would you cause that service to be loaded in
> a component, given that the loadService function is part of the deployment
> component ? Or would you suggest that loadService becomes a 'default'
> TaskContext operation ? That would solve the bootstrap problem.
My 2 cents... This discussion is about the (motivated!) need for _workflow_
support somewhere in the "Development Process". Reusing/misusing/abusing
the TaskContext Services for that is not the right way to do, I think,
since our component model is designed to optimise different needs than a
(deployment) workflow...
I do support workflow design efforts, but I would like to see them done
_outside_ of the RTT context; projects like Kepler/Ptolemy or Taverna or
Eclise Workflow are focused on such workflow tools...
> Peter
Herman