wicket-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Grigorov <mgrigo...@apache.org>
Subject Re: stack traces in serialization caches
Date Wed, 22 Aug 2012 07:44:20 GMT
I think I have found the problem.
Should be better with the fix in
https://issues.apache.org/jira/browse/WICKET-4722

On Fri, Aug 10, 2012 at 2:53 PM, Martin Grigorov <mgrigorov@apache.org> wrote:
> No, these are no errors.
> These are kept only in case of error.
> We can improve though by removing them in Component#detach(). I see no
> reason to keep them around after the first render of the page.
> Please file a ticket.
>
> On Fri, Aug 10, 2012 at 2:45 PM, Andrew Geery <andrew.geery@gmail.com> wrote:
>> I'm using Wicket 1.5.7.  I understand how to turn the stacktraces on and
>> off (in development more I have both those settings turned on).  My
>> question is more: the files look like they are indicating an error is
>> happening, but I don't get a stacktrace at run-time.  For example, if I
>> have a mismatch between the Java class and the HTML I get a stacktrace at
>> run-time in development mode.  I'm running in development mode and I'm not
>> getting any stacktraces.  However, when I look at the wicket-filestore
>> files I am seeing stacktraces.  My questions are:
>>
>> (1) Do the stacktraces in the wicket-filestore files indicate that there is
>> an error? The app seems to work fine, but a stacktrace would indicate an
>> error to me...
>> (2) If these are indeed errors, why are the errors on the wicket-filestore
>> files not being thrown at run-time when running in dev mode?
>>
>> To make this more concrete, one place I'm seeing the errors is around
>> ModalWindow components.  Is the stacktrace simply saying that the
>> ModalWindow is not rendered on the page (which would be true, it is not yet
>> shown), but that it is present in the page's hierarchy?
>>
>> Thanks
>> Andrew
>>
>> On Fri, Aug 10, 2012 at 3:12 AM, Martin Grigorov <mgrigorov@apache.org>wrote:
>>
>>> Hi,
>>>
>>> Which version of Wicket do you use ?
>>>
>>> See
>>> org.apache.wicket.settings.IDebugSettings#setLinePreciseReportingOnAddComponentEnabled
>>> and
>>> org.apache.wicket.settings.IDebugSettings#setLinePreciseReportingOnNewComponentEnabled.
>>> When set to true these create an exception and saves its stacktrace as
>>> String in the Component's meta data. This stacktrace is used to find
>>> when and where the problem happened.
>>>
>>> These stacktraces are printed only if
>>> org.apache.wicket.settings.IDebugSettings#getComponentUseCheck()
>>> returns true.
>>>
>>>
>>> On Fri, Aug 10, 2012 at 4:16 AM, Andrew Geery <andrew.geery@gmail.com>
>>> wrote:
>>> > I have a question about why I am seeing stack traces in my
>>> wicket-filestore
>>> > files.  This question has been asked before (
>>> >
>>> http://apache-wicket.1842946.n4.nabble.com/Strange-content-serialized-td1933194.html
>>> ),
>>> > but I don't understand the answer.  When I run the app, I don't get any
>>> > errors -- all of the components render fine.  However, in the files I see
>>> > errors like this:
>>> >
>>> > The webmarkupcontainer with id 'content' that failed to render was added
>>> >
>>> > In the previous thread, the answer was that the error was there because
>>> > there was a discrepancy between the Java hierarchy and the HTML file.
>>> >  However, if there was an error, wouldn't I get a run-time error (since
I
>>> > am running the app in development mode)?  Why, when there isn't
>>> > a discrepancy, is there a stack trace in the cache?
>>> >
>>> > Thanks
>>> > Andrew
>>>
>>>
>>>
>>> --
>>> Martin Grigorov
>>> jWeekend
>>> Training, Consulting, Development
>>> http://jWeekend.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Mime
View raw message