On Wednesday 18 April 2007 15:47, Caire Giovanni wrote: > could be to declare the DynamicImport-package manifest header
This may be the only solution, but ultimately it depends on what the Jade code actually does and what kind of hooks are available. For instance; many libraries that relies on classloading from text or similar input allows you to provide the classloader or factories for the construction of the objects. If that exists in Jade, you should not use the DynamicImport at all, and instead have the Core's factory delegate back to the extension bundle, typically via a service. Cheers Niclas
