On Wed, Sep 2, 2009 at 11:52 AM, Tobias Girschick<[email protected]> wrote: > On Wed, 2009-09-02 at 12:26 +0300, Nina Jeliazkova wrote: > Descriptor engine relies on introspection to find classes implementing > certain (descriptor) interfaces. Since Java Web Start mechanism for > loading classes is a bit different , this behaviour is not quite unexpected.
Ah, my mistake... I though the iteration was failing... > Although I am not an author of it, I've struggled before with trying to make > Descriptor engine load classess from jars other than CDK / on the default > class path. A (rough) workaround is to explicitly define the descriptor > class names in a list, but that's far from elegant. I have on my TODO list an API extension that allow you to pass the engine a list of classes, which are expected to be on the classpath... I'll put some priority to this, so please let me know further requirements... For example, it would likely help if I add a version that takes a ClassLoader too, not? So that loading descriptors from jars outside the classpath is possible too... Nina, my sincere apologies that I had not followed up on that... I remember we spoke about it on the CDK workshop... :( Egon -- Post-doc @ Uppsala University http://chem-bla-ics.blogspot.com/ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Cdk-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdk-user
