Can you explain little bit more about this line: "But when you use web services instead of IIOP to access a SLSB you lose some infrastructure services like transaction propagation."
I searched but didn't understand it.
When using container-managed transactions, you set attributes to define the transaction type of the method. When using any of the following: # Required # Mandatory # Supports If the caller has a transaction, it will be bound to the transaction used on this method (so if the caller's transaction rolls back the client transaction will roll back also). If the caller is remote, the only way for this to work is if the protocol being used is IIOP.
So, when using an EJB to expose a web service, you should think that it's methods should have only "requires new" or "not supported" transaction behavior.