Hi David, Thank for your answer! Yes, your are right buddy class loading is Equinox proprietary. For me that's not a problem because I tied myself to use equinox. I did so because if you want to deploy in a traditional application sever you will have to use a bridge approach and equinox already provide that bridge. I though the standard already provided a something similar to buddy class-loading (dynamic imports?), or at least that was the answer some-one gave to me on the equinox list. I haven't had the time to check the details myself. For me, buddy-class loading works just fine and I didn't bother too much with the philosophical implications of this. I also need the same trick for things like loading entities, quartz jobs, etc.
Cheers, Ernesto David Leangen-8 wrote: > > > Hi Ernesto, > > Thanks. > >> Just one question why not use buddy class-loading techniques to >> "solve" serialization problem? > > Simple: at least for now, this is a non-standard extension for Eclipse/ > Equinox. :-) > > I am aware of some proposals to modify the OSGi spec, but as far as I > know, that's not getting anywhere yet. In any case, I am still > pondering over whether or not the framework should even directly > serialize those private classes... Haven't yet come to any conclusions. > > > Cheers, > =David > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- View this message in context: http://www.nabble.com/Wicket-serialization-problems-for-OSGi-users-tp22653816p22657119.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
