On Thu, Jul 3, 2008 at 2:53 PM, Edward Yakop <[EMAIL PROTECTED]> wrote: > On Thu, Jul 3, 2008 at 8:24 PM, Daniel Stoch <[EMAIL PROTECTED]> wrote: >> But there is a one assumption, that bundle with Wicket classes (you >> probably have a Wicket bundled somehow in your app, don't you? :)), >> should have a dynamic import for all classes which can be located in >> many different bundles: >> DynamicImport-Package: *" > > I don't think you should use DynamicImport-Package.
I know it is not a very good practise, but Wicket jars/bundles already have "DynamicImport-Package: *" ;). And sometimes is hard to avoid this. > In pax wicket, we creates a delegating class resolver that tracks > IClassResolver services. So each bundle must export its IClassResolver service? What about bundles independent from Wicket? -- Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
