Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-30 Thread Tobias Soloschenko 

Hi,

good to hear and thanks for the feedback.

kind regards

Tobias

Am 30.10.16 um 10:04 schrieb Francesco Chicchiriccò:


On 2016-10-28 14:37 (+0100), Martin Grigorov  wrote:

On Fri, Oct 28, 2016 at 12:01 PM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:


On 2016-10-27 14:18 (+0200), Martin Grigorov  wrote:

Hi,

Good news!
It is a bug in Wicket Bootstrap:
https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-

7.x/bootstrap-core/src/main/java/de/agilecoders/wicket/
core/markup/html/bootstrap/dialog/Alert.html#L10

This  uses a Label in Java. (No idea why).
Since https://issues.apache.org/jira/browse/WICKET-6219 this is not
possible.

Hi,
we are still having problems when upgrading to Wicket 7.5.0 [1], possibly
because of the same reason as above (e.g. WICKET-6219): in deployment mode
everything works fine, but in development mode a stacktrace is reported (as
shown in [1]): could you please explain what is needed to change, taking
[2] as reference?


I've added a comment in the ticket explaining what was the problem in
Wicket Bootstrap.
Looking at AbstractFieldPanel and its specializations I have the feeling
the problem is the same.

FYI we have solved all Syncope admin console issues with Wicket 7.5.0 and 
resolved SYNCOPE-962.

The actual fix was

https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blobdiff;f=client/console/src/main/resources/org/apache/syncope/client/console/wicket/markup/html/bootstrap/dialog/BaseModal.html;h=ddf2c9ef8ee4c311e0578862cf7d887fa94e91d5;hp=30689677a83ff9715603cde96e2b1ebe5c7dd30b;hb=dd9e95e;hpb=1bc21e3eb330f44c490baf3448565b4fa6598308

for modal windows.


Anyway we could improve the error message by adding the relative path to
the page, so it is more easier to find which component has problems.

Oh, this would be good anyway.
Regards.


[1] https://issues.apache.org/jira/browse/SYNCOPE-962
[2] https://github.com/apache/syncope/blob/2_0_X/client/
console/src/main/resources/org/apache/syncope/client/
console/wicket/markup/html/form/AbstractFieldPanel.html

-
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: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-30 Thread Francesco Chicchiriccò 


On 2016-10-28 14:37 (+0100), Martin Grigorov  wrote: 
> On Fri, Oct 28, 2016 at 12:01 PM, Francesco Chicchiriccò <
> ilgro...@apache.org> wrote:
> 
> > On 2016-10-27 14:18 (+0200), Martin Grigorov  wrote:
> > > Hi,
> > >
> > > Good news!
> > > It is a bug in Wicket Bootstrap:
> > > https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-
> > 7.x/bootstrap-core/src/main/java/de/agilecoders/wicket/
> > core/markup/html/bootstrap/dialog/Alert.html#L10
> > >
> > > This  uses a Label in Java. (No idea why).
> > > Since https://issues.apache.org/jira/browse/WICKET-6219 this is not
> > > possible.
> >
> > Hi,
> > we are still having problems when upgrading to Wicket 7.5.0 [1], possibly
> > because of the same reason as above (e.g. WICKET-6219): in deployment mode
> > everything works fine, but in development mode a stacktrace is reported (as
> > shown in [1]): could you please explain what is needed to change, taking
> > [2] as reference?
> >
> 
> I've added a comment in the ticket explaining what was the problem in
> Wicket Bootstrap.
> Looking at AbstractFieldPanel and its specializations I have the feeling
> the problem is the same.

FYI we have solved all Syncope admin console issues with Wicket 7.5.0 and 
resolved SYNCOPE-962.

The actual fix was

https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blobdiff;f=client/console/src/main/resources/org/apache/syncope/client/console/wicket/markup/html/bootstrap/dialog/BaseModal.html;h=ddf2c9ef8ee4c311e0578862cf7d887fa94e91d5;hp=30689677a83ff9715603cde96e2b1ebe5c7dd30b;hb=dd9e95e;hpb=1bc21e3eb330f44c490baf3448565b4fa6598308

for modal windows.

> Anyway we could improve the error message by adding the relative path to
> the page, so it is more easier to find which component has problems.

Oh, this would be good anyway.
Regards.

> > [1] https://issues.apache.org/jira/browse/SYNCOPE-962
> > [2] https://github.com/apache/syncope/blob/2_0_X/client/
> > console/src/main/resources/org/apache/syncope/client/
> > console/wicket/markup/html/form/AbstractFieldPanel.html

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-28 Thread Martin Grigorov 
On Fri, Oct 28, 2016 at 12:01 PM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:

> On 2016-10-27 14:18 (+0200), Martin Grigorov  wrote:
> > Hi,
> >
> > Good news!
> > It is a bug in Wicket Bootstrap:
> > https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-
> 7.x/bootstrap-core/src/main/java/de/agilecoders/wicket/
> core/markup/html/bootstrap/dialog/Alert.html#L10
> >
> > This  uses a Label in Java. (No idea why).
> > Since https://issues.apache.org/jira/browse/WICKET-6219 this is not
> > possible.
>
> Hi,
> we are still having problems when upgrading to Wicket 7.5.0 [1], possibly
> because of the same reason as above (e.g. WICKET-6219): in deployment mode
> everything works fine, but in development mode a stacktrace is reported (as
> shown in [1]): could you please explain what is needed to change, taking
> [2] as reference?
>

I've added a comment in the ticket explaining what was the problem in
Wicket Bootstrap.
Looking at AbstractFieldPanel and its specializations I have the feeling
the problem is the same.
Anyway we could improve the error message by adding the relative path to
the page, so it is more easier to find which component has problems.


>
> Thank you very much.
> Regards.
>
> [1] https://issues.apache.org/jira/browse/SYNCOPE-962
> [2] https://github.com/apache/syncope/blob/2_0_X/client/
> console/src/main/resources/org/apache/syncope/client/
> console/wicket/markup/html/form/AbstractFieldPanel.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-28 Thread Francesco Chicchiriccò 
On 2016-10-27 14:18 (+0200), Martin Grigorov  wrote: 
> Hi,
> 
> Good news!
> It is a bug in Wicket Bootstrap:
> https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-7.x/bootstrap-core/src/main/java/de/agilecoders/wicket/core/markup/html/bootstrap/dialog/Alert.html#L10
> 
> This  uses a Label in Java. (No idea why).
> Since https://issues.apache.org/jira/browse/WICKET-6219 this is not
> possible.

Hi,
we are still having problems when upgrading to Wicket 7.5.0 [1], possibly 
because of the same reason as above (e.g. WICKET-6219): in deployment mode 
everything works fine, but in development mode a stacktrace is reported (as 
shown in [1]): could you please explain what is needed to change, taking [2] as 
reference?

Thank you very much.
Regards.

[1] https://issues.apache.org/jira/browse/SYNCOPE-962
[2] 
https://github.com/apache/syncope/blob/2_0_X/client/console/src/main/resources/org/apache/syncope/client/console/wicket/markup/html/form/AbstractFieldPanel.html

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-27 Thread Joachim Rohde 
Wow. Thanks a lot.

On 10/27/2016 03:17 PM, Martin Grigorov wrote:
> 0.10.11 should be at Maven Central any time soon!
> 
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
> 
> On Thu, Oct 27, 2016 at 3:06 PM, Martin Grigorov 
> wrote:
> 
>> The release script is running...
>>
>> Martin Grigorov
>> Wicket Training and Consulting
>> https://twitter.com/mtgrigorov
>>
>> On Thu, Oct 27, 2016 at 3:03 PM, Francesco Chicchiriccò <
>> ilgro...@apache.org> wrote:
>>
>>>
>>>
>>> On 2016-10-27 14:40 (+0200), Joachim Rohde  wrote:
 Great. Thanks for the fast reply Martin. Do you have already a clue
>>> when a new version of Wicket Bootstrap will be released?
>>>
>>> ..or an easy way to backport your fix?
>>>
>>> Regards.
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>
> 

-- 
SOLVIT GmbH
Joachim Rohde

Softwareentwicklung

Lise-Meitner-Straße 4
24941 Flensburg

Telefon: +49 461 57 49 85 94
Fax: +49 461 57 49 88 99

Geschäftsführung:
Benjamin Klink,
Karsten Paulsen,
Helge Werlein

Amtsgericht Flensburg HRB 9450 FL
St.-Nr.: 15/296/14057 - USt-Id.: DE 283 368 011

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-27 Thread Francois Meillet 
super !

François



> Le 27 oct. 2016 à 15:17, Martin Grigorov  a écrit :
> 
> 0.10.11 should be at Maven Central any time soon!
> 
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
> 
> On Thu, Oct 27, 2016 at 3:06 PM, Martin Grigorov 
> wrote:
> 
>> The release script is running...
>> 
>> Martin Grigorov
>> Wicket Training and Consulting
>> https://twitter.com/mtgrigorov
>> 
>> On Thu, Oct 27, 2016 at 3:03 PM, Francesco Chicchiriccò <
>> ilgro...@apache.org> wrote:
>> 
>>> 
>>> 
>>> On 2016-10-27 14:40 (+0200), Joachim Rohde  wrote:
 Great. Thanks for the fast reply Martin. Do you have already a clue
>>> when a new version of Wicket Bootstrap will be released?
>>> 
>>> ..or an easy way to backport your fix?
>>> 
>>> Regards.
>>> 
>>> 
>>> -
>>> 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: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-27 Thread Martin Grigorov 
0.10.11 should be at Maven Central any time soon!

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Oct 27, 2016 at 3:06 PM, Martin Grigorov 
wrote:

> The release script is running...
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, Oct 27, 2016 at 3:03 PM, Francesco Chicchiriccò <
> ilgro...@apache.org> wrote:
>
>>
>>
>> On 2016-10-27 14:40 (+0200), Joachim Rohde  wrote:
>> > Great. Thanks for the fast reply Martin. Do you have already a clue
>> when a new version of Wicket Bootstrap will be released?
>>
>> ..or an easy way to backport your fix?
>>
>> Regards.
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-27 Thread Martin Grigorov 
The release script is running...

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Oct 27, 2016 at 3:03 PM, Francesco Chicchiriccò  wrote:

>
>
> On 2016-10-27 14:40 (+0200), Joachim Rohde  wrote:
> > Great. Thanks for the fast reply Martin. Do you have already a clue when
> a new version of Wicket Bootstrap will be released?
>
> ..or an easy way to backport your fix?
>
> Regards.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-27 Thread Francesco Chicchiriccò 


On 2016-10-27 14:40 (+0200), Joachim Rohde  wrote: 
> Great. Thanks for the fast reply Martin. Do you have already a clue when a 
> new version of Wicket Bootstrap will be released?

..or an easy way to backport your fix?

Regards.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-27 Thread Joachim Rohde 
Great. Thanks for the fast reply Martin. Do you have already a clue when a new 
version of Wicket Bootstrap will be released?

On 10/27/2016 02:18 PM, Martin Grigorov wrote:
> Hi,
> 
> Good news!
> It is a bug in Wicket Bootstrap:
> https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-7.x/bootstrap-core/src/main/java/de/agilecoders/wicket/core/markup/html/bootstrap/dialog/Alert.html#L10
> 
> This  uses a Label in Java. (No idea why).
> Since https://issues.apache.org/jira/browse/WICKET-6219 this is not
> possible.
> 
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
> 
> On Thu, Oct 27, 2016 at 1:10 PM, Joachim Rohde  wrote:
> 
>> We are having a custom FeedbackPanel which extends from NotificationPanel.
>> After upgrading from Wicket 7.4.0 to 7.5.0 an
>> unexpected runtime exception is thrown as soon as an error message should
>> be rendered (see below).
>>
>> I have created a quickstart with a simple link which demonstrates this
>> behavior. With Wicket 7.4.0 everything works as
>> expected. With Wicket 7.5.0 you'll get an exception.
>>
>> When using the Wicket FeedbackPanel everything works fine. I have no clue
>> if this is a bug in Wicket itself or Wicket
>> Bootstrap. Any help is appreciated.
>>
>> Joachim
>>
>>
>> The generated exception:
>>
>> Unexpected RuntimeException
>>
>> Last cause: The component(s) below failed to render. Possible reasons
>> could be that: 1) you have added a component in
>> code but forgot to reference it in the markup (thus the component will
>> never be rendered), 2) if your components were
>> added in a parent container then make sure the markup for the child
>> container includes them in .
>>
>> 1. [Component id = message]
>>
>> Stacktrace
>>
>> Root cause:
>>
>> org.apache.wicket.WicketRuntimeException: The component(s) below failed
>> to render. Possible reasons could be that: 1)
>> you have added a component in code but forgot to reference it in the
>> markup (thus the component will never be rendered),
>> 2) if your components were added in a parent container then make sure the
>> markup for the child container includes them
>> in .
>>
>> 1. [Component id = message]
>>
>>  at org.apache.wicket.Page.checkRendering(Page.java:666)
>>  at org.apache.wicket.Page.endComponentRender(Page.java:317)
>>  at org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(
>> XmlPartialPageUpdate.java:127)
>>  at org.apache.wicket.page.PartialPageUpdate.writeComponents(
>> PartialPageUpdate.java:248)
>>  at org.apache.wicket.page.PartialPageUpdate.writeTo(
>> PartialPageUpdate.java:161)
>>  at org.apache.wicket.ajax.AjaxRequestHandler.respond(
>> AjaxRequestHandler.java:358)
>>  at org.apache.wicket.request.cycle.RequestCycle$
>> HandlerExecutor.respond(RequestCycle.java:895)
>>  at org.apache.wicket.request.RequestHandlerStack.execute(
>> RequestHandlerStack.java:64)
>>  at org.apache.wicket.request.RequestHandlerStack.execute(
>> RequestHandlerStack.java:97)
>>  at org.apache.wicket.request.cycle.RequestCycle.execute(
>> RequestCycle.java:265)
>>  at org.apache.wicket.request.cycle.RequestCycle.
>> processRequest(RequestCycle.java:222)
>>  at org.apache.wicket.request.cycle.RequestCycle.
>> processRequestAndDetach(RequestCycle.java:293)
>>  at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(
>> WicketFilter.java:261)
>>  at org.apache.wicket.protocol.http.WicketFilter.
>> processRequest(WicketFilter.java:203)
>>  at org.apache.wicket.protocol.http.WicketFilter.doFilter(
>> WicketFilter.java:284)
>>  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
>> ApplicationFilterChain.java:239)
>>  at org.apache.catalina.core.ApplicationFilterChain.doFilter(
>> ApplicationFilterChain.java:206)
>>  at org.apache.catalina.core.StandardWrapperValve.invoke(
>> StandardWrapperValve.java:217)
>>  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:142)
>>  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:518)
>>  at org.apache.coyote.http11.AbstractHttp11Processor.process(
>> AbstractHttp11Processor.java:1091)
>>  at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.
>> process(AbstractProtocol.java:673)
>>  at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
>> doRun(NioEndpoint.java:1500)
>>  at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-27 Thread Martin Grigorov 
https://github.com/l0rdn1kk0n/wicket-bootstrap/issues/642

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Oct 27, 2016 at 2:18 PM, Martin Grigorov 
wrote:

> Hi,
>
> Good news!
> It is a bug in Wicket Bootstrap: https://github.com/
> l0rdn1kk0n/wicket-bootstrap/blob/wicket-7.x/bootstrap-
> core/src/main/java/de/agilecoders/wicket/core/
> markup/html/bootstrap/dialog/Alert.html#L10
> This  uses a Label in Java. (No idea why).
> Since https://issues.apache.org/jira/browse/WICKET-6219 this is not
> possible.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, Oct 27, 2016 at 1:10 PM, Joachim Rohde  wrote:
>
>> We are having a custom FeedbackPanel which extends from
>> NotificationPanel. After upgrading from Wicket 7.4.0 to 7.5.0 an
>> unexpected runtime exception is thrown as soon as an error message should
>> be rendered (see below).
>>
>> I have created a quickstart with a simple link which demonstrates this
>> behavior. With Wicket 7.4.0 everything works as
>> expected. With Wicket 7.5.0 you'll get an exception.
>>
>> When using the Wicket FeedbackPanel everything works fine. I have no clue
>> if this is a bug in Wicket itself or Wicket
>> Bootstrap. Any help is appreciated.
>>
>> Joachim
>>
>>
>> The generated exception:
>>
>> Unexpected RuntimeException
>>
>> Last cause: The component(s) below failed to render. Possible reasons
>> could be that: 1) you have added a component in
>> code but forgot to reference it in the markup (thus the component will
>> never be rendered), 2) if your components were
>> added in a parent container then make sure the markup for the child
>> container includes them in .
>>
>> 1. [Component id = message]
>>
>> Stacktrace
>>
>> Root cause:
>>
>> org.apache.wicket.WicketRuntimeException: The component(s) below failed
>> to render. Possible reasons could be that: 1)
>> you have added a component in code but forgot to reference it in the
>> markup (thus the component will never be rendered),
>> 2) if your components were added in a parent container then make sure the
>> markup for the child container includes them
>> in .
>>
>> 1. [Component id = message]
>>
>>  at org.apache.wicket.Page.checkRendering(Page.java:666)
>>  at org.apache.wicket.Page.endComponentRender(Page.java:317)
>>  at org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(X
>> mlPartialPageUpdate.java:127)
>>  at org.apache.wicket.page.PartialPageUpdate.writeComponents(Par
>> tialPageUpdate.java:248)
>>  at org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPage
>> Update.java:161)
>>  at org.apache.wicket.ajax.AjaxRequestHandler.respond(AjaxReques
>> tHandler.java:358)
>>  at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor
>> .respond(RequestCycle.java:895)
>>  at org.apache.wicket.request.RequestHandlerStack.execute(Reques
>> tHandlerStack.java:64)
>>  at org.apache.wicket.request.RequestHandlerStack.execute(Reques
>> tHandlerStack.java:97)
>>  at org.apache.wicket.request.cycle.RequestCycle.execute(Request
>> Cycle.java:265)
>>  at org.apache.wicket.request.cycle.RequestCycle.processRequest(
>> RequestCycle.java:222)
>>  at org.apache.wicket.request.cycle.RequestCycle.processRequestA
>> ndDetach(RequestCycle.java:293)
>>  at org.apache.wicket.protocol.http.WicketFilter.processRequestC
>> ycle(WicketFilter.java:261)
>>  at org.apache.wicket.protocol.http.WicketFilter.processRequest(
>> WicketFilter.java:203)
>>  at org.apache.wicket.protocol.http.WicketFilter.doFilter(Wicket
>> Filter.java:284)
>>  at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:239)
>>  at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:206)
>>  at org.apache.catalina.core.StandardWrapperValve.invoke(Standar
>> dWrapperValve.java:217)
>>  at org.apache.catalina.core.StandardContextValve.invoke(Standar
>> dContextValve.java:106)
>>  at org.apache.catalina.authenticator.AuthenticatorBase.invoke(A
>> uthenticatorBase.java:502)
>>  at org.apache.catalina.core.StandardHostValve.invoke(StandardHo
>> stValve.java:142)
>>  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo
>> rtValve.java:79)
>>  at org.apache.catalina.valves.AbstractAccessLogValve.invoke(Abs
>> tractAccessLogValve.java:616)
>>  at org.apache.catalina.core.StandardEngineValve.invoke(Standard
>> EngineValve.java:88)
>>  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd
>> apter.java:518)
>>  at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
>> tractHttp11Processor.java:1091)
>>  at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
>> .process(AbstractProtocol.java:673)
>>  at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
>> (NioEndpoint.java:1500)
>>  at

Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel

2016-10-27 Thread Martin Grigorov 
Hi,

Good news!
It is a bug in Wicket Bootstrap:
https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-7.x/bootstrap-core/src/main/java/de/agilecoders/wicket/core/markup/html/bootstrap/dialog/Alert.html#L10

This  uses a Label in Java. (No idea why).
Since https://issues.apache.org/jira/browse/WICKET-6219 this is not
possible.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Oct 27, 2016 at 1:10 PM, Joachim Rohde  wrote:

> We are having a custom FeedbackPanel which extends from NotificationPanel.
> After upgrading from Wicket 7.4.0 to 7.5.0 an
> unexpected runtime exception is thrown as soon as an error message should
> be rendered (see below).
>
> I have created a quickstart with a simple link which demonstrates this
> behavior. With Wicket 7.4.0 everything works as
> expected. With Wicket 7.5.0 you'll get an exception.
>
> When using the Wicket FeedbackPanel everything works fine. I have no clue
> if this is a bug in Wicket itself or Wicket
> Bootstrap. Any help is appreciated.
>
> Joachim
>
>
> The generated exception:
>
> Unexpected RuntimeException
>
> Last cause: The component(s) below failed to render. Possible reasons
> could be that: 1) you have added a component in
> code but forgot to reference it in the markup (thus the component will
> never be rendered), 2) if your components were
> added in a parent container then make sure the markup for the child
> container includes them in .
>
> 1. [Component id = message]
>
> Stacktrace
>
> Root cause:
>
> org.apache.wicket.WicketRuntimeException: The component(s) below failed
> to render. Possible reasons could be that: 1)
> you have added a component in code but forgot to reference it in the
> markup (thus the component will never be rendered),
> 2) if your components were added in a parent container then make sure the
> markup for the child container includes them
> in .
>
> 1. [Component id = message]
>
>  at org.apache.wicket.Page.checkRendering(Page.java:666)
>  at org.apache.wicket.Page.endComponentRender(Page.java:317)
>  at org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(
> XmlPartialPageUpdate.java:127)
>  at org.apache.wicket.page.PartialPageUpdate.writeComponents(
> PartialPageUpdate.java:248)
>  at org.apache.wicket.page.PartialPageUpdate.writeTo(
> PartialPageUpdate.java:161)
>  at org.apache.wicket.ajax.AjaxRequestHandler.respond(
> AjaxRequestHandler.java:358)
>  at org.apache.wicket.request.cycle.RequestCycle$
> HandlerExecutor.respond(RequestCycle.java:895)
>  at org.apache.wicket.request.RequestHandlerStack.execute(
> RequestHandlerStack.java:64)
>  at org.apache.wicket.request.RequestHandlerStack.execute(
> RequestHandlerStack.java:97)
>  at org.apache.wicket.request.cycle.RequestCycle.execute(
> RequestCycle.java:265)
>  at org.apache.wicket.request.cycle.RequestCycle.
> processRequest(RequestCycle.java:222)
>  at org.apache.wicket.request.cycle.RequestCycle.
> processRequestAndDetach(RequestCycle.java:293)
>  at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(
> WicketFilter.java:261)
>  at org.apache.wicket.protocol.http.WicketFilter.
> processRequest(WicketFilter.java:203)
>  at org.apache.wicket.protocol.http.WicketFilter.doFilter(
> WicketFilter.java:284)
>  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:239)
>  at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:206)
>  at org.apache.catalina.core.StandardWrapperValve.invoke(
> StandardWrapperValve.java:217)
>  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:142)
>  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:518)
>  at org.apache.coyote.http11.AbstractHttp11Processor.process(
> AbstractHttp11Processor.java:1091)
>  at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.
> process(AbstractProtocol.java:673)
>  at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
> doRun(NioEndpoint.java:1500)
>  at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
> run(NioEndpoint.java:1456)
>  at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
>  at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(
>