Okay I figured out what my problem was: When creating the jar I forgot to also put my compiled interfaced to the jar. I only had the implemented interfaces in the jar. So during registration when the implementation was about to load Class.forName failed because it couldn't instance the interface, only its implementation. (Hope this can help someone in the future) ...
> -----Original Message----- > From: Martin Dobiasch [mailto:martin.dobia...@dobibrennda.at] > Sent: Tuesday, December 14, 2010 11:36 AM > To: dev@api.openoffice.org > Subject: RE: [api-dev] Jar-Problem extension installation > > > unopkg still has trouble executing the registration Java code at > > at.univie.MidiCSD.impl.RegistrationHandler in your MidiCSDext.jar, but > > the empty CannotRegisterImplementationException message is of course > > unhelpful in finding out why. > > > > Do you have an empty class path now? (Also, I am not completely sure, > > but I think unopkg should use class path settings from OOo's "Tools - > > Options... - Java" dialog, not from the CLASSPATH environment variable; > > please check those settings, too.) > > I played around with my RegistrationHandler (default class from > eclipse-plugin). It had problems with getting the resource of the > class-names. > > But now my problem is: the RegistrationHandler can't load any classes. > They are in the jar-file but something is going wrong when I try to > Load them. With Class.forName() > > Any ideas what my mistake is? > > Thanks a lot for your help! > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org > For additional commands, e-mail: dev-h...@api.openoffice.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
