Hi Ariel, > "Usually, you don't deal with this loader directly. Instead it is > registered for a particular URL scheme, and you use the dispatch > mechanism provided by the application framework, dispatching URLs the > loader is registered for." > > I think the road to follow is querying a dispatch object for this > command URL, and then calling dispatch() on the returned object, passing > the arguments specified in every service in that call. > That is, XComponentLoader::loadComponentFromURL() seems not to be the > proper one (although it works...)
This document was in fact written before there was an XComponentLoader interface, when XDispatch/Provider was the only choice to load a specific component. I'll correct that in the documentation (that is, I'll replace the "dispatch" references with a mention of XComponentLoader). Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
