Hi,
I came across the situation that many of our bean classes throw an exception when loading. Storing works fine.
This happens because of final fields inside the bean class and no fitting constructor. This behavior would mean, that I have to create a lot of boilerplate code for de-/serializing these objects when using deepsampler.
This brought to my mind, that maybe getAllFields should be extensible. With that I could e.g. write my own logic on which fields should be serialized in a more generic way, without having to declare BeanFactoryExtensions for all cases.
If this is not the way deepsampler should work -> Alternative:
- Available constructors should get analyzed to identify which fields are needed and which can be omitted. Maybe this behavior could be summarized in a configuration of deepsampler. Something like "strict, lenient".
Please let me know if this makes sense for you or if I'm missing something here.
Best regards,
Michel Pittelkow
Hi,
I came across the situation that many of our bean classes throw an exception when loading. Storing works fine.
This happens because of final fields inside the bean class and no fitting constructor. This behavior would mean, that I have to create a lot of boilerplate code for de-/serializing these objects when using deepsampler.
This brought to my mind, that maybe getAllFields should be extensible. With that I could e.g. write my own logic on which fields should be serialized in a more generic way, without having to declare BeanFactoryExtensions for all cases.
If this is not the way deepsampler should work -> Alternative:
Please let me know if this makes sense for you or if I'm missing something here.
Best regards,
Michel Pittelkow