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.
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
Or submit it soon rather.
Scott O'Bryan 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
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
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
To answer Mitthias, I'm going to be testing against Pluto and Oracle's
WSRP. I *MAY* add Gridsphere to the test since it's Websphere like.
Now, Arash, you are replying to a different issue. I noticed that
Tomahawk has added support for PortletFilters and I guess I jumped the
gun on wanting
Hi scott,
my post was generally about portlet support.
you are right the second type method can be fixed by a wrapper which
implements HttpServlet and wraps Portlet.
I prefer to use a method which works in all portals JSR168, or WSRP and even
in future JSR 286, if some solution works for
Yeah, that was my origonal thought. I'll reopen MYFACES-1448 which is a
task to do just that. All we need is something simple to do the
Non-Wrapper initialization code. It would need an init and a
destroy as well as a pre-lifecycle and post-lifecycle call, but these
could be done with the
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
