afaik 1.4 snapshots should have native portlet 2.0 support.

-igor

On Wed, Mar 4, 2009 at 6:58 AM, Wilhelmsen Tor Iver <[email protected]> wrote:
>> (using Netbeans, wicket 1.4rc2, glassfish v3,
>> portlet-container from open-portal project)
>
> I thought the portlet-container in effect was dead since the Sun Portal
> is dead? They have ditched that in favor of a solution based on Liferay
> 5.2 called Web Space (codename WebSynergy during development):
> https://webspace.dev.java.net/download.html - note that it uses
> Glassfish v2.1 in case you require features from v3.
>
> Around here we use a patched snapshot of 1.4 (using an adapted version
> of the older portlet 2.0 patch) for Wicket portlets. (Or have I been
> sleeping and we get "real" Portlet 2.0 "out of the box" in 1.4 now?)
>
> I noticed some differences between what we do (which works :) ) and what
> you posted:
>
> 1) In web.xml we have a filter mapping for each portlet:
>
>        <filter-mapping>
>                <filter-name>bookmark</filter-name>
>                <url-pattern>/basic/*</url-pattern>
>                <dispatcher>REQUEST</dispatcher>
>                <dispatcher>INCLUDE</dispatcher>
>                <dispatcher>FORWARD</dispatcher>
>                <dispatcher>ERROR</dispatcher>
>        </filter-mapping>
>
> 2) We also declare the application in the filter element:
>
>                <init-param>
>                        <param-name>applicationClassName</param-name>
>
> <param-value>no.nsb.intranet.bookmark.wicket.BookmarkApplication
>                        </param-value>
>                </init-param>
>
> 3) You also seem to be missing an init-parameter for viewPage, in our
> case e.g.
>
>                <init-param>
>                        <name>wicketFilterPath</name>
>                        <value>/basic</value>
>                </init-param>
>                <init-param>
>                        <name>viewPage</name>
>                        <value>/basic/list</value>
>                </init-param>
>
>   though in theory it should use the application's getHomePage(), I
> guess...
>
> 4) We do not have anything in sun-web.xml, though I guess we would
> benefit from a shared classloader with Web Space.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to