Quoting Rajarshi Guha <rajarshi.g...@gmail.com>: > On Tue, Jan 12, 2010 at 4:15 PM, Vincent Le Guilloux > <vincent.le-guill...@univ-orleans.fr> wrote: >> The problem is actually the java.class.path property. This property >> does not actually contains the full classpath, but only the classpath >> as defined at the application startup. This results, in my case, in a >> single jar file explored on the loop: myApp.jar, which obviously does >> not contains any CDK descriptor class. >> >> So here is my questions: >> 1. Are you aware of this? > > Yes > >> 2. In the default case (when we create a descriptor engine using the >> default parameters), why don't you simply load all descriptors classes >> available in the CDK? In such case, there is no need to check any jar >> file as we have already a direct access to all classes. > > Yes, this is one way to go, but assumes that you have all the > descriptor jar files in your class path. This will be true if you're > using the big jar file, but not neessarily true if you're using the > modular jar files. > > Another reason for introspection rather than hardcoding th listis that > doesn't require someone to make sure that the hard coded list is > updated when new descriptors are added or old ones removed. >
Yes, I wasn't really talking about harcoding descriptor classes, but rather doing the introspection directly in the CDK package, without using the classpath property to check jars. As we are actually in the CDK jar when using the DescriptorEngine, to my mind there is no need to pass through the classpath to get default CDK descriptors. > This approach also lets users define their own desriptor classes in > separate jar files. > Yep. > Have you tried using the constructor that lets you specify a list of > jar file names - so thatyou don't have to depend on the classpath? If > you can collect the jar file names, this constructor should address > your problem > Yes indeed :) Thank you for you answer! Cheers :) Vincent > -- > Rajarshi Guha > NIH Chemical Genomics Center > > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Cdk-user mailing list Cdk-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdk-user
