Re: Feedback message related problem--info,debug etc take string arguments which is not very flexible

2008-06-02 Thread atul singh
I can do that within a day or 2..(Meaning with the patch..).does any core
dev see an issue if info,debug etc start taking Serializable as parameter
like error().??
Thanks

On Mon, Jun 2, 2008 at 10:48 AM, Erik van Oosten [EMAIL PROTECTED]
wrote:

 Hi, Atul,

 That sounds like a reasonable request to me (I am no core member). Its best
 to open a new issue in Wicket's jira, preferably with a patch attached.

 Regards,
   Erik.


 atul singh wrote:

 Hi,
 I see that only error() feedback takes a serializabel message. This allows
 me to pass any java object as message and implement custom filtering of
 messages by components.
 but info,debug etc take a string and so do not help me in that kind of
 filtering.
 Actually what we have is a TabbedWizard thing, a hybrid of TabbedPanel and
 Wizard. We have such a requirement to target feedback messages to very
 specific feedback components on any of the tabs. This is also not possible
 by implementing this logic based on the reporting component. I wanted the
 implementation to be generic , just based on info encapsulated in the
 message.
 Can anyone suggest an alternative?
 Can the info(),debug() etc method signatures be changed to have such
 flexibility???
 Thanks





 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: Feedback message related problem--info,debug etc take string arguments which is not very flexible

2008-06-02 Thread Igor Vaynberg
we havent done it yet because it is an API break. so we have been
waiting for wicket1.5/2.0 whatever to do this.

-igor

On Mon, Jun 2, 2008 at 12:17 AM, atul singh [EMAIL PROTECTED] wrote:
 I can do that within a day or 2..(Meaning with the patch..).does any core
 dev see an issue if info,debug etc start taking Serializable as parameter
 like error().??
 Thanks

 On Mon, Jun 2, 2008 at 10:48 AM, Erik van Oosten [EMAIL PROTECTED]
 wrote:

 Hi, Atul,

 That sounds like a reasonable request to me (I am no core member). Its best
 to open a new issue in Wicket's jira, preferably with a patch attached.

 Regards,
   Erik.


 atul singh wrote:

 Hi,
 I see that only error() feedback takes a serializabel message. This allows
 me to pass any java object as message and implement custom filtering of
 messages by components.
 but info,debug etc take a string and so do not help me in that kind of
 filtering.
 Actually what we have is a TabbedWizard thing, a hybrid of TabbedPanel and
 Wizard. We have such a requirement to target feedback messages to very
 specific feedback components on any of the tabs. This is also not possible
 by implementing this logic based on the reporting component. I wanted the
 implementation to be generic , just based on info encapsulated in the
 message.
 Can anyone suggest an alternative?
 Can the info(),debug() etc method signatures be changed to have such
 flexibility???
 Thanks





 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Feedback message related problem--info,debug etc take string arguments which is not very flexible

2008-06-01 Thread Erik van Oosten

Hi, Atul,

That sounds like a reasonable request to me (I am no core member). Its 
best to open a new issue in Wicket's jira, preferably with a patch attached.


Regards,
   Erik.

atul singh wrote:

Hi,
I see that only error() feedback takes a serializabel message. This allows
me to pass any java object as message and implement custom filtering of
messages by components.
but info,debug etc take a string and so do not help me in that kind of
filtering.
Actually what we have is a TabbedWizard thing, a hybrid of TabbedPanel and
Wizard. We have such a requirement to target feedback messages to very
specific feedback components on any of the tabs. This is also not possible
by implementing this logic based on the reporting component. I wanted the
implementation to be generic , just based on info encapsulated in the
message.
Can anyone suggest an alternative?
Can the info(),debug() etc method signatures be changed to have such
flexibility???
Thanks

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]