Difference between revisions of "Documentation/DevGuide/WritingUNO/Test the Registration"
From Apache OpenOffice Wiki
< Documentation | DevGuide
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Writing UNO Components) |
OOoWikiBot (Talk | contribs) m (Robot: Automated text replacement (-Category:Documentation/Developers Guide/Professional UNO +Category:Documentation/Developers Guide/Writing UNO)) |
||
Line 20: | Line 20: | ||
{{PDL1}} | {{PDL1}} | ||
− | [[Category:Documentation/Developers Guide/ | + | [[Category:Documentation/Developers Guide/Writing UNO]] |
Revision as of 07:25, 4 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
A short OpenOffice.org Basic program indicates if the program runs went smoothly, by selecting Tools – Macro and entering a new macro name on the left, such as TestImageShrink
and click New to create a new procedure. In the procedure, enter the appropriate code of the component. The test routine for ImageShrink
would be:
Sub TestImageShrink oTestComp = createUnoService("org.openoffice.test.ImageShrink") MsgBox oTestComp.dbg_methods MsgBox oTestComp.dbg_properties MsgBox oTestComp.dbg_supportedInterfaces end sub
The result should be three dialogs showing the methods, properties and interfaces supported by the implementation. Note that the interface attributes do not appear as get/set methods, but as properties in Basic. If the dialogs do not show what is expected, refer to the section Troubleshooting.
Content on this page is licensed under the Public Documentation License (PDL). |