class OclEven : OclOperationBase
{
protected override void Init()
{
InternalInit("Even", new [] {Support.IntegerType}, Support.BooleanType );
}
public override void Evaluate(IOclOperationParameters oclParameters)
{
Support.MakeNewBoolean(oclParameters.Result, (Support.GetAsInteger(oclParameters.Values[0]) & 1) == 0);
}
}

But, then this got me thinking. My model is what is dependant on this custom Ocl class, not my EcoSpace. I have 2 EcoSpaces, one for runtime that connects to a database, and one for Unit Tests that utilizes memory. Why should I have to attribute both of these classes? In a perfect OO world, I should attribute my model shouldn't I? Then, each of my EcoSpaces would pick it up because the connect to the same model.

Rick Weyrauch

BUT: When I try to prototype and test the model, I still get the errors that my custom OCL operations are unknown. Can you please check this?

My current version: 6.0.0.5648