https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-520 controller <p>When I invoke an RPC which expects no input, it shouldn't matter what the content/type header is set to. Unfortunately you MUST have a content type other than application/json (or xml, or their variants) in order to get the call routed to the correct REST method. This happens because the code that deserializes the string into a composite node asserts that there be something defined.</p> <p>Instead of enforcing content at the deserialization (which is not aware of whether input is required or not) we should allow deserialization to return null, and perform the proper validation when have the RPC call definition.</p> <p>Operating System: Mac OS<br/> Platform: PC</p> CONTROLLER-520

Invoking an RPC with no expend input should not fail when content type is set to application/json

Bug Resolved Cannot Reproduce Devin Avery Devin Avery Thu, 29 May 2014 19:09:16 +0000 Thu, 14 May 2015 08:20:39 +0000 Thu, 14 May 2015 08:20:39 +0000 Helium restconf 0 5 <p>Did not end up having time to get to this. If we can fix before release great, otherwise it should move off to lithium</p> <p>Tried to reproduce (with cancel-toast which takes no inout) but it works properly no matter what the content type is. This was fixed upstream as the front-end parsing code now returns null if no input is provided and the proper checking is done in the service methods.</p> Development External issue ID 1100 External issue URL ODL SR Target Milestone Rank 0|i02kwn: