https://devel.data-in-motion.biz/jenkins/job/Eclipse%20Sensinact/org.eclipse.sensinact.gateway.core$impl/31/mavenArtifacts/impl-0.0.2-SNAPSHOT-tests.jarimpl-0.0.2-SNAPSHOT-tests.jarorg.eclipse.sensinact.gateway.core/impl/0.0.2-SNAPSHOT/impl-0.0.2-SNAPSHOT-tests.jarimpl-0.0.2-SNAPSHOT.jarimpl-0.0.2-SNAPSHOT.jarorg.eclipse.sensinact.gateway.core/impl/0.0.2-SNAPSHOT/impl-0.0.2-SNAPSHOT.jarimpl-0.0.2-SNAPSHOT.pomimpl-0.0.2-SNAPSHOT.pomorg.eclipse.sensinact.gateway.core/impl/0.0.2-SNAPSHOT/impl-0.0.2-SNAPSHOT.pomfalse#3142074571Eclipse Sensinact » SensiNact core implementation #3131falsefalse31-1SUCCESS1723107714776https://devel.data-in-motion.biz/jenkins/job/Eclipse%20Sensinact/org.eclipse.sensinact.gateway.core$impl/31/core/api/src/main/java/org/eclipse/sensinact/core/notification/LifecycleNotification.javasouthbound/virtual/virtual-temperature-sensor/src/main/java/org/eclipse/sensinact/gateway/southbound/virtual/temperature/VirtualTemperatureDto.javacore/api/src/main/java/org/eclipse/sensinact/core/notification/ResourceMetaDataNotification.javanorthbound/rest/src/main/java/org/eclipse/sensinact/northbound/rest/impl/RestNorthbound.javacore/api/src/main/java/org/eclipse/sensinact/core/notification/ResourceActionNotification.javacore/api/src/main/java/org/eclipse/sensinact/core/notification/ResourceDataNotification.javanorthbound/rest/src/test/java/org/eclipse/sensinact/northbound/rest/integration/notification/ResourceNotificationsTest.javanorthbound/session/session-impl/src/test/java/org/eclipse/sensinact/nortbound/session/integration/SessionSubscribeTest.javacore/impl/src/test/java/org/eclipse/sensinact/core/notification/impl/NotificationSenderTest.javanorthbound/websocket/src/main/java/org/eclipse/sensinact/northbound/ws/impl/WebSocketEndpoint.java9d68852a61656138c22694f9e0988f6b0a9a1e951716221106000https://devel.data-in-motion.biz/jenkins/user/timothyjwardtimothyjwardtimothyjward@apache.orgInclude the model name in topic notifications Filtering at the model level is extremely useful as it permits efficient tracking of multiple providers using the same model. The model URI is required to ensure strict uniqueness, however the model uri is difficult to represent in topic syntax, and would need large amounts of escaping. The trade off is therefore to allow the model name to be used in the topic for rapid checking, with the filter being available for more precise matching if needed. Signed-off-by: Tim Ward <timothyjward@apache.org> 2024-05-20 17:05:06 +01009d68852a61656138c22694f9e0988f6b0a9a1e95Include the model name in topic notificationseditcore/impl/src/test/java/org/eclipse/sensinact/core/notification/impl/NotificationSenderTest.javaeditnorthbound/websocket/src/main/java/org/eclipse/sensinact/northbound/ws/impl/WebSocketEndpoint.javaeditnorthbound/rest/src/test/java/org/eclipse/sensinact/northbound/rest/integration/notification/ResourceNotificationsTest.javaeditcore/api/src/main/java/org/eclipse/sensinact/core/notification/ResourceActionNotification.javaeditcore/api/src/main/java/org/eclipse/sensinact/core/notification/ResourceDataNotification.javaeditnorthbound/session/session-impl/src/test/java/org/eclipse/sensinact/nortbound/session/integration/SessionSubscribeTest.javaeditsouthbound/virtual/virtual-temperature-sensor/src/main/java/org/eclipse/sensinact/gateway/southbound/virtual/temperature/VirtualTemperatureDto.javaeditcore/api/src/main/java/org/eclipse/sensinact/core/notification/ResourceMetaDataNotification.javaeditnorthbound/rest/src/main/java/org/eclipse/sensinact/northbound/rest/impl/RestNorthbound.javaeditcore/api/src/main/java/org/eclipse/sensinact/core/notification/LifecycleNotification.javacore/models/provider/src/main/resources/model/sensinact.ecorecore/impl/src/test/java/org/eclipse/sensinact/core/integration/EMFUpdateServiceTest.javacore/models/provider/src/main/resources/model/sensinact.genmodel4410aac42c5a5724db1a96b563512940ce02aeb61716543632000https://devel.data-in-motion.biz/jenkins/user/ggruneGuido Gruneg.grune@datainmotion.comuse real eClass from service not from reference Signed-off-by: Guido Grune <g.grune@datainmotion.com> 2024-05-24 11:40:32 +02004410aac42c5a5724db1a96b563512940ce02aeb6use real eClass from service not from referenceeditcore/models/provider/src/main/resources/model/sensinact.ecoreeditcore/impl/src/test/java/org/eclipse/sensinact/core/integration/EMFUpdateServiceTest.javaeditcore/models/provider/src/main/resources/model/sensinact.genmodelcore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ServiceImpl.javacore/impl/src/main/java/org/eclipse/sensinact/core/model/nexus/ModelNexus.javacore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/EMFModel.javacore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/EMFModelBuilder.javacore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ModelImpl.javacore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/EMFService.javacore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ServiceBuilderImpl.javacore/api/src/main/java/org/eclipse/sensinact/core/model/Model.javacore/impl/src/test/java/org/eclipse/sensinact/core/integration/EMFUpdateServiceTest.javacore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/SensinactEMFModelManager.javacore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/EMFServiceBuilder.javacore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ModelBuilderImpl.javacore/impl/src/main/java/org/eclipse/sensinact/core/impl/SetValueCommand.javacore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/SensinactModelManagerImpl.javaa648fd6334494a065bf1355a64b37a945dcffeed1716916215000https://devel.data-in-motion.biz/jenkins/user/j.albertj.albertj.albert@data-in-motion.bizfixed NPE due to missing service EClass Signed-off-by: Juergen Albert <j.albert@data-in-motion.biz> 2024-05-28 19:10:15 +0200a648fd6334494a065bf1355a64b37a945dcffeedfixed NPE due to missing service EClassaddcore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/EMFServiceBuilder.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ModelImpl.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ServiceImpl.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/impl/SetValueCommand.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ModelBuilderImpl.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/model/nexus/ModelNexus.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/SensinactModelManagerImpl.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ServiceBuilderImpl.javaaddcore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/EMFModel.javaaddcore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/EMFService.javaeditcore/api/src/main/java/org/eclipse/sensinact/core/model/Model.javaeditcore/impl/src/test/java/org/eclipse/sensinact/core/integration/EMFUpdateServiceTest.javaaddcore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/EMFModelBuilder.javaeditcore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/model/SensinactEMFModelManager.javacore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ModelImpl.javacore/impl/src/test/java/org/eclipse/sensinact/core/model/nexus/impl/NexusTest.javacore/impl/src/main/java/org/eclipse/sensinact/core/model/nexus/ModelNexus.javacore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/SensinactModelManagerImpl.javacore/impl/src/test/java/org/eclipse/sensinact/core/model/impl/ModelBuildingTest.javad221b6126804814251557f7d4cda8d11e7c9300d1718189135000https://devel.data-in-motion.biz/jenkins/user/timothyjwardtimothyjwardtimothyjward@apache.orgImplement model deletion in the Model Manager The model manager API provides a deletion method, but this was not implemented. This commit implements deletion logic, which delegates to the Model Nexus. The Model Nexus: 1. Finds the Model 2. If found it deletes any and all providers using the model, then it deletes the model from its owning EPackage 3. If the EPackage is now empty of models then the EPackage is removed from the Model Nexus The ModelImpl has also been updated to check the the model is still registered before allowing any action. This prevents deleted models from being used after they are deleted. Signed-off-by: Tim Ward <timothyjward@apache.org> 2024-06-12 11:45:35 +0100d221b6126804814251557f7d4cda8d11e7c9300dImplement model deletion in the Model Managereditcore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/ModelImpl.javaeditcore/impl/src/test/java/org/eclipse/sensinact/core/model/impl/ModelBuildingTest.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/model/nexus/ModelNexus.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/model/impl/SensinactModelManagerImpl.javaeditcore/impl/src/test/java/org/eclipse/sensinact/core/model/nexus/impl/NexusTest.javacore/impl/src/main/java/org/eclipse/sensinact/core/dto/impl/AbstractUpdateDto.javacore/impl/src/main/java/org/eclipse/sensinact/core/whiteboard/impl/SensinactWhiteboard.javacore/impl/src/test/java/org/eclipse/sensinact/core/command/impl/WhiteboardImplTest.javacore/impl/src/main/java/org/eclipse/sensinact/core/extract/impl/EMFGenericDtoDataExtractor.javacore/impl/src/test/java/org/eclipse/sensinact/core/extract/impl/CustomBaseValueDtoExtractorTest.javacore/impl/src/main/java/org/eclipse/sensinact/core/extract/impl/GenericDtoDataExtractor.javacore/impl/src/main/java/org/eclipse/sensinact/core/extract/impl/AnnotationMapping.javacore/annotation/src/main/java/org/eclipse/sensinact/core/annotation/dto/NullAction.javacore/impl/src/test/java/org/eclipse/sensinact/core/extract/impl/GenericDtoExtractorTest.javacore/impl/src/main/java/org/eclipse/sensinact/core/impl/SetValueCommand.java068be1017ad07f297a0316652e66e9dec24123041718714782000https://devel.data-in-motion.biz/jenkins/user/timothyjwardtimothyjwardtimothyjward@apache.orgAdd support for nullable data which should not create a resource In some cases null is a valid value to return, but should not be used to initialize a resource. For example if a DTO contains some optional resources which may never be set for some providers, but will be set for others, and those resources may be null, then this was not previously possible Signed-off-by: Tim Ward <timothyjward@apache.org> 2024-06-18 13:46:22 +0100068be1017ad07f297a0316652e66e9dec2412304Add support for nullable data which should not create a resourceeditcore/impl/src/test/java/org/eclipse/sensinact/core/extract/impl/CustomBaseValueDtoExtractorTest.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/extract/impl/AnnotationMapping.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/extract/impl/GenericDtoDataExtractor.javaeditcore/impl/src/test/java/org/eclipse/sensinact/core/extract/impl/GenericDtoExtractorTest.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/dto/impl/AbstractUpdateDto.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/whiteboard/impl/SensinactWhiteboard.javaeditcore/annotation/src/main/java/org/eclipse/sensinact/core/annotation/dto/NullAction.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/extract/impl/EMFGenericDtoDataExtractor.javaeditcore/impl/src/test/java/org/eclipse/sensinact/core/command/impl/WhiteboardImplTest.javaeditcore/impl/src/main/java/org/eclipse/sensinact/core/impl/SetValueCommand.javacore/impl/src/main/java/org/eclipse/sensinact/core/extract/impl/EMFGenericDtoDataExtractor.javacore/api/src/main/java/org/eclipse/sensinact/core/push/dto/GenericDto.javacore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/dto/EMFGenericDto.java61101a6c9a361235909f11624cf1e8ea199fb1261718721481000https://devel.data-in-motion.biz/jenkins/user/timothyjwardtimothyjwardtimothyjward@apache.orgReinstate final modifier for GenericDto The EMF dto altered the GenericDto so that it could extend it. The GenericDto was intentionally final to prevent usage mistakes in the API. There are few fields and we should copy them. Signed-off-by: Tim Ward <timothyjward@apache.org> 2024-06-18 15:38:01 +010061101a6c9a361235909f11624cf1e8ea199fb126Reinstate final modifier for GenericDtoeditcore/impl/src/main/java/org/eclipse/sensinact/core/extract/impl/EMFGenericDtoDataExtractor.javaeditcore/api/src/main/java/org/eclipse/sensinact/core/push/dto/GenericDto.javaeditcore/emf-api/src/main/java/org/eclipse/sensinact/core/emf/dto/EMFGenericDto.javacore/impl/src/main/java/org/eclipse/sensinact/core/impl/SetValueCommand.javacore/impl/src/test/java/org/eclipse/sensinact/core/integration/DataUpdateServiceTest.javac9be1b379b44dcb0c5400ff44d4664ab3202c7641718728864000https://devel.data-in-motion.biz/jenkins/user/timothyjwardtimothyjwardtimothyjward@apache.orgFix missing check in SetValueCommand The UPDATE_IF_PRESENT logic would always run even if the data value was not null. This has been fixed and regression tests added for all NullAction behaviours. Signed-off-by: Tim Ward <timothyjward@apache.org> 2024-06-18 17:41:04 +0100c9be1b379b44dcb0c5400ff44d4664ab3202c764Fix missing check in SetValueCommandeditcore/impl/src/main/java/org/eclipse/sensinact/core/impl/SetValueCommand.javaeditcore/impl/src/test/java/org/eclipse/sensinact/core/integration/DataUpdateServiceTest.javahttps://devel.data-in-motion.biz/jenkins/user/ggruneGuido Grunehttps://devel.data-in-motion.biz/jenkins/user/timothyjwardtimothyjwardhttps://devel.data-in-motion.biz/jenkins/user/j.albertj.alberthttps://devel.data-in-motion.biz/jenkins/job/Eclipse%20Sensinact/org.eclipse.sensinact.gateway.core$impl/31/mavenArtifacts/