[jira] [Updated] (CMIS-656) Provide extension points for the protocol handling logic

["Carlo Sciolla (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CMIS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo Sciolla updated CMIS-656:
-------------------------------

    Attachment: noreflection.patch

The provided patch only affects the AtomPub binding (and partially the Browser binding, which is left broken for the time being) in the following ways:

- a new ServiceCall single method interface is created, with a method call having the same interface as all Service methods used to have

- single classes per service area (e.g. ObjectService) are translated into packages (e.g. org.apache.chemistry.opencmis.server.impl.atompub.object)

- classes inside the service packages implement the ServiceCall interface, thus implementing a single service call each

- the dispatch logic at servlet level is similar to what it used to be, with the Dispatcher now not using reflection anymore to point to the service logic but rather concrete instances of ServiceCall

- CmisAtomPubServlet has a protected registerDispatch method to allow subclasses to override the default bindings
                
> Provide extension points for the protocol handling logic
> --------------------------------------------------------
>
>                 Key: CMIS-656
>                 URL: https://issues.apache.org/jira/browse/CMIS-656
>             Project: Chemistry
>          Issue Type: Improvement
>          Components: opencmis-server
>    Affects Versions: OpenCMIS 0.9.0 beta 1
>            Reporter: Carlo Sciolla
>         Attachments: noreflection.patch
>
>
> Chemistry takes full control over the serialization process, including all details of the underlying HTTP communication. Extension points or APIs in this process would allow implementors to leverage greater flexibility to fine tune the serialization process, or to implement extensions over the standard CMIS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira