Message handling in a service-oriented architecture

1. An article comprising a non-transitory machine-readable storage medium embodying instructions that when performed by one or more machines result in operations comprising:

initiating a service call to a backend system by a user interface in a service-oriented architecture;

receiving a service answer from the backend system encapsulating a backend error object;

mapping the backend error object to a front end error object; and

presenting a front end error message derived from the front end error object in the user interface;

wherein the backend error object contains variables that are each described by a type and a corresponding business semantic, the variables being used to generate the front end error object.

2. An article as in claim 1 , wherein the mapping comprises accessing a mapping table mapping backend error objects to front end error objects.

3. An article as in claim 2 , wherein the mapping table comprises a backend error preview for each backend error object.

4. An article as in claim 2 , wherein the mapping table comprises a front end error preview characterizing the front end error message.

5. An article as in claim 1 , wherein the backend error object comprises a short text description characterizing an error and a long text description characterizing the error, the long text description containing more characters than the short text description.

6. An article as in claim 1 , wherein the backend error object characterizes a severity of a corresponding error.

7. An article as in claim 1 , wherein the tangible machine-readable storage medium further embodies instructions that when performed by one or more machines result in operations comprising:

initiating, by the user interface, a service based on variables encapsulated in the backend error object to obtain error information to include in the front end error message.

8. An article as in claim 1 , wherein the front end error object includes all attributes of the backend error object.

9. An article as in claim 1 , wherein the front end error object includes a subset of attributes of the backend error object and additional attributes not included in the backend error object.

10. An article as in claim 1 , wherein a backend error message in the backend error object cannot be overrun and is required to be presented in the front end error message.

11. A computer-implemented method comprising:

initiating a service call to a backend system by a user interface in a service-oriented architecture;

receiving a service answer from the backend system encapsulating a backend error object;

mapping the backend error object to a front end error object; and

presenting, in the user interface, a front end error message derived from variables in the front end error object;

wherein the backend error object contains variables that are each described by a type and a corresponding business semantic, the variables being used to generate the front end error object.

12. A method as in claim 11 , wherein the mapping comprises accessing a mapping table mapping backend error objects to front end error objects.

13. A method as in claim 12 , wherein the mapping table comprises a backend error preview for each backend error object.

14. A method as in claim 12 , wherein the mapping table comprises a front end error preview characterizing the front end error message.

15. A method as in claim 11 , wherein the backend error object characterizes a severity of a corresponding error.

16. A method as in claim 11 further comprising:

initiating, by the user interface, a service based on variables encapsulated in the backend error object to obtain error information to include in the front end error message.

17. A method as in claim 11 , wherein the front end error object includes all attributes of the backend error object.

18. A method as in claim 11 , wherein the front end error object includes a subset of attributes of the backend error object and additional attributes not included in the backend error object.

19. A method as in claim 11 , wherein the backend error object comprises a short text description characterizing an error and a long text description characterizing the error, the long text description containing more characters than the short text description.

20. A system comprising:

a front end system comprising a user interface; and

a backend system coupled to the front end system via TCP/IP in a service-oriented architecture;

the front end system initiating a service call to the backend system via the user interface;

the backend system generating a service answer to the service call that includes a backend error object;

the front end system mapping the backend error object to a front end error object so that a front end error message derived from the front end error object can be presented in the user interface, the front end error message being different than a backend error message included in the backend error object;

wherein the backend error object consists of:

an ID field for an identification for a corresponding message;

a short text field that includes a first number of characters to describe the corresponding message;

a long text field that includes a second number of characters to describe the corresponding message, the second number being greater than the first number;

a severity field that characterizes a severity of the corresponding message;

a preview field that includes a preview of the message;

a variables table containing variables that includes an identification of each variable, a type of each variable, a length of each variable, and a description of each variable.