OK, another wrap-up of the future of Pax Wicket (PW). There had been no release for PW for quite a while now. Still a lot is going on in the background and I want to wrap this up a little bit:
1) PW integration into Wicket Brian and I've experienced a lot with PW in wicket-15 branch. We've splitted the packages, tried to upgrade to wicket-15 and various other things. According to our experiences it does make much sense to maintain this project separated at anyhow. Therefore we've started to introduce the idea into Wicket. After some (hard) discussions in the wicket-community we've basically retrieved their "go" and start now to provide full-featured OSGi support in Wicket. This does NOT mean that you're on the lost track starting with PW right now! The same ppl working on the OSGi support in PW are also working on Wicket now --> We hope to make a more or less drop-in-replacement here. Till there is something use-full in Wicket (based almost on the PW code) we encourage you very much to work with PW to get us as much feedback as possible! 2) PW in other projects While there are various projects in the closed source already using PW there are now also two opensource projects using PW *) http://openengsb.org (http://github.com/openengsb/openengsb) is using PW 0.7.2 right now is an ESB like framework basing it's admin console on PW *) http://karaf.apche.org ( https://svn.apache.org/repos/asf/karaf/sandbox/pieber/karaf-webconsole/trunk/) basing on PW 0.8.0 (trunk). The karaf-webconsole project is an administration base console trying to get the best out of extension and adaption using pax-wicket. Both projects are under heavy development testing PW on heart and soul. So don't be afraid that it's not usable by now already :-) 3) Future releases OK, now that we're merging PW with Wicket does this mean that development on PW stops immediately? NO, it will definitely not! Since karaf-webconsole and the openengsb are based on this project (besides various closed source projects) there is no way the support can stop before there is a full alternative in wicket itself. It will only mean that optional-non-priority-features may be delayed a little bit, but main extensions and bug-fixes will be included into future pax-wicket releases. So, the roadmap for the next releases and a time-plan: ==0.8.0 (this weak; latest next)== Including the remaining examples and documentation; also an bundle-listener and various other api-refactorings helping with the development of PW/Wicket apps ==0.9.0 (~KW 37)== Port of the code to 1.5; if we've already finished the osgification of wicket in the wicket-project by then basing on 1.5.RC6 with an external wicket bundle ==0.10.0 (~KW 40)== Basing integration on Whiteboard, war and wab support; trying to get rid of the "mystic" imports using R4.3 weaving hooks. ==0.11.0== I really hope that this release is not required and that we've finished the wicket-osgi support by then. If not I'm sure we come up with further tasks and tweaks by then :-) So, this project is still alive and worth a try! Feel free to ask any questions or report any problems and we'll help as good as possible! Kind regards, Andreas
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
