Why do we need a bean to bean mapper like dozer in a web application

Question

In simple terms, why do we need 'a bean to bean mapping service' (like Dozer) in a web-application.

Suppose I'm working on a web-service.

1. I'm receiving an XML in request.
2. I fetch the the values from XML elements.
3. Perform the required operation on the fetched values.
4. Prepare the response XML.
5. Send the response XML as response

Why should I add one more steps of mapping XML elements to own custom elements.

I'm not able to convince myself, probably because I'm not able to think of a better situation/reason.

Please suggest, with example if possible.

Answer 1

It helps to reduce coupling between the presentation (i.e. the XML schema) and the business logic. For example in case of schema changes you don't have to touch the business logic, just the mapping between the objects.

In simple cases it might not be worth the additional complexity. But if the objects are used extensively in the business logic component you should consider it.