Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi there,
using the openoffice-eclipse plugin we implemented 2 uno. extensions (as
.pkg and as oxt) in Java and installed them in OpenOfficePortable v3.2,
in LibreOffice 3.3 and in a self-build LibreOfficePortable 3.3

After the installation, both packages worked fine, but randomly we get
com.sun.star.loader.CannotActivateFactoryExceptuion with messages like
"No factory object for de.foo.baz.FoobazImpl."

Both uno-pakages were installed using Extras:ExtensionManager.
Experimenting with unopkg validate before starting scalc has the same
effect. Using the extension manager we see that the packages are
sometimes disabled but unopkg verify does not give any hints.


Any help is urgently welcome

-- 

--ukriegel
-----------------------------------------------------------------------------
Dr. E.Ulrich Kriegel,Fraunhofer-Institut für Software- und Systemtechnik ISST 
Sichere Business IT-Infrastrukturen, Wissenschaftlicher Mitarbeiter
Am Steinplatz 2, 10623 Berlin, Germany
Telefon: +49 (0) 30 / 2 43 06-446 
mailto:ulrich.kriegel@isst.fraunhofer.de
http://www.isst.fraunhofer.de
==============================================================================



-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.