You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Maxim Solodovnik <so...@gmail.com> on 2017/07/31 15:14:44 UTC
Wicket 8 (M7) release
Hello All,
As I can see there are no issues against M7, maybe it's time for release?
Maybe it also worth to release 8.0.0?
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Maxim Solodovnik <so...@gmail.com>.
I have restarted our demo app 3 days ago :( (the version was updated)
Will check at the end of the week
I have 2 versions of same system:
A based on M6
B based on SNAPSHOT
B was started just now
A is running for 3 days
memory consumption almost the same ...
On Mon, Aug 7, 2017 at 4:55 PM, Sebastien <se...@gmail.com> wrote:
> Hi KB,
>
> Thanks for your inputs!
>
> The demo app is wicket-jquery-ui-samples:
> https://github.com/sebfz1/wicket-jquery-ui
>
> online here:
> http://www.7thweb.net/wicket-jquery-ui/
>
> If you want to give a try at profiling, you are very welcome! :)
>
> In the meantime, I launch the HPROF on the server and I will let it collect
> data for some hours. Will see what comes out...
> By monitoring the traffic, I also saw queries to the InspectorPage (yes,
> I've got the inspector page in "production"! But that's a demo app, that's
> why...).
> I know the inspector page can be memory consuming, so maybe it's an hit...
>
> Best regards,
> Sebastien
>
> On Mon, Aug 7, 2017 at 11:42 AM, Korbinian Bachl <
> korbinian.bachl@whiskyworld.de> wrote:
>
>> Hello Sebastien,
>>
>> that sounds bad - how big is the heap space you gave to your server?
>>
>> I'm running our app now on a testserver for 10 days and the memory usage
>> seems normal - even though I also did some jMeter on it during the last
>> week, spawning many many threads and requests;
>>
>> Heap from 8-Snapshot here reads as follows at the current time:
>>
>> Heap Memory Usage:
>> Memory that Java Virtual Machine initially requested to the Operating
>> System: 2.147.483.648 Bytes
>> Memory that Java Virtual Machine is guaranteed to receive from the
>> Operating System: 2.144.337.920 Bytes
>> Maximum Memory that Java Virtual Machine may get from the Operating
>> System: 2.144.337.920 Bytes. Note that this is not guaranteed.
>> Memory that Java Virtual Machine uses at this time: 1.018.066.976 Bytes
>>
>> While our production one after nealry 10 weeks uptime reads this:
>>
>> Heap Memory Usage:
>> Memory that Java Virtual Machine initially requested to the Operating
>> System: 4.294.967.296 Bytes
>> Memory that Java Virtual Machine is guaranteed to receive from the
>> Operating System: 4.151.836.672 Bytes
>> Maximum Memory that Java Virtual Machine may get from the Operating
>> System: 4.151.836.672 Bytes. Note that this is not guaranteed.
>> Memory that Java Virtual Machine uses at this time: 1.014.171.432 Bytes
>>
>>
>>
>> So far nothing big difference - both are far away from maximumg level;
>>
>> What kind of demo app is this?
>>
>> Best,
>>
>> KB
>>
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Sebastien <se...@gmail.com>.
Hi KB,
Thanks for your inputs!
The demo app is wicket-jquery-ui-samples:
https://github.com/sebfz1/wicket-jquery-ui
online here:
http://www.7thweb.net/wicket-jquery-ui/
If you want to give a try at profiling, you are very welcome! :)
In the meantime, I launch the HPROF on the server and I will let it collect
data for some hours. Will see what comes out...
By monitoring the traffic, I also saw queries to the InspectorPage (yes,
I've got the inspector page in "production"! But that's a demo app, that's
why...).
I know the inspector page can be memory consuming, so maybe it's an hit...
Best regards,
Sebastien
On Mon, Aug 7, 2017 at 11:42 AM, Korbinian Bachl <
korbinian.bachl@whiskyworld.de> wrote:
> Hello Sebastien,
>
> that sounds bad - how big is the heap space you gave to your server?
>
> I'm running our app now on a testserver for 10 days and the memory usage
> seems normal - even though I also did some jMeter on it during the last
> week, spawning many many threads and requests;
>
> Heap from 8-Snapshot here reads as follows at the current time:
>
> Heap Memory Usage:
> Memory that Java Virtual Machine initially requested to the Operating
> System: 2.147.483.648 Bytes
> Memory that Java Virtual Machine is guaranteed to receive from the
> Operating System: 2.144.337.920 Bytes
> Maximum Memory that Java Virtual Machine may get from the Operating
> System: 2.144.337.920 Bytes. Note that this is not guaranteed.
> Memory that Java Virtual Machine uses at this time: 1.018.066.976 Bytes
>
> While our production one after nealry 10 weeks uptime reads this:
>
> Heap Memory Usage:
> Memory that Java Virtual Machine initially requested to the Operating
> System: 4.294.967.296 Bytes
> Memory that Java Virtual Machine is guaranteed to receive from the
> Operating System: 4.151.836.672 Bytes
> Maximum Memory that Java Virtual Machine may get from the Operating
> System: 4.151.836.672 Bytes. Note that this is not guaranteed.
> Memory that Java Virtual Machine uses at this time: 1.014.171.432 Bytes
>
>
>
> So far nothing big difference - both are far away from maximumg level;
>
> What kind of demo app is this?
>
> Best,
>
> KB
>
Re: Wicket 8 (M7) release
Posted by Korbinian Bachl <ko...@whiskyworld.de>.
Hello Sebastien,
that sounds bad - how big is the heap space you gave to your server?
I'm running our app now on a testserver for 10 days and the memory usage seems normal - even though I also did some jMeter on it during the last week, spawning many many threads and requests;
Heap from 8-Snapshot here reads as follows at the current time:
Heap Memory Usage:
Memory that Java Virtual Machine initially requested to the Operating System: 2.147.483.648 Bytes
Memory that Java Virtual Machine is guaranteed to receive from the Operating System: 2.144.337.920 Bytes
Maximum Memory that Java Virtual Machine may get from the Operating System: 2.144.337.920 Bytes. Note that this is not guaranteed.
Memory that Java Virtual Machine uses at this time: 1.018.066.976 Bytes
While our production one after nealry 10 weeks uptime reads this:
Heap Memory Usage:
Memory that Java Virtual Machine initially requested to the Operating System: 4.294.967.296 Bytes
Memory that Java Virtual Machine is guaranteed to receive from the Operating System: 4.151.836.672 Bytes
Maximum Memory that Java Virtual Machine may get from the Operating System: 4.151.836.672 Bytes. Note that this is not guaranteed.
Memory that Java Virtual Machine uses at this time: 1.014.171.432 Bytes
So far nothing big difference - both are far away from maximumg level;
What kind of demo app is this?
Best,
KB
----- Ursprüngliche Mail -----
> Von: "Sebastien" <se...@gmail.com>
> An: dev@wicket.apache.org
> Gesendet: Montag, 7. August 2017 10:12:51
> Betreff: Re: Wicket 8 (M7) release
> Hi,
>
> Just to let you know: I deployed the wicket8.x of my demo app and it ran
> for 5 days before failing down (out of memory)
>
> SEVERE [ajp-nio-8009-exec-2]
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3332)
> at
> java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
> at
> java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
> at java.lang.StringBuilder.append(StringBuilder.java:136)
> at org.apache.wicket.Page.checkRendering(Page.java:662)
> at org.apache.wicket.Page.onAfterRender(Page.java:805)
> at org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:209)
> at org.apache.wicket.Component.afterRender(Component.java:919)
> at org.apache.wicket.Component.render(Component.java:2335)
> at org.apache.wicket.Page.renderPage(Page.java:987)
> at
> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124)
> at
> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236)
> at
> org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:202)
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)
> at
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204)
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> at
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)
> at
> org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:868)
>
> There is nothing else in there. I should really run a profiler...
>
> Best regards,
> Sebastien.
>
> On Sun, Aug 6, 2017 at 7:34 PM, Maxim Solodovnik <so...@gmail.com>
> wrote:
>
>> As far as I can see nothing blocks the release
>> +1 :)
>>
>> On Mon, Aug 7, 2017 at 12:25 AM, Andrea Del Bene <an...@gmail.com>
>> wrote:
>> > I guess now we are ready to start the release of M7, right?
>> >
>> >
>> > On 05/08/2017 17:12, Maxim Solodovnik wrote:
>> >>
>> >> https://github.com/apache/wicket/pull/228
>> >>
>> >> On Sat, Aug 5, 2017 at 12:04 PM, Maxim Solodovnik <solomax666@gmail.com
>> >
>> >> wrote:
>> >>>
>> >>> OK, thanks
>> >>> will prepare PR
>> >>>
>> >>> On Sat, Aug 5, 2017 at 11:59 AM, Martin Grigorov
>> >>> <ma...@gmail.com> wrote:
>> >>>>
>> >>>> Hi Maxim,
>> >>>>
>> >>>> On Aug 5, 2017 3:28 AM, "Maxim Solodovnik" <so...@gmail.com>
>> wrote:
>> >>>>
>> >>>> Hello All,
>> >>>>
>> >>>> I would like to update version on libraries being used by wicket to
>> the
>> >>>> most recent versions is it OK?
>> >>>>
>> >>>>
>> >>>> Sure!
>> >>>>
>> >>>>
>> >>>> report can be get as follows (with some exceptions of course):
>> >>>>
>> >>>> mvn versions:display-dependency-updates
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Sat, Aug 5, 2017 at 3:26 AM, Tobias Soloschenko <
>> >>>> tobiassoloschenko@googlemail.com> wrote:
>> >>>>
>> >>>>> +1 for M7
>> >>>>>
>> >>>>> kind regards
>> >>>>>
>> >>>>> Tobias
>> >>>>>
>> >>>>>> Am 04.08.2017 um 18:56 schrieb Korbinian Bachl <
>> >>>>>
>> >>>>> korbinian.bachl@whiskyworld.de>:
>> >>>>>>
>> >>>>>> Please a thousand +1 (non-binding)
>> >>>>>>
>> >>>>>> :)
>> >>>>>>
>> >>>>>> ----- Ursprüngliche Mail -----
>> >>>>>>>
>> >>>>>>> Von: "Andrea Del Bene" <an...@gmail.com>
>> >>>>>>> An: dev@wicket.apache.org
>> >>>>>>> Gesendet: Freitag, 4. August 2017 17:12:43
>> >>>>>>> Betreff: Re: Wicket 8 (M7) release
>> >>>>>>> Hi,
>> >>>>>>>
>> >>>>>>> I think we are ready to promote Wicket 8 to GA but I would wait for
>> >>>>>>> September as August is usually a very quite month (at least in
>> >>>>>>> Europe)
>> >>>>>
>> >>>>> so
>> >>>>>>>
>> >>>>>>> it risks to be overlooked. But I have no objection to prepare a M7
>> in
>> >>>>>
>> >>>>> the
>> >>>>>>>
>> >>>>>>> meantime.
>> >>>>>>>
>> >>>>>>> What do you think?
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> WBR
>> >>>> Maxim aka solomax
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> WBR
>> >>> Maxim aka solomax
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Sebastien <se...@gmail.com>.
Hi,
Just to let you know: I deployed the wicket8.x of my demo app and it ran
for 5 days before failing down (out of memory)
SEVERE [ajp-nio-8009-exec-2]
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at
java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
at
java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuilder.append(StringBuilder.java:136)
at org.apache.wicket.Page.checkRendering(Page.java:662)
at org.apache.wicket.Page.onAfterRender(Page.java:805)
at org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:209)
at org.apache.wicket.Component.afterRender(Component.java:919)
at org.apache.wicket.Component.render(Component.java:2335)
at org.apache.wicket.Page.renderPage(Page.java:987)
at
org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124)
at
org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236)
at
org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:202)
at
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)
at
org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
at
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)
at
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
at
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)
at
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)
at
org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:868)
There is nothing else in there. I should really run a profiler...
Best regards,
Sebastien.
On Sun, Aug 6, 2017 at 7:34 PM, Maxim Solodovnik <so...@gmail.com>
wrote:
> As far as I can see nothing blocks the release
> +1 :)
>
> On Mon, Aug 7, 2017 at 12:25 AM, Andrea Del Bene <an...@gmail.com>
> wrote:
> > I guess now we are ready to start the release of M7, right?
> >
> >
> > On 05/08/2017 17:12, Maxim Solodovnik wrote:
> >>
> >> https://github.com/apache/wicket/pull/228
> >>
> >> On Sat, Aug 5, 2017 at 12:04 PM, Maxim Solodovnik <solomax666@gmail.com
> >
> >> wrote:
> >>>
> >>> OK, thanks
> >>> will prepare PR
> >>>
> >>> On Sat, Aug 5, 2017 at 11:59 AM, Martin Grigorov
> >>> <ma...@gmail.com> wrote:
> >>>>
> >>>> Hi Maxim,
> >>>>
> >>>> On Aug 5, 2017 3:28 AM, "Maxim Solodovnik" <so...@gmail.com>
> wrote:
> >>>>
> >>>> Hello All,
> >>>>
> >>>> I would like to update version on libraries being used by wicket to
> the
> >>>> most recent versions is it OK?
> >>>>
> >>>>
> >>>> Sure!
> >>>>
> >>>>
> >>>> report can be get as follows (with some exceptions of course):
> >>>>
> >>>> mvn versions:display-dependency-updates
> >>>>
> >>>>
> >>>>
> >>>> On Sat, Aug 5, 2017 at 3:26 AM, Tobias Soloschenko <
> >>>> tobiassoloschenko@googlemail.com> wrote:
> >>>>
> >>>>> +1 for M7
> >>>>>
> >>>>> kind regards
> >>>>>
> >>>>> Tobias
> >>>>>
> >>>>>> Am 04.08.2017 um 18:56 schrieb Korbinian Bachl <
> >>>>>
> >>>>> korbinian.bachl@whiskyworld.de>:
> >>>>>>
> >>>>>> Please a thousand +1 (non-binding)
> >>>>>>
> >>>>>> :)
> >>>>>>
> >>>>>> ----- Ursprüngliche Mail -----
> >>>>>>>
> >>>>>>> Von: "Andrea Del Bene" <an...@gmail.com>
> >>>>>>> An: dev@wicket.apache.org
> >>>>>>> Gesendet: Freitag, 4. August 2017 17:12:43
> >>>>>>> Betreff: Re: Wicket 8 (M7) release
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> I think we are ready to promote Wicket 8 to GA but I would wait for
> >>>>>>> September as August is usually a very quite month (at least in
> >>>>>>> Europe)
> >>>>>
> >>>>> so
> >>>>>>>
> >>>>>>> it risks to be overlooked. But I have no objection to prepare a M7
> in
> >>>>>
> >>>>> the
> >>>>>>>
> >>>>>>> meantime.
> >>>>>>>
> >>>>>>> What do you think?
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> WBR
> >>>> Maxim aka solomax
> >>>
> >>>
> >>>
> >>> --
> >>> WBR
> >>> Maxim aka solomax
> >>
> >>
> >>
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>
Re: Wicket 8 (M7) release
Posted by Maxim Solodovnik <so...@gmail.com>.
As far as I can see nothing blocks the release
+1 :)
On Mon, Aug 7, 2017 at 12:25 AM, Andrea Del Bene <an...@gmail.com> wrote:
> I guess now we are ready to start the release of M7, right?
>
>
> On 05/08/2017 17:12, Maxim Solodovnik wrote:
>>
>> https://github.com/apache/wicket/pull/228
>>
>> On Sat, Aug 5, 2017 at 12:04 PM, Maxim Solodovnik <so...@gmail.com>
>> wrote:
>>>
>>> OK, thanks
>>> will prepare PR
>>>
>>> On Sat, Aug 5, 2017 at 11:59 AM, Martin Grigorov
>>> <ma...@gmail.com> wrote:
>>>>
>>>> Hi Maxim,
>>>>
>>>> On Aug 5, 2017 3:28 AM, "Maxim Solodovnik" <so...@gmail.com> wrote:
>>>>
>>>> Hello All,
>>>>
>>>> I would like to update version on libraries being used by wicket to the
>>>> most recent versions is it OK?
>>>>
>>>>
>>>> Sure!
>>>>
>>>>
>>>> report can be get as follows (with some exceptions of course):
>>>>
>>>> mvn versions:display-dependency-updates
>>>>
>>>>
>>>>
>>>> On Sat, Aug 5, 2017 at 3:26 AM, Tobias Soloschenko <
>>>> tobiassoloschenko@googlemail.com> wrote:
>>>>
>>>>> +1 for M7
>>>>>
>>>>> kind regards
>>>>>
>>>>> Tobias
>>>>>
>>>>>> Am 04.08.2017 um 18:56 schrieb Korbinian Bachl <
>>>>>
>>>>> korbinian.bachl@whiskyworld.de>:
>>>>>>
>>>>>> Please a thousand +1 (non-binding)
>>>>>>
>>>>>> :)
>>>>>>
>>>>>> ----- Ursprüngliche Mail -----
>>>>>>>
>>>>>>> Von: "Andrea Del Bene" <an...@gmail.com>
>>>>>>> An: dev@wicket.apache.org
>>>>>>> Gesendet: Freitag, 4. August 2017 17:12:43
>>>>>>> Betreff: Re: Wicket 8 (M7) release
>>>>>>> Hi,
>>>>>>>
>>>>>>> I think we are ready to promote Wicket 8 to GA but I would wait for
>>>>>>> September as August is usually a very quite month (at least in
>>>>>>> Europe)
>>>>>
>>>>> so
>>>>>>>
>>>>>>> it risks to be overlooked. But I have no objection to prepare a M7 in
>>>>>
>>>>> the
>>>>>>>
>>>>>>> meantime.
>>>>>>>
>>>>>>> What do you think?
>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>
>>
>>
>
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Maxim Solodovnik <so...@gmail.com>.
https://github.com/apache/wicket/pull/228
On Sat, Aug 5, 2017 at 12:04 PM, Maxim Solodovnik <so...@gmail.com> wrote:
> OK, thanks
> will prepare PR
>
> On Sat, Aug 5, 2017 at 11:59 AM, Martin Grigorov
> <ma...@gmail.com> wrote:
>> Hi Maxim,
>>
>> On Aug 5, 2017 3:28 AM, "Maxim Solodovnik" <so...@gmail.com> wrote:
>>
>> Hello All,
>>
>> I would like to update version on libraries being used by wicket to the
>> most recent versions is it OK?
>>
>>
>> Sure!
>>
>>
>> report can be get as follows (with some exceptions of course):
>>
>> mvn versions:display-dependency-updates
>>
>>
>>
>> On Sat, Aug 5, 2017 at 3:26 AM, Tobias Soloschenko <
>> tobiassoloschenko@googlemail.com> wrote:
>>
>>> +1 for M7
>>>
>>> kind regards
>>>
>>> Tobias
>>>
>>> > Am 04.08.2017 um 18:56 schrieb Korbinian Bachl <
>>> korbinian.bachl@whiskyworld.de>:
>>> >
>>> > Please a thousand +1 (non-binding)
>>> >
>>> > :)
>>> >
>>> > ----- Ursprüngliche Mail -----
>>> >> Von: "Andrea Del Bene" <an...@gmail.com>
>>> >> An: dev@wicket.apache.org
>>> >> Gesendet: Freitag, 4. August 2017 17:12:43
>>> >> Betreff: Re: Wicket 8 (M7) release
>>> >
>>> >> Hi,
>>> >>
>>> >> I think we are ready to promote Wicket 8 to GA but I would wait for
>>> >> September as August is usually a very quite month (at least in Europe)
>>> so
>>> >> it risks to be overlooked. But I have no objection to prepare a M7 in
>>> the
>>> >> meantime.
>>> >>
>>> >> What do you think?
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Maxim Solodovnik <so...@gmail.com>.
OK, thanks
will prepare PR
On Sat, Aug 5, 2017 at 11:59 AM, Martin Grigorov
<ma...@gmail.com> wrote:
> Hi Maxim,
>
> On Aug 5, 2017 3:28 AM, "Maxim Solodovnik" <so...@gmail.com> wrote:
>
> Hello All,
>
> I would like to update version on libraries being used by wicket to the
> most recent versions is it OK?
>
>
> Sure!
>
>
> report can be get as follows (with some exceptions of course):
>
> mvn versions:display-dependency-updates
>
>
>
> On Sat, Aug 5, 2017 at 3:26 AM, Tobias Soloschenko <
> tobiassoloschenko@googlemail.com> wrote:
>
>> +1 for M7
>>
>> kind regards
>>
>> Tobias
>>
>> > Am 04.08.2017 um 18:56 schrieb Korbinian Bachl <
>> korbinian.bachl@whiskyworld.de>:
>> >
>> > Please a thousand +1 (non-binding)
>> >
>> > :)
>> >
>> > ----- Ursprüngliche Mail -----
>> >> Von: "Andrea Del Bene" <an...@gmail.com>
>> >> An: dev@wicket.apache.org
>> >> Gesendet: Freitag, 4. August 2017 17:12:43
>> >> Betreff: Re: Wicket 8 (M7) release
>> >
>> >> Hi,
>> >>
>> >> I think we are ready to promote Wicket 8 to GA but I would wait for
>> >> September as August is usually a very quite month (at least in Europe)
>> so
>> >> it risks to be overlooked. But I have no objection to prepare a M7 in
>> the
>> >> meantime.
>> >>
>> >> What do you think?
>>
>
>
>
> --
> WBR
> Maxim aka solomax
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Martin Grigorov <ma...@gmail.com>.
Hi Maxim,
On Aug 5, 2017 3:28 AM, "Maxim Solodovnik" <so...@gmail.com> wrote:
Hello All,
I would like to update version on libraries being used by wicket to the
most recent versions is it OK?
Sure!
report can be get as follows (with some exceptions of course):
mvn versions:display-dependency-updates
On Sat, Aug 5, 2017 at 3:26 AM, Tobias Soloschenko <
tobiassoloschenko@googlemail.com> wrote:
> +1 for M7
>
> kind regards
>
> Tobias
>
> > Am 04.08.2017 um 18:56 schrieb Korbinian Bachl <
> korbinian.bachl@whiskyworld.de>:
> >
> > Please a thousand +1 (non-binding)
> >
> > :)
> >
> > ----- Ursprüngliche Mail -----
> >> Von: "Andrea Del Bene" <an...@gmail.com>
> >> An: dev@wicket.apache.org
> >> Gesendet: Freitag, 4. August 2017 17:12:43
> >> Betreff: Re: Wicket 8 (M7) release
> >
> >> Hi,
> >>
> >> I think we are ready to promote Wicket 8 to GA but I would wait for
> >> September as August is usually a very quite month (at least in Europe)
> so
> >> it risks to be overlooked. But I have no objection to prepare a M7 in
> the
> >> meantime.
> >>
> >> What do you think?
>
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello All,
I would like to update version on libraries being used by wicket to the
most recent versions is it OK?
report can be get as follows (with some exceptions of course):
mvn versions:display-dependency-updates
On Sat, Aug 5, 2017 at 3:26 AM, Tobias Soloschenko <
tobiassoloschenko@googlemail.com> wrote:
> +1 for M7
>
> kind regards
>
> Tobias
>
> > Am 04.08.2017 um 18:56 schrieb Korbinian Bachl <
> korbinian.bachl@whiskyworld.de>:
> >
> > Please a thousand +1 (non-binding)
> >
> > :)
> >
> > ----- Ursprüngliche Mail -----
> >> Von: "Andrea Del Bene" <an...@gmail.com>
> >> An: dev@wicket.apache.org
> >> Gesendet: Freitag, 4. August 2017 17:12:43
> >> Betreff: Re: Wicket 8 (M7) release
> >
> >> Hi,
> >>
> >> I think we are ready to promote Wicket 8 to GA but I would wait for
> >> September as August is usually a very quite month (at least in Europe)
> so
> >> it risks to be overlooked. But I have no objection to prepare a M7 in
> the
> >> meantime.
> >>
> >> What do you think?
>
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Tobias Soloschenko <to...@googlemail.com>.
+1 for M7
kind regards
Tobias
> Am 04.08.2017 um 18:56 schrieb Korbinian Bachl <ko...@whiskyworld.de>:
>
> Please a thousand +1 (non-binding)
>
> :)
>
> ----- Ursprüngliche Mail -----
>> Von: "Andrea Del Bene" <an...@gmail.com>
>> An: dev@wicket.apache.org
>> Gesendet: Freitag, 4. August 2017 17:12:43
>> Betreff: Re: Wicket 8 (M7) release
>
>> Hi,
>>
>> I think we are ready to promote Wicket 8 to GA but I would wait for
>> September as August is usually a very quite month (at least in Europe) so
>> it risks to be overlooked. But I have no objection to prepare a M7 in the
>> meantime.
>>
>> What do you think?
Re: Wicket 8 (M7) release
Posted by Korbinian Bachl <ko...@whiskyworld.de>.
Please a thousand +1 (non-binding)
:)
----- Ursprüngliche Mail -----
> Von: "Andrea Del Bene" <an...@gmail.com>
> An: dev@wicket.apache.org
> Gesendet: Freitag, 4. August 2017 17:12:43
> Betreff: Re: Wicket 8 (M7) release
> Hi,
>
> I think we are ready to promote Wicket 8 to GA but I would wait for
> September as August is usually a very quite month (at least in Europe) so
> it risks to be overlooked. But I have no objection to prepare a M7 in the
> meantime.
>
> What do you think?
Re: Wicket 8 (M7) release
Posted by Sebastien <se...@gmail.com>.
I will re-deploy my 8.x version and send you the log in the few days (the
time it crashes).
I don't know if they will be useful, I don't remember something eloquent in
there, that's why I wanted to profile it...
On Mon, Jul 31, 2017 at 8:43 PM, Martin Grigorov <mg...@apache.org>
wrote:
> examples7.x use Tomcat image from OpenShift, and it has the scripts by
> default.
>
> I think any of the free providers (like OpenShift, Heroku, ...) shutdown
> the app if it is not used for some time. When someone requests the app they
> start it again. I think this is what was happening here.
>
> I've just checked the logs of examples8x and there are some interesting
> problems:
>
> 1.
> Caused by: java.lang.RuntimeException: An error occurred while getting the
> model object for Component: [Component id = word, page =
> org.apache.wicket.examples.hangman.Guess, path = word, type =
> org.apache.wicket.markup.html.basic.Label, isVisible = true, isVersioned =
> false, markup = [markup =
> file:/var/lib/openshift/592dc27b89f5cfabc700006d/app-
> root/data/apache-tomcat-8.5.15/webapps/ROOT/WEB-INF/
> classes/org/apache/wicket/examples/hangman/Guess.html
> <span wicket:id="word">WICK_T</span>, index = 0, current = '<span
> wicket:id="word">' (line 0, column 0)]]
> at
> org.apache.wicket.Component.getDefaultModelObject(Component.java:1651)
> at
> org.apache.wicket.Component.getDefaultModelObjectAsString(
> Component.java:1672)
> at
> org.apache.wicket.markup.html.basic.Label.onComponentTagBody(Label.java:
> 115)
> at
> org.apache.wicket.markup.html.panel.DefaultMarkupSourcingStrategy.
> onComponentTagBody(DefaultMarkupSourcingStrategy.java:70)
> at
> org.apache.wicket.Component.internalRenderComponent(Component.java:2595)
> ... 40 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.wicket.examples.hangman.Guess.lambda$new$
> 1f219a47$1(Guess.java:45)
> at
> org.apache.wicket.Component.getDefaultModelObject(Component.java:1644)
>
> 2.
> ERROR - DefaultExceptionMapper - Unexpected error occurred
> org.jboss.weld.context.NonexistentConversationException: WELD-000321: No
> conversation found to restore for id 2
> at
> org.jboss.weld.context.AbstractConversationContext.initialize(
> AbstractConversationContext.java:240)
> at
> org.jboss.weld.context.http.LazyHttpConversationContextImpl.initialize(
> LazyHttpConversationContextImpl.java:90)
> at
> org.jboss.weld.context.http.LazyHttpConversationContextImp
> l.checkContextInitialized(LazyHttpConversationContextImpl.java:124)
> at
> org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(
> AbstractConversationContext.java:483)
> at
> org.jboss.weld.bean.builtin.ConversationBean.newInstance(
> ConversationBean.java:31)
> at
> org.jboss.weld.bean.builtin.ConversationBean.newInstance(
> ConversationBean.java:16)
> at
> org.jboss.weld.bean.builtin.AbstractDecorableBuiltInBean.create(
> AbstractDecorableBuiltInBean.java:52)
> at
> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> at
> org.jboss.weld.bean.ContextualInstanceStrategy$
> DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
> at
> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> at
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(
> ContextBeanInstance.java:99)
> at
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(
> ProxyMethodHandler.java:99)
> at
> org.jboss.weldx.enterprise.context.Conversation$1584357708$Proxy$_$$_
> WeldClientProxy.getId(Unknown
> Source)
> at
> org.apache.wicket.cdi.ConversationPropagator.onRequestHandlerResolved(
> ConversationPropagator.java:108)
>
> 3. (fixed already)
> ERROR - DefaultExceptionMapper - Unexpected error occurred
> java.lang.NullPointerException
> at
> org.apache.wicket.core.request.handler.PageProvider.
> getPageClass(PageProvider.java:261)
> at
> org.apache.wicket.core.request.handler.RenderPageRequestHandler.
> getPageClass(RenderPageRequestHandler.java:163)
>
> 4. This one needs attention !
> ERROR - JavaSerializer - error writing object [Page class =
> org.apache.wicket.examples.tree.NestedTreePage, id = 0, render count = 1]:
> null
> java.util.ConcurrentModificationException
> at java.util.ArrayList.writeObject(ArrayList.java:766)
> at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(
> ObjectOutputStream.java:1432)
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at
> java.io.ObjectOutputStream.defaultWriteFields(
> ObjectOutputStream.java:1548)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(
> ObjectOutputStream.java:1432)
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at
> org.apache.wicket.serialize.java.JavaSerializer$
> SerializationCheckerObjectOutputStream.writeObjectOverride(
> JavaSerializer.java:368)
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
> at
> org.apache.wicket.serialize.java.JavaSerializer.serialize(
> JavaSerializer.java:82)
> at
> org.apache.wicket.pageStore.AbstractPageStore.serializePage(
> AbstractPageStore.java:133)
> at
> org.apache.wicket.pageStore.DefaultPageStore.createSerializedPage(
> DefaultPageStore.java:281)
> at
> org.apache.wicket.pageStore.DefaultPageStore.storePage(
> DefaultPageStore.java:61)
> at
> org.apache.wicket.pageStore.AsynchronousPageStore$PageSavingRunnable.run(
> AsynchronousPageStore.java:225)
> at java.lang.Thread.run(Thread.java:748)
>
>
> But none of them look bad enough to stop the app.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Mon, Jul 31, 2017 at 9:28 PM, Sebastien <se...@gmail.com> wrote:
>
> > Hi Martin,
> >
> > Yes, that's what I was referring to.
> > What I'm afraid of, is that this start & stop script may hide an
> underlying
> > problem... Do you remember such instabilities with examples7.x?
> >
> > Thanks & best regards,
> > Sebastien.
> >
> > On Mon, Jul 31, 2017 at 8:18 PM, Martin Grigorov <mg...@apache.org>
> > wrote:
> >
> > > Hi Sebastien,
> > >
> > > Do you talk about the OpenShift deployment of examples8x ?
> > > I've added start and stop action hook scripts for it and since then it
> > > seems to work fine.
> > >
> > > Martin Grigorov
> > > Wicket Training and Consulting
> > > https://twitter.com/mtgrigorov
> > >
> >
>
Re: Wicket 8 (M7) release
Posted by Maxim Solodovnik <so...@gmail.com>.
+1 for M7
WBR, Maxim
(from mobile, sorry for the typos)
On Aug 4, 2017 22:12, "Andrea Del Bene" <an...@gmail.com> wrote:
> Hi,
>
> I think we are ready to promote Wicket 8 to GA but I would wait for
> September as August is usually a very quite month (at least in Europe) so
> it risks to be overlooked. But I have no objection to prepare a M7 in the
> meantime.
>
> What do you think?
>
Re: Wicket 8 (M7) release
Posted by Andrea Del Bene <an...@gmail.com>.
Hi,
I think we are ready to promote Wicket 8 to GA but I would wait for
September as August is usually a very quite month (at least in Europe) so
it risks to be overlooked. But I have no objection to prepare a M7 in the
meantime.
What do you think?
Re: Wicket 8 (M7) release
Posted by Korbinian Bachl <ko...@whiskyworld.de>.
Hi,
our dev system is running 8 snapshot now for about 2 weeks without any problem. I would like to push 8 into production, but not before M7 is here as I dont want a production to depend on a snapshot - any chance M7 will get out the next days?
Best,
KB
----- Ursprüngliche Mail -----
> Von: "Andrea Del Bene" <an...@gmail.com>
> An: dev@wicket.apache.org
> Gesendet: Montag, 31. Juli 2017 21:00:56
> Betreff: Re: Wicket 8 (M7) release
> Hi,
>
> as Martin said the 8.x examples site is running fine for a while now.
> Beside this, also my user guide examples site is running without any
> problem since I did the restyling, which was almost a month ago.
>
> Andrea.
>
>
> On 31/07/2017 20:43, Martin Grigorov wrote:
>> examples7.x use Tomcat image from OpenShift, and it has the scripts by
>> default.
>>
>> I think any of the free providers (like OpenShift, Heroku, ...) shutdown
>> the app if it is not used for some time. When someone requests the app they
>> start it again. I think this is what was happening here.
>>
>> I've just checked the logs of examples8x and there are some interesting
>> problems:
>>
>> 1.
>> Caused by: java.lang.RuntimeException: An error occurred while getting the
>> model object for Component: [Component id = word, page =
>> org.apache.wicket.examples.hangman.Guess, path = word, type =
>> org.apache.wicket.markup.html.basic.Label, isVisible = true, isVersioned =
>> false, markup = [markup =
>> file:/var/lib/openshift/592dc27b89f5cfabc700006d/app-root/data/apache-tomcat-8.5.15/webapps/ROOT/WEB-INF/classes/org/apache/wicket/examples/hangman/Guess.html
>> <span wicket:id="word">WICK_T</span>, index = 0, current = '<span
>> wicket:id="word">' (line 0, column 0)]]
>> at
>> org.apache.wicket.Component.getDefaultModelObject(Component.java:1651)
>> at
>> org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1672)
>> at
>> org.apache.wicket.markup.html.basic.Label.onComponentTagBody(Label.java:115)
>> at
>> org.apache.wicket.markup.html.panel.DefaultMarkupSourcingStrategy.onComponentTagBody(DefaultMarkupSourcingStrategy.java:70)
>> at
>> org.apache.wicket.Component.internalRenderComponent(Component.java:2595)
>> ... 40 more
>> Caused by: java.lang.NullPointerException
>> at
>> org.apache.wicket.examples.hangman.Guess.lambda$new$1f219a47$1(Guess.java:45)
>> at
>> org.apache.wicket.Component.getDefaultModelObject(Component.java:1644)
>>
>> 2.
>> ERROR - DefaultExceptionMapper - Unexpected error occurred
>> org.jboss.weld.context.NonexistentConversationException: WELD-000321: No
>> conversation found to restore for id 2
>> at
>> org.jboss.weld.context.AbstractConversationContext.initialize(AbstractConversationContext.java:240)
>> at
>> org.jboss.weld.context.http.LazyHttpConversationContextImpl.initialize(LazyHttpConversationContextImpl.java:90)
>> at
>> org.jboss.weld.context.http.LazyHttpConversationContextImpl.checkContextInitialized(LazyHttpConversationContextImpl.java:124)
>> at
>> org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:483)
>> at
>> org.jboss.weld.bean.builtin.ConversationBean.newInstance(ConversationBean.java:31)
>> at
>> org.jboss.weld.bean.builtin.ConversationBean.newInstance(ConversationBean.java:16)
>> at
>> org.jboss.weld.bean.builtin.AbstractDecorableBuiltInBean.create(AbstractDecorableBuiltInBean.java:52)
>> at
>> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>> at
>> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>> at
>> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
>> at
>> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99)
>> at
>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99)
>> at
>> org.jboss.weldx.enterprise.context.Conversation$1584357708$Proxy$_$$_WeldClientProxy.getId(Unknown
>> Source)
>> at
>> org.apache.wicket.cdi.ConversationPropagator.onRequestHandlerResolved(ConversationPropagator.java:108)
>>
>> 3. (fixed already)
>> ERROR - DefaultExceptionMapper - Unexpected error occurred
>> java.lang.NullPointerException
>> at
>> org.apache.wicket.core.request.handler.PageProvider.getPageClass(PageProvider.java:261)
>> at
>> org.apache.wicket.core.request.handler.RenderPageRequestHandler.getPageClass(RenderPageRequestHandler.java:163)
>>
>> 4. This one needs attention !
>> ERROR - JavaSerializer - error writing object [Page class =
>> org.apache.wicket.examples.tree.NestedTreePage, id = 0, render count = 1]:
>> null
>> java.util.ConcurrentModificationException
>> at java.util.ArrayList.writeObject(ArrayList.java:766)
>> at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>> java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028)
>> at
>> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
>> at
>> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>> at
>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>> at
>> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>> at
>> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>> at
>> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>> at
>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>> at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
>> at
>> org.apache.wicket.serialize.java.JavaSerializer$SerializationCheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:368)
>> at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
>> at
>> org.apache.wicket.serialize.java.JavaSerializer.serialize(JavaSerializer.java:82)
>> at
>> org.apache.wicket.pageStore.AbstractPageStore.serializePage(AbstractPageStore.java:133)
>> at
>> org.apache.wicket.pageStore.DefaultPageStore.createSerializedPage(DefaultPageStore.java:281)
>> at
>> org.apache.wicket.pageStore.DefaultPageStore.storePage(DefaultPageStore.java:61)
>> at
>> org.apache.wicket.pageStore.AsynchronousPageStore$PageSavingRunnable.run(AsynchronousPageStore.java:225)
>> at java.lang.Thread.run(Thread.java:748)
>>
>>
>> But none of them look bad enough to stop the app.
>>
>> Martin Grigorov
>> Wicket Training and Consulting
>> https://twitter.com/mtgrigorov
>>
>> On Mon, Jul 31, 2017 at 9:28 PM, Sebastien <se...@gmail.com> wrote:
>>
>>> Hi Martin,
>>>
>>> Yes, that's what I was referring to.
>>> What I'm afraid of, is that this start & stop script may hide an underlying
>>> problem... Do you remember such instabilities with examples7.x?
>>>
>>> Thanks & best regards,
>>> Sebastien.
>>>
>>> On Mon, Jul 31, 2017 at 8:18 PM, Martin Grigorov <mg...@apache.org>
>>> wrote:
>>>
>>>> Hi Sebastien,
>>>>
>>>> Do you talk about the OpenShift deployment of examples8x ?
>>>> I've added start and stop action hook scripts for it and since then it
>>>> seems to work fine.
>>>>
>>>> Martin Grigorov
>>>> Wicket Training and Consulting
>>>> https://twitter.com/mtgrigorov
Re: Wicket 8 (M7) release
Posted by Andrea Del Bene <an...@gmail.com>.
Hi,
as Martin said the 8.x examples site is running fine for a while now.
Beside this, also my user guide examples site is running without any
problem since I did the restyling, which was almost a month ago.
Andrea.
On 31/07/2017 20:43, Martin Grigorov wrote:
> examples7.x use Tomcat image from OpenShift, and it has the scripts by
> default.
>
> I think any of the free providers (like OpenShift, Heroku, ...) shutdown
> the app if it is not used for some time. When someone requests the app they
> start it again. I think this is what was happening here.
>
> I've just checked the logs of examples8x and there are some interesting
> problems:
>
> 1.
> Caused by: java.lang.RuntimeException: An error occurred while getting the
> model object for Component: [Component id = word, page =
> org.apache.wicket.examples.hangman.Guess, path = word, type =
> org.apache.wicket.markup.html.basic.Label, isVisible = true, isVersioned =
> false, markup = [markup =
> file:/var/lib/openshift/592dc27b89f5cfabc700006d/app-root/data/apache-tomcat-8.5.15/webapps/ROOT/WEB-INF/classes/org/apache/wicket/examples/hangman/Guess.html
> <span wicket:id="word">WICK_T</span>, index = 0, current = '<span
> wicket:id="word">' (line 0, column 0)]]
> at
> org.apache.wicket.Component.getDefaultModelObject(Component.java:1651)
> at
> org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1672)
> at
> org.apache.wicket.markup.html.basic.Label.onComponentTagBody(Label.java:115)
> at
> org.apache.wicket.markup.html.panel.DefaultMarkupSourcingStrategy.onComponentTagBody(DefaultMarkupSourcingStrategy.java:70)
> at
> org.apache.wicket.Component.internalRenderComponent(Component.java:2595)
> ... 40 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.wicket.examples.hangman.Guess.lambda$new$1f219a47$1(Guess.java:45)
> at
> org.apache.wicket.Component.getDefaultModelObject(Component.java:1644)
>
> 2.
> ERROR - DefaultExceptionMapper - Unexpected error occurred
> org.jboss.weld.context.NonexistentConversationException: WELD-000321: No
> conversation found to restore for id 2
> at
> org.jboss.weld.context.AbstractConversationContext.initialize(AbstractConversationContext.java:240)
> at
> org.jboss.weld.context.http.LazyHttpConversationContextImpl.initialize(LazyHttpConversationContextImpl.java:90)
> at
> org.jboss.weld.context.http.LazyHttpConversationContextImpl.checkContextInitialized(LazyHttpConversationContextImpl.java:124)
> at
> org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:483)
> at
> org.jboss.weld.bean.builtin.ConversationBean.newInstance(ConversationBean.java:31)
> at
> org.jboss.weld.bean.builtin.ConversationBean.newInstance(ConversationBean.java:16)
> at
> org.jboss.weld.bean.builtin.AbstractDecorableBuiltInBean.create(AbstractDecorableBuiltInBean.java:52)
> at
> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> at
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
> at
> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> at
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99)
> at
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99)
> at
> org.jboss.weldx.enterprise.context.Conversation$1584357708$Proxy$_$$_WeldClientProxy.getId(Unknown
> Source)
> at
> org.apache.wicket.cdi.ConversationPropagator.onRequestHandlerResolved(ConversationPropagator.java:108)
>
> 3. (fixed already)
> ERROR - DefaultExceptionMapper - Unexpected error occurred
> java.lang.NullPointerException
> at
> org.apache.wicket.core.request.handler.PageProvider.getPageClass(PageProvider.java:261)
> at
> org.apache.wicket.core.request.handler.RenderPageRequestHandler.getPageClass(RenderPageRequestHandler.java:163)
>
> 4. This one needs attention !
> ERROR - JavaSerializer - error writing object [Page class =
> org.apache.wicket.examples.tree.NestedTreePage, id = 0, render count = 1]:
> null
> java.util.ConcurrentModificationException
> at java.util.ArrayList.writeObject(ArrayList.java:766)
> at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at
> org.apache.wicket.serialize.java.JavaSerializer$SerializationCheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:368)
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
> at
> org.apache.wicket.serialize.java.JavaSerializer.serialize(JavaSerializer.java:82)
> at
> org.apache.wicket.pageStore.AbstractPageStore.serializePage(AbstractPageStore.java:133)
> at
> org.apache.wicket.pageStore.DefaultPageStore.createSerializedPage(DefaultPageStore.java:281)
> at
> org.apache.wicket.pageStore.DefaultPageStore.storePage(DefaultPageStore.java:61)
> at
> org.apache.wicket.pageStore.AsynchronousPageStore$PageSavingRunnable.run(AsynchronousPageStore.java:225)
> at java.lang.Thread.run(Thread.java:748)
>
>
> But none of them look bad enough to stop the app.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Mon, Jul 31, 2017 at 9:28 PM, Sebastien <se...@gmail.com> wrote:
>
>> Hi Martin,
>>
>> Yes, that's what I was referring to.
>> What I'm afraid of, is that this start & stop script may hide an underlying
>> problem... Do you remember such instabilities with examples7.x?
>>
>> Thanks & best regards,
>> Sebastien.
>>
>> On Mon, Jul 31, 2017 at 8:18 PM, Martin Grigorov <mg...@apache.org>
>> wrote:
>>
>>> Hi Sebastien,
>>>
>>> Do you talk about the OpenShift deployment of examples8x ?
>>> I've added start and stop action hook scripts for it and since then it
>>> seems to work fine.
>>>
>>> Martin Grigorov
>>> Wicket Training and Consulting
>>> https://twitter.com/mtgrigorov
>>>
Re: Wicket 8 (M7) release
Posted by Martin Grigorov <mg...@apache.org>.
examples7.x use Tomcat image from OpenShift, and it has the scripts by
default.
I think any of the free providers (like OpenShift, Heroku, ...) shutdown
the app if it is not used for some time. When someone requests the app they
start it again. I think this is what was happening here.
I've just checked the logs of examples8x and there are some interesting
problems:
1.
Caused by: java.lang.RuntimeException: An error occurred while getting the
model object for Component: [Component id = word, page =
org.apache.wicket.examples.hangman.Guess, path = word, type =
org.apache.wicket.markup.html.basic.Label, isVisible = true, isVersioned =
false, markup = [markup =
file:/var/lib/openshift/592dc27b89f5cfabc700006d/app-root/data/apache-tomcat-8.5.15/webapps/ROOT/WEB-INF/classes/org/apache/wicket/examples/hangman/Guess.html
<span wicket:id="word">WICK_T</span>, index = 0, current = '<span
wicket:id="word">' (line 0, column 0)]]
at
org.apache.wicket.Component.getDefaultModelObject(Component.java:1651)
at
org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1672)
at
org.apache.wicket.markup.html.basic.Label.onComponentTagBody(Label.java:115)
at
org.apache.wicket.markup.html.panel.DefaultMarkupSourcingStrategy.onComponentTagBody(DefaultMarkupSourcingStrategy.java:70)
at
org.apache.wicket.Component.internalRenderComponent(Component.java:2595)
... 40 more
Caused by: java.lang.NullPointerException
at
org.apache.wicket.examples.hangman.Guess.lambda$new$1f219a47$1(Guess.java:45)
at
org.apache.wicket.Component.getDefaultModelObject(Component.java:1644)
2.
ERROR - DefaultExceptionMapper - Unexpected error occurred
org.jboss.weld.context.NonexistentConversationException: WELD-000321: No
conversation found to restore for id 2
at
org.jboss.weld.context.AbstractConversationContext.initialize(AbstractConversationContext.java:240)
at
org.jboss.weld.context.http.LazyHttpConversationContextImpl.initialize(LazyHttpConversationContextImpl.java:90)
at
org.jboss.weld.context.http.LazyHttpConversationContextImpl.checkContextInitialized(LazyHttpConversationContextImpl.java:124)
at
org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:483)
at
org.jboss.weld.bean.builtin.ConversationBean.newInstance(ConversationBean.java:31)
at
org.jboss.weld.bean.builtin.ConversationBean.newInstance(ConversationBean.java:16)
at
org.jboss.weld.bean.builtin.AbstractDecorableBuiltInBean.create(AbstractDecorableBuiltInBean.java:52)
at
org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
at
org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
at
org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99)
at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99)
at
org.jboss.weldx.enterprise.context.Conversation$1584357708$Proxy$_$$_WeldClientProxy.getId(Unknown
Source)
at
org.apache.wicket.cdi.ConversationPropagator.onRequestHandlerResolved(ConversationPropagator.java:108)
3. (fixed already)
ERROR - DefaultExceptionMapper - Unexpected error occurred
java.lang.NullPointerException
at
org.apache.wicket.core.request.handler.PageProvider.getPageClass(PageProvider.java:261)
at
org.apache.wicket.core.request.handler.RenderPageRequestHandler.getPageClass(RenderPageRequestHandler.java:163)
4. This one needs attention !
ERROR - JavaSerializer - error writing object [Page class =
org.apache.wicket.examples.tree.NestedTreePage, id = 0, render count = 1]:
null
java.util.ConcurrentModificationException
at java.util.ArrayList.writeObject(ArrayList.java:766)
at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
at
org.apache.wicket.serialize.java.JavaSerializer$SerializationCheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:368)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
at
org.apache.wicket.serialize.java.JavaSerializer.serialize(JavaSerializer.java:82)
at
org.apache.wicket.pageStore.AbstractPageStore.serializePage(AbstractPageStore.java:133)
at
org.apache.wicket.pageStore.DefaultPageStore.createSerializedPage(DefaultPageStore.java:281)
at
org.apache.wicket.pageStore.DefaultPageStore.storePage(DefaultPageStore.java:61)
at
org.apache.wicket.pageStore.AsynchronousPageStore$PageSavingRunnable.run(AsynchronousPageStore.java:225)
at java.lang.Thread.run(Thread.java:748)
But none of them look bad enough to stop the app.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Jul 31, 2017 at 9:28 PM, Sebastien <se...@gmail.com> wrote:
> Hi Martin,
>
> Yes, that's what I was referring to.
> What I'm afraid of, is that this start & stop script may hide an underlying
> problem... Do you remember such instabilities with examples7.x?
>
> Thanks & best regards,
> Sebastien.
>
> On Mon, Jul 31, 2017 at 8:18 PM, Martin Grigorov <mg...@apache.org>
> wrote:
>
> > Hi Sebastien,
> >
> > Do you talk about the OpenShift deployment of examples8x ?
> > I've added start and stop action hook scripts for it and since then it
> > seems to work fine.
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
>
Re: Wicket 8 (M7) release
Posted by Sebastien <se...@gmail.com>.
Hi Martin,
Yes, that's what I was referring to.
What I'm afraid of, is that this start & stop script may hide an underlying
problem... Do you remember such instabilities with examples7.x?
Thanks & best regards,
Sebastien.
On Mon, Jul 31, 2017 at 8:18 PM, Martin Grigorov <mg...@apache.org>
wrote:
> Hi Sebastien,
>
> Do you talk about the OpenShift deployment of examples8x ?
> I've added start and stop action hook scripts for it and since then it
> seems to work fine.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
Re: Wicket 8 (M7) release
Posted by Martin Grigorov <mg...@apache.org>.
Hi Sebastien,
Do you talk about the OpenShift deployment of examples8x ?
I've added start and stop action hook scripts for it and since then it
seems to work fine.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Jul 31, 2017 at 7:18 PM, Sebastien <se...@gmail.com> wrote:
> Hi,
>
> Does the investigation about the server recurring downtime give something ?
> @andrea ?
>
> I did have a recurring crash in my demo app in wicket 8.x, which does not
> seem to repro in wicket 7.x.
> As said earlier, I did not had time to profile on my side so I was counting
> on Andrea's investigation to know if there could an issue in wicket 8
> itself...
>
> Best regards,
> Sebastien
>
> On Jul 31, 2017 5:31 PM, "Martin Grigorov" <mg...@apache.org> wrote:
>
> > +1 from me for 8.0.0
> > I don't have any planned API breaks in mind.
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Mon, Jul 31, 2017 at 6:19 PM, Tobias Soloschenko <
> > tobiassoloschenko@googlemail.com> wrote:
> >
> > > Hi,
> > >
> > > > Am 31.07.2017 um 17:18 schrieb Maxim Solodovnik <
> solomax666@gmail.com
> > >:
> > > >
> > > > Sure
> > > > Sorry Tobias, I wasn't aware there is something in progress :(
> > >
> > > Oh I didn’t mentioned it, yet. So it was my fault. :-)
> > >
> > > >
> > > > On Mon, Jul 31, 2017 at 10:16 PM, Tobias Soloschenko
> > > > <to...@googlemail.com> wrote:
> > > >> Hi,
> > > >>
> > > >> I am going to provide a patch to wicket-8.x with some changes
> > regarding
> > > the push API, today.
> > > >>
> > > >> Maybe it is possible that it can be reviewed and merged first?
> > > >>
> > > >> kind regards
> > > >>
> > > >> Tobias
> > > >>
> > > >>> Am 31.07.2017 um 17:14 schrieb Maxim Solodovnik <
> > solomax666@gmail.com
> > > >:
> > > >>>
> > > >>> Hello All,
> > > >>>
> > > >>> As I can see there are no issues against M7, maybe it's time for
> > > release?
> > > >>> Maybe it also worth to release 8.0.0?
> > > >>>
> > > >>> --
> > > >>> WBR
> > > >>> Maxim aka solomax
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> > >
> > > kind regards
> > >
> > > Tobias
> > >
> > >
> >
>
Re: Wicket 8 (M7) release
Posted by Sebastien <se...@gmail.com>.
Good to know! Thanks Maxim!
Re: Wicket 8 (M7) release
Posted by Maxim Solodovnik <so...@gmail.com>.
Our main app works on 8.x (both M6 and 8.0.0-SNAPSHOT) flawlessly
without restarts
On Mon, Jul 31, 2017 at 11:18 PM, Sebastien <se...@gmail.com> wrote:
> Hi,
>
> Does the investigation about the server recurring downtime give something ?
> @andrea ?
>
> I did have a recurring crash in my demo app in wicket 8.x, which does not
> seem to repro in wicket 7.x.
> As said earlier, I did not had time to profile on my side so I was counting
> on Andrea's investigation to know if there could an issue in wicket 8
> itself...
>
> Best regards,
> Sebastien
>
> On Jul 31, 2017 5:31 PM, "Martin Grigorov" <mg...@apache.org> wrote:
>
>> +1 from me for 8.0.0
>> I don't have any planned API breaks in mind.
>>
>> Martin Grigorov
>> Wicket Training and Consulting
>> https://twitter.com/mtgrigorov
>>
>> On Mon, Jul 31, 2017 at 6:19 PM, Tobias Soloschenko <
>> tobiassoloschenko@googlemail.com> wrote:
>>
>> > Hi,
>> >
>> > > Am 31.07.2017 um 17:18 schrieb Maxim Solodovnik <solomax666@gmail.com
>> >:
>> > >
>> > > Sure
>> > > Sorry Tobias, I wasn't aware there is something in progress :(
>> >
>> > Oh I didn’t mentioned it, yet. So it was my fault. :-)
>> >
>> > >
>> > > On Mon, Jul 31, 2017 at 10:16 PM, Tobias Soloschenko
>> > > <to...@googlemail.com> wrote:
>> > >> Hi,
>> > >>
>> > >> I am going to provide a patch to wicket-8.x with some changes
>> regarding
>> > the push API, today.
>> > >>
>> > >> Maybe it is possible that it can be reviewed and merged first?
>> > >>
>> > >> kind regards
>> > >>
>> > >> Tobias
>> > >>
>> > >>> Am 31.07.2017 um 17:14 schrieb Maxim Solodovnik <
>> solomax666@gmail.com
>> > >:
>> > >>>
>> > >>> Hello All,
>> > >>>
>> > >>> As I can see there are no issues against M7, maybe it's time for
>> > release?
>> > >>> Maybe it also worth to release 8.0.0?
>> > >>>
>> > >>> --
>> > >>> WBR
>> > >>> Maxim aka solomax
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > > WBR
>> > > Maxim aka solomax
>> >
>> > kind regards
>> >
>> > Tobias
>> >
>> >
>>
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Sebastien <se...@gmail.com>.
Hi,
Does the investigation about the server recurring downtime give something ?
@andrea ?
I did have a recurring crash in my demo app in wicket 8.x, which does not
seem to repro in wicket 7.x.
As said earlier, I did not had time to profile on my side so I was counting
on Andrea's investigation to know if there could an issue in wicket 8
itself...
Best regards,
Sebastien
On Jul 31, 2017 5:31 PM, "Martin Grigorov" <mg...@apache.org> wrote:
> +1 from me for 8.0.0
> I don't have any planned API breaks in mind.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Mon, Jul 31, 2017 at 6:19 PM, Tobias Soloschenko <
> tobiassoloschenko@googlemail.com> wrote:
>
> > Hi,
> >
> > > Am 31.07.2017 um 17:18 schrieb Maxim Solodovnik <solomax666@gmail.com
> >:
> > >
> > > Sure
> > > Sorry Tobias, I wasn't aware there is something in progress :(
> >
> > Oh I didn’t mentioned it, yet. So it was my fault. :-)
> >
> > >
> > > On Mon, Jul 31, 2017 at 10:16 PM, Tobias Soloschenko
> > > <to...@googlemail.com> wrote:
> > >> Hi,
> > >>
> > >> I am going to provide a patch to wicket-8.x with some changes
> regarding
> > the push API, today.
> > >>
> > >> Maybe it is possible that it can be reviewed and merged first?
> > >>
> > >> kind regards
> > >>
> > >> Tobias
> > >>
> > >>> Am 31.07.2017 um 17:14 schrieb Maxim Solodovnik <
> solomax666@gmail.com
> > >:
> > >>>
> > >>> Hello All,
> > >>>
> > >>> As I can see there are no issues against M7, maybe it's time for
> > release?
> > >>> Maybe it also worth to release 8.0.0?
> > >>>
> > >>> --
> > >>> WBR
> > >>> Maxim aka solomax
> > >>
> > >
> > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> >
> > kind regards
> >
> > Tobias
> >
> >
>
Re: Wicket 8 (M7) release
Posted by Martin Grigorov <mg...@apache.org>.
+1 from me for 8.0.0
I don't have any planned API breaks in mind.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Jul 31, 2017 at 6:19 PM, Tobias Soloschenko <
tobiassoloschenko@googlemail.com> wrote:
> Hi,
>
> > Am 31.07.2017 um 17:18 schrieb Maxim Solodovnik <so...@gmail.com>:
> >
> > Sure
> > Sorry Tobias, I wasn't aware there is something in progress :(
>
> Oh I didn’t mentioned it, yet. So it was my fault. :-)
>
> >
> > On Mon, Jul 31, 2017 at 10:16 PM, Tobias Soloschenko
> > <to...@googlemail.com> wrote:
> >> Hi,
> >>
> >> I am going to provide a patch to wicket-8.x with some changes regarding
> the push API, today.
> >>
> >> Maybe it is possible that it can be reviewed and merged first?
> >>
> >> kind regards
> >>
> >> Tobias
> >>
> >>> Am 31.07.2017 um 17:14 schrieb Maxim Solodovnik <solomax666@gmail.com
> >:
> >>>
> >>> Hello All,
> >>>
> >>> As I can see there are no issues against M7, maybe it's time for
> release?
> >>> Maybe it also worth to release 8.0.0?
> >>>
> >>> --
> >>> WBR
> >>> Maxim aka solomax
> >>
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
> kind regards
>
> Tobias
>
>
Re: Wicket 8 (M7) release
Posted by Tobias Soloschenko <to...@googlemail.com>.
Hi,
> Am 31.07.2017 um 17:18 schrieb Maxim Solodovnik <so...@gmail.com>:
>
> Sure
> Sorry Tobias, I wasn't aware there is something in progress :(
Oh I didn’t mentioned it, yet. So it was my fault. :-)
>
> On Mon, Jul 31, 2017 at 10:16 PM, Tobias Soloschenko
> <to...@googlemail.com> wrote:
>> Hi,
>>
>> I am going to provide a patch to wicket-8.x with some changes regarding the push API, today.
>>
>> Maybe it is possible that it can be reviewed and merged first?
>>
>> kind regards
>>
>> Tobias
>>
>>> Am 31.07.2017 um 17:14 schrieb Maxim Solodovnik <so...@gmail.com>:
>>>
>>> Hello All,
>>>
>>> As I can see there are no issues against M7, maybe it's time for release?
>>> Maybe it also worth to release 8.0.0?
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>
>
>
>
> --
> WBR
> Maxim aka solomax
kind regards
Tobias
Re: Wicket 8 (M7) release
Posted by Maxim Solodovnik <so...@gmail.com>.
Sure
Sorry Tobias, I wasn't aware there is something in progress :(
On Mon, Jul 31, 2017 at 10:16 PM, Tobias Soloschenko
<to...@googlemail.com> wrote:
> Hi,
>
> I am going to provide a patch to wicket-8.x with some changes regarding the push API, today.
>
> Maybe it is possible that it can be reviewed and merged first?
>
> kind regards
>
> Tobias
>
>> Am 31.07.2017 um 17:14 schrieb Maxim Solodovnik <so...@gmail.com>:
>>
>> Hello All,
>>
>> As I can see there are no issues against M7, maybe it's time for release?
>> Maybe it also worth to release 8.0.0?
>>
>> --
>> WBR
>> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: Wicket 8 (M7) release
Posted by Tobias Soloschenko <to...@googlemail.com>.
Hi,
I am going to provide a patch to wicket-8.x with some changes regarding the push API, today.
Maybe it is possible that it can be reviewed and merged first?
kind regards
Tobias
> Am 31.07.2017 um 17:14 schrieb Maxim Solodovnik <so...@gmail.com>:
>
> Hello All,
>
> As I can see there are no issues against M7, maybe it's time for release?
> Maybe it also worth to release 8.0.0?
>
> --
> WBR
> Maxim aka solomax