[rhq-project/rhq] c9d5d9: Bug 1122444 - Server responds with 204 even if it ...

Branch: refs/heads/master Home: https://github.com/rhq-project/rhq Commit: c9d5d91254a6032f9cb2c9f427c6f9d1b7f361ce https://github.com/rhq-project/rhq/commit/c9d5d91254a6032f9cb2c9f427c6f9d... Author: Libor Zoubek <lzoubek(a)redhat.com&gt; Date: 2014-09-29 (Mon, 29 Sep 2014) Changed paths: M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/rest/MetricHandlerBean.java M modules/integration-tests/rest-api/src/test/java/org/rhq/modules/integrationTests/restApi/MetricsTest.java Log Message: ----------- Bug 1122444 - Server responds with 204 even if it fails to find the schedule upon POST /metric/data/raw request As POST /metric/data/raw accepts data points for various schedule IDs rejecting all data, just because several have invalid scheduleId may not be a good idea. Current fix does: * return 204 (No content) in case all scheduleIds are valid and all data were accepted * returns 201 (rejected data) in case some data points were rejected and some accepted * returns 403 (rejected data) in case all data points were rejected This commit also fixes endpoint POST /metric/data/raw/{resourceId} which now returns 403 in case there is at least 1 non-existing metric for given resource ID (this case was previously failing on NPE) Commit: 29186360a4103ad82a86dcc2b257f354c2bf7b1b https://github.com/rhq-project/rhq/commit/29186360a4103ad82a86dcc2b257f35... Author: Libor Zoubek <lzoubek(a)redhat.com&gt; Date: 2014-09-29 (Mon, 29 Sep 2014) Changed paths: M modules/common/jboss-as-dmr-client/src/main/java/org/rhq/common/jbossas/client/controller/InfinispanJBossASClient.java M modules/enterprise/server/installer/src/main/java/org/rhq/enterprise/server/installer/ServerInstallUtil.java M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/rest/AbstractRestBean.java Log Message: ----------- Bug 1122444 - Server responds with 204 even if it fails to find the schedule Get ISPN cache to work correctly for REST: REST api was using incorrect cache name - so used cache was not preconfigured at all, thatswhy cache entries never expired. Now, we'll deploy rhqRestCache which is preconfigured with lifespan=15m and max-idle=5min. This means, cache entry will be dropped and refreshed every 15minutes no matter how often is accessed and also if not accessed for longer than 5minutes. Commit: 39f45463d9c17aaef108dcc177898d0bd5319335 https://github.com/rhq-project/rhq/commit/39f45463d9c17aaef108dcc177898d0... Author: Libor Zoubek <lzoubek(a)jezzovo.net&gt; Date: 2014-09-29 (Mon, 29 Sep 2014) Changed paths: M modules/common/jboss-as-dmr-client/src/main/java/org/rhq/common/jbossas/client/controller/InfinispanJBossASClient.java M modules/enterprise/server/installer/src/main/java/org/rhq/enterprise/server/installer/ServerInstallUtil.java M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/rest/AbstractRestBean.java M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/rest/MetricHandlerBean.java M modules/integration-tests/rest-api/src/test/java/org/rhq/modules/integrationTests/restApi/MetricsTest.java Log Message: ----------- Merge pull request #104 from lzoubek/bugs/1122444 Bug 1122444 - Server responds with 204 even if it fails to find the sche... Compare: https://github.com/rhq-project/rhq/compare/b4b0238a2351...39f45463d9c1