Named operations bypass any normalization done by fields

[Curtis Hovey]

When calling named operations on the web service, the IField API is only used to validate the parameter.

The IField.set() method is never called (because there is no real context to which to assign the value). When IField do normalization in the set() method, that normalization won't happen on named operation parameters.

The fix would be to create a "parameters context object" which is bound to the field and call set() to set the parameters value. And then retrieve the value to use for the underlying method calls from this parameter object.

[Curtis Hovey (sinzui)]

The create milestone form used the NoneableTextWidget to prevent meaningless code names from being created, but the field marshaller does not honour the rules, see bug 400268.

[Francis J. Lacoste (flacoste)]

It might be worthwhile to explicitely mark fields that do normalization.

Define a INormalizedField that only define a normalize(value) method. Instead of creating a fake context on which we can call the set() method to retrieve the normalized value, ResourceOperation could simply call normalize() on fields that support it, otherwise use the unmarshalled value directly.

[Robert Collins (lifeless)]

Setting the LP task to low - if / when a bug requires this in order to be fixed, it can escalate this bug, but until then we're not suffering AFAICT.