Difference between revisions of "Documentation/DevGuide/WritingUNO/Make Registration Available to OpenOffice.org"
From Apache OpenOffice Wiki
< Documentation | DevGuide
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Documentation/Developers Guide/Writing UNO) |
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Documentation/Developers Guide/Writing UNO Components) |
||
| Line 17: | Line 17: | ||
{{PDL1}} | {{PDL1}} | ||
| − | [[Category:Documentation/ | + | [[Category:Documentation/Developer's Guide/Writing UNO Components]] |
Revision as of 11:17, 5 June 2008
- Class Definition with Helper Class
- Implementing Your Own Interfaces
- Providing a Single Factory Using a Helper Method
- Write Registration Info Using a Helper Method
- Implementing without Helpers
- Storing the Service Manager for Further Use
- Create Instance with Arguments
- Possible Structures for Java Components
- Running and Debugging Java Components
- Register Component File
- Make Registration Available to OpenOffice.org
- Test the Registration
- Debugging
- The Java Environment in OpenOffice.org
- Troubleshooting
OpenOffice.org must be told to use the registry. Close all OpenOffice.org parts, including the Quickstarter that runs in the Windows task bar. Edit the file uno(.ini|rc) in <OfficePath>/program as follows:
[Bootstrap] UNO_TYPES=$SYSBINDIR/types.rdb $SYSBINDIR/<your_registry>.rdb UNO_SERVICES=$SYSBINDIR/services.rdb $SYSBINDIR/<your_registry>.rdb
For details about the syntax of uno(.ini|rc) and alternative registration procedures, refer to the section Deployment Options for Components. If OpenOffice.org is restarted, the component should be available.
| Content on this page is licensed under the Public Documentation License (PDL). |
