Hi David, Antilia simply use equinox extensions for class-loading that way you can use "normal" Wicket components... No need to modify Wicket or your components. There I just create the extensions points I need to allow extending components at some places (e.g. toolbars). The projects I mentioned are not a framework: just the skeleton showing how to encapsulate Wicket into a bundle and how to create an application depending on that bundle.
What I wanted to says is that you not always have to face the problems you mentioned: it might depend on how you build your application. But I do agree the OSGi road is not for the faint hearted and people should carefully consider their requirements before jumping into it: moreover if you can achieve extensibility and modularity with other means. Best regards, Ernesto On Thu, Jan 28, 2010 at 8:06 AM, David Leangen <[email protected]> wrote: > > > > I have seen OSGi successfully used with Wicket on production > environments... > > With no problems with the serialization issues you mentioned. > > Yes, I am using pax-wicket for this. > > What I meant was--as I understood from the original post--the person wanted > to use wicket in OSGi without using a framework. If that is the case, it is > a huge headache. > > > How does Antilla solve the problem? Do they have an elegant solution? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
