about SecuredServlet in tempo ui-fw and portlet

[jgilc]

Hello everybody,
I wish to know if I am wrong guessing that SecuredServlet tries to
resemble a spring mvc MultiActionController for porlet purposes? then
why for the portlet solution the idea was abandoned using instead the
jsonupdate servlet?
By the way, in the comments header of the jsonupdate there is
$Id: TaskManagementServicesFacade.java
wouldn't it be nice if there were a Service Facade for all task
related operations instead of having to deal with all inner workings:
TMS, TMP, etc in order to facilitate multi UI task management app
development? what is not the same with having tempo services ready for
integration with and established UI like some CRM app or another human-
centric management app.
Looking tempo code at tms-client project, it seems to me that somebody
tried to facilitate tests doing a facade for TMS client and TMP
services named TempoClient class.
My first approach was something like TempoClient but looking at
SecuredServlet as multiaction servlet and portlet controller I am
trying to guess what would be the better solution: a whole task action
helper class (Task Operations' Facade) or some action classes along
its corresponding views?
I'll be glad to collaborate but I need some insight.
Thank you in advance,
and Best Regards,
Gil.