Nikhil-n17 commented on issue #1980:
URL: https://github.com/apache/fury/issues/1980#issuecomment-2547772360
Previously in the legacy app, we had single fury instance to serialise and
deserialis. Database only contains the serialised by this instance. With the
existing app being migrated to new system ( System B ) in which we have DTO
refactoring, we have done some refactorings to DTO ( renaming and reusing the
possible DTOs).
Example
System A - Legacy app - Database already contains data written by this app.
```
public class DTOStructSystemB {
String stringField;
int intField;
CustomDTOR1 customDTOR1;
CustomDTOR2 customDTOR2;
}
public class CustomDTOR1 {
String name;
String age;
}
public class CustomDTOR2 {
String name;
String age;
}
/* Both CustomDTOR2 and CustomDTOR1 were registered in fury instance */
```
System B - Migrating to this new System B - won't be using the DTOs or fury
instance old app used.
```
public class DTOStructSystemB {
String stringField;
int intField;
CustomDTOinNewSystem customDTOinNewSystem;
CustomDTOinNewSystem customDTOinNewSystem;
}
public class CustomDTOinNewSystem {
String name;
String age;
}
```
We are looking for a way to create fury instance in System B in such that,
both class are correctly deserialised to `CustomDTOinNewSystem`, we are forced
to have another DTO of same structure just to be able to deserialise the data
written from legacy app.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
