Tonio,

what are the wicket/liferay versions that you are using?

My problem with filtermapping and porltet names are currently registered in
liferay's JIRA

You can take a look at:
http://issues.liferay.com/browse/LPS-1911

But anyway, its working :) !

My fear right now is about using all wicket's features as a portlet. I need
to know if there is any real world case of wicket apps as portlets. If there
is, if uses a wide range of wicket's components and features... Knowing
that, i'ĺl fell more safe to use wicket as my standard framework for
portlets development in Liferay 5 (5.2).

(sorry for the bad english :))

thanks !

Bruno



2009/5/11 Tonio Caputo <ton...@exeo.com.ar>

> Bruno,
>
> Well that is a surprise for me, this is my web file
>
>    <filter-mapping>
>        <filter-name>kmkApplication</filter-name>
>        <url-pattern>/kmk/*</url-pattern>
>        <dispatcher>REQUEST</dispatcher>
>        <dispatcher>INCLUDE</dispatcher>
>        <dispatcher>FORWARD</dispatcher>
>    </filter-mapping>
>
> and my portlet file
>
>   <portlet-name>kmkApplication</portlet-name>
>   <init-param>
>      <name>wicketFilterPath</name>
>      <value>/kmk</value>
>    </init-param>
>    <supports>
>
> and it works pretty well :)
>
> I remember another thing, while I was pasting this XML don't use
> * for the *supports* tag, I begin writting something like
>   <supports>
>      <mime-type>*/*</mime-type>
>      <portlet-mode>VIEW</portlet-mode>
>      <portlet-mode>EDIT</portlet-mode>
>    </supports>
>
> and finally need to put at least two items with mime-types *"text/html"*
> and
> *"text/xml"*
> if not it won't work.
>
> The important thing is just to get it working, hope it helps
> tonio
>
>
>
> On Mon, May 11, 2009 at 11:57 AM, Bruno Ledesma <led.br...@gmail.com>
> wrote:
>
> > 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
> > > >
> > >
> >
>

Reply via email to