On Wed, Nov 28, 2012 at 4:10 PM, Thijs <vonk.th...@gmail.com> wrote:

> Hi Colin,
>
> How much I hate to tell you, but your mostly on your own.
> We are currently on Wicket 1.4 for our portlets and also planning an
> upgrade to Wicket 6. But portlet support is at your own risk as non of the
> core committers is comfortable with portlets so it's no longer a core
> feature.
> Most information on the portlet stuff can be found here [1] and here[2] is
> a working but not fully tested code base for Wicket 6.
> Most of the people (that I know of) using Wicket portlet use Liferay. I
> don't know of any people using IBM portal.
>
> Hope this helps.
>
> Thijs
>
> [1] 
> https://issues.apache.org/**jira/browse/WICKET-4019<https://issues.apache.org/jira/browse/WICKET-4019>
> [2] 
> https://github.com/**matthiasgasser/wicket-portlet<https://github.com/matthiasgasser/wicket-portlet>


This is another work in progress of upgrading wicketstuff-portlet to Wicket
6 :
https://github.com/zeratul021/core/commit/0209130543de8490a4972f55164c9900d2951a28

As far as I know the developer also uses Liferay.


>
>
> On 28-11-2012 8:52, Colin Chalmers wrote:
>
>> Hello all,
>>
>> We currently have a wicket-1.5.9 application running at a client and next
>> year they want to migrate this to IBM Portal based on JSR-286.
>> I have read some mixed messages on the maillist concerning wicket support
>> for portlets and specifically the IBM Portal container so I am unsure of
>> the current status.
>>
>> Before embarking on this I'd like to verify the current portlet support
>> and
>> am interested in hearing from anyone who has experience with Wicket
>> portlets running inside the IBM Portal conatiner.
>>
>> rgds
>>
>> Colin
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> users-unsubscribe@wicket.**apache.org<users-unsubscr...@wicket.apache.org>
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>

Reply via email to