Hey Harald, On Mon, Jul 4, 2011 at 10:47 PM, Harald Wellmann <[email protected]> wrote: > thanks for providing the pointers and the brand new intro in the Pax Wicket > wiki.
I'm very sorry for the lack of documentation. But I planed to get it done, provide the documentation and do the project marketing then. I missed to recognize the BIG need for pax-wicket. Sorry for that. > This is now at least something to get started, and I'm beginning to see that > there is some overlap with wicket-osgi or even the chance of wicket-osgi > becoming obsolete in the near future as Pax Wicket matures or just shifts > its priorities a little from hacking to documenting all its goodies ;-) You're highly welcomed to work out the problems with us together. I would be very happy if I don't have to document everything from top-to-bottom but could rather start at your special needs and extend pax-wicket and the documentation where required. Any idea/discussion on IRC/lists is highly welcomed. In addition, as typical for ops4j projects, anyone is welcomed to create an account and start hacking/writing docs :) > Some points after a very quick first look and comparison: > > - Pax Wicket head does not compile > (https://ops4j1.jira.com/browse/PAXWICKET-164) Not true :) This is really a JDK bug. If you upgrade to the latest JDK version it works. > - Pax Wicket is based on Wicket 1.4.17, wicket-osgi on 1.5-SNAPSHOT True for the moment. But I don't think that the upgrade will cost that much and most of the user base is still on 1.4.x. In fact it is possible to port your existing 1.4.x wicket app (typically) within hours. I did this to several of the apps at my company and it worked like a charm. > - Wicket 1.4.17 uses DynamicImport-Package: * - are you sure Pax Wicket > would work without that? I'm because we do NOT use the standard wicket packages. We pack wicket into the pax-wicket package and reexport them. If you're familiar with the maven-bundle-plugin feel free to take a look here (https://github.com/ops4j/org.ops4j.pax.wicket/blob/master/service/pom.xml) and see what I mean. > - The official Wicket 1.5 artifacts are not OSGi friendly, so if you upgrade > Pax Wicket to 1.5, you'd have to use wicket-bundle from Wicketstuff, just > like wicket-osgi. (Of course, I'd much prefer the Wicket core project to > provide properly osgified artifacts without split packages and dynamic > imports so we could scrap wicket-bundle...) I'm completely with you. Since it doesn't make much sense to use a different wicket version than pax-wicket I like our current approach to repack all libs directly in pax-wicket. But I've no problem to be convinced to use the wicketstuff wicket bundles or adapted wicket core packages. Kind regards, Andreas > > Cheers, > Harald > > > --------------------------------------------------------------------- > 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]
