You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Johannes Geppert <jo...@web.de> on 2011/01/27 07:52:41 UTC

portlet2 plugin

Hi,

is there any chance to get the portlet2 plugin out of the sandbox?
I use this sandbox plugin and it works great except the eventing.

Johannes

-----
---
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep

-- 
View this message in context: http://old.nabble.com/portlet2-plugin-tp30774658p30774658.html
Sent from the Struts - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Johannes Geppert <jo...@web.de>.
solved.

https://issues.apache.org/jira/browse/WW-3566

Johannes


Lukasz Lenart wrote:
> 
> 2011/1/27 Johannes Geppert <jo...@web.de>:
>> I agree to René the portlet2 version brings advantages to the developer
>> and i think it is production ready. I work with it since over an year
>> without trouble.
>>
>> When the events feature is marked as known TODO this plugin is ready for
>> shipping out in next struts2 version.
> 
> Could you register an issue to not forget?
> 
> 
> Kind regards
> -- 
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
> Kapituła Javarsovia http://javarsovia.pl
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
> 
> 
> 


-----
---
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep

-- 
View this message in context: http://old.nabble.com/portlet2-plugin-tp30774658p30775781.html
Sent from the Struts - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Lukasz Lenart <lu...@googlemail.com>.
2011/1/27 Johannes Geppert <jo...@web.de>:
> I agree to René the portlet2 version brings advantages to the developer
> and i think it is production ready. I work with it since over an year
> without trouble.
>
> When the events feature is marked as known TODO this plugin is ready for
> shipping out in next struts2 version.

Could you register an issue to not forget?


Kind regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia http://javarsovia.pl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Johannes Geppert <jo...@web.de>.
I agree to René the portlet2 version brings advantages to the developer
and i think it is production ready. I work with it since over an year
without trouble.

When the events feature is marked as known TODO this plugin is ready for
shipping out in next struts2 version.

Johannes


Rene Gielen wrote:
> 
> Actual state:
> - JSR286 nature with automatic detection of the API version to use is
> implemented, but was not heavily tested till now. For test automation,
> we still lack a test container environment for 286 as we had for 168
> (customized embedded Pluto)
> 
> - Events are not supported, and there is a good amount of work to do.
> Nevertheless, even without event support the new plugin has major
> advantages when working in a 286 environment
> 
> Given that Johannes gives us the input that things seem to be working in
> the real world (I think even production in his case), we should consider
> to move it into the main codebase. It should be by design a drop-in
> replacement for the current plugin and it is backwards compatible. I
> would say - let's go for it.
> 
> - René
> 
> On 27.01.11 08:37, Lukasz Lenart wrote:
>> 2011/1/27 Johannes Geppert <jo...@web.de>:
>>> is there any chance to get the portlet2 plugin out of the sandbox?
>>> I use this sandbox plugin and it works great except the eventing.
>> 
>> What about the eventing, is it possible to improve that?
>> 
>> 
>> Regards
> 
> -- 
> René Gielen
> IT-Neering.net
> Saarstrasse 100, 52062 Aachen, Germany
> Tel: +49-(0)241-4010770
> Fax: +49-(0)241-4010771
> Cel: +49-(0)163-2844164
> http://twitter.com/rgielen
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
> 
> 
> 


-----
---
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep

-- 
View this message in context: http://old.nabble.com/portlet2-plugin-tp30774658p30775129.html
Sent from the Struts - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Nils-Helge Garli Hegvik <ni...@gmail.com>.
Hi!

During the weekend I spent some time getting the embedded environment
updated to Pluto 2.0.2. So now it should be possible to use it with
JSR286 portlets.

Nils-H

On Thu, Jan 27, 2011 at 10:27 AM, Rene Gielen <gi...@it-neering.net> wrote:
> Hey Nils,
>
> thanks for jumping in! Good to have this on Github so we could fork it.
> May we bother you with some questions if we don't get it fixed
> ourselves? Last time I tried it, it wasn't working ...
>
> - René
>
> On 27.01.11 09:51, Nils-Helge Garli Hegvik wrote:
>> On Thu, Jan 27, 2011 at 8:56 AM, Rene Gielen <gi...@it-neering.net> wrote:
>>> Actual state:
>>> - JSR286 nature with automatic detection of the API version to use is
>>> implemented, but was not heavily tested till now. For test automation,
>>> we still lack a test container environment for 286 as we had for 168
>>> (customized embedded Pluto)
>>>
>>> - René
>>
>>
>> The embedded pluto container worked with JSR286 some time ago, but
>> here might have been changes that have "broken" it. I don't think it
>> should be too much work adapting it to a newer version of pluto. If
>> someone wants to hack on it the code is here:
>> https://github.com/nilsga/maven-jetty-pluto-embedded
>>
>> Nils-H
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>
> --
> René Gielen
> IT-Neering.net
> Saarstrasse 100, 52062 Aachen, Germany
> Tel: +49-(0)241-4010770
> Fax: +49-(0)241-4010771
> Cel: +49-(0)163-2844164
> http://twitter.com/rgielen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Nils-Helge Garli Hegvik <ni...@gmail.com>.
Yeah, I'm still around, trying to keep an eye on what's happening, so
I'll try to answer questions if you have any. It's really strange
though, it's been quiet around the JSR286 plugin for a looong time,
and then suddenly 4 people send me emails about it (outside struts
lists) in the same week. What a coincidence.

Nils-H

On Thu, Jan 27, 2011 at 10:27 AM, Rene Gielen <gi...@it-neering.net> wrote:
> Hey Nils,
>
> thanks for jumping in! Good to have this on Github so we could fork it.
> May we bother you with some questions if we don't get it fixed
> ourselves? Last time I tried it, it wasn't working ...
>
> - René
>
> On 27.01.11 09:51, Nils-Helge Garli Hegvik wrote:
>> On Thu, Jan 27, 2011 at 8:56 AM, Rene Gielen <gi...@it-neering.net> wrote:
>>> Actual state:
>>> - JSR286 nature with automatic detection of the API version to use is
>>> implemented, but was not heavily tested till now. For test automation,
>>> we still lack a test container environment for 286 as we had for 168
>>> (customized embedded Pluto)
>>>
>>> - René
>>
>>
>> The embedded pluto container worked with JSR286 some time ago, but
>> here might have been changes that have "broken" it. I don't think it
>> should be too much work adapting it to a newer version of pluto. If
>> someone wants to hack on it the code is here:
>> https://github.com/nilsga/maven-jetty-pluto-embedded
>>
>> Nils-H
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>
> --
> René Gielen
> IT-Neering.net
> Saarstrasse 100, 52062 Aachen, Germany
> Tel: +49-(0)241-4010770
> Fax: +49-(0)241-4010771
> Cel: +49-(0)163-2844164
> http://twitter.com/rgielen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Rene Gielen <gi...@it-neering.net>.
Hey Nils,

thanks for jumping in! Good to have this on Github so we could fork it.
May we bother you with some questions if we don't get it fixed
ourselves? Last time I tried it, it wasn't working ...

- René

On 27.01.11 09:51, Nils-Helge Garli Hegvik wrote:
> On Thu, Jan 27, 2011 at 8:56 AM, Rene Gielen <gi...@it-neering.net> wrote:
>> Actual state:
>> - JSR286 nature with automatic detection of the API version to use is
>> implemented, but was not heavily tested till now. For test automation,
>> we still lack a test container environment for 286 as we had for 168
>> (customized embedded Pluto)
>>
>> - René
> 
> 
> The embedded pluto container worked with JSR286 some time ago, but
> here might have been changes that have "broken" it. I don't think it
> should be too much work adapting it to a newer version of pluto. If
> someone wants to hack on it the code is here:
> https://github.com/nilsga/maven-jetty-pluto-embedded
> 
> Nils-H
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
> 

-- 
René Gielen
IT-Neering.net
Saarstrasse 100, 52062 Aachen, Germany
Tel: +49-(0)241-4010770
Fax: +49-(0)241-4010771
Cel: +49-(0)163-2844164
http://twitter.com/rgielen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Nils-Helge Garli Hegvik <ni...@gmail.com>.
On Thu, Jan 27, 2011 at 8:56 AM, Rene Gielen <gi...@it-neering.net> wrote:
> Actual state:
> - JSR286 nature with automatic detection of the API version to use is
> implemented, but was not heavily tested till now. For test automation,
> we still lack a test container environment for 286 as we had for 168
> (customized embedded Pluto)
>
> - René


The embedded pluto container worked with JSR286 some time ago, but
here might have been changes that have "broken" it. I don't think it
should be too much work adapting it to a newer version of pluto. If
someone wants to hack on it the code is here:
https://github.com/nilsga/maven-jetty-pluto-embedded

Nils-H

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Frans Thamura <fr...@meruvian.org>.
Liferay as I know also have problem when implement 168

Too complex may be


/m/

-----Original Message-----
From: Rene Gielen <gi...@it-neering.net>
Date: Thu, 27 Jan 2011 08:56:43 
To: Struts Developers List<de...@struts.apache.org>
Reply-To: "Struts Developers List" <de...@struts.apache.org>
Subject: Re: portlet2 plugin

Actual state:
- JSR286 nature with automatic detection of the API version to use is
implemented, but was not heavily tested till now. For test automation,
we still lack a test container environment for 286 as we had for 168
(customized embedded Pluto)

- Events are not supported, and there is a good amount of work to do.
Nevertheless, even without event support the new plugin has major
advantages when working in a 286 environment

Given that Johannes gives us the input that things seem to be working in
the real world (I think even production in his case), we should consider
to move it into the main codebase. It should be by design a drop-in
replacement for the current plugin and it is backwards compatible. I
would say - let's go for it.

- René

On 27.01.11 08:37, Lukasz Lenart wrote:
> 2011/1/27 Johannes Geppert <jo...@web.de>:
>> is there any chance to get the portlet2 plugin out of the sandbox?
>> I use this sandbox plugin and it works great except the eventing.
> 
> What about the eventing, is it possible to improve that?
> 
> 
> Regards

-- 
René Gielen
IT-Neering.net
Saarstrasse 100, 52062 Aachen, Germany
Tel: +49-(0)241-4010770
Fax: +49-(0)241-4010771
Cel: +49-(0)163-2844164
http://twitter.com/rgielen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Rene Gielen <gi...@it-neering.net>.
Actual state:
- JSR286 nature with automatic detection of the API version to use is
implemented, but was not heavily tested till now. For test automation,
we still lack a test container environment for 286 as we had for 168
(customized embedded Pluto)

- Events are not supported, and there is a good amount of work to do.
Nevertheless, even without event support the new plugin has major
advantages when working in a 286 environment

Given that Johannes gives us the input that things seem to be working in
the real world (I think even production in his case), we should consider
to move it into the main codebase. It should be by design a drop-in
replacement for the current plugin and it is backwards compatible. I
would say - let's go for it.

- René

On 27.01.11 08:37, Lukasz Lenart wrote:
> 2011/1/27 Johannes Geppert <jo...@web.de>:
>> is there any chance to get the portlet2 plugin out of the sandbox?
>> I use this sandbox plugin and it works great except the eventing.
> 
> What about the eventing, is it possible to improve that?
> 
> 
> Regards

-- 
René Gielen
IT-Neering.net
Saarstrasse 100, 52062 Aachen, Germany
Tel: +49-(0)241-4010770
Fax: +49-(0)241-4010771
Cel: +49-(0)163-2844164
http://twitter.com/rgielen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: portlet2 plugin

Posted by Lukasz Lenart <lu...@googlemail.com>.
2011/1/27 Johannes Geppert <jo...@web.de>:
> is there any chance to get the portlet2 plugin out of the sandbox?
> I use this sandbox plugin and it works great except the eventing.

What about the eventing, is it possible to improve that?


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia http://javarsovia.pl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org