Re: getPage(pageReference) == null since Wicket 6.10.0

2013-11-06 Thread Ondrej Zizka
Try the JBoss EAP 6.1: http://www.jboss.org/jbossas/downloads/ I didn't have much trouble using that with Wicket 6.x. Ondra On 5.11.2013 18:19, Dieter Tremel wrote: Am 12.10.2013 12:19, schrieb Dieter Tremel: Sometimes I have the impression that a Glassfish and wicket are not a couple in

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-11-06 Thread David Beer
JBoss AS 7 and Wildfly 8 work nicely with Wicket. On 6 November 2013 15:25, Ondrej Zizka ozi...@redhat.com wrote: Try the JBoss EAP 6.1: http://www.jboss.org/jbossas/downloads/ I didn't have much trouble using that with Wicket 6.x. Ondra On 5.11.2013 18:19, Dieter Tremel wrote: Am

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-11-06 Thread Dieter Tremel
Thank You, will try that. Dieter Am 06.11.2013 17:14, schrieb David Beer: JBoss AS 7 and Wildfly 8 work nicely with Wicket. On 6 November 2013 15:25, Ondrej Zizka ozi...@redhat.com wrote: Try the JBoss EAP 6.1: http://www.jboss.org/jbossas/downloads/ I didn't have much trouble using

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-11-05 Thread Dieter Tremel
Am 12.10.2013 12:19, schrieb Dieter Tremel: Sometimes I have the impression that a Glassfish and wicket are not a couple in great love. Seems that Glassfish and Oracle are not in great love either, since commercial Glassfish is dead, and this is no good future for the open source edition:

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-10-14 Thread Dieter Tremel
Am 12.10.2013 21:58, schrieb Martin Grigorov: The problem is that most of us use Tomcat/Jetty and we don't test other web containers. Hi, I always saw the decision between full Java EE and Spring Framework, and Spring always made the impression to be a solution for all problems and you have to

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-10-14 Thread Martin Grigorov
Hi, On Mon, Oct 14, 2013 at 10:10 AM, Dieter Tremel tre...@tremel-computer.dewrote: Am 12.10.2013 21:58, schrieb Martin Grigorov: The problem is that most of us use Tomcat/Jetty and we don't test other web containers. Hi, I always saw the decision between full Java EE and Spring

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-10-14 Thread Martijn Dashorst
Our current stack for big applications (10-20k concurrent users) is: - wicket 6 (we upgrade with every release, across all projects almost simultaneously, couple of million lines of code, about 3000 pages, 3000 panels, etc) - spring for wiring hibernate, cxf and classpath scans, and some DI -

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-10-12 Thread Sven Meier
See WICKET-5380 Sven On 10/12/2013 10:20 AM, Dieter Tremel wrote: Hello wicket-community, in the last time I had to work on another project, so my wicket-work paused and I just upgraded to the new versions. So I was rather astonished that the mechanism I implemented for the return page after

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-10-12 Thread Dieter Tremel
Thank you Sven. I am glad that it is well known and will be fixed in 6.12, and little bid sad about the hours I spent of studying my code and testing. I should have asked more early in the mailing list, your support is always great. Sometimes I have the impression that a Glassfish and wicket are

Re: getPage(pageReference) == null since Wicket 6.10.0

2013-10-12 Thread Martin Grigorov
On Sat, Oct 12, 2013 at 1:19 PM, Dieter Tremel tre...@tremel-computer.dewrote: Thank you Sven. I am glad that it is well known and will be fixed in 6.12, and little bid sad about the hours I spent of studying my code and testing. I should have asked more early in the mailing list, your