I think you can write an implementation of this interface for eXo portal
if you know a bit about its internals.. If eXo portal supports the
portlet 2.0 spec, then it should be really simple since the portal will
already have some way of generating resource urls, and you will delegate
the call to this mechanism.. AFAIK, resource URLs are important for
resource serving and wicket Ajax functionality..
Pierre Goupil wrote:
Hello again,
I did find this wiki page. Quoting it :
---
First of all, you need to make sure the portal (e.g. Liferay ) provides an
implementation of the Apache Portals Bridges
PortletResourceURLFactoryinterface, see:
PortletResourceURLFactory<http://portals.apache.org/bridges/multiproject/portals-bridges-common/xref/org/apache/portals/bridges/common/PortletResourceURLFactory.html>
---
I don't know whether this interface is fully portlet spec compliant or not,
but anyways, my portal of choice is eXo platform (in WebOS mode) and it
doesn't provide it.
I am stuck or... ?
Regards,
Pierre
On Mon, Nov 10, 2008 at 1:48 PM, Nino Saturnino Martinez Vazquez Wael <
[EMAIL PROTECTED]> wrote:
Could people who use wicket in some portal container create a wiki page and
report if it's working, working with problems or just not working?
maybe a sub page to this: http://cwiki.apache.org/WICKET/portal-howto.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
