The purpose of web services are to allow applications to communicate. It is an "integration" techology. It is not an "implementation" technology.
The Java servlet code above is technology dependent, e.g. Java objects, so it cannot considered "universal."
Keep in mind that "services" in a SOA and "web services" are different concepts, i.e. they are not the same.
Web Service Example
For example, if you wanted to expose data to many applications in an enterprise and also prevent any application from directly connecting to the database management system, you could create a "web service" for this. Here you would still have an application that actually connects to the database and retrieves the data. The web service would simply sit in the middle. Client applications would use the web service to get the data. Firewalls and all types of security measures would protect the database management system (DBMS). No client applications would know the location of the DBMS. Only the internal application would know.
Service Example
Your organization sends consultants on many speaking engagements and you want to centralize the processes for making these reservations. You could create a "service" that will handle all reservations from checking calendars, contacting and paying third-parties, getting all required approvals and sending notifications, and whatever else. This "service" is an example of what an SOA is all about. How exactly this "service" is implemented and if it uses other services and "possibly" one or more "web services" are implementation details. The "service" is a method of encapsulating and exposing a business process efficiently. SOA is a strategic business methodology mostly and requires significant stakeholders to be implemented correctly...if they have the right resources