SOA : Is it Object Oriented, procedural, or both?

I'm a long time C++ developer and have spent time to develop good OO methodologies and practices. I'm also a fan of Design Patterns.

� 

I'm just entering the SOA world, and trying to get into the spirit of it. I am a bit confused about what the "best practices" and "best designs" are when it comes time to designing�  an individual service.

� 

In some of the literature I've seen about SOA, there seems to be an assertion that service implementations are really just units of functionality. So I envision a typical service� has a variety of "functions" to perform work, but objects aren't really necessary. One could argue that objects should be created for each "function" provided by the service, but if the service is supposed to be functional, objects might just clutter things up.

� 

Obviously, I'm confused.

� 

I guess my question i ...