The calling order of Signature.initSign()/initVerify() and setParameter() order may be restricted by the underlying provider. Some provider need to call setParameter() first, some other need to call initSign()/initVerify(). An application may have to switch between the two modes in order to work with them both.

It would be nice to have an enhancement that the methods could be called in any order. The compatibility could be an issue. In the long term, alternatively, deprecating the methods and combining the configuration methods into one method might be a solution.