Actually, when using paged tags any required parameter must be added by hand, reconstructing the source URL:

@Path("/{foo}/{bar}")
public Resolution myEvent() {
...
}

<l:pagedList param-foo="${action.foo}" param-bar="${action.bar}">
...
</l:pagedList>

In its current implementation, the paged tag will complain if any required parameter is missing. Instead, they should be added automatically with the current value found in the request object. If there is any need to NOT add these values automatically, an attribute addUriParams=false should be used.

NOTE: THIS IS A CHANGE IN BEHAVIOR. It is extremely unlikely that this breaks any existing code, but existing tags may have already specified the value and end up with the same parameter/value may be added twice. Other than that, it should not have any downside.