Spring bundles are not required except if Wicket will use Spring IoC As the bundle name mention it : Geronimo Servlet is a specification implementing the Servlet API defined in J2EE. This one is mandatory
Regards, Charles Moulliard Senior Enterprise Architect Apache Camel Committer ***************************** blog : http://cmoulliard.blogspot.com twitter : http://twitter.com/cmoulliard On Mon, Oct 19, 2009 at 4:32 PM, kamil szabo <[email protected]> wrote: > Thanks for reply, > > i just tried PaxWeb, the jetty was included inside of it... > > Is it necessary to bring in big guns like geronimo and spring? Cause > wicket is mostly working - no problem conecting to server, browse > pages, use standard components... Only when it comes to resources... > > Or you've allready came throug this and your way is only working so far? > > 2009/10/19 Charles Moulliard <[email protected]>: >> Hi Kamil, >> >> I use Apache Wicket top of Apache Felix Karaf currently. >> >> To be able to run easily wicket with felix, you have to use PAX Web, >> Jetty bundle and of course Wicket. Here is my list of bundles used >> >> <feature name="http" version="1.2.0-SNAPSHOT"> >> <config >> name="org.ops4j.pax.web">org.osgi.service.http.port=8181</config> >> >> <bundle>mvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/1.1.2</bundle> >> >> <bundle>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jetty-bundle/6.1.14_1</bundle> >> <bundle>mvn:org.ops4j.pax.web/pax-web-bundle/0.6.0</bundle> >> </feature> >> >> <feature name="wicket" version="1.4.1"> >> <bundle>mvn:org.apache.wicket/wicket/1.4.1</bundle> >> <bundle>mvn:org.apache.wicket/wicket-ioc/1.4.1</bundle> >> <bundle>mvn:org.apache.wicket/wicket-spring/1.4.1</bundle> >> <bundle>mvn:org.apache.wicket/wicket-extensions/1.4.1</bundle> >> </feature> >> >> Remark : Apache Felix Karaf is a distribution software running top of >> Apache Felix (or Equinox if you want). The big advantage is that karaf >> provides you a provisioning mechanism who helo you to define the >> bundles to be deployed. >> >> You can find more info here : >> >> http://camel.apache.org/tutorial-osgi-camel-part2c.html >> >> and here >> >> http://cmoulliard.blogspot.com/2009/04/power-of-apache-wicket-and-spring-osgi.html >> >> and here for Apache Karaf : >> >> http://felix.apache.org/site/46-provisioning.html >> >> Regards, >> >> Charles Moulliard >> Senior Enterprise Architect >> Apache Camel Committer >> >> ***************************** >> blog : http://cmoulliard.blogspot.com >> twitter : http://twitter.com/cmoulliard >> >> >> >> On Mon, Oct 19, 2009 at 3:23 PM, kamil szabo <[email protected]> wrote: >>> Hey, >>> >>> im working on application trying to put these technologies together, >>> but i'm stuck. >>> >>> I folowed few mailing lists where someone was told to create custom >>> WicketApplicationFactory, custom WicketFilter and WicketServlet, and >>> then register the servlet in HttpService (of felix.http). After few >>> standard problems I managed to make a bundle with wicket jars as >>> classpath and made Wicket work but... >>> >>> Some form components does not work, like Pallete - seems like no >>> javascript resources were downloaded from the wicket.extensions.jar, >>> no exception is thrown, just buttons does not work. Ajax does not work >>> either. And I can't find a way to adress images, i followed the >>> documentation on felix.http site but there is just too little >>> information for me. >>> >>> Can someone tell me if this can somehow work? >>> Are there some technological problems that can't make Ajax and some >>> wocket components work correctly? >>> And how to address resources? (service.registerResources("/static", >>> "/etc/www", null); or where should they be) >>> >>> Or where can i find some more infos on these thema... >>> >>> Is there someone who made his way through this and can please help me? >>> I need to make it OSGi way, I would have no problem to deploy it in >>> app server... >>> >>> Thx in advance Kamil Szabo >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
