CoreandServices.book - Ocean - Schlumberger

Using the convenience class is the easiest way to do this since it implements
IDescribedArgumentsSource.
Custom Worksteps
public abstract class DescribedArgumentsByReflection :
IDescribedArgumentsSource
{
public DescribedArgument[] DescribedArguments { get; }
protected DescribedArgumentsByReflection();
}
Each public property in your derived argument package class becomes a
DescribedArgument object. All of the DescribedArguments objects are packaged
into an array, and the array is returned whenever needed.
Ocean uses the DescribedArguments array from your argument package to retrieve all
of the argument information used in the convenience functionality such as building the
default UI’s.
Advanced - Argument Package Alternatives
The alternatives are an advanced topic; a typical developer would just use the
convenience class.
Now that we have covered the details of how argument packages work internally, we can
discuss the two alternatives:
• Implementing IDescribedArgumentsSource yourself. This is more work, but you
still get to use all the Ocean convenience functionality.
• Writing an argument package class that neither implements
IDescribedArgumentsSource nor derives from
DescribedArgumentsByReflection. This means you will not get the Ocean
convenience functionality.
Advanced - Implementing IDescribedArguments-Source
You should implement IDescribedArgumentsSource yourself when you want to
reuse an existing class that already encapsulates the arguments. Implementing the
interface lets you avoid rewriting your code to force it into
DescribedArgumentsByReflection.
This technique still gives you all of the benefits of the Ocean convenience functionality:
default UI’s and Workflow editor interoperability.
Schlumberger Private
Workflow 6-297