Debugger is not triggering in CHANGESET_BEGIN and CHANGESET_END

[Former Member]

Hi All,

I am not able to debug in method /IWBEP/IF_MGW_APPL_SRV_RUNTIME~CHANGESET_BEGIN and in /IWBEP/IF_MGW_APPL_SRV_RUNTIME~CHANGESET_END .

I have redefined these methods and using batch operation .

However getentity is triggering for each batch request.

Regards,

Ajay

[former_member184867 · Accepted solution]

As the names of methods suggest, they are associated with some kind of change. In READ/QUERY you are not changing anything, so the call never comes to *_CHANGESET methods.  Here is the explanation why it happens.

Below is a sample payload for a BATCH request containing only QUERY operation

--batch
Content-Type: application/http
Content-Transfer-Encoding: binary
GET TravelagencyCollection HTTP/1.1
--batch
Content-Type: application/http
Content-Transfer-Encoding: binary
GET CarrierCollection?$format=json HTTP/1.1
--batch--

Below is a sample payload for a BATCH request containing POST  operation

--batch
Content-Type: multipart/mixed; boundary=changeset
--changeset
Content-Type: application/http
Content-Transfer-Encoding: binary
POST TravelagencyCollection HTTP/1.1
Content-Type: application/atom+xml
Content-Length: ###
<AtomPub representation of Travel Agency 1>***
--changeset
Content-Type: application/http
Content-Transfer-Encoding: binary
POST TravelagencyCollection HTTP/1.1
Content-Type: application/atom+xml
Content-Length: ###
<AtomPub representation of Travel Agency 2>***
--changeset--
--batch--

The difference is the changeset information being sent in the second payload. This needs to be done if you are doing CREATE - UPDATE - DELETE using the BATCH operation in Gateway.

For READ - QUERY we do not need to pass the changeset information.

This is the reason why the call does not go to *_CHANGESET methods.

Regards,

Atanu

[AshwinDutt]

Hello Ajay,

I see since its a GET operation in BATCH mode its not stopping.

Check for any Create/Update/Delete operation in BATCH mode, It will stop.

Regards,

Ashwin