SV: Remove support for Portlets in Wicket 1.5
Usually -1 votes should be accompanied by a justification if you want them to be considered seriously. Why are you voting -1? Moving portlet support to a separate project (instead of core or extensions) makes more sense, that is at least one justification. (I guess this would in effect be making a portlet bridge like IIRC the support pre-1.4-m2 used. But then it could be moved over to the Apache portlet bridge project as a whole, if that is still active?) Popularity of JSR-168/286 seems to be waning, and people instead use portals implemented directly on top of a content system instead... - Tor Iver - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: SV: Remove support for Portlets in Wicket 1.5
A -1 vote would be a vote against dropping support. You seem to be making an argument for dropping it. Plus it wasn't your -1, was it? On Sep 2, 2010 3:41 AM, Wilhelmsen Tor Iver toriv...@arrive.no wrote: Usually -1 votes should be accompanied by a justification if you want them to be considered seriously. Why are you voting -1? Moving portlet support to a separate project (instead of core or extensions) makes more sense, that is at least one justification. (I guess this would in effect be making a portlet bridge like IIRC the support pre-1.4-m2 used. But then it could be moved over to the Apache portlet bridge project as a whole, if that is still active?) Popularity of JSR-168/286 seems to be waning, and people instead use portals implemented directly on top of a content system instead... - Tor Iver - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
SV: SV: Remove support for Portlets in Wicket 1.5
A -1 vote would be a vote against dropping support. You seem to be making an argument for dropping it. Plus it wasn't your -1, was it? Ah, then I misunderstood. Was a bit early in the morning I guess. And if you only wanted a reply from him you would have sent a private email instead of posting to the public list, would you not? :) - Tor Iver - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: SV: Remove support for Portlets in Wicket 1.5
On Thu, Sep 2, 2010 at 6:50 AM, Wilhelmsen Tor Iver toriv...@arrive.no wrote: And if you only wanted a reply from him you would have sent a private email instead of posting to the public list, would you not? :) No, because I would want their reply to go to the list. The -1 should be taken seriously if it has a valid justification. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: SV: Remove support for Portlets in Wicket 1.5
this has already been done, its a bit too late for -1 votes. the thread was started aug 11. -igor On Thu, Sep 2, 2010 at 3:52 AM, James Carman ja...@carmanconsulting.com wrote: On Thu, Sep 2, 2010 at 6:50 AM, Wilhelmsen Tor Iver toriv...@arrive.no wrote: And if you only wanted a reply from him you would have sent a private email instead of posting to the public list, would you not? :) No, because I would want their reply to go to the list. The -1 should be taken seriously if it has a valid justification. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Remove support for Portlets in Wicket 1.5
-1 On Wed, Aug 11, 2010 at 8:35 PM, Martin Grigorov mgrigo...@apache.orgwrote: Hi, I just created a ticket (https://issues.apache.org/jira/browse/WICKET-2976 ) to remove the support for Portlets in Wicket 1.5. It is currently broken because of the re-work of WicketFilter and request processing. Since none of the active core developers use this technology in his daily job it is hard for us to support it. Now is the time to vote against this decision and give us a hand to improve it or just silently agree. martin-g P.S. I sent this email earlier today but for some reason it was rejected. Excuse me if you receive it for second time. -- Best regards, Paul Szulc http://www.paulszulc..com
Re: Remove support for Portlets in Wicket 1.5
Usually -1 votes should be accompanied by a justification if you want them to be considered seriously. Why are you voting -1? On Wed, Sep 1, 2010 at 11:06 AM, Paul Szulc paul.sz...@gmail.com wrote: -1 On Wed, Aug 11, 2010 at 8:35 PM, Martin Grigorov mgrigo...@apache.orgwrote: Hi, I just created a ticket (https://issues.apache.org/jira/browse/WICKET-2976 ) to remove the support for Portlets in Wicket 1.5. It is currently broken because of the re-work of WicketFilter and request processing. Since none of the active core developers use this technology in his daily job it is hard for us to support it. Now is the time to vote against this decision and give us a hand to improve it or just silently agree. martin-g P.S. I sent this email earlier today but for some reason it was rejected. Excuse me if you receive it for second time. -- Best regards, Paul Szulc http://www.paulszulc..com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Remove support for Portlets in Wicket 1.5
Hi, With r985443 the support for portlets is completely removed. The code is copied to https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-portlets . Check the list of modified files in the commit to see which other files in Wicket are modified. To bring the wicketstuff project in shape you may also need to check WicketFilter class in 1.4.x. martin-g On Thu, Aug 12, 2010 at 9:42 AM, Wilhelmsen Tor Iver toriv...@arrive.nowrote: So next step is someone with experience in portlets to try to create a separate project with the classes from org.apache.wicket.protocol.http.portlet and whatever else is needed. Probably mostly a WicketPortletFilter to be used in front of WicketFilter that builds on the portlet-oriented code from the 1.4.x branch and sets up what is needed if it detects a portlet request? - Tor Iver
Re: Remove support for Portlets in Wicket 1.5
Hi, -1 to removing it We are using Wicket and portlets in many projects. At a minimum move it to wicketstuff. thanks, José Antonio Matute
Re: Remove support for Portlets in Wicket 1.5
-1 to removing it As soon as uPortal supports JSR-286 (and it does, just not in a release yet) I'll be using Wicket for my portlet development and have been training my team in readiness. At a minimum move it to wicketstuff. thanks, Steve On 12/08/2010, at 5:19 AM, Rodolfo Hansen wrote: I used wikcet 1.4 inside Liferay 5.2 and sent a tiny patch that was implemented in 1.4.7 I no longer use wicket inside a portlet container, but I can help support it. On Wed, 2010-08-11 at 14:45 -0400, James Carman wrote: I'd say at least move it to wicketstuff, so that if there's some other person out there with the will and means to take the project on, they can do so. On Wed, Aug 11, 2010 at 2:35 PM, Martin Grigorov mgrigo...@apache.org wrote: Hi, I just created a ticket (https://issues.apache.org/jira/browse/WICKET-2976) to remove the support for Portlets in Wicket 1.5. It is currently broken because of the re-work of WicketFilter and request processing. Since none of the active core developers use this technology in his daily job it is hard for us to support it. Now is the time to vote against this decision and give us a hand to improve it or just silently agree. martin-g P.S. I sent this email earlier today but for some reason it was rejected. Excuse me if you receive it for second time. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Remove support for Portlets in Wicket 1.5
0, non-committed. There seems to be some interest here. Hopefully the community supports it in wicketstuff. +1 non-committed to moving to wicketstuff. On Aug 11, 2010 11:18 PM, Steve Swinsburg steve.swinsb...@gmail.com wrote: -1 to removing it As soon as uPortal supports JSR-286 (and it does, just not in a release yet) I'll be using Wicket for my portlet development and have been training my team in readiness. At a minimum move it to wicketstuff. thanks, Steve On 12/08/2010, at 5:19 AM, Rodolfo Hansen wrote: I used wikcet 1.4 inside Liferay 5.2 and sent ...
Re: Remove support for Portlets in Wicket 1.5
Ok, we have 1.5-M1 released. So next step is someone with experience in portlets to try to create a separate project with the classes from org.apache.wicket.protocol.http.portlet and whatever else is needed. On Thu, Aug 12, 2010 at 8:59 AM, Nick Heudecker nheudec...@gmail.comwrote: 0, non-committed. There seems to be some interest here. Hopefully the community supports it in wicketstuff. +1 non-committed to moving to wicketstuff. On Aug 11, 2010 11:18 PM, Steve Swinsburg steve.swinsb...@gmail.com wrote: -1 to removing it As soon as uPortal supports JSR-286 (and it does, just not in a release yet) I'll be using Wicket for my portlet development and have been training my team in readiness. At a minimum move it to wicketstuff. thanks, Steve On 12/08/2010, at 5:19 AM, Rodolfo Hansen wrote: I used wikcet 1.4 inside Liferay 5.2 and sent ...
Re: Remove support for Portlets in Wicket 1.5
So next step is someone with experience in portlets to try to create a separate project with the classes from org.apache.wicket.protocol.http.portlet and whatever else is needed. Probably mostly a WicketPortletFilter to be used in front of WicketFilter that builds on the portlet-oriented code from the 1.4.x branch and sets up what is needed if it detects a portlet request? - Tor Iver
Remove support for Portlets in Wicket 1.5
Hi, I just created a ticket (https://issues.apache.org/jira/browse/WICKET-2976) to remove the support for Portlets in Wicket 1.5. It is currently broken because of the re-work of WicketFilter and request processing. Since none of the active core developers use this technology in his daily job it is hard for us to support it. Now is the time to vote against this decision and give us a hand to improve it or just silently agree. martin-g P.S. I sent this email earlier today but for some reason it was rejected. Excuse me if you receive it for second time.
Re: Remove support for Portlets in Wicket 1.5
I'd say at least move it to wicketstuff, so that if there's some other person out there with the will and means to take the project on, they can do so. On Wed, Aug 11, 2010 at 2:35 PM, Martin Grigorov mgrigo...@apache.org wrote: Hi, I just created a ticket (https://issues.apache.org/jira/browse/WICKET-2976) to remove the support for Portlets in Wicket 1.5. It is currently broken because of the re-work of WicketFilter and request processing. Since none of the active core developers use this technology in his daily job it is hard for us to support it. Now is the time to vote against this decision and give us a hand to improve it or just silently agree. martin-g P.S. I sent this email earlier today but for some reason it was rejected. Excuse me if you receive it for second time. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Remove support for Portlets in Wicket 1.5
I used wikcet 1.4 inside Liferay 5.2 and sent a tiny patch that was implemented in 1.4.7 I no longer use wicket inside a portlet container, but I can help support it. On Wed, 2010-08-11 at 14:45 -0400, James Carman wrote: I'd say at least move it to wicketstuff, so that if there's some other person out there with the will and means to take the project on, they can do so. On Wed, Aug 11, 2010 at 2:35 PM, Martin Grigorov mgrigo...@apache.org wrote: Hi, I just created a ticket (https://issues.apache.org/jira/browse/WICKET-2976) to remove the support for Portlets in Wicket 1.5. It is currently broken because of the re-work of WicketFilter and request processing. Since none of the active core developers use this technology in his daily job it is hard for us to support it. Now is the time to vote against this decision and give us a hand to improve it or just silently agree. martin-g P.S. I sent this email earlier today but for some reason it was rejected. Excuse me if you receive it for second time. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
