Hi,
with Glassfish4 we get a lot of Exceptions when a page gets serialized.
org.apache.wicket.serialize.java.JavaSerializer - Error serializing object class
..
org.apache.wicket.core.util.objects.checker.CheckingObjectOutputStream$ObjectCheckException:
The object type is not Serializable!
A prob
I use this URL to check:
http://central.maven.org/maven2/org/apache/wicket/wicket-core/6.17.0/
Most probably the index of search.maven.org is broken ...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Sep 9, 2014 at 6:03 AM, Hendy Irawan wrote:
> After 3 d
After 3 days Wicket 6.17.0 is still not available from Maven Central:
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.wicket%22%20AND%20a%3A%22wicket-core%22
Please check.
Ironically (but good) Wicketstuff 6.17.0 is already available in Maven
Central.
Hendy
--
View this message i
Hi, all. I'm traveling at the moment, but I plan to be back in San
Francisco around the start of JavaOne. Do any Wicket users plan on being
in town for the conference? Would you like me to organize a
meet-and-greet at a local restaurant or even (depending on the number of
guests) at my place? P
Hi,
You should use Wicket.Ajax.post() instead of jQuery.ajax() to make Ajax
call. Otherwise Wicket won't be able to calculate the baseUrl and all urls
created in this request cycle would be wrong.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Sep 8, 2014
Hi everyone,
I have a problem with AbstractDefaultAjaxBehavior on receiving POST request
sent by client side. Target on respond method does not seem to work - it
process post request but target.add(component) does not refresh a component
in parameter.
What I'm trying to do is process post reques
Hm, thinking some more, the general solution would be to fail if a
variant is requested, and it is among a set of whitelisted variants,
and the markup is not found. For other variants, using the default
would probably be fine. This is more general than our current usecase,
but still significant I b
Both solutions are not ideal, since we do not want our tests to become
brittle. We want to functionally test components in multiple variants,
but where the variants vary in mere layout (css classes), we do not
want to have tests break just because the layout changes (as long as
the component still
Hi,
There is nothing specific for this.
But you can use
various org.apache.wicket.util.tester.WicketTester#executeTest() methods to
check the response against a valid response pre-saved in a file.
Or you can use org.apache.wicket.util.tester.WicketTester#assertContains()
to check that a specific S