there two kind of portals
some use Servlet classes as a base for Portlet and other Portlet Classes,
and subclasses classes like PortletRequest from HttpServletRequest.
some develop Portlet classes from scratch.
lots of problems arise in second type of portlet API implementation which
the Portlet classes can not be casted to Servlet classes.
IBM websphere is from first kind.
Liferay is second type.
pluto is some thing between:
package org.apache.pluto.internal.impl;
....
public abstract class PortletRequestImpl extends HttpServletRequestWrapper
implements PortletRequest, InternalPortletRequest {
....
as you see they have subclasses HttpServletRequestWrapper
so they have all methods of HttpServlet
so I think its better that we don't test portlet patch implementation on
pluto.
On 10/10/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
Scott,
testing against Pluto (Portlet RI)?
-M
On 10/10/06, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
> I added seven issues to the Trinidad Portlet component in Jira and one
> to the MyFaces Portlet_Support component. That should get us started.
> We'll have to have MYFACES-1448, MYFACES-1383, and ADFFACES-234 done
> before we can start, however.
>
> I do have a fix for MYFACES-1383, but it needs some testing. Hopefully
> I'll be able to check it in soon.
>
> Scott
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
--
Arash Rajaeeyan
