[STANBOL-573] Add Factory for ContentItems and Blobs

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.0-incubating
• Fix Version/s: enhancer-0.10.0
• Component/s: Enhancer
• Assignee: Rupert Westenthaler
• Reporter: Rupert Westenthaler
• Created: 05/Apr/12 06:22
• Updated: 17/Jul/13 15:16
• Resolved: 11/Apr/12 09:52

Description

Currently the used implementation for ContentItems/Blobs is hardcoded for the Stanbol Enhancer. The same is true for other components that do use the Java API of the Enhancer (e.g. the Contenthub).

The introduction of a ContentItemFactory that registers itself as OSGI service would allow to change the used implementation based on a configuration.

A simple usage scenario where this would make sense in the enhancement of big media files. Currently those files are kept in-memory, because thats the way how the currently used InMemoryContentItem/InMemoryBlob implementation works.
While having the data in memory is best suited for typically enhancement requests (small to medium sized textual content) this might become troublesome for users that whant to extract and enhance metadata from media files (e.g. ID3 tags from MP3 or Exif metadata from TIF images). The facrory pattern would allow to configure a ContentItem/Blob implementation that keeps the parsed content in temporary files.

Issue Links

• relates to: STANBOL-574 Add ContentItem/Blob implementation that stores the parsed content in a temporary file