Hi Jochen,
>What is a CWS?
Child Work Space. A branch in CVS with a new feature set.
>> No, it does not make sense. You still needed to add a classfile to your
>> application or the "application bean". Because if we could execute the
>> code which finds ourselves, we would not need to find ourseves andmore.
>> And if we need to use the code to find the code, we have an unsolved
>> problem.
>
>I'm sorry, I'm quite new, and I used to think that one should NOT
>incorporate officebean.jar(as with the oo1.1 examples) into ones
>application because it has a relative path to libofficebean.so and thus
>to the OO installation?
I was not talking about officebean.jar etc. I was talking about the UNO
bootstrap class needed for transparent UNO loading. It is not needed,
only optional, but it would have been needed, if the OOoBean relied on
it.
>> The OOoBean is meant to be used as a baseclass in application beans. The
>> applications beans then are specialized to whatever the application
>> needs. These can use the transparent class loader (UNO bootstrap
>> mechanism) and implement the bean info etc.
>
>... and those Application Beans can also be Applications like
>"my-java-app-that-shows-a-oo-writer"?
Yes, of course. In this case you will probalby not need a "real" Java
Bean, with bean info and stuff, in this case you most likely can use
OOoBean as it is. You just have to make sure that it can find soffice
and its jar files, e.g. by having the class files where they belong
(under program/classes) and having them in your CLASSPATH. Or your
class loader has to make sure it can find them, and soffice.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
