On Thu, Jul 3, 2008 at 3:35 PM, Edward Yakop <[EMAIL PROTECTED]> wrote: > On Thu, Jul 3, 2008 at 9:27 PM, Daniel Stoch <[EMAIL PROTECTED]> wrote: >> 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. > > Isn't this in general depends on the IClassResolver of wicket application? > If IClassResolver is set and the rest of wicket bundles uses > Application class resolver, it would be irrelevant whether the other > wicket jars/bundles has DynamicImport-Package declaration.
Ok, but what about other (non-wicket) mechanisms, which do not use IClassResolver (eg. creating proxy by Proxy.newProxyInstance(...) - it uses classloader directly)? -- Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
