Sheryl,
No. We already know that.
We want to define generic condition class in policy/conditions.xml file. And we
want use that condition class with different input params (properties - look
for "CustomCondition" in following example) in tasks.xml file.
So for example:
<task id="urn:oodt:HelloWorld" name="Hello World"
class="org.apache.oodt.cas.workflow.examples.HelloWorld">
<conditions>
<condition id="urn:oodt:CustomCondition">
<property name="searchFile" value="VIIRS[0-9]{1,3}" />
</conditions>
<configuration>
<property name="Person" value="Task1" />
</configuration>
</task>
<task id="urn:oodt:HelloWorld1" name="Hello World1"
class="org.apache.oodt.cas.workflow.examples.HelloWorld1">
<conditions>
<condition id="urn:oodt:CustomCondition">
<property name="searchFile" value="CrIs_[0-9]{1,3}" />
</conditions>
<configuration>
<property name="Person" value="Task2" />
</configuration>
</task>
Thanks
Chintu
________________________________________
From: Sheryl John [[email protected]]
Sent: Tuesday, April 10, 2012 10:46 PM
To: [email protected]
Cc: Mistry, Chintu (GSFC-586.0)[COLUMBUS TECHNOLOGIES AND SERVICES INC]
Subject: Re: workflow task/condition question
Hi Ryan,
You can specify properties for your conditions in the conditions.xml.
There's an example with properties for "urn:oodt:CheckForMetadataKeys" in the
/policy/conditions.xml. Also check out the other examples.
So if you're defining a new condition class, you'll have add that to the
conditions.xml and include properties for that condition.
Is that what you were looking for?
On Tue, Apr 10, 2012 at 12:35 PM, Gerard, Ryan S. (GSFC-586.0)[COLUMBUS
TECHNOLOGIES AND SERVICES INC]
<[email protected]<mailto:[email protected]>> wrote:
Hello,
We have a question regarding our workflow tasks. We are configuring our
tasks.xml file and need to define some properties for our conditions. We would
like to create a general condition and reuse it for many tasks. Is there a way
to do this?
<task id="urn:oodt:HelloWorld" name="Hello World"
class="org.apache.oodt.cas.workflow.examples.HelloWorld">
<conditions>
<condition id="urn:oodt:TrueCondition"
IS THERE A WAY TO DEFINE A PROPERTY IN THE CONDITION
HERE
/>
</conditions>
<configuration>
<property name="Person" value="Chris" />
</configuration>
</task>
Thanks,
Ryan Gerard
--
-Sheryl