Hi,
I'll take a look soon!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Jun 16, 2016 at 8:04 AM, Dirk Forchel
wrote:
> Hi Martin,
> I've added a much more simpler test application to show what's not working
> (see myproject2.zip below).
> On the first p
Hi Fabio,
I agree that the removal of the default message is not really needed.
It has been done with https://issues.apache.org/jira/browse/WICKET-5735.
I've reverted this with https://issues.apache.org/jira/browse/WICKET-6181
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/m
Hello Bas,
first of all let me thank you and Martin for your great support and the
helpful thoughts and examples :-)
I am using wicket 7.30, the use of onBefore() is an old pattern I have
been used to, changed it now to
@Override
protected void onInitialize() {
super.onInitialize(
Hi Dieter,
It is quite easy to debug such issues by putting a breakpoint at line where
the exception is being thrown.
Once you have the debugger stopped there you could click on the stack
methods to see what was the parent object of the currently failing one.
Martin Grigorov
Wicket Training and C
Thanks Martin,
This is good news. Looking forward to 6.24.0.
Kind regards,
Fabio
On Fri, Jun 17, 2016 at 10:26 AM, Martin Grigorov
wrote:
> Hi Fabio,
>
> I agree that the removal of the default message is not really needed.
> It has been done with https://issues.apache.org/jira/browse/WICKET-5
Hello,
I think I have found it:
In my AbstractProvider superclass I implemented:
@Override
public IModel model(E object) {
return new JPAEntityModel<>((E) object);
}
PersonenTable uses a CachingProvider, a subclass of AbstractProvider
which overwrites
@Override
public
Hello Martin,
I tried this to learn it, but didn't find it.
I put a breakpoint at org.apache.wicket.serialize.java.JavaSerializer
SerializationCheckerObjectOutputStream#writeObjectOverride line 260 and
277 and looked at the variables content.
The obj was the complete page PersonenTable and I had
Do you see java.io.ObjectOutputStream#writeObject0() in the stack ?
Each occurrence of this method gives you information about the currently
being written object. The next occurrence of this method in the stack tells
you which Java object is the owner of the previous one.
I don't have time now to m
Hi Dieter,
That’s what I expected (and why I did not recommend it); The error you see
is because somewhere in the component tree inside your page serialization
breaks. Since it happens when wicket passes the page to an (internal)
ObjectOutputStream, the only way to debug it would be to set a brea
It is caused by a change for WICKET-5988
Now the body container is not added to the Border but it relies solely on
component resolving.
The problem is that the resolving is not used when visiting the children
Please file a ticket at JIRA!
Thanks!
On Jun 17, 2016 10:08 AM, "Martin Grigorov" wrote
10 matches
Mail list logo
