A quick look in the patch shows two code duplications but otherwise looks OK. I'd like to ask other OSGi users to take a look as well and add a comment.
On Tue, May 24, 2011 at 12:23 PM, Daan van Etten <[email protected]> wrote: > Op 27 apr 2011, om 09:43 heeft Daniele Dellafiore het volgende geschreven: > > This is also my main point to conversation. We're talking about being > > somewhere really close to a nice out of the box OSGi support. Why not > take a > > little effort to make it complete? Also, having packages that span > through > > different jars is not really good to me, OSGi or not. > > > > Anyway, > > > > Daan, I'm really interested in the classloading problem you had. Actually > I > > did succeed in making a wicket-spring webapp start and work 100%. > > But after the wicket package is reinstalled or just refreshed in the > > container, @SpringBean injection stop working with: > > My colleague created a JIRA ticket with an elaborate description of the > problem. There's also a patch included. > > https://issues.apache.org/jira/browse/WICKET-3737 > > Regards, > > Daan > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
