No problem at all. Glad we got it sorted out finally. Happy Wicketeering!
On Tue, Jul 7, 2009 at 12:39 PM,
fbonsignori wrote:
>
> I'm sorry ... I had just put the wrong component in the
> ComponentFeedbackPanel constructor!
>
> Thnx a lot for your help.
>
>
> James Carman-3 wrote:
>>
>> I'm sayi
I'm sorry ... I had just put the wrong component in the
ComponentFeedbackPanel constructor!
Thnx a lot for your help.
James Carman-3 wrote:
>
> I'm saying that you are not rendering all feedback messages, because
> you're using a ComponentFeedbackPanel (which only shows the feedback
> messages
On Tue, Jul 7, 2009 at 11:55 AM,
fbonsignori wrote:
>
> So you are suggesting me that the warning message
>
> "Component-targetted feedback message was left unrendered. This could be
> because you are missing a FeedbackPanel on the page. Message:
> [FeedbackMessage message = "Not yet implemented!"
So you are suggesting me that the warning message
"Component-targetted feedback message was left unrendered. This could be
because you are missing a FeedbackPanel on the page. Message:
[FeedbackMessage message = "Not yet implemented!", reporter =
datasourcebutton, level = ERROR]"
it's caused b
Because the ComponentFeedbackPanel only shows messages for a specific
component. A FeedbackPanel shows *all* feedback messages.
On Tue, Jul 7, 2009 at 11:21 AM,
fbonsignori wrote:
>
> Yes ... and this is pretty clear for me. The open point is another: why using
> a ComponentFeedbackPanel the mess
Yes ... and this is pretty clear for me. The open point is another: why using
a ComponentFeedbackPanel the message is not shown with warning and instead
using a FeedbackPanel the behaviour is as expected? It seems that using
ComponentFeedbackPanel the html code required to show the feedback messag
Right, basically Wicket is letting you know that you're ignoring an
error message by not rendering it, meaning you may be losing out on
valuable user feedback.
On Tue, Jul 7, 2009 at 11:10 AM,
fbonsignori wrote:
>
> Same behaviour.
>
>
> James Carman-3 wrote:
>>
>> What happens if you don't set th
Same behaviour.
James Carman-3 wrote:
>
> What happens if you don't set the max messages?
>
--
View this message in context:
http://www.nabble.com/Strange-behaviour-using-ComponentFeedbackPanel-tp24371713p24375174.html
Sent from the Wicket - User mailing list archive at Nabble.com.
--
What happens if you don't set the max messages?
On Tue, Jul 7, 2009 at 11:01 AM, fbonsignori <
filippo.bonsign...@logobject.ch> wrote:
>
> I set the max number of mess to 1 and if I use a FeedbackPanel I can read
> the
> error message, otherwise by using a ComponentFeedbackPanel the error
> messa
I set the max number of mess to 1 and if I use a FeedbackPanel I can read the
error message, otherwise by using a ComponentFeedbackPanel the error message
is not shown and the reported warning is logged.
James Carman-3 wrote:
>
> Yes, the response page. If you put a regular FeedbackPanel on th
Yes, the response page. If you put a regular FeedbackPanel on the page, how
many messages does it show?
On Tue, Jul 7, 2009 at 9:22 AM, fbonsignori wrote:
>
>
> James Carman-3 wrote:
> >
> > Perhaps there is a different error on the page?
> >
>
> Are you meaning about page rendering or what els
James Carman-3 wrote:
>
> Perhaps there is a different error on the page?
>
Are you meaning about page rendering or what else?
--
View this message in context:
http://www.nabble.com/Strange-behaviour-using-ComponentFeedbackPanel-tp24371713p24373248.html
Sent from the Wicket - User mailing li
Perhaps there is a different error on the page?
On Tue, Jul 7, 2009 at 7:37 AM, Filippo Bonsignori <
filippo.bonsign...@logobject.ch> wrote:
> Hi all,
> I'm developing on Wicket 1.4-rc4 and I'm obtaining a strange behaviour
> using the ComponentFeedbackPanel: the message is not shown in the
> bro
13 matches
Mail list logo
