Yep pretty much everything in the IT space could be describe as “subjective”. There is always more than one way to skin the cat with pros and cons for all. :lol:
POX over HTTP is not my personal favorite but that doesn’t really mean anything. I prefer not interacting with XML directly other than as the underlying glue for service interfaces.
Dealing with typed data in the context of classes/objects in the native language allows me to bring in and out different providers of the data without the developer really having to being concern about the underlying data provider. They program to the interface relying on the model rather than the underlying providers view of what the data should be whether it be XML, Ralational or some other format. New providers can be injected without changing the underlying code base.
You can do the same thing with POX over HTTP assuming you inject a services layer in there but then you end up with what I was describing early which would be perfectly fine. Using SOAP generally gets you into most tools capability to auto generate and interpret your XML as native objects. Some tools can do that with POX over HTTP but support of that is hit or miss depending on the tool set.
Does that make sense in all cases? Probably not but it really doesn’t hurt anything either. It does require some extra up front work so depending on the requirements, timing etc. you may want something quick and easy.
Haven’t really seen that be an issue but that is just my experience with it. Mileage may vary with others.