Home
Asset Picker
Developer Guide
Plugin development overview
Asset Picker facilitates easy integration with new content repositories without having to alter the core Asset Picker framework.
Components of plugin
A typical plugin contains the following components:
Service implementations
For each service declared in the service meta information file, there must be an implementation present inside the respective factoryClass.
Best approach selection
Although, it is possible to implement a service using either approaches, each approach has some advantages and limitations when it comes to the capabilities.

Asset Picker
- Administrator Guide
- Developer Guide
  - Overview
    Asset Picker facilitates easy integration with Content Management Systems and enables searching content from the Content Management Systems.
  - Plugin development overview
    Asset Picker facilitates easy integration with new content repositories without having to alter the core Asset Picker framework.
    - Components of plugin
      A typical plugin contains the following components:
      - Service meta information file
        The following are the pre-requisites for meta information file:
      - Service implementations
        For each service declared in the service meta information file, there must be an implementation present inside the respective factoryClass.
        RESTful approach
        The com.example.service.rest.CustomService class helps you understand REST based service implementation.
        Functional approach
        Refer to the com.example.service.functional.CustomService class to understand the functional service implementation.
        Best approach selection
        Although, it is possible to implement a service using either approaches, each approach has some advantages and limitations when it comes to the capabilities.
  - SDK Plugin Development
  - Verification and troubleshooting
- Release Notes

Best approach selection

Although, it is possible to implement a service using either approaches, each approach has some advantages and limitations when it comes to the capabilities.

RESTful approach
1. Advantages
  - Less verbose & reads closer to the typical HTTP interaction
  - Out of the box transport level error handling
  - Out of the box support for retrial in case of temporary outages
  - Out of the box support for proxied connectivity
  - Out of the box support for future enhancements in Asset Picker in this regard
2. Limitations
  - Cannot be used for non-RESTful or non-HTTP integrations, such as database or file system interactions
Functional approach
1. Advantages
  - Can be used for non-RESTful or non-HTTP integrations, such as database or file system interactions
2. Limitations
  - No out-of-the-box support available for transport level error handling, retrials, proxied connectivity, and any future enhancements from Asset Picker
  - Incorporation of logic for all the missing out of the box supports can make functional service very verbose

You can see that the Function approach is well suited for non-RESTful or non-HTTP based integrations. Any service implemented using RESTful approach can also be implemented using Functional approach by taking care of all the necessary out-of-the-box capabilities provided by Asset Picker. While Functional approach gives flexibility in terms of implementation design, it takes away a few useful capabilities.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.