I've "solved" this removing org.apache.wicket.request from Export-Package in wicket.core bundle jars. This works only because I'm not using request.ClientInfo class. Probablhy during runtime there will be other problems.
>From the OSGI perspective, having duplicate packages exported by different bundles is wrong. Should I fill a issue for this? On Mon, Apr 25, 2011 at 1:01 PM, Daniele Dellafiore <ilde...@gmail.com>wrote: > Hi. > > Whe I try to start my wicket webapp from Karaf, I receive a > NoClassFoundException agains Request. > The problem is that my app imports the package org.apache.wicket.request > from wicke.core bundle that have the package, but not the class. > The fact that the same package is exported from two bundles really does not > fit well in OSGI. > > Any possible solution? > > > -- > Daniele Dellafiore > http://danieledellafiore.net > -- Daniele Dellafiore http://danieledellafiore.net
