> I am starting to understand where my confusion is now. > > I looked at the ProtocolHandler example, and there is no idl. So, I > guess I have to manually register my protocolhandler, or the java > classes that it calls. > > How do I do that when the person installs the plugin, as I don't want > the users to have to do much to use the plugin.
No, just specify proper manifest.xml entries and unopkg/PackageManager UI will install you add-on zip (.uno.pkg) the right way. > Or, do I need to create an idl for the java classes that the > protocolhandler will call, and then go through the four steps to have a > java class from that, and then implement that interface? I don't understand. You mentioned in some previous mails that your add-on works when you just zip all files up and install that zip with pkgchk. pkgchk more or less just tries to install everything found in a zip, even if it makes no sense, e.g. a jaxrpc.jar will be detected as a UNO jar typelibrary. So if you want to correct that, you can use the new package bundle (since 2.0, extension .uno.pkg) format which lets you specify detailed media types for each particle of your add-on bundle. All other files are ignored. HTH, -Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
