If the Action in Line 193 throws an IllegalArgumentException (for reasons that are within the updateOperation (for Example an Enum-Entry can not be found by Name or whatever custom logic might throw an IllegalArgumentException) then it simply disappears.
I am sure that line of code is there for a reason, but maybe one should catch a more specific Exception instead all IllegalArgumentException in that line. Otherwise Exceptions thrown by DatabasePersistence or Processing the UpdateOperation are just swalloed and the user thinks everything is saved.
If the Action in Line 193 throws an IllegalArgumentException (for reasons that are within the updateOperation (for Example an Enum-Entry can not be found by Name or whatever custom logic might throw an IllegalArgumentException) then it simply disappears.
I am sure that line of code is there for a reason, but maybe one should catch a more specific Exception instead all IllegalArgumentException in that line. Otherwise Exceptions thrown by DatabasePersistence or Processing the UpdateOperation are just swalloed and the user thinks everything is saved.