"PATCH" rest verb - Forum - OpenEdge Development - Progress Community
 Forum

"PATCH" rest verb

  • Hi, it does not seem to be possible to use the "PATCH" verb with the OpenEdge REST Adapter - although when mapping the JSON input and OUTPUT to LONGCHAR and not a temp-table/ProDataset I could see that a nice fit.

    Are there any blocking issues with implementing PATCH requests with the REST Adapter?

    I know that PATCH may now be required for JSDO/OE Mobile/etc.. - but when using the REST Adapter for integration purposes this definitively makes sense.

    Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.

  • restful-api-design.readthedocs.org/.../methods.html

    Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.


  • Hi Mike,
    True, you cannot use PATCH and I would never debate with you its potential usefulness.  

    There are no issues that stand out that would block its adoption other than needing to update the HTTP request mapper and tools. 

    If PATCH begins being used by the JDSO technology, the REST services will need to comply, and whatever is in the REST services will be available for general REST interoperability.   That is the policy so far.

    Perhaps an enhancement request would be appropriate to get the process started ASAP?
     
    Mike J.

    From: Mike Fechner <bounce-mikefechner@community.progress.com>
    Reply-To: "TU.OE.Development@community.progress.com" <TU.OE.Development@community.progress.com>
    Date: Friday, January 16, 2015 at 5:28 AM
    To: "TU.OE.Development@community.progress.com" <TU.OE.Development@community.progress.com>
    Subject: [Technical Users - OE Development] "PATCH" rest verb

    Thread created by Mike Fechner

    Hi, it does not seem to be possible to use the "PATCH" verb with the OpenEdge REST Adapter - although when mapping the JSON input and OUTPUT to LONGCHAR and not a temp-table/ProDataset I could see that a nice fit.

    Are there any blocking issues with implementing PATCH requests with the REST Adapter?

    I know that PATCH may now be required for JSDO/OE Mobile/etc.. - but when using the REST Adapter for integration purposes this definitively makes sense.

    Stop receiving emails on this subject.

    Flag this post as spam/abuse.

  • Yepp ;-)
    Von: Michael Jacobs [mailto:bounce-mjacobs@community.progress.com]
    Gesendet: Freitag, 16. Januar 2015 12:45
    An: TU.OE.Development@community.progress.com
    Betreff: Re: [Technical Users - OE Development] "PATCH" rest verb
     
    Reply by Michael Jacobs
     
    Hi Mike,
    True, you cannot use PATCH and I would never debate with you its potential usefulness.  
     
    There are no issues that stand out that would block its adoption other than needing to update the HTTP request mapper and tools. 
     
    If PATCH begins being used by the JDSO technology, the REST services will need to comply, and whatever is in the REST services will be available for general REST interoperability.   That is the policy so far.
     
    Perhaps an enhancement request would be appropriate to get the process started ASAP?
     
    Mike J.
     
    From: Mike Fechner <bounce-mikefechner@community.progress.com>
    Reply-To: "TU.OE.Development@community.progress.com" <TU.OE.Development@community.progress.com>
    Date: Friday, January 16, 2015 at 5:28 AM
    To: "TU.OE.Development@community.progress.com" <TU.OE.Development@community.progress.com>
    Subject: [Technical Users - OE Development] "PATCH" rest verb
     
    Thread created by Mike Fechner

    Hi, it does not seem to be possible to use the "PATCH" verb with the OpenEdge REST Adapter - although when mapping the JSON input and OUTPUT to LONGCHAR and not a temp-table/ProDataset I could see that a nice fit.

    Are there any blocking issues with implementing PATCH requests with the REST Adapter?

    I know that PATCH may now be required for JSDO/OE Mobile/etc.. - but when using the REST Adapter for integration purposes this definitively makes sense.

    Stop receiving emails on this subject.

    Flag this post as spam/abuse.

    Stop receiving emails on this subject.

    Flag this post as spam/abuse.

    Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.

  • I will +1 it if you add it in the Ideas section J
  • Architect of the SmartComponent Library and WinKit

    Consultingwerk Ltd.