The static Reference< XContent > getContent() in
ucbhelper/source/client/content.cxx at line 327ff is called to create
help content, with the xId being
vnd.sun.star.help://?Language=en&System=&Version=${PRODUCTVERSION}.
(Yeah, the ${PRODUCTVERSION} should have been expanded I guess; that
is not the problem here I hope.)
As there is no help (because I don't build any help contents or help
code for Android or iOS, as the help text, and help display concept,
needs to be rewritten / redesigned anyway for these platforms, it
throws a com.sun.star.ucb.ContentCreationException.
I don't see from where exactly it is called (as I haven't built the
calling code for debugging; doing that now, hopefully I guessed
correctly from where it is called): But anyway, in the log I see the
Java message mentioned in the Subject,
java.lang.reflect.UndeclaredThrowableException. I wonder what that
means, anybody have any idea?
Shouldn't this ContentCreationException be caught somewhere in the C++
stack already, so that it never gets out to the Java levels (where
Dalvik then gets upset because it apparently is thrown by something
that doesn't declare throwing such an exception)?
Or is building without xmlhelp doomed to fail at run-time? (I have
made xmlhelp conditional on DESKTOP in the */prj/build.lst files where
it is mentioned.)
--tml
Context
- Android: java.lang.reflect.UndeclaredThrowableException from	com.sun.star.ucb.ContentCreationException: Unable to create Content · Tor Lillqvist
 
   
 
  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.