Thijs Vonk wrote:
Ate Douma wrote:
Thanks to both of you!
Note though that you have to build a svn copy of the
portlet-container.
RC2 contains a bug I found which prevents Ajax to work correctly.
Will try that.
-
To
Got it to work after building portlet-bridges-common from the trunk
source.
- The change I made to PortletWindowUtils which seems to work (so far
*crosses fingers*):
public static String getPortletWindowId(PortletSession session)
{
final Object tmp =
To dig up this old thread:
I now use Ate Douma's patch for JSR-286 support from
https://issues.apache.org/jira/browse/WICKET-1620 which has removed the
need for the portal to implement the Apache portlet bridge's two
interfaces. A small step for man etc. :)
There now is an issue - the same I had
Wilhelmsen Tor Iver wrote:
To dig up this old thread:
I now use Ate Douma's patch for JSR-286 support from
https://issues.apache.org/jira/browse/WICKET-1620 which has removed the
need for the portal to implement the Apache portlet bridge's two
interfaces. A small step for man etc. :)
Well,
Ate Douma wrote:
Wilhelmsen Tor Iver wrote:
To dig up this old thread:
I now use Ate Douma's patch for JSR-286 support from
https://issues.apache.org/jira/browse/WICKET-1620 which has removed the
need for the portal to implement the Apache portlet bridge's two
interfaces. A small step for man
For b) I hope to get started on that ASAP.
Excellent news! :)
(Since this is so significant for us I might have a go at adding the
support later this week if I can wrap my head around the source and API
docs... testing for the presence of the Portlet 2.0 API as you mentioned
is probably the
I don't know the Sun Portal that well, but AFAIK they have (or are working on) beta Portlet API 2.0 (JSR-286) support
already.
As the interfaces which Wicket Portlet currently needs from Apache Portals Bridges Common are natively supported with
JSR-286, the easiest solution is:
a) waiting for
We have (wisely :) ) chosen Wicket as web framework, but also chosen Sun
Portal as the portal engine (not just Pluto but the commercial product).
This causes a problem since Sun apparently haven't implemented the two
interfaces required by Apache's bridge, so Wicket 1.3.x portlets do not
work
Liferay is not really supported, We have it running but have hacked
wicket to do so (in a combindation of a bridges implementation and a
custom wicket version). Especially to get the Ajax stuff working correctly.
We are hoping that with portlet 2.0 supported both by Liferay and wicket
that the
