| Re: [basyx-dev] Release of 1.0.1 (JAVA) |
|
Dear BaSyx Community, additionally to the already existing images of the Off-the-Shelf-Components, there are now also images for ARM architecture available.
You can identify them by the arm32v7 suffix in the tag name. Best regards, Frank -- Frank Schnicke Expert »Industrie 4.0 System Architectures« Dept. Virtual Engineering Fraunhofer IESE
Fraunhofer-Platz 1 | 67663 Kaiserslautern
+49 631 6800-2259
frank.schnicke@xxxxxxxxxxxxxxxxxx www.iese.fraunhofer.de - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25 Jahre Fraunhofer IESE – Engineering the Digital Future Reisen Sie mit uns in die Vergangenheit, aber vor allem in die digitale Zukunft! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Von: basyx-dev <basyx-dev-bounces@xxxxxxxxxxx>
Im Auftrag von Schnicke, Frank Dear BaSyx Community, as previously indicated, the release of BaSyx Java 1.0.1 has happened today. You can find the release in the master-branch. Additionally, the off-the-shelf components have been updated. This release will include the following updates as also described in the release plan [1]:
·
Fixes crash when invoking an Operation with zero OutputVariables
·
Fixes ProviderException only accepting Exceptions instead of Throwables during construction
·
Fixes inconsistent handling of HTTP/REST endpoints
·
Fixes ProviderException incorrectly handling the message of the passed Throwable (Bug 573180)
·
Fixes BaSyxHttpServer failing silently
·
Fixes Camunda having a dependency conflict
·
Fixes inconsistency in handling AASX files in contrast to AASX Package Explorer and increased compatibility (e.g.
Bug 571725,
Bug 571725)
·
Fixes issues in XML (De-)serialization in regard to OperationVariables used in Operations
·
Fixes issue with SubmodelElements that have an idShort starting with "value"
·
Fixes missing modelType of Qualifier
·
Fixes issue with deserializing an AAS Environment in JSON when only a reference to an Asset was included
·
Fixes wrong exception handling when a nonexisting HTTP path was accessed
·
Adds missing Capability SubmodelElement
·
Fixes HTTPS issue with OpenJDK
·
Fixes wrong ID creation during AASX serialization
·
Enforces created AASX files only including absolute paths for increased AASX Package Explorer compatibility (Bug 571592)
·
Fixes wrong initialization for Submodels stored in MongoDB
·
Fixes HTTPSConnector being in the wrong folder
·
Fixes MongoDB backend not correctly deleting Submodels
·
Fixes handling of XMLGregorianCalendar as Property value
·
Fixes wrong serialization of billOfMaterial entry in Asset Additionally, the new class AASXPackageExplorerConformantHelper
is introduced that will address different interpretations of the spec in regard to the AASX Package Explorer. Changing the standard behavior of BaSyx to align the differences was not possible this time due to possibly breaking third party applications depending
on BaSyx as result. Best regards, Frank [1]
https://projects.eclipse.org/projects/technology.basyx/releases/1.0.1-java -- Frank Schnicke Expert »Industrie 4.0 System Architectures« Dept. Virtual Engineering Fraunhofer IESE
Fraunhofer-Platz 1 | 67663 Kaiserslautern
+49 631 6800-2259 frank.schnicke@xxxxxxxxxxxxxxxxxx - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25 Jahre Fraunhofer IESE – Engineering the Digital Future Reisen Sie mit uns in die Vergangenheit, aber vor allem in die digitale Zukunft! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |