Hi Isomorphic,
today's nightly (v10.1p_2016-04-13) introduced a bug for me where dsRequest.getOperationId() returns "dsName_dsOperationType" instead of the configured operationId sent from the client.
I can see the correct operationId in the developer console, but get the wrong from dsRequest.getOperationId() in my IDACall subclasses' handleDSRequest().
Eclipse debug / Developer Console screenshot:
MyIDACall method:
This was working as expected with yesterday's nightly (v10.1p_2016-04-12).
Could you check if something was changed here?
Thank you & Best regards
Blama
today's nightly (v10.1p_2016-04-13) introduced a bug for me where dsRequest.getOperationId() returns "dsName_dsOperationType" instead of the configured operationId sent from the client.
I can see the correct operationId in the developer console, but get the wrong from dsRequest.getOperationId() in my IDACall subclasses' handleDSRequest().
Eclipse debug / Developer Console screenshot:
MyIDACall method:
Code:
public DSResponse handleDSRequest(DSRequest dsRequest, RPCManager rpc, RequestContext context) throws Exception { // Logger logger = new Logger(LMSIDACall.class); String dsID = dsRequest.getDataSource().getID(); String operationType = dsRequest.getOperationType(); String operationID = dsRequest.getOperationId() != null ? dsRequest.getOperationId() : "null"; // Most likely always not null
This was working as expected with yesterday's nightly (v10.1p_2016-04-12).
Could you check if something was changed here?
Thank you & Best regards
Blama
Comment