About
-
- First commit 12 February 2011
- Latest commit 07 February 2012
| Last Week | All Time | |
|---|---|---|
| Commits: | 0 | 291 |
| Files changed: | 0 | 2,430 |
| Change in LOC: | 0 | 38,388 |
Reviews
2 active reviews
Counts may include data that you cannot access.
Line History
 
Commit Activity
52 week commits volume
Commits by day
Commits by hour
Commit calendar
pbryan
pbryan
resolved OPENIDM-550
07 Feb
Now uses new org.forgerock.json.resource.* version 1.2.2, which resolves this issue.
pbryan
pbryan
pbryan
"If-Match: *" now derives the version from the fetched resource.
modified
JsonServerResource.java
pbryan
New version 1.2.2.
modified
pom.xml
pbryan
New snapshot version 1.2.3-SNAPSHOT.
modified
pom.xml
pbryan
New version 1.2.2.
added
1.2.2
pbryan
"If-Match: *" now derives the version from the fetched resource.
modified
JsonServerResource.java
pbryan
Use fixed upstream org.forgerock.json.resource.* libraries.
modified
pom.xml
pbryan
Use fixed upstream org.forgerock.json.resource.* libraries.
modified
pom.xml
pbryan
Avoid spuriously reading resource.
modified
JsonServerResource.java
pbryan
Changed version to 1.2.2-SNAPSHOT.
modified
pom.xml
pbryan
Update version to 1.2.1.
modified
pom.xml
pbryan
New 1.2.1 release.
added
1.2.1
pbryan
Avoid spuriously reading resource.
modified
JsonServerResource.java
pbryan
commented on OPENIDM-547
30 Jan
1. Note: Laszlo's note about removing his fix from the put() method was incorrect. The null checks were in fact there.
2. Actual cause: When the Restlet code sees an invalid tag in the If-Match or If-None-Match header, instead of throwing an exception, merely logs the problem as INFO, and populates the tag list with a null value.
3. Implemented solution: New checks in the doHandle method determine if null values appear in the Match or NoneMatch condition tag lists, and if so, throws a Bad Request (400) resource exception with an explanation message (e.g. "Invalid If-Match tag").
4. Note: The new code I've checked-in has now removed the checks in the put() method, as the doHandle() method does all of this checking.
2. Actual cause: When the Restlet code sees an invalid tag in the If-Match or If-None-Match header, instead of throwing an exception, merely logs the problem as INFO, and populates the tag list with a null value.
3. Implemented solution: New checks in the doHandle method determine if null values appear in the Match or NoneMatch condition tag lists, and if so, throws a Bad Request (400) resource exception with an explanation message (e.g. "Invalid If-Match tag").
4. Note: The new code I've checked-in has now removed the checks in the put() method, as the doHandle() method does all of this checking.
pbryan
Change org.forgerock.json.resource.* dependencies to 1.2.0 to resolve OPENIDM-547 and OPENIDM-548.
modified
pom.xml
pbryan
Change org.forgerock.json.resource.* dependencies to 1.2.0 to resolve OPENIDM-547 and OPENIDM-548.
modified
pom.xml
pbryan
Update version to 1.3.0-SNAPSHOT.
modified
pom.xml
pbryan
Update version to 1.2.1-SNAPSHOT.
modified
pom.xml
pbryan
Change version to 1.2.0.
modified
pom.xml
pbryan
Handle case where Restlet represents invalid If-Match/If-None-Match tags with null conditions.
Avoid spurious read of resource in unambiguous create (PUT w. If-None-Match: *).
Avoid spurious read of resource in unambiguous create (PUT w. If-None-Match: *).
modified
JsonServerResource.java
pbryan
commented on OPENIDM-547
27 Jan
Will definitely fix the NPE. FYI, an unquoted ETag value is invalid.
