google-nomulus/javatests/google/registry/flows/contact/testdata
mcilwain 33505f4df7 Make async flow logic handle missing client transaction IDs
Per EPP RFC 5730, the <clTRID> element is optional. However, we weren't handling
it not being specified in asynchronous contact/host deletions because we were
adding it directly as a parameter value on a task, which does not allow null and
thus threw a NullPointerException.

This fixes handling for nulls (the parameter isn't set at all) and adds a test.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=194123259
2018-05-05 23:21:55 -04:00
..
contact_check.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_check_50.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_check_51.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_check_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_create.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_create_decline_disclosure.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_create_hebrew_int.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_create_hebrew_loc.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_create_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_delete.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_delete_no_cltrid.xml Make async flow logic handle missing client transaction IDs 2018-05-05 23:21:55 -04:00
contact_delete_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_delete_response_no_cltrid.xml Make async flow logic handle missing client transaction IDs 2018-05-05 23:21:55 -04:00
contact_info.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_info_no_authinfo.xml Contact authInfo should not be visible to all registrars in <info> flows 2016-09-22 14:30:05 -04:00
contact_info_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_info_response_linked.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_info_response_no_authinfo.xml Contact authInfo should not be visible to all registrars in <info> flows 2016-09-22 14:30:05 -04:00
contact_transfer_approve.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_approve_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_approve_with_authinfo.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_cancel.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_cancel_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_cancel_with_authinfo.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query_response_client_approved.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query_response_client_cancelled.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query_response_client_rejected.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query_response_server_approved.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query_response_server_cancelled.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query_with_authinfo.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_query_with_roid.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_reject.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_reject_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_reject_with_authinfo.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_request.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_request_no_authinfo.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_transfer_request_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_update.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_update_add_remove_same.xml Add a missing test to ContactUpdateFlow 2016-09-14 15:55:52 -04:00
contact_update_decline_disclosure.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_update_hebrew_int.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_update_hebrew_loc.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_update_localized.xml Replace command.applyTo() with inlined builder operations 2016-11-02 15:19:34 -04:00
contact_update_partial_postalinfo.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_update_partial_postalinfo_preserve_int.xml Replace command.applyTo() with inlined builder operations 2016-11-02 15:19:34 -04:00
contact_update_prohibited_status.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_update_remove_client_update_prohibited.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00
contact_update_response.xml mv com/google/domain/registry google/registry 2016-05-13 18:55:08 -04:00