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,debu
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 requ
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
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 th