Well, its kind of curious... the 2nd issue that you posted:
2). Never call your appl/portlet-name with the same name
as the url-mapping.
In fact, I was not able to see my portlet if the portlet name and
filter-mapping are differents.
Just to confirm , when you say URL Mapping do you mean...?
<filter-mapping>
<filter-name>wickportlet</filter-name>
<url-pattern>/wickportlet/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
I had to put a url-pattern equal to the portlet name, and without any
different char (like '-').
The first issue, i didn't knew nothing about it.
thanks!
Bruno Ledesma
2009/5/11 Tonio Caputo <ton...@exeo.com.ar>
> Hi Bruno,
>
> I'm a beginner in wicket, also in liferay and was able to
> use wicket to construct a portlet.
>
> My first experience was a bit tough, a lot of minor problems
> Take a look at all the things find in the internet, I was trying to
> make a simple doc with all the issues but I was not able.
>
> The 2 most important things I remember:
>
> 1). Add to your portal-ext.properties this line
> portlet.container.impl=sun
>
> 2). Never call your appl/portlet-name with the same name
> as the url-mapping.
>
> Hope this helps
> tonio
>
>
>
>
>
> On Mon, May 11, 2009 at 10:44 AM, Bruno Ledesma <led.br...@gmail.com>
> wrote:
>
> > Hello Everyone!
> >
> > Im currently developing portlets with Wicket 1.4-rc2 and liferay 5.2 .
> They
> > have some compatibility issues (portlet names must be equal the wicket
> > filter-mappings). Does anyone know anyother issues? I saw in liferay
> foruns
> > some guys that are developing portlets (in liferay) with wicket, but i
> dont
> > know if they handled compatibilty issues changing some wicket or liferay
> > code...
> >
> > If someone that did this kind of job, it would be great to have some
> > feedback!
> >
> > thanks !
> >
> > Bruno Ledesma
> >
>
