Hi Cedric,
Cedric Bosdonnat wrote:
Hi Juergen, all,
I've found a small problem with the uno-skeletonmaker when refactoring
code. The idl code was building correctly after the refactoring, but
there was an error when running the uno-skeletonmaker afterwards. The
error message was something like this:
Error: Rejecting types due to incompatibility!
In fact, I found out that the incompatibility came from a version of the
component which was deployed on my OOo before the refactoring. removing
the extension from OOo made the uno-skeletonmaker work again.
The uno-skeletonmaker was run using a command like the following one:
uno-skeletonmaker
-env:BOOTSTRAPINI="/opt/openoffice.org2.3/program/bootstraprc" component
--java5 -o ./source -l file:////opt/openoffice.org2.3/program/types.rdb
-l types.rdb -n my.serviceImpl -t myService
What does the uno-skeletonmaker do with OOo extensions? Is this normal?
Is there any way to avoid such strange things?
extensions are well integrated in the office type system and when you
use the skeletonmaker with the env:INIFILENAME option you will use the
whole type system of the office. The type system detects here an
incompatible type change and reports this problem. That is totally correct.
In this case you shouldn't use the env:INIFILENAME option but the
env:UNO_TYPES option to use the types.rdb only.
I got the same error when removing the extension and replacing it with a
new one without restarting OOo. Is this a bug in the types managment?
no
Juergen
Thanks for your answers,
Cedric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
