> > nick, have you tried asking on pax wicket mailing list? those guys use > > wicket with osgi all the time. perhaps they have a clean solution.
We have had numerous issues with this. We have a working solution, but IMO not a "clean" one. Actually, "opinion" is probably too strong a word, since I have not yet been able to fully investigate the issue. However, my feeling is that it will be impossible to find a "clean" or "ideal" solution in the OSGi world given the way Wicket classloading works, as you described in your original post. It would be nice if somebody from the OSGi world could sit down and redesign the serialization stuff with the Wicket team, but I doubt that will happen, since OSGi is only used by a small number of Wicket users. > Alternatively, may take a look at OsgiClassResolver.java > in the welo project which is hosted at google code. > OsgiClassResolver.java is an implementation (improvement needed) > of IClassResolver to resolve classes that are stored in osgi bundles. I tried googling this, but did not fine a "welo project". Can you provide us with a link? Cheers, David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
