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? 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? Thanks for your answers, Cedric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
