This could be fixed either by changing the implementation so it does check those values, or by changing the spec so that it no longer says they are invalid. This bug was originally reported against the MX4J implementation, which did make the validity checks: apparently they caused some existing software to fail there. So the safest choice would seem to be to change the spec. For example, it could say:
"The persistPolicy and currencyTimeLimit fields are meaningless for constructors, but are not considered invalid."
###@###.### 2005-03-07 09:46:20 GMT