Implementing Contextual Web Services, Page 3
This article has discussed HTTP's stateless nature and how Web Services can be implemented by using vendor-specific and standard JAX-RPC interfaces to gain access to Web Service context and HTTP Session under which the user operates. The context enables developers to implement advanced domain services with several features such as personalization, versioning, security, mediation, and so on. However, developers should take due diligence before using any vendor-specific interfaces because they will put them in vendor lock-ins and perhaps cause inherent migration problems in the future.
About the Author
Ayyappan Gandhirajan is an Architect with Perot Systems, Bangalore, India. He has a Master's degree in Software Systems from BITS, Pilani, India and a Bachelors degree in Electronics & Communication Engineering from MK University, India. He has 10 years of profound software experience in Travel, Telecom/Mobility, Healthcare, and e-commerce domains using technologies such as SOA, ESB, Web Service, Web Service Security, and J2EE. Prior to Perot Systems, he worked with Hewlett-Packard, India for five years in Mobility & SOA. He can be reached at G_Ayyapparaj@yahoo.com or firstname.lastname@example.org.
Page 3 of 3