I'd like to use dozer as a tool for generating Java converters at build time. These converters would then do conversions at run time and avoid the overhead of reflection. My use case is to speed up the development process so my need is not for flexibility once the project have been built and deployed.
Is this something that's supported today or will be supported in the near future by Dozer? Would you consider it a big task (effort wise) to create this feature? I might give it a try myself
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the same question. I was promted to take a look at dozer, when I was looking for a tool for convertion database entities into dto structures (My question that leads my to Dozer http://stackoverflow.com/questions/4113823/framework-for-converting-java-objects). Dozer seems to be the thing I need, but I don't want to mess with reflection. Its better to be comile stage process of converters generation with a special maven plugin for that purpose. It is even better to be a source code generation instead of bytecode. Are you working on that feature now? Do you need volunteers for that work?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First of all volunteers are always welcome! Simlpy drop me a mail (buzdin at gmail dot com) and we can discuss where to start.
Secondly, in my opinion replicating Dozer functionality in bytecode only is impossible.
Dozer maps using both runtime and static information.
Nobody is working on that feature now. The first step is simply creating a Factory/Builder layer, which is independent of Dozer features, but provides a generic mapper constructor. This part can be contributed without deep understanding of framework code. I could provide a list of atomic operations needed for Dozer usage. The hard part is to integrate this to Dozer, but I think it is possible.
Dmitry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I'm going to reraise a question that I found have been asked earlier in the forum about two years ago: https://sourceforge.net/projects/dozer/forums/forum/452529/topic/1965618
I'd like to use dozer as a tool for generating Java converters at build time. These converters would then do conversions at run time and avoid the overhead of reflection. My use case is to speed up the development process so my need is not for flexibility once the project have been built and deployed.
Is this something that's supported today or will be supported in the near future by Dozer? Would you consider it a big task (effort wise) to create this feature? I might give it a try myself
I have the same question. I was promted to take a look at dozer, when I was looking for a tool for convertion database entities into dto structures (My question that leads my to Dozer http://stackoverflow.com/questions/4113823/framework-for-converting-java-objects). Dozer seems to be the thing I need, but I don't want to mess with reflection. Its better to be comile stage process of converters generation with a special maven plugin for that purpose. It is even better to be a source code generation instead of bytecode. Are you working on that feature now? Do you need volunteers for that work?
Hi,
First of all volunteers are always welcome! Simlpy drop me a mail (buzdin at gmail dot com) and we can discuss where to start.
Secondly, in my opinion replicating Dozer functionality in bytecode only is impossible.
Dozer maps using both runtime and static information.
Nobody is working on that feature now. The first step is simply creating a Factory/Builder layer, which is independent of Dozer features, but provides a generic mapper constructor. This part can be contributed without deep understanding of framework code. I could provide a list of atomic operations needed for Dozer usage. The hard part is to integrate this to Dozer, but I think it is possible.
Dmitry