https://bugs.documentfoundation.org/show_bug.cgi?id=152972

            Bug ID: 152972
           Summary: Javamaker fails with "unknown entity"
           Product: LibreOffice
           Version: 7.3.6.2 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: sdk
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: dloch...@aussiebb.com.au

Created attachment 184570
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184570&action=edit
This IDL definition fails JAVAMAKER after running IDLC and REGMERGE
successfully.

I've developed two succesful Calc extensions, both written in Java using the
old method of hand-coding everything.  However a current project using
'javamaker' fails when that utility diagnoses:
    ERROR: Unknown entity 'com.sun.star.uno.XComponentContext'

Both 'idlc' and 'regmerge' run successfully.

Similar behaviour is reported on github also at
https://flywire.github.io/lo-p/47-Calc_Add-ins.html - see Chapter 47, section
2.4. "Problems with Office Types".

QUOTE:
"Office's idlc.exe and regmerge.exe tools are happy to process these types, but
javamaker.exe always fails to recognize 'com.sun.star.table.XCellRange' and
'com.sun.star.sheet.XVolatileResult', reporting an "Unknown entity" error. I
tried calling javamaker with the inclusion of extra Office RDB files, such as
services.rdb and offapi.rdb, but with no success.

I was unable to find an add-in example online that uses XCellRange, perhaps
because it's more natural to pass a cell range to a function as an array.
UNQUOTE

Attempting to run idlc / regmerge / javamaker on an earlier hand-coded
extension which has run successfully over several versions of LibreOffice
results in exactly the same problem.  Since this earlier extension works, is
simpler, and shows the same problem it's copied here as an example.  Note, the
directive to "include" <com.sun.star.uno.XComponentContext.idl> was inserted to
see if it fixed the problem, but isn't in the original IDL definition.

Regards!

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to