Difference between revisions of "Documentation/DevGuide/JavaBean/Using the OOoBean"
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:JavaBean for Office Components) |
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Documentation/Developers Guide/JavaBean for Office Components) |
||
Line 13: | Line 13: | ||
{{PDL1}} | {{PDL1}} | ||
− | [[Category:Documentation/ | + | [[Category:Documentation/Developer's Guide/JavaBean for Office Components]] |
Revision as of 09:11, 5 June 2008
The Java class OOoBean
can be instantiated directly, or application classes can be derived from this class. If a real Java Bean is to be created, which for example can be used in Java Bean UI builders, it has to be subclassed. The application class then might use the UNO bootstrapping mechanism to find the OOoBean
, OpenOffice.org and its API classes. This mechanism is not build into OOoBean
itself because it can not be used to find itself. And once the OOoBean
class has been found, you intrinsically also find the OpenOffice.org installation and the API classes.
A standard OpenOffice.org is a prerequisite. The OpenOffice.org executable, as well as the UNO libraries and runtime, is found using the Java Class Loader. Moving or copying the needed class files will not result in a working OOoBean
.
Content on this page is licensed under the Public Documentation License (PDL). |