TBO and RESTful services

Tom Nanos

     I have a question about RESTful Services 7.3 and custom TBOs.  In one of our repositories (D7.1) there is a custom TBO that, among other things, applies an overlay to a PDF document dynamically at view time.  Historically to ensure this works correctly in an external application like PDF Annotation Services or CARA, we package the classes and supporting JARs with the deployment, and all works correctly.  We are currently deploying DCTM REST Services 7.3 to our infrastructure, and did the same with the TBO for this repository - package the classes and supporting JARs with the REST build (as somewhat indicated in the Development Guide).  But when requesting a document, the TBO is never invoked, and only the original PDF rendition is served to the browser.  An example URL used is this:

http://rest-app-server/dctm-rest/repositories/target-docbase/objects/090fffff800488b0/content-media?format=pdf

Am I calling for the content incorrectly?  Or is there some other code that needs to be added to enable the TBO to be invoked at view time?

The TBO JARs appear to be downloaded by DFC into the cache folder.  The only thing of any potential meaning I can find in the logs is this:

2017-02-13 14:13:03,209 INFO localhost-startStop-1 org.springframework.web.context.support.AnnotationConfigWebApplicationContext - No annotated classes found for specified class/package [com.foo.bar.bof.tbo.implementations]

Thanks in advance

-Tom

Alvaro_de_Andres

I'm quit sure REST honors TBOs, when deployed as modules in the repository, so you should only bundle the interface (in case you added new methods) as you usually did in WDK applications, because the implementation is automatically downloaded from the GR and run as any other TBO.