Sebastian, I also deployed your quickstart in wildfly-8.0Final with no changes, and all seems well. As for the quickstart test, you would need to use cdi-unit as a test dependency to enable the cdi aspects for the wicket-tester. To successfully add that please look at the test section in the wicket-cdi-1.1 code. In there you will find an extended version of WicketTester that properly starts and stops the different contexts. Without using a package like cdi-unit or arquillian, I am afraid you will always get a Context based exception because there is no cdi service provider activated.
On Fri, Oct 24, 2014 at 11:15 AM, John Sarman <[email protected]> wrote: > I was able to start your test app in Glassfish4 without changes. > > For Tomcat I added > <dependency> > <groupId>org.jboss.weld</groupId> > <artifactId>weld-core</artifactId> > <version>2.1.2.Final</version> > </dependency> > <dependency> > <groupId>org.jboss.weld.servlet</groupId> > <artifactId>weld-servlet-core</artifactId> > <version>2.1.2.Final</version> > </dependency> > to the pom. > > I then added > <listener> > <!-- initialize Weld in servlet environment --> > > <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class> > </listener> > > to web.xml > > The homepage then loaded fine as well. If you look in wicket-examples you > can find these CDI related additions to the pom.xml and the web.xml. > > Hope this helps > > John Sarman > > > > > On Fri, Oct 24, 2014 at 4:12 AM, Sebastien <[email protected]> wrote: > >> Hi Martin, >> >> On Thu, Oct 23, 2014 at 8:27 PM, Martin Grigorov <[email protected]> >> wrote: >> >> > Ticket please. >> > With quickstart will be processed sooner ;-) >> > >> >> Fair :) >> https://issues.apache.org/jira/browse/WICKET-5733 >> >> Best regards, >> Sebastien. >> > >
