Version 2

    The bug occurs when sending a document object which is not a file in the activity service.


    So, if you have this JSON string for the object.


    "object":{ "displayName":"A test document",
               "summary":"Test document text",

    JiveObjectProvider is used to get the Document object. In the method object(..), even if it's not a file, the FileProvider is used to retrieve the document.

    Then, in the method object(..), there is a hack that catches WebServiceExceptions, and then tries to use the DocumentProvider in case it is actually a document.


    The problem though, is that File provider's method lookupContent(..) throws BeanCreationException instead of NotFoundException (that extends WebServiceException).

    Indeed, when trying to build the exception in CoreErrorBuilder, the line jiveTextProviderFactory.get() throw this exception with the following message:

    Error creating bean with name 'scopedTarget.jiveTextProviderFactory': Scope 'request' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton


    Is it a problem on my part? It didn't seem to be in the known issues.