This doesn't happen with CVS head any more. When you look at your
stack trace the root cause says "Caused by:
wicket.WicketRuntimeException: Markup not found. Component class:
example.EditPricing". With cvs head that is a MarkupNotFoundException
which will not be catched on its way up the call stac
I was able to create the error again with a different markup file. Hopefully this helps:
wicket.WicketRuntimeException: Markup of type 'html' for component 'example.EditPricing' not found or invalid Enable debug messages for wicket.util.resource.Resource to get a list of all filenames tried:
[Pag
wicket-releated markup
> > > problem. Ie a component is attached to a tag it does not support. The
> > > message should be something like: component x does not support markup tag
> > > of
> > > type y, or something similar.
> > >
> > > -Igor
>
to a tag it does not support. The
> > message should be something like: component x does not support markup tag of
> > type y, or something similar.
> >
> > -Igor
> >
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [m
nal Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Eelco Hillenius
> > Sent: Tuesday, October 25, 2005 3:04 PM
> > To: wicket-user@lists.sourceforge.net
> > Subject: Re: [Wicket-user] Markup not found
> >
> > S
nal Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Eelco Hillenius
> Sent: Tuesday, October 25, 2005 3:04 PM
> To: wicket-user@lists.sourceforge.net
> Subject: Re: [Wicket-user] Markup not found
>
> Sounds like a good idea.
>
> Eelco
&
ind in the deepest cause.
>
> -Igor
>
>
>
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Francis Amanfo
> Sent: Tuesday, October 25, 2005 2:40 PM
> To: wicket-user@lists.sourceforge.net
> Subject: Re: [Wicket-
oSent: Tuesday, October 25, 2005 2:40 PMTo:
wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] Markup
not found
This "Markup not found" exception thing is extremely misleading and
think needs addressing if Wicket is seriously aiming at going mainstream. In
my early d
I've been bitten by the Markup Not Found error as well. It would be
nice if that message was accompanied by some bit of information about
what markup it was expecting to find, But unfortunately the stack
trace was devoid of any helpful information.
As it sits, the message is just about as eff
This "Markup not found" exception thing is extremely misleading and
think needs addressing if Wicket is seriously aiming at going
mainstream. In my early days of Wicket I struggled so much with it. It
can happen because the markup really doesn't exist but also sometimes
when there is an error in yo
No, there was nothing about the "is wrong" bit. Just that it couldn't find it.On 10/25/05, Juergen Donnerstag <
[EMAIL PROTECTED]> wrote:yes, the stacktrace you get is something like
ERROR
-
RequestCycle
- Unexpected runtime exception[page = [Page class = wicket.markup.html.basic.Sim
yes, the stacktrace you get is something like
ERROR - RequestCycle - Unexpected runtime exception
[page = [Page class = wicket.markup.html.basic.SimplePage, id = 0]]
wicket.WicketRuntimeException: Markup of type 'html' for component
'wicket.markup.html.basic.SimplePage' not found or
Just put this in an random markup file:
and you'll get the stack trace. ;)
On 10/25/05, Nick Heudecker <[EMAIL PROTECTED]> wrote:
> I checked my old logs and wasn't able to find the stack trace. Apologies.
>
>
> On 10/25/05, Juergen Donnerstag < [EMAIL PROTECTED]> wrote:
> > Yes I agree, but p
I checked my old logs and wasn't able to find the stack trace. Apologies.On 10/25/05, Juergen Donnerstag <
[EMAIL PROTECTED]> wrote:Yes I agree, but please with stacktrace, markup etc.. Just "it does
not work" doesn't help much to find the cause.JuergenOn 10/25/05, Martijn Dashorst <[EMAIL PROTECT
Yes I agree, but please with stacktrace, markup etc.. Just "it does
not work" doesn't help much to find the cause.
Juergen
On 10/25/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> eh... bug-REPORT that is :-)
>
> Martijn
>
>
>
> On 10/25/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> > We sh
eh... bug-REPORT that is :-)
Martijn
On 10/25/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
We should create a bug for this.
Martijn
On 10/25/05, Nick Heudecker <[EMAIL PROTECTED]
> wrote:
Yep, it was horribly incorrect markup. I would've expected a parse error, not a not found error.On 10/24/
We should create a bug for this.
Martijn
On 10/25/05, Nick Heudecker <[EMAIL PROTECTED]> wrote:
Yep, it was horribly incorrect markup. I would've expected a parse error, not a not found error.On 10/24/05,
Eelco Hillenius <
[EMAIL PROTECTED]> wrote:There might be a problem parsing your markup, so
Yep, it was horribly incorrect markup. I would've expected a parse error, not a not found error.On 10/24/05, Eelco Hillenius <
[EMAIL PROTECTED]> wrote:There might be a problem parsing your markup, so that it can't be
loaded properly. Can you send us your complete stacktrace?EelcoOn 10/24/05, Nick
There might be a problem parsing your markup, so that it can't be
loaded properly. Can you send us your complete stacktrace?
Eelco
On 10/24/05, Nick Heudecker <[EMAIL PROTECTED]> wrote:
> I've been staring at this for hours, but can't figure out what would cause a
> "Markup not found" error when
19 matches
Mail list logo
