Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
One thing that prevents from using a binding technology like JAXB, instead of a classic dom/sax-based xml technology is the fact that, when reading xml, it seems to be strongly oriented to instantiate the classes that it manages.
Many times, i want to read values from xml and set them to properties of already created instances.
Is there a simple way to tell JAXB that it has to apply values to the class that i have instead of create a new one?
Use the JAXB objects as DTOs. Then you can use
PropertyUtils.copyProperties(..)/BeanUtils.copyProperties(..)(from commons-beanutils) to transfer the properties to your already-partially-populated objects.