Difference between revisions of "Documentation/DevGuide/WritingUNO/Storing the Service Manager for Further Use"
From Apache OpenOffice Wiki
< Documentation | DevGuide
m (1 revision(s)) |
OOoWikiBot (Talk | contribs) m (FINAL VERSION FOR L10N) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
|NextPage=Documentation/DevGuide/WritingUNO/Create Instance with Arguments | |NextPage=Documentation/DevGuide/WritingUNO/Create Instance with Arguments | ||
}} | }} | ||
| + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/WritingUNO/{{SUBPAGENAME}}}} | ||
{{DISPLAYTITLE:Storing the Service Manager for Further Use}} | {{DISPLAYTITLE:Storing the Service Manager for Further Use}} | ||
A component usually runs in the office process. There is no need to create an interprocess channel explicitly. A component does not have to create a service manager, because it is provided to the single factory of an implementation by the service manager during a call to <code>createInstance()</code> or <code>createInstanceWithContext()</code>. The single factory receives an <code>XComponentContext</code> or an <code>XMultiServiceFactory</code>, and passes it to the corresponding constructor of the service implementation. From the component context, the implementation gets the service manager using <code>getServiceManager()</code> at the <idl>com.sun.star.uno.XComponentContext</idl> interface. | A component usually runs in the office process. There is no need to create an interprocess channel explicitly. A component does not have to create a service manager, because it is provided to the single factory of an implementation by the service manager during a call to <code>createInstance()</code> or <code>createInstanceWithContext()</code>. The single factory receives an <code>XComponentContext</code> or an <code>XMultiServiceFactory</code>, and passes it to the corresponding constructor of the service implementation. From the component context, the implementation gets the service manager using <code>getServiceManager()</code> at the <idl>com.sun.star.uno.XComponentContext</idl> interface. | ||
{{PDL1}} | {{PDL1}} | ||
| − | [[Category: Writing UNO Components]] | + | |
| + | [[Category:Documentation/Developer's Guide/Writing UNO Components]] | ||
Latest revision as of 08:50, 13 May 2009
- 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 component usually runs in the office process. There is no need to create an interprocess channel explicitly. A component does not have to create a service manager, because it is provided to the single factory of an implementation by the service manager during a call to createInstance() or createInstanceWithContext(). The single factory receives an XComponentContext or an XMultiServiceFactory, and passes it to the corresponding constructor of the service implementation. From the component context, the implementation gets the service manager using getServiceManager() at the com.sun.star.uno.XComponentContext interface.
| Content on this page is licensed under the Public Documentation License (PDL). |
