After having a closer look at the code I can say it’s not a bug or typo, and exceptions I had resulted from fully rewritten url-building code. In my case web-users have to switch often between ssl and non-ssl pages so I have to swap <preetyLink id="..."/> and <a href="pretty builded url"/> when showing cross-protocol links. PF 2.x builder engine inteface accepted Object as url path params, PF 3.x – Map<String, String>, so I’ve adopted my code accordingly, providing arbitrary non-null map keys for path params. As I can see now, in 3.x I must use null map keys for path params and non-null keys for query params. Otherwise 'Invalid number of parameters ...' is raised.
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.