Yeah, this is due to to the fix I did for
http://issues.apache.org/jira/browse/WICKET-694
I'm rolling that fix back now until we have a better solution.
Eelco
On 6/25/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
>
> i'm getting the exception below.
>
> have there been any recent changes to mar
oh, i see now that's 1.2.6 not 1.3... still it's about the same stack trace.
Jonathan Locke wrote:
>
>
> ah. i think maybe it's not just me:
>
> https://issues.apache.org/jira/browse/WICKET-592
>
>
> Jonathan Locke wrote:
>>
>> i'm getting the exception below.
>>
>> have there been any
ah. i think maybe it's not just me:
https://issues.apache.org/jira/browse/WICKET-592
Jonathan Locke wrote:
>
> i'm getting the exception below.
>
> have there been any recent changes to markup finding or is this probably
> my own issue?
>
> thanks,
>
> jon
>
> --
>
> WicketM
this does at least appear to have started happening after updating wicket
(either in the past few days or today).
Jonathan Locke wrote:
>
> i'm getting the exception below.
>
> have there been any recent changes to markup finding or is this probably
> my own issue?
>
> thanks,
>
> jon
>
i'm getting the exception below.
have there been any recent changes to markup finding or is this probably my
own issue?
thanks,
jon
--
WicketMessage: Unable to find the markup for the component. That may be due
to transparent containers or components implementing IComponentResolve
