#11722: Fixed for invalid HTTP response when creating content-type wi…

…th (#11740) (#11742) existing variable
dotCMS · May 26, 2017 · 29a0898 · 29a0898
1 parent 8f9140b
commit 29a0898
Showing 1 changed file with 8 additions and 0 deletions.
diff --git a/dotCMS/src/main/java/com/dotcms/rest/api/v1/contenttype/ContentTypeResource.java b/dotCMS/src/main/java/com/dotcms/rest/api/v1/contenttype/ContentTypeResource.java
@@ -97,6 +97,10 @@ public final Response createType(@Context final HttpServletRequest req, final St
 
 			response = ExceptionMapperUtil.createResponse(null, "Content-type is not valid ("+ e.getMessage() +")");
 
+		} catch (DotDataException e) {
+
+			response = ExceptionMapperUtil.createResponse(null, "Content-type is not valid ("+ e.getMessage() +")");
+
 		} catch (Exception e) {
 
 			response = ExceptionMapperUtil.createResponse(e, Response.Status.INTERNAL_SERVER_ERROR);
@@ -150,6 +154,10 @@ public Response updateType(@PathParam("id") final String id, final String json,
 
 			response = ExceptionMapperUtil.createResponse(e, Response.Status.NOT_FOUND);
 
+		} catch (DotDataException e) {
+
+			response = ExceptionMapperUtil.createResponse(null, "Content-type is not valid ("+ e.getMessage() +")");
+
 		} catch (Exception e) {
 
 			response = ExceptionMapperUtil.createResponse(e, Response.Status.INTERNAL_SERVER_ERROR);