- Description
- describes a class of service which will be used for deep TypeDetection
in a generic way
Due to the registered types, flat TypeDetection is already possible, i.e.
the assignment of types (e.g. to a URL) only on the basis of configuration data.
If, however, you imagine special cases (e.g. modifying the file extension of a
Writer file from .sdw to .doc), it quickly becomes clear that you cannot always
get a correct result with flat detection. To be certain to get correct results,
you need deep detection, i.e. the file itself has to be examined.
And that is exactly the function of DetectServices. They get all the information
collected so far on a document and then decide which type to assign it to.
In the new modular model, such a detector is meant as UNO service which registers
itself in the office and is requested by the generic type detection if necessary.
Therefore you need two pieces of information:
-
The ServiceName - This must be a valid UNO service name.
It is also an entry in the corresponding configuration list.
Example: "com.company.devision.DetectService"
Note that this realy means the implementation name of the service.
Because it's not possible otherwise to distinguish between more then one
registered detect services in same office installation! But it's possible for
the generic type detection to create an uno service by his implementation name too.
-
A list of Types able to be recognized by this service -
You can also implement and register detectors for groups of types.
See service TypeDetection and his configuration for further informations.
- See also
- TypeDetection
- Developers Guide
- OfficeDev - Integrating Import and Export Filters
- OfficeDev - XML Filter Detection
|