3

I have recently added some @RestResource classes to a managed package and the implementations have been changing from version to version of the managed package.

I had assumed that when the managed package is installed it would always be the version of the @RestResource from the latest version of the managed package that would be used when a REST request is handled. But I have one example where this did not appear to be the case.

Is the versioning behavior for this situation documented anywhere?

Improve this question
6
  • Hey Keith, could you explain more of the details of the example that didn't meet your expectations?
    – Benj
    Commented Jan 5, 2014 at 18:13
  • Sure. I added some debug logging to the class, created a new package version and deployed it. When invoking over HTTP the logging did not appear. When invoking from the developer console via Apex it did. (Detailed logging for the managed package was turned on via a case.) Got me concerned about what the versioning model is.
    – Keith C
    Commented Jan 6, 2014 at 20:44
  • Did you ever solve this problem? I'm running into something similar right now.
    – Charles Koppelman
    Commented Jan 8, 2019 at 15:58
  • @CharlesKoppelman Sorry, as far as I remember I didn't get to the bottom of this.
    – Keith C
    Commented Jan 8, 2019 at 16:47
  • 1
    @CharlesKoppelman Sorry again - no recollection as it was 5 years ago.
    – Keith C
    Commented Jan 8, 2019 at 17:27

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .