Documentation updates
This commit is contained in:
James Agnew
parent
c0c85d7c8c
commit
04b79a7b6f
|
|
@ -12,7 +12,7 @@
|
|||
title: "Documentation fixes"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "Add a collection of new methods on the generic client which support the <b><a href=\"./apidocs/ca/uhn/fhir/rest/client/IGenericClient.html#read(java.lang.Class,%20ca.uhn.fhir.model.primitive.UriDt)\">read</a></b>, <b><a href=\"./apidocs/ca/uhn/fhir/rest/client/IGenericClient.html#vread(java.lang.Class,%20ca.uhn.fhir.model.primitive.UriDt)\">read</a></b>, and <b><a href=\"./apidocs/ca/uhn/fhir/rest/client/IGenericClient.html#search(java.lang.Class,%20ca.uhn.fhir.model.primitive.UriDt)\">search</a></b> operations using an absolute URL. This allows developers to perform these operations using URLs they obtained from other sources (or external resource references within resources). In addition, the existing read/vread operations will now access absolute URL references if they are passed in. Thanks to Doug Martin of the Regenstrief Center for Biomedical Informatics for contributing this implementation!"
|
||||
title: "Add a collection of new methods on the generic client which support the <b>read</b> and <b>search</b> operations using an absolute URL. This allows developers to perform these operations using URLs they obtained from other sources (or external resource references within resources). In addition, the existing read/vread operations will now access absolute URL references if they are passed in. Thanks to Doug Martin of the Regenstrief Center for Biomedical Informatics for contributing this implementation!"
|
||||
- item:
|
||||
type: "fix"
|
||||
title: "Server implementation was not correctly figuring out its own FHIR Base URL when deployed on Amazon Web Service server. Thanks to Jeffrey Ting and Bill De Beaubien of Systems Made Simple for their help in figuring out this issue!"
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
- item:
|
||||
type: "add"
|
||||
title: "<b>API CHANGE:</b> The \"FHIR structures\" for DSTU1 (the classes which model the resources and composite datatypes) have been moved out of the core JAR into their own JAR, in order to allow support for DEV resources, and DSTU2 resources when thast version is finalized. See the <a href=\"./doc_dstu2.html\">DSTU2 page</a> for more information."
|
||||
title: "<b>API CHANGE:</b> The \"FHIR structures\" for DSTU1 (the classes which model the resources and composite datatypes) have been moved out of the core JAR into their own JAR, in order to allow support for DEV resources, and DSTU2 resources when thast version is finalized. See the DSTU2 page for more information."
|
||||
- item:
|
||||
type: "fix"
|
||||
title: "<b>Deprecated API Removal</b>: The following classes (which were deprocated previously) have now been removed: <ul> <li><b>ISecurityManager</b>: If you are using this class, the same functionality is available through the more general purpose <a href=\"http://jamesagnew.github.io/hapi-fhir/doc_rest_server_interceptor.html\">server interceptor</a> capabilities.</li> <li><b>CodingListParam</b>: This class was made redundant by the <a href=\"http://jamesagnew.github.io/hapi-fhir/apidocs/ca/uhn/fhir/rest/param/TokenOrListParam.html\">TokenOrListParam</a> class, which can be used in its place.</li> </ul>"
|
||||
title: "<b>Deprecated API Removal</b>: The following classes (which were deprocated previously) have now been removed: <ul> <li><b>ISecurityManager</b>: If you are using this class, the same functionality is available through the more general purpose server interceptor capabilities.</li> <li><b>CodingListParam</b>: This class was made redundant by the TokenOrListParam class, which can be used in its place.</li> </ul>"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "<b>API Change</b>: The IResource#getResourceMetadata() method has been changed from returning <code>Map<ResourceMetadataKeyEnum<?>, Object></code> to returning a new type called <code>ResourceMetadataMap</code>. This new type implements <code>Map<ResourceMetadataKeyEnum<?>, Object></code> itself, so this change should not break existing code, but may require a clean build in order to run correctly."
|
||||
|
|
@ -109,7 +109,7 @@
|
|||
- item:
|
||||
issue: "59"
|
||||
type: "fix"
|
||||
title: "Clean up the way that Profile resources are automatically exported by the server for custom resource profile classes. See the <a href=\"http://jamesagnew.github.io/hapi-fhir/apidocs/ca/uhn/fhir/model/api/annotation/ResourceDef.html\">@ResourceDef</a> JavaDoc for information on how this works."
|
||||
title: "Clean up the way that Profile resources are automatically exported by the server for custom resource profile classes. See the @ResourceDef JavaDoc for information on how this works."
|
||||
- item:
|
||||
issue: "73"
|
||||
type: "add"
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@
|
|||
- item:
|
||||
issue: "152"
|
||||
type: "add"
|
||||
title: "Add a new parser validation mechanism (see the <a href=\"./doc_validation.html\">validation page</a> for info) which can be used to validate resources as they are being parsed, and optionally fail if invalid/unexpected elements are found in resource bodies during parsing."
|
||||
title: "Add a new parser validation mechanism (see the validation page for info) which can be used to validate resources as they are being parsed, and optionally fail if invalid/unexpected elements are found in resource bodies during parsing."
|
||||
- item:
|
||||
type: "fix"
|
||||
title: "IParser#parseResource(Class, String) method, which is used to parse a resource into the given structure will now throw a DataFormatException if the structure is for the wrong type of resource for the one actually found in the input String (or Reader). For example, if a Patient resource is being parsed into Organization.class this will now cause an error. Previously, the XML parser would ignore the type and the JSON parser would fail. This also caused operations to not parse correctly if they returned a resource type other than parameters with JSON encoding (e.g. the $everything operation on UHN's test server). Thanks to Avinash Shanbhag for reporting!"
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@
|
|||
title: "Fix issue in testpage-overlay's new Java configuration where only the first configured server actually gets used."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "Introduce <a href=\"./apidocs-jpaserver/ca/uhn/fhir/jpa/dao/IJpaServerInterceptor.html\">IJpaServerInterceptor</a> interceptors for JPA server which can be used for more fine grained operations."
|
||||
title: "Introduce IJpaServerInterceptor interceptors for JPA server which can be used for more fine grained operations."
|
||||
- item:
|
||||
issue: "241"
|
||||
type: "fix"
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
title: "Remove a dependency on a Java 1.7 class (ReflectiveOperationException) in several spots in the codebase. This dependency was accidentally introduced in 1.3, and animal-sniffer-plugin failed to detect it (sigh)."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "Add two new server interceptors: <a href=\"./apidocs/ca/uhn/fhir/rest/server/interceptor/RequestValidatingInterceptor.html\">RequestValidatingInterceptor</a> and <a href=\"./apidocs/ca/uhn/fhir/rest/server/interceptor/ResponseValidatingInterceptor.html\">ResponseValidatingInterceptor</a> which can be used to validate incoming requests or outgoing responses using the standard FHIR validation tools. See the <a href=\"./doc_rest_server_interceptor.html#RequestResponse_Validation\">Server Validation Page</a> for examples of how to use these interceptors. These intereptors have both been enabled on the <a href=\"http://fhirtest.uhn.ca\">public test page</a>."
|
||||
title: "Add two new server interceptors: RequestValidatingInterceptor and ResponseValidatingInterceptor which can be used to validate incoming requests or outgoing responses using the standard FHIR validation tools. See the Server Validation Page for examples of how to use these interceptors. These intereptors have both been enabled on the <a href=\"http://fhirtest.uhn.ca\">public test page</a>."
|
||||
- item:
|
||||
issue: "259"
|
||||
type: "fix"
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@
|
|||
title: "Added options to the CLI upload-examples command which allow it to cache the downloaded content file, or use an arbitrary one. Thanks to Adam Carbone for the pull request!"
|
||||
- item:
|
||||
type: "fix"
|
||||
title: "REST search parameters with a prefix/comparator had not been updated to use the DSTU2 style prefixes (gt2011-01-10) instead of the DSTU1 style prefixes (>2011-01-01). The client has been updated so that it uses the new prefixes if the client has a DSTU2+ context. The server has been updated so that it now supports both styles. <br/><br/> As a part of this change, a new enum called <a href=\"./apidocs/ca/uhn/fhir/rest/param/ParamPrefixEnum.html\">ParamPrefixEnum</a> has been introduced. This enum replaces the old <a href=\"./apidocs/ca/uhn/fhir/model/dstu/valueset/QuantityCompararatorEnum.html\">QuantityCompararatorEnum</a> which has a typo in its name and can not represent several new prefixes added since DSTU1."
|
||||
title: "REST search parameters with a prefix/comparator had not been updated to use the DSTU2 style prefixes (gt2011-01-10) instead of the DSTU1 style prefixes (>2011-01-01). The client has been updated so that it uses the new prefixes if the client has a DSTU2+ context. The server has been updated so that it now supports both styles. <br/><br/> As a part of this change, a new enum called ParamPrefixEnum has been introduced. This enum replaces the old QuantityCompararatorEnum which has a typo in its name and can not represent several new prefixes added since DSTU1."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "JPA server number and quantity search params now follow the rules for the use of precision in search terms outlined in the <a href=\"https://www.hl7.org/fhir/search.html\">search page</a> of the FHIR specification. For example, previously a 1% tolerance was applied for all searches (10% for approximate search). Now, a tolerance which respects the precision of the search term is used (but still 10% for approximate search)."
|
||||
|
|
@ -127,11 +127,11 @@
|
|||
- item:
|
||||
issue: "315"
|
||||
type: "add"
|
||||
title: "Add a new method to FhirContext called <code><a href=\"./apidocs/ca/uhn/fhir/context/FhirContext.html#setDefaultTypeForProfile-java.lang.String-java.lang.Class-\">setDefaultTypeForProfile</a></code> which can be used to specify that when recources are received which declare support for specific profiles, a specific custom structures should be used instead of the default. For example, if you have created a custom Observation class for a specific profile, you could use this method to cause your custom type to be used by the parser for resources in a search bundle you receive. <br/><br/> See the documentation page on <a href=\"./doc_extensions.html\">Profiles and Extensions</a> for more information."
|
||||
title: "Add a new method to FhirContext called <code>setDefaultTypeForProfile</code> which can be used to specify that when recources are received which declare support for specific profiles, a specific custom structures should be used instead of the default. For example, if you have created a custom Observation class for a specific profile, you could use this method to cause your custom type to be used by the parser for resources in a search bundle you receive. <br/><br/> See the documentation page on Profiles and Extensions for more information."
|
||||
- item:
|
||||
issue: "315"
|
||||
type: "fix"
|
||||
title: "Parsing/Encoding a custom resource type which extends a base type sometimes caused the FhirContext to treat all future parses of the same resource as using the custom type even when this was not wanted. <br/><br/> Custom structures may now be explicitly declared by profile using the <code><a href=\"./apidocs/ca/uhn/fhir/context/FhirContext.html#setDefaultTypeForProfile-java.lang.String-java.lang.Class-\">setDefaultTypeForProfile</a></code> method. <br/><br/> This issue was discovered and fixed as a part of the implementation of issue #315."
|
||||
title: "Parsing/Encoding a custom resource type which extends a base type sometimes caused the FhirContext to treat all future parses of the same resource as using the custom type even when this was not wanted. <br/><br/> Custom structures may now be explicitly declared by profile using the <code>setDefaultTypeForProfile</code> method. <br/><br/> This issue was discovered and fixed as a part of the implementation of issue #315."
|
||||
- item:
|
||||
issue: "321"
|
||||
type: "add"
|
||||
|
|
@ -141,7 +141,7 @@
|
|||
title: "JPA server now allows searching by token parameter using a system only and no code, giving a search for any tokens which match the given token with any code. Previously the expected behaviour for this search was not clear in the spec and HAPI had different behaviour from the other reference servers."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "Introduce a JAX-RS client provider which can be used instead of the default Apache HTTP Client provider to provide low level HTTP services to HAPI's REST client. See <a href=\"./doc_rest_client_alternate_provider.html\">JAX-RS & Alternate HTTP Client Providers</a> for more information. <br/><br/> This is useful in cases where you have other non-FHIR REST clients using a JAX-RS provider and want to take advantage of the rest of the framework. <br/><br/> Thanks to Peter Van Houte from Agfa for the amazing work!"
|
||||
title: "Introduce a JAX-RS client provider which can be used instead of the default Apache HTTP Client provider to provide low level HTTP services to HAPI's REST client. See JAX-RS & Alternate HTTP Client Providers for more information. <br/><br/> This is useful in cases where you have other non-FHIR REST clients using a JAX-RS provider and want to take advantage of the rest of the framework. <br/><br/> Thanks to Peter Van Houte from Agfa for the amazing work!"
|
||||
- item:
|
||||
issue: "312"
|
||||
type: "fix"
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
- item:
|
||||
type: "fix"
|
||||
title: "Performance has been improved for the initial FhirContext object creation by avoiding a lot of unnecessary reflection. HAPI FHIR 1.5 had a regression compared to previous releases and this has been corrected, but other improvements have been made so that this release is faster than previous releases too. <br/><br/> In addition, a new \"deferred scan\" mode has been implemented for even faster initialization on slower environments (e.g. Android). See the <a href=\"./doc_rest_client_http_config.html#performance\">performance documentation</a> for more information. <br/><br/> The following shows our benchmarks for context initialization across several versions of HAPI: <ul> <li>Version 1.4: <b>560ms</b></li> <li>Version 1.5: <b>800ms</b></li> <li>Version 1.6: <b>340ms</b></li> <li>Version 1.6 (deferred mode): <b>240ms</b></li> </ul>"
|
||||
title: "Performance has been improved for the initial FhirContext object creation by avoiding a lot of unnecessary reflection. HAPI FHIR 1.5 had a regression compared to previous releases and this has been corrected, but other improvements have been made so that this release is faster than previous releases too. <br/><br/> In addition, a new \"deferred scan\" mode has been implemented for even faster initialization on slower environments (e.g. Android). See the performance documentation for more information. <br/><br/> The following shows our benchmarks for context initialization across several versions of HAPI: <ul> <li>Version 1.4: <b>560ms</b></li> <li>Version 1.5: <b>800ms</b></li> <li>Version 1.6: <b>340ms</b></li> <li>Version 1.6 (deferred mode): <b>240ms</b></li> </ul>"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "Bump the version of a few dependencies to the latest versions (dependent HAPI modules listed in brackets): <ul> <li>Spring (JPA, Web Tester): 4.2.5 -> 4.3.0</li> <li>Spring-Data (JPA): 1.9.2 -> 1.10.1</li> <!--<li>Hibernate ORM (JPA): 5.1.0 -> 5.2.0</li>--> <li>Hibernate Search (JPA): 5.5.2 -> 5.5.3</li> <li>Jetty (CLI): 9.3.9 -> 9.3.10</li> </ul>"
|
||||
|
|
@ -117,7 +117,7 @@
|
|||
- item:
|
||||
issue: "363"
|
||||
type: "add"
|
||||
title: "JPA server can now be configured to allow external references (i.e. references that point to resources on other servers). See <a href=\"./doc_jpa.html\">JPA Documentation</a> for information on how to use this. Thanks to Naminder Soorma for the suggestion!"
|
||||
title: "JPA server can now be configured to allow external references (i.e. references that point to resources on other servers). See JPA Documentation for information on how to use this. Thanks to Naminder Soorma for the suggestion!"
|
||||
- item:
|
||||
issue: "366"
|
||||
type: "fix"
|
||||
|
|
@ -125,7 +125,7 @@
|
|||
- item:
|
||||
issue: "364"
|
||||
type: "fix"
|
||||
title: "Enable parsers to parse and serialize custom resources that contain custom datatypes. An example has been added which shows how to do this <a href=\"./doc_custom_structures.html\">here</a>"
|
||||
title: "Enable parsers to parse and serialize custom resources that contain custom datatypes. An example has been added which shows how to do this in the docs."
|
||||
- item:
|
||||
type: "fix"
|
||||
title: "JSON parser was incorrectly encoding resource language attribute in JSON as an array instead of a string. Thanks to David Hay for reporting!"
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@
|
|||
title: "RestfulServer with no explicitly set FhirContext fails to detect the presents of DSTU3 structures. Thanks to GitHub user @vijayt27 for reporting!"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "As the <a href=\"https://github.com/eBay/cors-filter\">eBay CORS interceptor</a> project has gone dormant, we have introduced a new HAPI server interceptor which can be used to implement CORS support instead of using the previously recommended Servlet Filter. All server examples as well as the CLI have been switched to use this new interceptor. See the <a href=\"./doc_cors.html\">CORS Documentation</a> for more information."
|
||||
title: "As the <a href=\"https://github.com/eBay/cors-filter\">eBay CORS interceptor</a> project has gone dormant, we have introduced a new HAPI server interceptor which can be used to implement CORS support instead of using the previously recommended Servlet Filter. All server examples as well as the CLI have been switched to use this new interceptor. See the CORS Documentation for more information."
|
||||
- item:
|
||||
issue: "480"
|
||||
type: "fix"
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
- item:
|
||||
type: "add"
|
||||
title: "Support for FHIR R4 (current working draft) has been <b>added</b> (in a new module called <code>hapi-fhir-structures-r4</code> ) and support for FHIR DSTU1 ( <code>hapi-fhir-structures-dstu</code> ) has been <b>removed</b> . Removing support for the legacy DSTU1 FHIR version was a difficult decision, but it allows us the opportunitity to clean up the codebase quite a bit, and remove some confusing legacy parts of the API (such as the legacy Atom Bundle class). <br/><br/> A new redesigned table of HAPI FHIR versions to FHIR version support has been added to the <a href=\"http://hapifhir.io/download.html\">Download Page</a>"
|
||||
title: "Support for FHIR R4 (current working draft) has been <b>added</b> (in a new module called <code>hapi-fhir-structures-r4</code> ) and support for FHIR DSTU1 ( <code>hapi-fhir-structures-dstu</code> ) has been <b>removed</b> . Removing support for the legacy DSTU1 FHIR version was a difficult decision, but it allows us the opportunitity to clean up the codebase quite a bit, and remove some confusing legacy parts of the API (such as the legacy Atom Bundle class). <br/><br/> A new redesigned table of HAPI FHIR versions to FHIR version support has been added to the Download Page"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "HAPI FHIR's modules have been restructured for more consistency and less coupling between unrelated parts of the API. <br/><br/> A new complete list of HAPI FHIR modules has been added to the <a href=\"http://hapifhir.io/download.html\">Download Page</a> . Key changes include: <ul> <li> HAPI FHIR's <b>client</b> codebase has been moved out of <code>hapi-fhir-base</code> and in to a new module called <code>hapi-fhir-client</code>. Client users now need to explicitly add this JAR to their project (and non-client users now no longer need to depend on it) </li> <li> HAPI FHIR's <b>server</b> codebase has been moved out of <code>hapi-fhir-base</code> and in to a new module called <code>hapi-fhir-server</code>. Server users now need to explicitly add this JAR to their project (and non-server users now no longer need to depend on it) </li> <li> As a result of the client and server changes above, we no longer need to produce a special Android JAR which contains the client, server (which added space but was not used) and structures. There is now a normal module called <code>hapi-fhir-android</code> which is added to your Android Gradle file along with whatever structures JARs you wish to add. See the <a href=\"https://github.com/hapifhir/hapi-fhir-android-integration-test\">Android Integration Test</a> to see a sample project using HAPI FHIR 3.0.0. <b>Note that this has been reported to work by some people but others are having issues with it!</b> In order to avoid delaying this release any further we are releasing now despite these issues. If you are an Android guru and want to help iron things out please get in touch. If not, it might be a good idea to stay on HAPI FHIR 2.5 until the next point release of the 3.x series. </li> <li> A new JAR containing FHIR utilities called <code>hapi-fhir-utilities</code> has been added. This JAR reflects the ongoing harmonization between HAPI FHIR and the FHIR RI codebases and is generally required in order to use HAPI at this point (if you are using a dependency manager such as Maven or Gradle it will be brought in to your project automatically as a dependency) </li> </ul>"
|
||||
title: "HAPI FHIR's modules have been restructured for more consistency and less coupling between unrelated parts of the API. <br/><br/> A new complete list of HAPI FHIR modules has been added to the Download Page. Key changes include: <ul> <li> HAPI FHIR's <b>client</b> codebase has been moved out of <code>hapi-fhir-base</code> and in to a new module called <code>hapi-fhir-client</code>. Client users now need to explicitly add this JAR to their project (and non-client users now no longer need to depend on it) </li> <li> HAPI FHIR's <b>server</b> codebase has been moved out of <code>hapi-fhir-base</code> and in to a new module called <code>hapi-fhir-server</code>. Server users now need to explicitly add this JAR to their project (and non-server users now no longer need to depend on it) </li> <li> As a result of the client and server changes above, we no longer need to produce a special Android JAR which contains the client, server (which added space but was not used) and structures. There is now a normal module called <code>hapi-fhir-android</code> which is added to your Android Gradle file along with whatever structures JARs you wish to add. See the <a href=\"https://github.com/hapifhir/hapi-fhir-android-integration-test\">Android Integration Test</a> to see a sample project using HAPI FHIR 3.0.0. <b>Note that this has been reported to work by some people but others are having issues with it!</b> In order to avoid delaying this release any further we are releasing now despite these issues. If you are an Android guru and want to help iron things out please get in touch. If not, it might be a good idea to stay on HAPI FHIR 2.5 until the next point release of the 3.x series. </li> <li> A new JAR containing FHIR utilities called <code>hapi-fhir-utilities</code> has been added. This JAR reflects the ongoing harmonization between HAPI FHIR and the FHIR RI codebases and is generally required in order to use HAPI at this point (if you are using a dependency manager such as Maven or Gradle it will be brought in to your project automatically as a dependency) </li> </ul>"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "In order to allow the reoganizations and decoupling above to happen, a number of important classes and interfaces have been moved to new packages. A sample list of these changes is listed below. When upgrading to 3.0.0 your project may well show a number of compile errors related to missing classes. In most cases this can be resolved by simply removing the HAPI imports from your classes and asking your IDE to \"Organize Imports\" once again. This is an annoying change we do realize, but it is neccesary in order to allow the project to continue to grow. <ul> <li>IGenericClient moved from package ca.uhn.fhir.rest.client to package ca.uhn.fhir.rest.client.api</li> <li>IRestfulClient moved from package ca.uhn.fhir.rest.client to package ca.uhn.fhir.rest.client.api</li> <li>AddProfileTagEnum moved from package ca.uhn.fhir.rest.server to package ca.uhn.fhir.context.api</li> <li>IVersionSpecificBundleFactory moved from package ca.uhn.fhir.rest.server to package ca.uhn.fhir.context.api</li> <li>BundleInclusionRule moved from package ca.uhn.fhir.rest.server to package ca.uhn.fhir.context.api</li> <li>RestSearchParameterTypeEnum moved from package ca.uhn.fhir.rest.server to package ca.uhn.fhir.rest.api</li> <li>EncodingEnum moved from package ca.uhn.fhir.rest.server to package ca.uhn.fhir.rest.api</li> <li>Constants moved from package ca.uhn.fhir.rest.server to package ca.uhn.fhir.rest.api</li> <li>IClientInterceptor moved from package ca.uhn.fhir.rest.client to package ca.uhn.fhir.rest.client.api</li> <li>ITestingUiClientFactory moved from package ca.uhn.fhir.util to package ca.uhn.fhir.rest.server.util</li> </ul>"
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
title: "The version of a few dependencies have been bumped to the latest versions (dependent HAPI modules listed in brackets): <ul> <li>Spring (JPA): 4.3.10 -> 5.0.0</li> <li>Jackson (JPA): 2.8.1 -> 2.9.2</li> </ul>"
|
||||
- item:
|
||||
type: "fix"
|
||||
title: "The Android client module has been restored to working order, and no longer requires a special classifier or an XML parser to be present in order to work. This means that the hapi-fhir-android library is much less likely to cause conflicts with other libraries imported into an Android application via Gradle. <br/><br/> See the <a href=\"http://hapifhir.io/doc_android.html\">HAPI FHIR Android Documentation</a> for more information. As a part of this fix, all dependencies on the StAX API have been removed in environments where StAX is not present (such as Android). The client will now detect this case, and explicitly request JSON payloads from servers, meaning that Android clients no longer need to include two parser stacks"
|
||||
title: "The Android client module has been restored to working order, and no longer requires a special classifier or an XML parser to be present in order to work. This means that the hapi-fhir-android library is much less likely to cause conflicts with other libraries imported into an Android application via Gradle. <br/><br/> See the HAPI FHIR Android Documentation for more information. As a part of this fix, all dependencies on the StAX API have been removed in environments where StAX is not present (such as Android). The client will now detect this case, and explicitly request JSON payloads from servers, meaning that Android clients no longer need to include two parser stacks"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "A performance to the JPA server has been made which reduces the number of writes to index tables when updating a resource with contents that only make minor changes to the resource content. In many cases this can noticeably improve update performance."
|
||||
|
|
@ -17,7 +17,7 @@
|
|||
title: "Fix an error in JPA server when using Derby Database, where search queries with a search URL longer than 255 characters caused a mysterious failure. Thanks to Chris Schuler and Bryn Rhodes for all of their help in reproducing this issue."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "JPA server now supports the use of the <code>Cache-Control</code> header in order to allow the client to selectively disable the search result cache. This directive can also be used to disable result paging and return results faster when only a small number of results is needed. See the <a href=\"http://hapifhir.io/doc_jpa.html\">JPA Page</a> for more information."
|
||||
title: "JPA server now supports the use of the <code>Cache-Control</code> header in order to allow the client to selectively disable the search result cache. This directive can also be used to disable result paging and return results faster when only a small number of results is needed. See the JPA Page for more information."
|
||||
- item:
|
||||
type: "fix"
|
||||
title: "In certain cases in the JPA server, if multiple threads all attempted to update the same resource simultaneously, the optimistic lock failure caused a \"gap\" in the history numbers to occur. This would then cause a mysterious failure when trying to update this resource further. This has been resolved."
|
||||
|
|
|
|||
|
|
@ -43,4 +43,4 @@
|
|||
title: "A bug was fixed in the JPA server when performing a validate operation with a mode of DELETE on a server with referential integrity disabled, the validate operation would delete resource reference indexes as though the delete was actually happening, which negatively affected searching for the resource being validated."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "The HAPI FHIR Server framework now has initial support for multitenancy. At this time the support is limited to the server framework (not the client, JPA, or JAX-RS frameworks). See <a href=\"http://hapifhir.io/doc_rest_server.html\">Server Documentation</a> for more information."
|
||||
title: "The HAPI FHIR Server framework now has initial support for multitenancy. At this time the support is limited to the server framework (not the client, JPA, or JAX-RS frameworks). See Server Documentation for more information."
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
title: "HAPI FHIR now supports JDK 9 and JDK 10, both for building HAPI FHIR as well as for use. JDK 8 remains supported and is the minimum requirement in order to build or use HAPI FHIR."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "A new command has been added to the HAPI FHIR CLI tool: \"migrate-database\". This command performs the schema modifications required when upgrading HAPI FHIR JPA to a new version (previously this was a manual process involving running scripts and reindexing everything). <br/><br/> See the <a href=\"http://hapifhir.io/doc_cli.html#migrate-database\">command documentation</a> for more information on how to use this tool. Please post in the HAPI FHIR Google Group if you run into issues, as this is a brand new framework and we still need lots of help with testing."
|
||||
title: "A new command has been added to the HAPI FHIR CLI tool: \"migrate-database\". This command performs the schema modifications required when upgrading HAPI FHIR JPA to a new version (previously this was a manual process involving running scripts and reindexing everything). <br/><br/> See the command documentation for more information on how to use this tool. Please post in the HAPI FHIR Google Group if you run into issues, as this is a brand new framework and we still need lots of help with testing."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "The version of a few dependencies have been bumped to the latest versions (dependent HAPI modules listed in brackets): <ul> <li>Gson (JSON Parser): 2.8.1 -> 2.8.5</li> <li>Spring Framework (JPA): 5.0.3.RELEASE -> 5.0.8.RELEASE</li> <li>Hibernate ORM (JPA): 5.2.16.Final -> 5.3.6.Final</li> <li>Hibernate Search (JPA): 5.7.1.Final -> 5.10.3.Final</li> <li>Jetty (CLI): 9.4.8.v20171121 -> 9.4.12.v20180830</li> <li>Commons-Codec (All): 1.10 -> 1.11</li> <li>Commons-Lang (All): 3.7 -> 3.8</li> <li>Commons-IO (All): 2.5 -> 2.6</li> <li>Spring-Data (JPA): 1.11.6.RELEASE -> 2.0.7.RELEASE</li> </ul>"
|
||||
|
|
@ -60,7 +60,7 @@
|
|||
title: "A bug in the HAPI FHIR CLI was fixed, where uploading terminology for R4 could cause an error about the incorrect FHIR version. Thanks to Rob Hausam for the pull request!"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "A new method has been added to AuthorizationInterceptor that can be used to create rules allowing FHIR patch operations. See <a href=\"http://hapifhir.io/doc_rest_server_security.html#Authorizing_Patch_Operations\">Authorizing Patch Operations</a> for more information."
|
||||
title: "A new method has been added to AuthorizationInterceptor that can be used to create rules allowing FHIR patch operations. See Authorizing Patch Operations for more information."
|
||||
- item:
|
||||
issue: "1018"
|
||||
type: "add"
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@
|
|||
title: "When invoking an operation using the fluent client on an instance, the operation would accidentally invoke against the server if the provided ID did not include a type. This has been corrected so that an IllegalArgumentException is now thrown."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "A new operation has been added to the JPA server called <code>$trigger-subscription</code> . This can be used to cause a transaction to redeliver a resource that previously triggered. See <a href=\"https://smilecdr.com/docs/current/fhir_repository/subscription.html#manually-triggering-subscriptions\">this link</a> for a description of how this feature works. Note that you must add the SubscriptionRetriggeringProvider as shown in the sample project <a href=\"https://github.com/hapifhir/hapi-fhir-jpaserver-starter/blob/master/src/main/java/ca/uhn/fhir/jpa/demo/JpaServerDemo.java\">here</a>."
|
||||
title: "A new operation has been added to the JPA server called <code>$trigger-subscription</code> . This can be used to cause a transaction to redeliver a resource that previously triggered. See <a href=\"https://smilecdr.com/docs/current/fhir_repository/subscription.html#manually-triggering-subscriptions\">this link</a> for a description of how this feature works. Note that you must add the SubscriptionRetriggeringProvider as shown in the sample project."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "When operating in R4 mode, the HAPI FHIR server will now populate Bundle.entry.response for history and search results, which is did not previously do."
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@
|
|||
title: "<b>New Feature</b>: Support for the new R5 draft resources has been added. This support includes the client, server, and JPA server. Note that these definitions will change as the R5 standard is modified until it is released, so use with caution!"
|
||||
- item:
|
||||
type: "add"
|
||||
title: "<b>New Feature</b>: A new interceptor called <code>ConsentInterceptor</code> has been added. This interceptor allows JPA based servers to make appropriate consent decisions related to resources that and operations that are being returned. See <a href=\"http://hapifhir.io/doc_rest_server_security.html\">Server Security</a> for more information."
|
||||
title: "<b>New Feature</b>: A new interceptor called <code>ConsentInterceptor</code> has been added. This interceptor allows JPA based servers to make appropriate consent decisions related to resources that and operations that are being returned. See Server Security for more information."
|
||||
- item:
|
||||
type: "add"
|
||||
title: "<b>New Feature</b>: The JPA server now supports GraphQL for DSTU3 / R4 / R5 servers."
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
<th:block th:if="${changelog.changes.get(version).releaseDate} == null">
|
||||
Note: This version of HAPI FHIR is a SNAPSHOT (prerelease), meaning that it has
|
||||
not yet been released, but all changes and fixes listed here are available to try
|
||||
out as <a href="/docs/introduction/downloading_and_importing.html#snapshot">Snapshot Builds</a>.
|
||||
out as <a href="/hapi-fhir/docs/introduction/downloading_and_importing.html#snapshot">Snapshot Builds</a>.
|
||||
</th:block>
|
||||
<th:block th:if="${changelog.changes.get(version).releaseDate} != null">
|
||||
**Released:** <th:block th:text="${changelog.changes.get(version).releaseDate.getValueAsString()}"/>
|
||||
|
|
|
|||
|
|
@ -6051,7 +6051,7 @@ Bundle bundle = client.search().forResource(Patient.class)<br/>
|
|||
</action>
|
||||
<action type="add">
|
||||
Introduce
|
||||
<![CDATA[<a href="./apidocs-jpaserver/ca/uhn/fhir/jpa/dao/IJpaServerInterceptor.html">IJpaServerInterceptor</a>]]>
|
||||
IJpaServerInterceptor
|
||||
interceptors for JPA server which can be used for more fine grained operations.
|
||||
</action>
|
||||
<action type="fix" issue="241">
|
||||
|
|
|
|||
Loading…
Reference in New Issue