Hey Martin, On Mon, Jul 4, 2011 at 10:24 PM, Martin Grigorov <[email protected]> wrote: > Good work!
Thank you :) > Do you have any plans to upgrade PAX-Wicket to Wicket 1.5 ? > I saw that you have custom Output|Input ObjectStream impls. > In Wicket 1.5 IObjectStreamFactory class is gone, so you'll need to > use the new ISerializer interface. Definitely. I know that there are some infrastructural changes in 1.5 which means that there will be a pax-wicket release for 1.4.x and one for 1.5.x. TBH I'm not sure right now how I want to tackle this. Either aligning the major (major.minor.micro) version to the pax-wicket or provide two complete different versions (0.8.0.w15 and 0.8.0.w14). Anyhow I will provide a 1.5 compatible version within the next 1-2 months. > For more info you can check > https://issues.apache.org/jira/browse/WICKET-3778 > https://github.com/wicketstuff/core/tree/master/jdk-1.5-parent/gae-initializer-parent/gae-initializer/src/main/java/org/wicketstuff/gae > https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/serializer-kryo > > The GAE code is exactly what you'll need to do for PAX. Thank you very much for those pointers. This does not look as it would create any big problems if added to the pax-wicket model. Kind regards, Andreas > > On Mon, Jul 4, 2011 at 9:19 PM, pieber <[email protected]> wrote: >> Hey, >> >> Sorry that I jump in so late, but it needed some time to spread the news of >> this list if you're not a subscriber of the wicket user list :) >> >> I've taken up the development of pax-wicket which is a framework for the >> integration of wicket to the osgi platform. While pax-wicket provides >> various other features at it's core we've solved the classloader, >> serialization and injection (spring & blueprint). While most of you may >> already know about pax-wicket >> (http://ops4j1.jira.com/wiki/display/paxwicket/Pax+Wicket and >> https://github.com/ops4j/org.ops4j.pax.wicket) there had been LOTS of >> changes in the last months and it is much easier to use by now! OK, with >> that said back to the problem at hand. >> >> @WICKET-3737: We've used a similar approach as you've described. We >> automatically attache Classresolver and InjectionResolver services to each >> bundle and delegate the classloading to the bundle which contains the class. >> This also allows to use classes not exported :) In fact you use case is >> quite simple to implement with pax-wicket. >> >> @SpringWicket annotation: We use the same approach as you've described. The >> only difference is that we extend the model a little bit further to allow >> import from the blueprint AND spring context from one bundle. Otherwise we >> limit the import to the bundle creating the blueprint or spring context. >> >> Feel free to give it a look. I've registered again and stay here and at the >> pax lists for help and further infos :) I'm also available in the wicket and >> pax IRC channels (pieber). Feel free to ping me. >> >> Kind regards, >> Andreas >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Wicket-and-OSGi-tp3617698p3644390.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > 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]
