The embedded documents do not support any particular database related service, instead, they're
usual ::com::sun::star::document::OfficeDocuments.
The only thing worth mentioning here is that they support the
::com::sun::star::container::XChild interface, whose
::com::sun::star::container::XChild::getParent method can be used to
obtain the database document which the embedded document belongs to.
provides functionality for treating the container as part of a hierarchy
of a database document's sub documents.
The ::com::sun::star::ucb::XCommandProcessor::execute method
of a DocumentDefinition supports at least the following commands, additionally to
the ones already supported by the DefinitionContent:
open: provides a ::com::sun::star::ucb::XDynamicResultSet
to enumerate the content of the document container.
delete: deletes the document container, including all contained documents.
URL: describes the name of the document definition to load,
TargetFrameName: isn't used.
SearchFlags: isn't used.
Arguments:
PropertyValue
Name = ActiveConnection
Value = The connection which should be used when opening the text document.
PropertyValue
Name = OpenMode
Value = string, "open" if the document should be opened in live mode (editing is not possible),
"openDesign" if the document should be open in design mode (editing is possible)
If this interface is supported, the object created using it (e.g., the object returned by
XMultiServiceFactory::createInstanceWithArguments()
) can be used as container elements.
