On Tue, Jul 12, 2011 at 8:27 AM, Charles Moulliard <[email protected]> wrote: > Hi Andreas, > > Great news to hear that pax-wicket project revives. I will have also a > look and provide you my feedback.
Thank you Charles; Feedback is also heartly welcomed! > BTW, when IoC will be added with > Spring or Blueprint, then Apache Wicket on OSGI platform will be one > of the de factor Web Framework Full IoC support is already added for pax-wicket. [1] might be a good place to see how this will look like from a user point of perspecitve. > (with probably Vaadin, other to be > defined and qualify) to be used for OSGI world ! Excellent. That's were we want to place Wicket :) BTW ASAP I have all features and documentation in place for pax-wicket (mid to end of August) I plan to work on the (Wicket based) karaf-webconsole project we've already talked about on several mailing lists. Although not ready yet still something might be interesting to follow once it starts. Kind regards, Andreas [1] https://issues.apache.org/jira/browse/KARAF-727 > > Regards, > > Charles Moulliard > > Apache Committer > > Blog : http://cmoulliard.blogspot.com > Twitter : http://twitter.com/cmoulliard > Linkedin : http://www.linkedin.com/in/charlesmoulliard > Skype: cmoulliard > > > > On Tue, Jul 12, 2011 at 8:19 AM, Andreas Pieber <[email protected]> wrote: >> Hey, >> >> Another approach to run your wicket applications within OSGi might be >> pax-wicket [1]. Both work without problems with Aries. Compared to >> Harald's approach pax-wicket does currently not support JSR330 and >> plain OSGi service injection (both planned for latest end of August), >> but it has the advantage of allowing you to split your components and >> pages via different bundles. In addition you have full blueprint and >> spring support by now allowing you to directly inject spring and >> blueprint beans on the bundle-level. >> >> While the framework is pretty stable by now (0.7.2 [2]) I'm currently >> completely re-writing the samples and documentation sections for the >> project. So there are missing spaces right now. I'm trying to fill >> them ASAP, but don't hesitate to hit the ops4j mailing lists or IRC >> channel [3] if you have any questions. >> >> Kind regards, >> Andreas >> >> [1] http://ops4j1.jira.com/wiki/display/paxwicket/Pax+Wicket >> [2] http://ops4j1.jira.com/wiki/display/paxwicket/Pax+Wicket+-+0.7.2 >> [3] http://ops4j1.jira.com/wiki/display/paxwicket/Support >> >> On Tue, Jul 12, 2011 at 8:10 AM, Charles Moulliard <[email protected]> >> wrote: >>> Hi Harald, >>> >>> What you have done seems really interesting and promising. I will have >>> a look and come back to you soon. I have used Apache Wicket + Spring >>> to integrate DAO layer so what you have done interest me >>> (https://github.com/cmoulliard/camel-osgi-servicemix-tutorial see >>> reportincident.web). >>> >>> Regards, >>> >>> Charles Moulliard >>> >>> Apache Committer >>> >>> Blog : http://cmoulliard.blogspot.com >>> Twitter : http://twitter.com/cmoulliard >>> Linkedin : http://www.linkedin.com/in/charlesmoulliard >>> Skype: cmoulliard >>> >>> >>> >>> On Mon, Jul 11, 2011 at 7:43 PM, Harald Wellmann <[email protected]> >>> wrote: >>>> In the past few weeks, I've been experimenting with both Aries and Wicket >>>> on >>>> OSGi. With a tiny glue component wicketstuff-osgi [1], the two frameworks >>>> nicely play together. >>>> >>>> Instead of creating another demo application, I simply took the Aries Blog >>>> sample and added an alternative web bundle based on Wicket. The backend >>>> bundles only required minor changes, like adding "implements Serializable" >>>> in a few places. >>>> >>>> See [2] for more details and links to the source code. The sample is based >>>> on Aries 0.3.0 and WicketStuff 1.5-SNAPSHOT. >>>> >>>> Just to show you are not limited to plain old Servlets and JSPs to build a >>>> web front-end on top of Aries ;-) >>>> >>>> Best regards, >>>> Harald >>>> >>>> [1] https://github.com/wicketstuff/core/wiki/Osgi >>>> [2] http://code.google.com/p/osgi-enterprise/wiki/AriesBlogWithWicket >>>> >>>> >>>> >>> >> >
