Correct. I mean it's crappy that we have to go through like 20 layers
of wrappers to make this thing work right. I imagine, though, that it's
going to be that way until the next Portlet Spec. Same way with Ajax.
The new Portlet spec is going to have a request type specifically for Ajax.
Arash Rajaeeyan wrote:
Hi
yes it makes sense.
you know the problem is Protlet is more limited than servlet
so some Portlet Classes (say PortletRequest) have less methods and
properties than their counter part (say HttpServlet)
so the wrapper which implements Servlet class and has wrapped a portlet
related class inside should return null or throw exception in some
special
cases.
so these wrappers behaviour is not completely same as their http servlet
counter parts.
I don't know if this functionality are used any where in trinidad or not.
as long as I find out in the codes there is no dependency on HttpServlet
classes
and in most places the JSF classes are used in trinidad.
for example in most places FacesContext is used and not ServletContext so
there is no problem in returning PortletContext in getFacesContext
