| Re: [tractusx-dev] Fw: Errors beause of EDC downgrade from 0.9.0 to 0.5.4 |
|
Hello Csaba, I have to admit, I do not get your point. We are a developing community not a support company and you want to use a version that is pretty much outdated. The reason,
why 24/05 was such a big change, is that the community decided that the concepts in 24/03 and earlier simply were not fit for the purpose, so they introduced a complete new setup using self sovereign identities and the decentralized claims protocol for credential
exchange. They deliberately decided to not stay compatible due to limitations of that old technology. Of course, nobody cares for the old stuff anymore, we had 4 releases since that release and a fifth upcoming. That is the technology that is supported and operational.
So, writing that there is no “proper” support and no “proper” documentation is not appropriate. There is no support for the old stuff and there are reasons that there cannot be expected any. The documentation is as it was at release time because efforts went
into the technologies introduced afterwards. It is difficult to get to run because some of the components like the MIW are abandoned and archived and the knowledge of what is needed to operate that old stack to a large degree left the community I do not like the way you summarize, because it sounds like an accuse to not provide something expectable. In this case, this is simply inappropriate. Concerning your question about acceptance, again what is your point? The stuff is open source, so use 24/03 for your project, but accept that others move on and use
current technology. Compatibility is a major target for version 24/05 and later but not for earlier versions and we try to gain acceptance for the current technology.
lars.blaumeiser@xxxxxxxxxxxxxx
Mandatory Disclosure Statement: www.cofinity-x.com/impressum 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> 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 ? Csaba Csikós Classified as Secret From: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> on behalf of Lars
Geyer-Blaumeiser via tractusx-dev <tractusx-dev@xxxxxxxxxxx> 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.
+49 176 13200141 lars.blaumeiser@xxxxxxxxxxxxxx
Mandatory Disclosure Statement:
www.cofinity-x.com/impressum 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> 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. This demo app uncomparable simpler, you can find it
https://github.com/smartSenseSolutions/edc-chat-application but the edc version is 0.9.0 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> 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.
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 GmbH Mandatory Disclosure Statement:
www.cofinity-x.com/impressum 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> 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.InvocationTargetException 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 |
