Clean up changes.xml
This commit is contained in:
James
parent
ea5a023e17
commit
6875da8556
2
pom.xml
2
pom.xml
|
|
@ -1059,6 +1059,7 @@
|
|||
<ignore></ignore>
|
||||
</action>
|
||||
</pluginExecution>
|
||||
<!--
|
||||
<pluginExecution>
|
||||
<pluginExecutionFilter>
|
||||
<groupId>
|
||||
|
|
@ -1098,6 +1099,7 @@
|
|||
<ignore></ignore>
|
||||
</action>
|
||||
</pluginExecution>
|
||||
-->
|
||||
</pluginExecutions>
|
||||
</lifecycleMappingMetadata>
|
||||
</configuration>
|
||||
|
|
|
|||
|
|
@ -6,16 +6,122 @@
|
|||
<title>HAPI FHIR Changelog</title>
|
||||
</properties>
|
||||
<body>
|
||||
<release version="2.3" date="TBD">
|
||||
<action type="add">
|
||||
Bump the version of a few dependencies to the
|
||||
latest versions (dependent HAPI modules listed in brackets):
|
||||
<![CDATA[
|
||||
<ul>
|
||||
<li>Hibernate (JPA): 5.1.0 -> 5.2.7</li>
|
||||
<li>Hibernate Search (JPA): 5.5.4 ->p; 5.7.0.CR1</li>
|
||||
<li>Hibernate Validator (JPA): 5.2.4 ->p; 5.3.4</li>
|
||||
<li>Spring (JPA): 4.3.1 -> 4.3.6</li>
|
||||
</ul>
|
||||
]]>
|
||||
</action>
|
||||
<action type="fix">
|
||||
CLI example uploader couldn't find STU3 examples after CI server
|
||||
was moved to build.fhir.org
|
||||
</action>
|
||||
<action type="fix">
|
||||
Fix issue in JPA subscription module that prevented purging stale
|
||||
subscriptions when many were present on Postgres
|
||||
</action>
|
||||
<action type="fix" issue="532">
|
||||
Server interceptor methods were being called twice unnecessarily
|
||||
by the JPA server, and the DaoConfig interceptor registration
|
||||
framework was not actually useful. Thanks to GitHub user
|
||||
@mattiuusitalo for reporting!
|
||||
</action>
|
||||
<action type="fix" issue="503">
|
||||
AuthorizationInterceptor on JPA server did not correctly
|
||||
apply rules on deleting resources in a specific compartment
|
||||
because the resource metadata was stripped by the JPA server
|
||||
before the interceptor could see it. Thanks to
|
||||
Eeva Turkka for reporting!
|
||||
</action>
|
||||
<action type="fix" issue="519">
|
||||
JPA server exported CapabilityStatement includes
|
||||
double entries for the _id parameter and uses the
|
||||
wrong type (string instead of token). Thanks to
|
||||
Robert Lichtenberger for reporting!
|
||||
</action>
|
||||
<action type="add" issue="504">
|
||||
Custom resource types which extend Binary must not
|
||||
have declared extensions since this is invalid in
|
||||
FHIR (and HAPI would just ignore them anyhow). Thanks
|
||||
to Thomas S Berg for reporting!
|
||||
</action>
|
||||
<action type="add">
|
||||
Standard HAPI zip/tar distributions did not include the project
|
||||
sources and JavaDoc JARs. Thanks to Keith Boone for pointing
|
||||
this out!
|
||||
</action>
|
||||
<action type="fix">
|
||||
Server AuthorizationInterceptor always rejects history operation
|
||||
at the type level even if rules should allow it.
|
||||
</action>
|
||||
<action type="fix">
|
||||
JPA server terminology service was not correctly validating or expanding codes
|
||||
in SNOMED CT or LOINC code systems. Thanks to David Hay for reporting!
|
||||
</action>
|
||||
<action type="fix" issue="539">
|
||||
Attempting to search for an invalid resource type (e.g. GET base/FooResource) should
|
||||
return an HTTP 404 and not a 400, per the HTTP spec. Thanks to
|
||||
GitHub user @CarthageKing for the pull request!
|
||||
</action>
|
||||
<action type="fix" issue="544">
|
||||
When parsing a Bundle containing placeholder fullUrls and references
|
||||
(e.g. "urn:uuid:0000-0000") the resource reference targets did not get
|
||||
populated with the given resources. Note that as a part of this
|
||||
change, <![CDATA[<code>IdType</code> and <code>IdDt</code>]]> have been modified
|
||||
so that when parsing a placeholder ID, the complete placeholder including the
|
||||
"urn:uuid:" or "urn:oid:" prefix will be placed into the ID part. Previously,
|
||||
the prefix was treated as the base URL, which led to strange behaviour
|
||||
like the placeholder being treated as a real IDs. Thanks to GitHub
|
||||
user @jodue for reporting!
|
||||
</action>
|
||||
<action type="add">
|
||||
Declared extensions with multiple type() options listed in the @Child
|
||||
annotation caused a crash on startup. Now this is supported.
|
||||
</action>
|
||||
<action type="add">
|
||||
STU3 XHTML parser for narrative choked if the narrative contained
|
||||
an <![CDATA[<code>&rsquot;</code>]]> entity string.
|
||||
</action>
|
||||
<action type="fix" issue="538">
|
||||
When parsing a quantity parameter on the server with a
|
||||
value and units but no system (e.g.
|
||||
<![CDATA[<code>GET [base]/Observation?value=5.4||mg</code>]]>)
|
||||
the unit was incorrectly treated as the system. Thanks to
|
||||
@CarthageKing for the pull request!
|
||||
</action>
|
||||
<action type="533">
|
||||
Correct a typo in the JPA ValueSet ResourceProvider which prevented
|
||||
successful operation under Spring 4.3. Thanks to
|
||||
Robbert van Waveren for the pull request!
|
||||
</action>
|
||||
<action type="remove">
|
||||
Deprecate the method
|
||||
<![CDATA[<code>ICompositeElement#getAllPopulatedChildElementsOfType(Class)</code>]]>
|
||||
as it is no longer used by HAPI and is just an annoying step
|
||||
in creating custom structures. Thanks to Allan Bro Hansen
|
||||
for pointing this out.
|
||||
</action>
|
||||
<action type="fix" issue="547">
|
||||
CapturingInterceptor did not buffer the response meaning
|
||||
that in many circumstances it did not actually capture
|
||||
the response. Thanks to Jenny Syed of Cerner for
|
||||
the pull request and contribution!
|
||||
</action>
|
||||
</release>
|
||||
<release version="2.2" date="2016-12-20">
|
||||
<action type="add">
|
||||
Bump the version of a few dependencies to the
|
||||
latest versions (dependent HAPI modules listed in brackets):
|
||||
<![CDATA[
|
||||
<ul>
|
||||
<li>Hibernate (JPA): 5.1.0 -> 5.2.7</li>
|
||||
<li>Hibernate Search (JPA): 5.5.4 ->p; 5.7.0.CR1</li>
|
||||
<li>Hibernate Validator (JPA): 5.2.4 ->p; 5.3.4</li>
|
||||
<li>Spring (JPA): 4.3.1 -> 4.3.6</li>
|
||||
<ul>
|
||||
<!--<li>spring (JPA): 4.3.1 -> 4.3.4</li>-->
|
||||
<li>Derby (CLI): 10.12.1.1 -> 10.13.1.1</li>
|
||||
<li>Jetty (CLI): 9.3.10.v20160621 -> 9.3.14.v20161028</li>
|
||||
<li>JAnsi (CLI): 1.13 -> 1.14</li>
|
||||
|
|
@ -23,7 +129,7 @@
|
|||
</ul>
|
||||
]]>
|
||||
</action>
|
||||
<action type="fix">
|
||||
<action type="fix">
|
||||
Fix issue in AuthorizationIntetceptor where
|
||||
transactions are blocked even when they
|
||||
should not be
|
||||
|
|
@ -174,101 +280,6 @@
|
|||
return CapabilityStatement instead of the previously used
|
||||
"Conformance" resource
|
||||
</action>
|
||||
<action type="fix">
|
||||
CLI example uploader couldn't find STU3 examples after CI server
|
||||
was moved to build.fhir.org
|
||||
</action>
|
||||
<action type="fix">
|
||||
Fix issue in JPA subscription module that prevented purging stale
|
||||
subscriptions when many were present on Postgres
|
||||
</action>
|
||||
<action type="fix" issue="532">
|
||||
Server interceptor methods were being called twice unnecessarily
|
||||
by the JPA server, and the DaoConfig interceptor registration
|
||||
framework was not actually useful. Thanks to GitHub user
|
||||
@mattiuusitalo for reporting!
|
||||
</action>
|
||||
<action type="fix" issue="503">
|
||||
AuthorizationInterceptor on JPA server did not correctly
|
||||
apply rules on deleting resources in a specific compartment
|
||||
because the resource metadata was stripped by the JPA server
|
||||
before the interceptor could see it. Thanks to
|
||||
Eeva Turkka for reporting!
|
||||
</action>
|
||||
<action type="fix" issue="519">
|
||||
JPA server exported CapabilityStatement includes
|
||||
double entries for the _id parameter and uses the
|
||||
wrong type (string instead of token). Thanks to
|
||||
Robert Lichtenberger for reporting!
|
||||
</action>
|
||||
<action type="add" issue="504">
|
||||
Custom resource types which extend Binary must not
|
||||
have declared extensions since this is invalid in
|
||||
FHIR (and HAPI would just ignore them anyhow). Thanks
|
||||
to Thomas S Berg for reporting!
|
||||
</action>
|
||||
<action type="add">
|
||||
Standard HAPI zip/tar distributions did not include the project
|
||||
sources and JavaDoc JARs. Thanks to Keith Boone for pointing
|
||||
this out!
|
||||
</action>
|
||||
<action type="fix">
|
||||
Server AuthorizationInterceptor always rejects history operation
|
||||
at the type level even if rules should allow it.
|
||||
</action>
|
||||
<action type="fix">
|
||||
JPA server terminology service was not correctly validating or expanding codes
|
||||
in SNOMED CT or LOINC code systems. Thanks to David Hay for reporting!
|
||||
</action>
|
||||
<action type="fix" issue="539">
|
||||
Attempting to search for an invalid resource type (e.g. GET base/FooResource) should
|
||||
return an HTTP 404 and not a 400, per the HTTP spec. Thanks to
|
||||
GitHub user @CarthageKing for the pull request!
|
||||
</action>
|
||||
<action type="fix" issue="544">
|
||||
When parsing a Bundle containing placeholder fullUrls and references
|
||||
(e.g. "urn:uuid:0000-0000") the resource reference targets did not get
|
||||
populated with the given resources. Note that as a part of this
|
||||
change, <![CDATA[<code>IdType</code> and <code>IdDt</code>]]> have been modified
|
||||
so that when parsing a placeholder ID, the complete placeholder including the
|
||||
"urn:uuid:" or "urn:oid:" prefix will be placed into the ID part. Previously,
|
||||
the prefix was treated as the base URL, which led to strange behaviour
|
||||
like the placeholder being treated as a real IDs. Thanks to GitHub
|
||||
user @jodue for reporting!
|
||||
</action>
|
||||
<action type="add">
|
||||
Declared extensions with multiple type() options listed in the @Child
|
||||
annotation caused a crash on startup. Now this is supported.
|
||||
</action>
|
||||
<action type="add">
|
||||
STU3 XHTML parser for narrative choked if the narrative contained
|
||||
an <![CDATA[<code>&rsquot;</code>]]> entity string.
|
||||
</action>
|
||||
<action type="fix" issue="538">
|
||||
When parsing a quantity parameter on the server with a
|
||||
value and units but no system (e.g.
|
||||
<![CDATA[<code>GET [base]/Observation?value=5.4||mg</code>]]>)
|
||||
the unit was incorrectly treated as the system. Thanks to
|
||||
@CarthageKing for the pull request!
|
||||
</action>
|
||||
<action type="533">
|
||||
Correct a typo in the JPA ValueSet ResourceProvider which prevented
|
||||
successful operation under Spring 4.3. Thanks to
|
||||
Robbert van Waveren for the pull request!
|
||||
</action>
|
||||
<action type="remove">
|
||||
Deprecate the method
|
||||
<![CDATA[<code>ICompositeElement#getAllPopulatedChildElementsOfType(Class)</code>]]>
|
||||
as it is no longer used by HAPI and is just an annoying step
|
||||
in creating custom structures. Thanks to Allan Bro Hansen
|
||||
for pointing this out.
|
||||
</action>
|
||||
<action type="fix" issue="547">
|
||||
CapturingInterceptor did not buffer the response meaning
|
||||
that in many circumstances it did not actually capture
|
||||
the response. Thanks to Jenny Syed of Cerner for
|
||||
the pull request and contribution!
|
||||
</action>
|
||||
</release>
|
||||
<release version="2.1" date="2016-11-11">
|
||||
<action type="add">
|
||||
|
|
|
|||
Loading…
Reference in New Issue