This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: Soap Activation or not?
Feed Title: Marc's Java Blog
Feed URL: http://www.logemann.org/day/index_java.xml
Feed Description: Java related topics for all major areas. So you will see J2ME, J2SE and J2EE issues here.
Lately i saw a customer system using SOAP to communicate from an Application on Server1 to another Application (or its Services) on Server2 within the same LAN. I didnt had the time to see the actual SOAP implementation but some issues came into my mind.
1. Why did they chose SOAP and not RMI/IIOP (by just developing SessionBeans) thus avoiding the envelope parsing and general XML overhead?
2. Does each SOAP impl. or any SOAP impl. at all support Activation/Passivation on AppServers?
3. Why did they give up the chance to create stateful Services?
4. What are Webservices good for, when the only "client" is an inhouse Application? Opening some more ports in the firewall between the servers cant be so hard...
Many questions... But at the end, the architecture irritated me.
Previous Topic
