although my vote is not counted but that's a good idea
just be aware that there are some incompatibilities between those versions.
although I don't think those effect trinidad but it is so good to upgrade
and be sure those incompatibilities will not affect trinidad
On 10/10/06, Matthias
Hello,
The navigationPane component creates a series of navigation items
representing one level in a navigation hierarchy. These items may either be
added as children or a menu model may be bound to the navigationPane
component.
Currently, on a PDA, navigationItem in a tabs , bar and button
Most of these probably result from trying to make sure Trinidad works
well with the impl;)
regards,
Martin
On 10/10/06, Arash Rajaeeyan [EMAIL PROTECTED] wrote:
although my vote is not counted but that's a good idea
just be aware that there are some incompatibilities between those versions.
114 is doing fine,
I use it since a couple of weeks now in my pom...
On 10/10/06, Martin Marinschek [EMAIL PROTECTED] wrote:
Most of these probably result from trying to make sure Trinidad works
well with the impl;)
regards,
Martin
On 10/10/06, Arash Rajaeeyan [EMAIL PROTECTED] wrote:
Scott,
Maybe Trinidad does not work completly with Portlets but it seems to
have some support. It seems to work with me.
I noticed 3 things so far:
1) org.apache.myfaces.trinidad.webapp.TrinidadFilter is not being called
so the user agent is set to null. This cause an exception and I did a
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
Is there a place where we could store public API's that are not part of
Faces in MyFaces? Would this be the shared-impl package? We'll likely
need to support an interface to handle some of our filter
functionality from a portlet. This interface would need be referenced
by the MyFaces Bridge
Hello,
The showDetail provides a means of toggling a group of components between being
disclosed or undisclosed.
On a desktop, it shows up as linked hide/show icon followed by a linked
disclosed/undisclosed Text.
If the prompt facet is present, this will be used instead of the disclosedText
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
Hi Scott,
we've had re-occuring discussions about a new commons-module. This
would probably be good candidate for this. Additionally, I've still
got to review a commit for a module by Shinsuke Sugaya, which is about
portlet compatibility - maybe it would be good to put it there.
regards,
16 matches
Mail list logo
