Re: Wicket Portlets and Liferay

[Tonio Caputo]

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

Re: Wicket Portlets and Liferay

[Bruno Ledesma]

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-namewickportlet/filter-name
url-pattern/wickportlet/*/url-pattern
dispatcherREQUEST/dispatcher
dispatcherFORWARD/dispatcher
dispatcherINCLUDE/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
 

Re: Wicket Portlets and Liferay

[Tonio Caputo]

Bruno,

Well that is a surprise for me, this is my web file

filter-mapping
filter-namekmkApplication/filter-name
url-pattern/kmk/*/url-pattern
dispatcherREQUEST/dispatcher
dispatcherINCLUDE/dispatcher
dispatcherFORWARD/dispatcher
/filter-mapping

and my portlet file

   portlet-namekmkApplication/portlet-name
   init-param
  namewicketFilterPath/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-modeVIEW/portlet-mode
  portlet-modeEDIT/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-namewickportlet/filter-name
url-pattern/wickportlet/*/url-pattern
dispatcherREQUEST/dispatcher
dispatcherFORWARD/dispatcher
dispatcherINCLUDE/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
  
 

Re: Wicket Portlets and Liferay

[Bruno Ledesma]

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-namekmkApplication/filter-name
url-pattern/kmk/*/url-pattern
dispatcherREQUEST/dispatcher
dispatcherINCLUDE/dispatcher
dispatcherFORWARD/dispatcher
/filter-mapping

 and my portlet file

   portlet-namekmkApplication/portlet-name
   init-param
  namewicketFilterPath/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-modeVIEW/portlet-mode
  portlet-modeEDIT/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-namewickportlet/filter-name
 url-pattern/wickportlet/*/url-pattern
 dispatcherREQUEST/dispatcher
 dispatcherFORWARD/dispatcher
 dispatcherINCLUDE/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
   
  
 

Re: Wicket Portlets and Liferay

[Tonio Caputo]

Bruno,

Looking at the issue, this is the reason of the difference

*Environment: Liferay's internal portlet container
(does not happen on Sun's portlet container)

**1). Add to your portal-ext.properties this line
 portlet.container.impl=sun

*This configuration makes liferay use Sun Portlet Container, so if your are
not
configuring liferay like this, not sure what will work or what not, I always
tried my examples using this configuration.

I'm in the middle of the same problem as you, use wicket or not, well not
much to say around it, we are just beginning, and we are using wicket
and portals for the first time.

We tried these things, perhaps it can help you:

- icefaces
  Definitely not usable until liferay 5.3 is available, and no sure what
will happen then.
  Personally I don't like JSF too much after dealing with it (2/3 years
ago).

- GWT
  it works, not sure if for all portlet-containers, or just liferay ( I
think
  just for liferay, I should check with the guy that test it),
  as I remember the only important issue: not too friendly to transform
  a GWT application  to a portlet, and GWT learning curve (although I think
  in this case it worth it's value).

- GI (Tibco General Interface)
  This is an interesting option, sure it works, the learning curve is high,
the trouble
  with it: you must get stuck to their look and feel and it's pure
javascript.

- There is a liferay framework also JSP/Struts thing
  You can imagine that if I don't like JSF too much, JSP/Struts won't be one
of my
   favorites, but it is there and it works.

If you like we can share some of this things in spanish, but there is not
much more than I can say for now, just use my e-mail.

Hope it helps
PD:  We share our bad english knowlege too :)
tonio



*
*
2009/5/11 Bruno Ledesma led.br...@gmail.com

 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-namekmkApplication/filter-name
 url-pattern/kmk/*/url-pattern
 dispatcherREQUEST/dispatcher
 dispatcherINCLUDE/dispatcher
 dispatcherFORWARD/dispatcher
 /filter-mapping
 
  and my portlet file
 
portlet-namekmkApplication/portlet-name
init-param
   namewicketFilterPath/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-modeVIEW/portlet-mode
   portlet-modeEDIT/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-namewickportlet/filter-name
  url-pattern/wickportlet/*/url-pattern
  dispatcherREQUEST/dispatcher
  dispatcherFORWARD/dispatcher
  dispatcherINCLUDE/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
   
   
   
   
   

Re: Wicket Portlets in Liferay 5

[Benjamin Ernst]

Hi Thijs,

thanks for your help, but you don't have to hurry. We faked the whole thing
by running our Wicket-App inside an iFrame in Liferay. It is just for a
showcase.

So we don't need it right now.

Thanks anyway,
Benjamin

On Thu, May 15, 2008 at 9:14 PM, Thijs Vonk [EMAIL PROTECTED] wrote:

 Hi Benjamin
 I'll see if I have some time left tomorrow, otherwise hopefully before next
 tuesday.

 Thijs


 Benjamin Ernst wrote:

 Hi Thijs,

 We are currently trying to integrate Liferay 5 with wicket 1.3. Can you
 give
 us the advise you offered? That would be very nice.

 Thank you in advance,
 Benjamin

 On Mon, May 5, 2008 at 11:33 PM, Thijs Vonk [EMAIL PROTECTED] wrote:



 Hi,

 Currently without building wicket against Liferay (using
 com.liferay.portlet.renderresponseimpl, instead of
 javax.portlet.renderresponse) it is not possible to run wicket without
 losing most of wickets functionality.
 I can, if you want, give you a patch and some instructions to get wicket
 working on liferay 5, but we are still modifying wicket and Liferay code
 to
 get things working as we want it. So I can't guaranty anything.

 Thijs


 Bobby Quninne wrote:



 Hi there, I am currently considering using wicket 1.3.3(and newer) with
 liferay 5. The site is going to be used for backend administration,
 standard CRUD
 stuff. How big a risk is it, using wicket portal and liferay?
 Thanks


 Thijs wrote:




 Hi,

 I'm working on getting wicket compatible with jsr-286 now. However
 while doing this I've noticed that Liferay has still some major issues
 regarding jsr-286. Especially regarding setting properties on the
 response
 (essentially setting response headers, cookies, etc)  there is still
 some
 work to be done. They also don't support the
 MARKUP_HEAD_ELEMENT_SUPPORT
 feaure jet, what would be a really nice addition because of the CSS and
 JS
 files wicket adds to it's pages.
 Comment and vote on http://support.liferay.com/browse/LEP-5828. and
 track it to follow the property changes

  I'm also planning on opening a Wicket-jira issue so that you can
 track the progress of the wicket implementation. But we will have to
 wait at
 least until the portlet 2.0 specifications get official and added to a
 maven
 repository before we can add anything to the wicket code base. Besides
 that
 it's a lot of work and I'm doing this in my free hours so don't get
 over
 excited just jet :).

 I'll post a message on the list when I open the jira issue, and I'll
 attach patches to that issue as soon as I feel confident about the work
 I've
 been doing.

 I hope that answers your questions a bit.
 Thijs


 gaugat wrote:




 I've read in the forums, that it is better to wait for Liferay 5
 (JSR
 286) to
 develop portlets in Apache Wicket. So has anyone developed portlets
 using
 Wicket and deployed them in Liferay 5?. If you have, is there a
 sample
 wicket portlet posted somewhere that I could look at? Are there
 still
 issues
 with Wicket and Liferay?




 -
 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]









 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay 5

[Thijs Vonk]

Hi Benjamin
I'll see if I have some time left tomorrow, otherwise hopefully before 
next tuesday.


Thijs

Benjamin Ernst wrote:

Hi Thijs,

We are currently trying to integrate Liferay 5 with wicket 1.3. Can you give
us the advise you offered? That would be very nice.

Thank you in advance,
Benjamin

On Mon, May 5, 2008 at 11:33 PM, Thijs Vonk [EMAIL PROTECTED] wrote:

  

Hi,

Currently without building wicket against Liferay (using
com.liferay.portlet.renderresponseimpl, instead of
javax.portlet.renderresponse) it is not possible to run wicket without
losing most of wickets functionality.
I can, if you want, give you a patch and some instructions to get wicket
working on liferay 5, but we are still modifying wicket and Liferay code to
get things working as we want it. So I can't guaranty anything.

Thijs


Bobby Quninne wrote:



Hi there, I am currently considering using wicket 1.3.3(and newer) with
liferay 5. The site is going to be used for backend administration,
standard CRUD
stuff. How big a risk is it, using wicket portal and liferay?
Thanks


Thijs wrote:


  

Hi,

I'm working on getting wicket compatible with jsr-286 now. However
while doing this I've noticed that Liferay has still some major issues
regarding jsr-286. Especially regarding setting properties on the response
(essentially setting response headers, cookies, etc)  there is still some
work to be done. They also don't support the MARKUP_HEAD_ELEMENT_SUPPORT
feaure jet, what would be a really nice addition because of the CSS and JS
files wicket adds to it's pages.
Comment and vote on http://support.liferay.com/browse/LEP-5828. and
track it to follow the property changes

 I'm also planning on opening a Wicket-jira issue so that you can
track the progress of the wicket implementation. But we will have to wait at
least until the portlet 2.0 specifications get official and added to a maven
repository before we can add anything to the wicket code base. Besides that
it's a lot of work and I'm doing this in my free hours so don't get over
excited just jet :).

I'll post a message on the list when I open the jira issue, and I'll
attach patches to that issue as soon as I feel confident about the work I've
been doing.

I hope that answers your questions a bit.
Thijs


gaugat wrote:




I've read in the forums, that it is better to wait for Liferay 5
(JSR
286) to
develop portlets in Apache Wicket. So has anyone developed portlets
using
Wicket and deployed them in Liferay 5?. If you have, is there a
sample
wicket portlet posted somewhere that I could look at? Are there
still
issues
with Wicket and Liferay?


  

-
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]





  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay 5

[Benjamin Ernst]

Hi Thijs,

We are currently trying to integrate Liferay 5 with wicket 1.3. Can you give
us the advise you offered? That would be very nice.

Thank you in advance,
Benjamin

On Mon, May 5, 2008 at 11:33 PM, Thijs Vonk [EMAIL PROTECTED] wrote:

 Hi,

 Currently without building wicket against Liferay (using
 com.liferay.portlet.renderresponseimpl, instead of
 javax.portlet.renderresponse) it is not possible to run wicket without
 losing most of wickets functionality.
 I can, if you want, give you a patch and some instructions to get wicket
 working on liferay 5, but we are still modifying wicket and Liferay code to
 get things working as we want it. So I can't guaranty anything.

 Thijs


 Bobby Quninne wrote:

  Hi there, I am currently considering using wicket 1.3.3(and newer) with
  liferay 5. The site is going to be used for backend administration,
  standard CRUD
  stuff. How big a risk is it, using wicket portal and liferay?
  Thanks
 
 
  Thijs wrote:
 
 
   Hi,
  
   I'm working on getting wicket compatible with jsr-286 now. However
   while doing this I've noticed that Liferay has still some major issues
   regarding jsr-286. Especially regarding setting properties on the response
   (essentially setting response headers, cookies, etc)  there is still some
   work to be done. They also don't support the MARKUP_HEAD_ELEMENT_SUPPORT
   feaure jet, what would be a really nice addition because of the CSS and JS
   files wicket adds to it's pages.
   Comment and vote on http://support.liferay.com/browse/LEP-5828. and
   track it to follow the property changes
  
I'm also planning on opening a Wicket-jira issue so that you can
   track the progress of the wicket implementation. But we will have to wait 
   at
   least until the portlet 2.0 specifications get official and added to a 
   maven
   repository before we can add anything to the wicket code base. Besides 
   that
   it's a lot of work and I'm doing this in my free hours so don't get over
   excited just jet :).
  
   I'll post a message on the list when I open the jira issue, and I'll
   attach patches to that issue as soon as I feel confident about the work 
   I've
   been doing.
  
   I hope that answers your questions a bit.
   Thijs
  
  
   gaugat wrote:
  
  
I've read in the forums, that it is better to wait for Liferay 5
(JSR
286) to
develop portlets in Apache Wicket. So has anyone developed portlets
using
Wicket and deployed them in Liferay 5?. If you have, is there a
sample
wicket portlet posted somewhere that I could look at? Are there
still
issues
with Wicket and Liferay?
   
   
   -
   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]

Re: Wicket Portlets in Liferay 5

[Bobby Quninne]

You have a rough guess estimate as to a wicket release that will address
JSR-268 compliance? 

Many thanks


Thijs wrote:
 
 Hi,
 
 Currently without building wicket against Liferay (using 
 com.liferay.portlet.renderresponseimpl, instead of 
 javax.portlet.renderresponse) it is not possible to run wicket without 
 losing most of wickets functionality.
 I can, if you want, give you a patch and some instructions to get wicket 
 working on liferay 5, but we are still modifying wicket and Liferay code 
 to get things working as we want it. So I can't guaranty anything.
 
 Thijs
 
 Bobby Quninne wrote:
 Hi there, I am currently considering using wicket 1.3.3(and newer) with
 liferay 5. 
 The site is going to be used for backend administration, standard CRUD
 stuff. 
 How big a risk is it, using wicket portal and liferay? 

 Thanks


 Thijs wrote:
   
 Hi,

 I'm working on getting wicket compatible with jsr-286 now. However while 
 doing this I've noticed that Liferay has still some major issues 
 regarding jsr-286. Especially regarding setting properties on the 
 response (essentially setting response headers, cookies, etc)  there is 
 still some work to be done. They also don't support the 
 MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice 
 addition because of the CSS and JS files wicket adds to it's pages.
 Comment and vote on http://support.liferay.com/browse/LEP-5828. and 
 track it to follow the property changes

  I'm also planning on opening a Wicket-jira issue so that you can track 
 the progress of the wicket implementation. But we will have to wait at 
 least until the portlet 2.0 specifications get official and added to a 
 maven repository before we can add anything to the wicket code base. 
 Besides that it's a lot of work and I'm doing this in my free hours so 
 don't get over excited just jet :).

 I'll post a message on the list when I open the jira issue, and I'll 
 attach patches to that issue as soon as I feel confident about the work 
 I've been doing.

 I hope that answers your questions a bit.
 Thijs

  

 gaugat wrote:
 
 I've read in the forums, that it is better to wait for Liferay 5 (JSR
 286) to
 develop portlets in Apache Wicket. So has anyone developed portlets
 using
 Wicket and deployed them in Liferay 5?. If you have, is there a sample
 wicket portlet posted somewhere that I could look at? Are there still
 issues
 with Wicket and Liferay?
   
   
 -
 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]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Wicket-Portlets-in-Liferay-5-tp16995052p17077583.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay 5

[Thijs]

No, as described it depends on several factors
1. my/other people's time to commit to this
2. official release of the portlet 2 specifications

Thijs

Bobby Quninne schreef:

You have a rough guess estimate as to a wicket release that will address
JSR-268 compliance? 


Many thanks


Thijs wrote:
  

Hi,

Currently without building wicket against Liferay (using 
com.liferay.portlet.renderresponseimpl, instead of 
javax.portlet.renderresponse) it is not possible to run wicket without 
losing most of wickets functionality.
I can, if you want, give you a patch and some instructions to get wicket 
working on liferay 5, but we are still modifying wicket and Liferay code 
to get things working as we want it. So I can't guaranty anything.


Thijs

Bobby Quninne wrote:


Hi there, I am currently considering using wicket 1.3.3(and newer) with
liferay 5. 
The site is going to be used for backend administration, standard CRUD
stuff. 
How big a risk is it, using wicket portal and liferay? 


Thanks


Thijs wrote:
  
  

Hi,

I'm working on getting wicket compatible with jsr-286 now. However while 
doing this I've noticed that Liferay has still some major issues 
regarding jsr-286. Especially regarding setting properties on the 
response (essentially setting response headers, cookies, etc)  there is 
still some work to be done. They also don't support the 
MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice 
addition because of the CSS and JS files wicket adds to it's pages.
Comment and vote on http://support.liferay.com/browse/LEP-5828. and 
track it to follow the property changes


 I'm also planning on opening a Wicket-jira issue so that you can track 
the progress of the wicket implementation. But we will have to wait at 
least until the portlet 2.0 specifications get official and added to a 
maven repository before we can add anything to the wicket code base. 
Besides that it's a lot of work and I'm doing this in my free hours so 
don't get over excited just jet :).


I'll post a message on the list when I open the jira issue, and I'll 
attach patches to that issue as soon as I feel confident about the work 
I've been doing.


I hope that answers your questions a bit.
Thijs

 


gaugat wrote:



I've read in the forums, that it is better to wait for Liferay 5 (JSR
286) to
develop portlets in Apache Wicket. So has anyone developed portlets
using
Wicket and deployed them in Liferay 5?. If you have, is there a sample
wicket portlet posted somewhere that I could look at? Are there still
issues
with Wicket and Liferay?
  
  
  

-
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]






  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay 5

[Bobby Quninne]

Are JSR-168 portlets also affected by this? 

If so, is there a version of wicket and liferay that are compatible?

Many thanks Thijs :-)


Thijs wrote:
 
 No, as described it depends on several factors
 1. my/other people's time to commit to this
 2. official release of the portlet 2 specifications
 
 Thijs
 
 Bobby Quninne schreef:
 You have a rough guess estimate as to a wicket release that will address
 JSR-268 compliance? 

 Many thanks


 Thijs wrote:
   
 Hi,

 Currently without building wicket against Liferay (using 
 com.liferay.portlet.renderresponseimpl, instead of 
 javax.portlet.renderresponse) it is not possible to run wicket without 
 losing most of wickets functionality.
 I can, if you want, give you a patch and some instructions to get wicket 
 working on liferay 5, but we are still modifying wicket and Liferay code 
 to get things working as we want it. So I can't guaranty anything.

 Thijs

 Bobby Quninne wrote:
 
 Hi there, I am currently considering using wicket 1.3.3(and newer) with
 liferay 5. 
 The site is going to be used for backend administration, standard CRUD
 stuff. 
 How big a risk is it, using wicket portal and liferay? 

 Thanks


 Thijs wrote:
   
   
 Hi,

 I'm working on getting wicket compatible with jsr-286 now. However
 while 
 doing this I've noticed that Liferay has still some major issues 
 regarding jsr-286. Especially regarding setting properties on the 
 response (essentially setting response headers, cookies, etc)  there
 is 
 still some work to be done. They also don't support the 
 MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice 
 addition because of the CSS and JS files wicket adds to it's pages.
 Comment and vote on http://support.liferay.com/browse/LEP-5828. and 
 track it to follow the property changes

  I'm also planning on opening a Wicket-jira issue so that you can
 track 
 the progress of the wicket implementation. But we will have to wait at 
 least until the portlet 2.0 specifications get official and added to a 
 maven repository before we can add anything to the wicket code base. 
 Besides that it's a lot of work and I'm doing this in my free hours so 
 don't get over excited just jet :).

 I'll post a message on the list when I open the jira issue, and I'll 
 attach patches to that issue as soon as I feel confident about the
 work 
 I've been doing.

 I hope that answers your questions a bit.
 Thijs

  

 gaugat wrote:
 
 
 I've read in the forums, that it is better to wait for Liferay 5 (JSR
 286) to
 develop portlets in Apache Wicket. So has anyone developed portlets
 using
 Wicket and deployed them in Liferay 5?. If you have, is there a
 sample
 wicket portlet posted somewhere that I could look at? Are there still
 issues
 with Wicket and Liferay?
   
   
   
 -
 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]



 

   
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Wicket-Portlets-in-Liferay-5-tp16995052p17078122.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay 5

[Thijs]

Bobby Quninne schreef:
Are JSR-168 portlets also affected by this? 
  
Not sure what you are asking. The current JSR-168 implementation in 
wicket is pretty much final, and for wicket 1.3.x will probably not 
change. However newer versions of wicket probably will not be backwards 
compatible, with JSR 168, but I don't know for sure...

If so, is there a version of wicket and liferay that are compatible?
  
As described below. An out of the box wicket version will NOT work on 
any version of Liferay. So there is no Wicket version that is compatible.
If you are willing to work with a patched version of wicket, then you 
can work with wicket 1.3.3 and LF5(as we are)



Thijs

Many thanks Thijs :-)


Thijs wrote:
  

No, as described it depends on several factors
1. my/other people's time to commit to this
2. official release of the portlet 2 specifications

Thijs

Bobby Quninne schreef:


You have a rough guess estimate as to a wicket release that will address
JSR-268 compliance? 


Many thanks


Thijs wrote:
  
  

Hi,

Currently without building wicket against Liferay (using 
com.liferay.portlet.renderresponseimpl, instead of 
javax.portlet.renderresponse) it is not possible to run wicket without 
losing most of wickets functionality.
I can, if you want, give you a patch and some instructions to get wicket 
working on liferay 5, but we are still modifying wicket and Liferay code 
to get things working as we want it. So I can't guaranty anything.


Thijs

Bobby Quninne wrote:



Hi there, I am currently considering using wicket 1.3.3(and newer) with
liferay 5. 
The site is going to be used for backend administration, standard CRUD
stuff. 
How big a risk is it, using wicket portal and liferay? 


Thanks


Thijs wrote:
  
  
  

Hi,

I'm working on getting wicket compatible with jsr-286 now. However
while 
doing this I've noticed that Liferay has still some major issues 
regarding jsr-286. Especially regarding setting properties on the 
response (essentially setting response headers, cookies, etc)  there
is 
still some work to be done. They also don't support the 
MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice 
addition because of the CSS and JS files wicket adds to it's pages.
Comment and vote on http://support.liferay.com/browse/LEP-5828. and 
track it to follow the property changes


 I'm also planning on opening a Wicket-jira issue so that you can
track 
the progress of the wicket implementation. But we will have to wait at 
least until the portlet 2.0 specifications get official and added to a 
maven repository before we can add anything to the wicket code base. 
Besides that it's a lot of work and I'm doing this in my free hours so 
don't get over excited just jet :).


I'll post a message on the list when I open the jira issue, and I'll 
attach patches to that issue as soon as I feel confident about the
work 
I've been doing.


I hope that answers your questions a bit.
Thijs

 


gaugat wrote:




I've read in the forums, that it is better to wait for Liferay 5 (JSR
286) to
develop portlets in Apache Wicket. So has anyone developed portlets
using
Wicket and deployed them in Liferay 5?. If you have, is there a
sample
wicket portlet posted somewhere that I could look at? Are there still
issues
with Wicket and Liferay?
  
  
  
  

-
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]





  
  

-
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]

Re: Wicket Portlets in Liferay 5

[Bobby Quinne]

Thank you very much for the prompt responses Thijs.
Will have to consider another framework for portlet development, 
at least until wicket-crew wrap up integration. 

Keep up the brilliant work!


Thijs wrote:
 
 Bobby Quninne schreef:
 Are JSR-168 portlets also affected by this? 
   
 Not sure what you are asking. The current JSR-168 implementation in 
 wicket is pretty much final, and for wicket 1.3.x will probably not 
 change. However newer versions of wicket probably will not be backwards 
 compatible, with JSR 168, but I don't know for sure...
 If so, is there a version of wicket and liferay that are compatible?
   
 As described below. An out of the box wicket version will NOT work on 
 any version of Liferay. So there is no Wicket version that is compatible.
 If you are willing to work with a patched version of wicket, then you 
 can work with wicket 1.3.3 and LF5(as we are)
 
 
 Thijs
 Many thanks Thijs :-)


 Thijs wrote:
   
 No, as described it depends on several factors
 1. my/other people's time to commit to this
 2. official release of the portlet 2 specifications

 Thijs

 Bobby Quninne schreef:
 
 You have a rough guess estimate as to a wicket release that will
 address
 JSR-268 compliance? 

 Many thanks


 Thijs wrote:
   
   
 Hi,

 Currently without building wicket against Liferay (using 
 com.liferay.portlet.renderresponseimpl, instead of 
 javax.portlet.renderresponse) it is not possible to run wicket without 
 losing most of wickets functionality.
 I can, if you want, give you a patch and some instructions to get
 wicket 
 working on liferay 5, but we are still modifying wicket and Liferay
 code 
 to get things working as we want it. So I can't guaranty anything.

 Thijs

 Bobby Quninne wrote:
 
 
 Hi there, I am currently considering using wicket 1.3.3(and newer)
 with
 liferay 5. 
 The site is going to be used for backend administration, standard
 CRUD
 stuff. 
 How big a risk is it, using wicket portal and liferay? 

 Thanks


 Thijs wrote:
   
   
   
 Hi,

 I'm working on getting wicket compatible with jsr-286 now. However
 while 
 doing this I've noticed that Liferay has still some major issues 
 regarding jsr-286. Especially regarding setting properties on the 
 response (essentially setting response headers, cookies, etc)  there
 is 
 still some work to be done. They also don't support the 
 MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice 
 addition because of the CSS and JS files wicket adds to it's pages.
 Comment and vote on http://support.liferay.com/browse/LEP-5828. and 
 track it to follow the property changes

  I'm also planning on opening a Wicket-jira issue so that you can
 track 
 the progress of the wicket implementation. But we will have to wait
 at 
 least until the portlet 2.0 specifications get official and added to
 a 
 maven repository before we can add anything to the wicket code base. 
 Besides that it's a lot of work and I'm doing this in my free hours
 so 
 don't get over excited just jet :).

 I'll post a message on the list when I open the jira issue, and I'll 
 attach patches to that issue as soon as I feel confident about the
 work 
 I've been doing.

 I hope that answers your questions a bit.
 Thijs

  

 gaugat wrote:
 
 
 
 I've read in the forums, that it is better to wait for Liferay 5
 (JSR
 286) to
 develop portlets in Apache Wicket. So has anyone developed portlets
 using
 Wicket and deployed them in Liferay 5?. If you have, is there a
 sample
 wicket portlet posted somewhere that I could look at? Are there
 still
 issues
 with Wicket and Liferay?
   
   
   
   
 -
 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]



 
 
   
   
 -
 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]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Wicket-Portlets-in-Liferay-5-tp16995052p17078837.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay 5

[Bobby Quninne]

Hi there, I am currently considering using wicket 1.3.3(and newer) with
liferay 5. 
The site is going to be used for backend administration, standard CRUD
stuff. 
How big a risk is it, using wicket portal and liferay? 

Thanks


Thijs wrote:
 
 Hi,
 
 I'm working on getting wicket compatible with jsr-286 now. However while 
 doing this I've noticed that Liferay has still some major issues 
 regarding jsr-286. Especially regarding setting properties on the 
 response (essentially setting response headers, cookies, etc)  there is 
 still some work to be done. They also don't support the 
 MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice 
 addition because of the CSS and JS files wicket adds to it's pages.
 Comment and vote on http://support.liferay.com/browse/LEP-5828. and 
 track it to follow the property changes
 
  I'm also planning on opening a Wicket-jira issue so that you can track 
 the progress of the wicket implementation. But we will have to wait at 
 least until the portlet 2.0 specifications get official and added to a 
 maven repository before we can add anything to the wicket code base. 
 Besides that it's a lot of work and I'm doing this in my free hours so 
 don't get over excited just jet :).
 
 I'll post a message on the list when I open the jira issue, and I'll 
 attach patches to that issue as soon as I feel confident about the work 
 I've been doing.
 
 I hope that answers your questions a bit.
 Thijs
 
  
 
 gaugat wrote:
 I've read in the forums, that it is better to wait for Liferay 5 (JSR
 286) to
 develop portlets in Apache Wicket. So has anyone developed portlets using
 Wicket and deployed them in Liferay 5?. If you have, is there a sample
 wicket portlet posted somewhere that I could look at? Are there still
 issues
 with Wicket and Liferay?
   
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Wicket-Portlets-in-Liferay-5-tp16995052p17061496.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay 5

[Thijs Vonk]

Hi,

I'm working on getting wicket compatible with jsr-286 now. However while 
doing this I've noticed that Liferay has still some major issues 
regarding jsr-286. Especially regarding setting properties on the 
response (essentially setting response headers, cookies, etc)  there is 
still some work to be done. They also don't support the 
MARKUP_HEAD_ELEMENT_SUPPORT feaure jet, what would be a really nice 
addition because of the CSS and JS files wicket adds to it's pages.
Comment and vote on http://support.liferay.com/browse/LEP-5828. and 
track it to follow the property changes


I'm also planning on opening a Wicket-jira issue so that you can track 
the progress of the wicket implementation. But we will have to wait at 
least until the portlet 2.0 specifications get official and added to a 
maven repository before we can add anything to the wicket code base. 
Besides that it's a lot of work and I'm doing this in my free hours so 
don't get over excited just jet :).


I'll post a message on the list when I open the jira issue, and I'll 
attach patches to that issue as soon as I feel confident about the work 
I've been doing.


I hope that answers your questions a bit.
Thijs



gaugat wrote:

I've read in the forums, that it is better to wait for Liferay 5 (JSR 286) to
develop portlets in Apache Wicket. So has anyone developed portlets using
Wicket and deployed them in Liferay 5?. If you have, is there a sample
wicket portlet posted somewhere that I could look at? Are there still issues
with Wicket and Liferay?
  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay

[Ate Douma]

Thijs wrote:

I'm trying to get wicket portlets to work in Liferay.

As fas as I can tell there are at least 2 issues at the moment:
1.) A nullpointer exception in WebResponse due to an issue in de Liferay
code that returns null in the encodeRedirectUrl (see
http://www.liferay.com/web/guest/community/forums/message_boards/message/249501
)

To answer a question on the liferay forum I need to know why the
encodeRedirectUrl is called. I think this is because of the
REDIRECT_TO_RENDER setting done by the WicketFilterPortletContext. But can
somebody confirm that?!

Hi Thijs,

I've looked a bit deeper into this issue and it turned out that this is (or 
was) a JSR-168 conformance problem indeed.
On Jetspeed-2 this didn't really cause any problems as we are more relaxed on this specific issue (in the end, redirects during rendering are not and will not 
ever be possible so allowing encoding doesn't hurt either).

But clearly this needed to be resolved independently of Jetspeed, so I've 
created a new issue, https://issues.apache.org/jira/browse/WICKET-1155, as well 
as
already resolved it :)
Please do check if this now works for you too.




2.) https://issues.apache.org/jira/browse/WICKET-1132
I have no clue what causes this issue or where to look. Can somebody give me
a push in the right direction? 

For this one, I really don't have a clue.
You'll probably need a Liferay expert here as this goes into the internal url 
handling of the Liferay portlet container and is beyond Wicket itself.

Regards,

Ate








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket Portlets in Liferay

[Thijs]

Ate,  your the man :)

I'll try to dive into the parameter problem this week.

Thnx

Thijs

Ate Douma wrote:

Thijs wrote:

I'm trying to get wicket portlets to work in Liferay.

As fas as I can tell there are at least 2 issues at the moment:
1.) A nullpointer exception in WebResponse due to an issue in de Liferay
code that returns null in the encodeRedirectUrl (see
http://www.liferay.com/web/guest/community/forums/message_boards/message/249501 


)

To answer a question on the liferay forum I need to know why the
encodeRedirectUrl is called. I think this is because of the
REDIRECT_TO_RENDER setting done by the WicketFilterPortletContext. 
But can

somebody confirm that?!

Hi Thijs,

I've looked a bit deeper into this issue and it turned out that this 
is (or was) a JSR-168 conformance problem indeed.
On Jetspeed-2 this didn't really cause any problems as we are more 
relaxed on this specific issue (in the end, redirects during rendering 
are not and will not ever be possible so allowing encoding doesn't 
hurt either).
But clearly this needed to be resolved independently of Jetspeed, so 
I've created a new issue, 
https://issues.apache.org/jira/browse/WICKET-1155, as well as

already resolved it :)
Please do check if this now works for you too.




2.) https://issues.apache.org/jira/browse/WICKET-1132
I have no clue what causes this issue or where to look. Can somebody 
give me
a push in the right direction? 

For this one, I really don't have a clue.
You'll probably need a Liferay expert here as this goes into the 
internal url handling of the Liferay portlet container and is beyond 
Wicket itself.


Regards,

Ate








-
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]

Re: Wicket portlets on LIferay

[Miso]

Thx for help, but this doesn't sort it out.

A tried:

code
...
protected void init() {

getRequestCycleSettings().setRenderStrategy(IRequestCycleSettings.ONE_PASS_RENDER);
super.init();
   }
...
/code

and also

code
...
protected void init() {
super.init();

getRequestCycleSettings().setRenderStrategy(IRequestCycleSettings.ONE_PASS_RENDER);
   }
...
/code

Any idea?

Miso
-- 
View this message in context: 
http://www.nabble.com/Wicket-portlets-on-LIferay-tf4231110.html#a12047909
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket portlets on LIferay

[Martijn Dashorst]

Now you are outside my area of expertise :-). I hope that Ate or Janne
is reading this.

Martijn

On 8/8/07, Miso [EMAIL PROTECTED] wrote:

 Thx for help, but this doesn't sort it out.

 A tried:

 code
 ...
 protected void init() {

 getRequestCycleSettings().setRenderStrategy(IRequestCycleSettings.ONE_PASS_RENDER);
 super.init();
}
 ...
 /code

 and also

 code
 ...
 protected void init() {
 super.init();

 getRequestCycleSettings().setRenderStrategy(IRequestCycleSettings.ONE_PASS_RENDER);
}
 ...
 /code

 Any idea?

 Miso
 --
 View this message in context: 
 http://www.nabble.com/Wicket-portlets-on-LIferay-tf4231110.html#a12047909
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Wicket joins the Apache Software Foundation as Apache Wicket
Apache Wicket 1.3.0-beta2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket portlets on LIferay

[Martijn Dashorst]

Also, make sure you are using the code from the experimental portlet
branch, as that is the only part where the portlet support is built
into (seeing you are using wicket 1.3 based code).

Martijn

On 8/8/07, Miso [EMAIL PROTECTED] wrote:

 Thx for help, but this doesn't sort it out.

 A tried:

 code
 ...
 protected void init() {

 getRequestCycleSettings().setRenderStrategy(IRequestCycleSettings.ONE_PASS_RENDER);
 super.init();
}
 ...
 /code

 and also

 code
 ...
 protected void init() {
 super.init();

 getRequestCycleSettings().setRenderStrategy(IRequestCycleSettings.ONE_PASS_RENDER);
}
 ...
 /code

 Any idea?

 Miso
 --
 View this message in context: 
 http://www.nabble.com/Wicket-portlets-on-LIferay-tf4231110.html#a12047909
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Wicket joins the Apache Software Foundation as Apache Wicket
Apache Wicket 1.3.0-beta2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket portlets on LIferay

[Miso]

Yes, I'm using this experimental portlet branch.
-- 
View this message in context: 
http://www.nabble.com/Wicket-portlets-on-LIferay-tf4231110.html#a12051724
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket portlets on LIferay

[Miso]

Me too :)
-- 
View this message in context: 
http://www.nabble.com/Wicket-portlets-on-LIferay-tf4231110.html#a12051726
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]