Hi, I am just porting my application to turbine-2.2-b1 using the decoupled torque. Using RunData.getParameters.setProperties(...) leads to an exception when one of the screen members is of type NumberKey. This happens because ParameterParser.setProperties tries to work on o.a.turbine.om.NumberKey and not on o.a.torque.om.NumberKey.
I think this is because the security system is still using the torque implementation coupled with turbine and not the decoupled version. (so it works fine with flux). What about in the future: Will setProperties be usable in future versions of torque or does it become deprecated ? Does a work around exist ? Uwe -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
