| 
Hello Lars, 
 
thanks for your answer and let me summarize and finalize the lessons learned from our email conversation about Tractus-X version 24.0.3 and if you have time please review it. 
 
- No proper support 
- No proper documentation 
- It is not recommended to start a greenfield project with this 
- It is very difficult get to run 
 
What can we expect about the acceptance/compatibility point of view of this version from those who would use the Eclipse Dataspace ?
 Best regards,
 
 
Csaba Csikós
 
 
 
 From: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> on behalf of Lars Geyer-Blaumeiser via tractusx-dev
 <tractusx-dev@xxxxxxxxxxx>Sent: Monday, May 26, 2025 1:33 PM
 To: tractusx developer discussions <tractusx-dev@xxxxxxxxxxx>
 Cc: Lars Geyer-Blaumeiser <lars.blaumeiser@xxxxxxxxxxxxxx>
 Subject: Re: [tractusx-dev] Fw: Errors beause of EDC downgrade from 0.9.0 to 0.5.4
   
Hi Csaba, 
 
you should be aware that the version 24/08 you are referring to is pretty old. Although the 0.7.3 from there technically still works in the current dataspace, you have to spend a lot of investment to reengineer the information from that time. We are currently
 preparing version 25/06 which will bring connector version 0.10.0. 
 
The MXD as such does not provide a tag concept, that is planned as we see the issues with an always updated reference which might fail any day but for historical reasons MXD does not have a tag concept. As the MXD is quite high end in the sense, that it makes
 use of latest concepts of the connector like management domains, it is not my favorite approach to get started for a greenfield project. You can have a look at the umbrella helm charts in the repository
https://github.com/eclipse-tractusx/tractus-x-umbrella , as this provides a simpler approach which also stubs the wallet implementation. But again, you should strive for the latest version to also get support from the community.
 
You should be aware, that setups pre-24/05 are very difficult to get running, as some of the relevant components are even archived. And a lot of people who were responsible for that versions already left the project. You will be alone setting that up. 
 
| Mit freundlichen Grüßen / Best Regards Dr. Lars Geyer-Blaumeiser   Application Architect Open-Source Advisor |  
  
 +49 176 13200141 
lars.blaumeiser@xxxxxxxxxxxxxx 
   Cofinity-X GmbH
 Breslauer
 Platz 4, 50668 Köln
 www.cofinity-x.com
 
 Amtsgericht Köln, HRB 112676
 Geschäftsführung: Hr. Thomas Rösch, Hr. Martin Galas
 
Mandatory Disclosure Statement:
www.cofinity-x.com/impressumThis e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information.
 
If you have received this e-mail in error, you are hereby notified, that any review, copying, or distribution of it is strictly prohibited. 
Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.  
  
 
 
 Von: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> im Auftrag von csaba cs via tractusx-dev <tractusx-dev@xxxxxxxxxxx>Gesendet: Montag, 26. Mai 2025 11:21
 An: tractusx developer discussions <tractusx-dev@xxxxxxxxxxx>
 Cc: csaba cs <cscsaba242@xxxxxxxx>
 Betreff: [tractusx-dev] Fw: Errors beause of EDC downgrade from 0.9.0 to 0.5.4
   
Hello Lars, 
 
thanks for your quick answer,  the project is greenfield and our devops decided to change from the 'planned' Tractus-X 24.08 (connector is 0.7.3) to 24.03 (connector is 0.5.4) 
 
I mentioned 0.9.0 because I have only a simplified demo app with EDC Connector 0.9.0 as good starting point to understand whole process and adding custom code as well 
 
Unfortunately the MXD is very huge with 30 containers  and I had many company network policy problems to build up this project.  
Plus no labels tags per versions as well in the MXD per edc release, as I see, so how can check how the x version of edc works ?  
I think there should be simpler one, MXD is not designed for beginners, sorry. 
 
 
Nowdays I realized many edc implemetation exist on GitHub but I have no clue how to continue, I have wasted many times  
 
(im not in the position to say, the Tractus-x should be start with the latest version, which i think the biggest problem) 
   
Best regards, 
 
Csaba 
 
 
Classified as Secret 
 From: Lars Geyer-Blaumeiser <lars.blaumeiser@xxxxxxxxxxxxxx>Sent: Monday, May 26, 2025 9:47 AM
 To: tractusx developer discussions <tractusx-dev@xxxxxxxxxxx>
 Cc: csaba cs <cscsaba242@xxxxxxxx>
 Subject: AW: [tractusx-dev] Errors beause of EDC downgrade from 0.9.0 to 0.5.4
   
Hello Csaba, 
 
it is not possible to downgrade from 0.9.0 to 0.5.4. 
 
Catena-X did a major breaking update with its 24/05 release which reflects in dataspace in the Jupiter release that became operational in Oct. 2024. The final connector version that was provided for the Jupiter release was 0.7.6. All versions prior to 0.7.0
 are not compatible with the current dataspace and all versions prior to 0.7.6 are not recommended to be used in the dataspace. 
 
Concerning documentation, there is general documentation in the upstream Eclipse Dataspace Components repository. This documentation is not version specific. Each version has release notes in the Github Release item. There are migrations guides in the docs
 folder of the tractusx-edc repository and alongside a management-api walkthrough which you find in a matching fashion in the tags of the corresponding version. 
 
| Mit freundlichen Grüßen / Best Regards Dr. Lars Geyer-Blaumeiser   Application Architect  |  
Open-Source Advisor 
Co-Lead Catena-X e.V. Architecture Committee 
Committer for Eclipse Tractus-X 
Member Catena-X e.V. Network Service Committee 
Lead Catena-X e.V. Dataspace Connectivity Expert Group 
Co-Lead Catena-X Next – Work Package 7: House Connection 
Contact for Tractus-X EDC planning and management 
Member Catena-X e.V. Data Sovereignty Expert Group 
Member Catena-X e.V. Digital Twin Expert Group 
  
+49 176 13200141 
lars.blaumeiser@xxxxxxxxxxxxxx 
 Cofinity-X GmbHBreslauer
 Platz 4, 50668 Köln
 www.cofinity-x.com
 
 Amtsgericht Köln, HRB 112676
 Geschäftsführung: Hr. Thomas Rösch, Hr. Martin Galas
 Mandatory Disclosure Statement:
www.cofinity-x.com/impressumThis e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information.
 If you have received this e-mail in error, you are hereby notified, that any review, copying, or distribution of it is strictly
 prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.    
 
 Von: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> im Auftrag von csaba cs via tractusx-dev <tractusx-dev@xxxxxxxxxxx>Gesendet: Donnerstag, 22. Mai 2025 11:40
 An: tractusx developer discussions <tractusx-dev@xxxxxxxxxxx>
 Cc: csaba cs <cscsaba242@xxxxxxxx>
 Betreff: [tractusx-dev] Errors beause of EDC downgrade from 0.9.0 to 0.5.4
   
Hello Guys, 
 
At our company we had to downgrade the EDC from 0.9.0 to 0.5.4 our apps throws this exception below 
(where mainly caused by empty config properties) 
 
Caused by: java.lang.reflect.InvocationTargetExceptionat java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.base/java.lang.reflect.Method.invoke(Unknown Source)
 at org.eclipse.edc.spi.system.injection.ProviderMethod.invoke(ProviderMethod.java:61)
 ... 20 more
 Caused by: java.lang.NullPointerException: edc.data.encryption.keys.alias
property not found
 at java.base/java.util.Objects.requireNonNull(Unknown Source)
 at org.eclipse.tractusx.edc.data.encryption.TxEncryptorExtension.createEncryptor(TxEncryptorExtension.java:59)
 ... 25 more
 
 
 
 
So, my question is : 
Is there any source where I can check what properties needed to 0.5.4 ?  
Is there any documentation for specific releases or we only have changelog ?  
What is the best way to putting together a small dataexchange with version 0.5.4 ? 
 
Thanks in advance, 
 
Csaba 
 
Classified as Secret |