How about including package name in the generated action-path URL?
This can be
1. FQN of the package (like how it is done for the JSPs currently)
("com/acme/web/accountservices" + "/ViewStatement/ViewStatement.do")
2. the inner most package name
("/accountservices" + "/ViewStatement/ViewStatement.do".
This will provide a better namespace for the action class path URLs. We will also be able to write Filters, security constraints,etc that take advantage of the URL patterns (say /accountservices/)