Common handler framework

1. A computer-based system comprising:

a computer, including a computer readable medium and processor;

a common handler framework, executing on the computer, that enables handlers for multiple different types of web services programming models to be used in a single handler chain;

a plurality of handlers, each using one of the multiple different types of web services programming models;

wherein the common handler framework

identifies an execution environment,

based on the execution environment, determines which of the plurality of handlers are native handlers configured to be used in the execution environment, and which are foreign handlers configured to be used in a different execution environment,

wraps each foreign handler such that it appears to the execution environment as a native handler,

adds the plurality of handlers to the single handler chain, and

at runtime, invokes each handler in the single handler chain, wherein each foreign handler in the single handler chain is invoked using a simulation layer of the common handler framework.

2. The computer-based system of claim 1 , wherein one of the multiple different types of web services programming models is JAX-WS.

3. The computer-based system of claim 1 , wherein one of the multiple different types of web services programming models is JAX-RPC.

4. The computer-based system of claim 1 , wherein the common handler framework provides data to a foreign handler in the format native to the web services programming model of the handler.

5. The computer-based system of claim 1 , wherein at least one of the handlers are provided by a middleware environment.

6. The computer-based system of claim 5 , wherein at least one the handler provided by the middleware environment includes a security handler.

7. The computer-based system of claim 5 , wherein at least one the handler provided by the middleware environment includes a reliable messaging handler.

8. The computer-based system of claim 5 , wherein at least one the handler provided by the middleware environment includes a transaction handler.

9. The computer-based system of claim 5 , wherein another handler is provided by a web service application running on the middleware environment.

10. The computer-based system of claim 1 , wherein the common handler framework provides for a wrapper over at least one of the handlers.

11. A non-transitory computer-readable storage medium including code to provide:

a common handler framework, executing on a computer, including a computer readable medium and processor, that enables handlers for multiple different types of web services programming models to be used in a single handler chain;

a plurality of handlers, each using one of the multiple different types of web services programming models;

wherein the common handler framework

identifies an execution environment,

based on the execution environment, determines which of the plurality of handlers are native handlers configured to be used in the execution environment, and which are foreign handlers configured to be used in a different execution environment,

wraps each foreign handler such that it appears to the execution environment as a native handler,

adding the plurality of handlers to the single handler chain, and

at runtime, invoking each handler in the single handler chain, wherein each foreign handler in the single handler chain is invoked using a simulation layer of the common handler framework.

12. The non-transitory computer-readable storage medium of claim 11 , wherein one of the multiple different types of web services programming models is JAX-WS.

13. The non-transitory computer-readable storage medium of claim 11 , wherein one of the multiple different types of web services programming models is a JAX-RPC.

14. The non-transitory computer-readable storage medium of claim 11 , wherein the common handler framework provides data a foreign handler in the format native to the web services programming model of the handler.

15. The non-transitory computer-readable storage medium of claim 11 , wherein at least one of the handlers is provided by a middleware environment.

16. The non-transitory computer-readable storage medium of claim 15 , wherein another handler is provided by a web service application running on the middleware environment.

17. The non-transitory computer-readable storage medium of claim 11 , wherein the common handler framework provides for a wrapper over at least one of the handlers.

18. A computer-based method comprising:

providing a common handler framework, executing on a computer, including a computer readable medium and processor, which enables handlers for multiple different types of web services programming models to be used in a single handler chain;

providing a plurality of handlers, each using one of the multiple different types of web services programming models;

identifying an execution environment;

based on the execution environment, determines which of the plurality of handlers are native handlers configured to be used in the execution environment, and which are foreign handlers configured to be used in a different execution environment; and

wrapping each foreign handler such that it appears to the execution environment as a native handler;

adding the plurality of handlers to the single handler chain, and

at runtime, invoking each handler in the single handler chain, wherein each foreign handler in the single handler chain is invoked using a simulation layer of the common handler framework.

19. The computer-based method of claim 18 , wherein one of the multiple different types of web services programming models is JAX-WS.

20. The computer-based method of claim 18 , wherein one of the multiple different types of web services programming models is JAX-RPC.

21. The computer-based method of claim 18 , wherein the common handler framework provides data to a foreign handler in the format native to the web services programming model of the handler.

22. The computer-based method of claim 18 , wherein at least one of the handlers are provided by a middleware environment.