7 Nov
2011
7 Nov
'11
11:46 p.m.
Hi,
This is not the cleanest part of Moose :).
If I understand correctly, you would like to specify a new Operator to be run at the end
of the default ImportingTask. There is no mechanism for that, because we never had the use
case.
The closest thing for is the way to run the CandidateOperator. Take a look at
MooseCompositeImporterTask. At the end of basicRun, the candidateOperator is run if it is
present.
It would probably be interesting to have some more extensibility here. But, what is your
use case?
Cheers,
Doru
On 7 Nov 2011, at 23:35, Stéphane Ducasse wrote:
Doru
long time ago :) there were importer post action plugin that we could register to Moose.
I reread my comment on Tasks and friends (I hate hate all the classes with not a single
comment - so I will take some time
when I can to see what I can write but this is really terrible) - this were the comments
I wrote when I wanted to build the new importer.
Now they do not describe the API and how to plug a new Task.
So how do we declare to an importer that a task should be run automatically after a model
is created?
May be by creating a compositeTask but I want it to run after the main model is created.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"What is more important: To be happy, or to make happy?"