By definition the term webservices was created to denominate the data flow on top of TCP/IP + SOAP. From a couple of years people started talking about RESTful as if it was a webservice. It is not more than a standardization on top of TCP/IP to transport aggregated data that should be translated into an Object for OO Languages...(a plain String)
RESTful web services are not based on TCP/IP, they are HTTP. HTTP is the protocol of the web, hence web service. Yes, the initial term web service was defined in terms of SOAP but that was a long time ago. It used to be the case that the term cocktail only specifically applied to alcoholic drinks made with bitters, sugar, and water.
SOAP is a degenerate spec in that it's almost entirely irrelavant aside from a handful of elements that are required by WSDL based services. Almost no one creates web services that don't follow the doc-literal style. To insist on defining web services in terms of SOAP is therefore pointless at best.
Can anybody please tell me why we should care so much about restful in terms of security, distributed transactions, EE Applications, etc? Why do people care so much about writting articles about it?
If you don't understand why REST is important, you should seek to understand. I doubt anyone will take the time to walk you through it all. You can start here:
REST Dissertation
The above talks about the fundamental concepts of REST which is roughly a backwards engineering of why the web works.
RESTful Webservices are not the same thing as REST. REST is an architectural approach that can be applied to many things. RESTful web services are a specific approach to web services that utilizes the restful aspects of HTTP. This book is a good resource for getting an understanding of that:
RESTful Web Services