I understand Seam simplifies the J2EE Programming model, but in what ways does it make life easier developing an SOA solution? In other words, what do I get in terms of SOA with Seam that I don't get if I stick to J2EE? Tks!
Seam is not something different. Its, in fact, based on JavaEE stack. So, it provides everything you got in JavaEE i.e. web services integration and stuff. But yes I would like to know which OSGi implementation it supports officially.
I'm going to be perfectly honest and stick my head out, perhaps risking criticism. I simply don't get what this term SOA means. Yes, I have read stuff about it and I just don't make the connection. Now, let's put these terms aside and talk about tangible things. Seam offers a killer business process integration, which frankly makes BPM something that can actually be used by a developer. Then, Seam offers a very nice REST integration so that it can create and consume REST web services very easily. Seam doesn't really have an integration with an ESB at this point, at least not that the Seam project members really talk about. And yes, Seam taps into all the web service stuff that the Java EE platform provides. Check out Gavin's talk and presentation on Seam and SOA.
Okay, so put my naivety aside on this topic. JBoss is a middleware company (or should I say division of RedHat). You can be pretty sure that there is going to be a lot of noise about how to pull Seam into the JBoss SOA stack in the very near future (and some noise made already). But frankly, until I get it, I'm not going to stand up hear and say stupid things about it.