When Web Services can handle security and transaction, J2EE would become not very useful.
J2EE is java specific architecture for enterprise solutions.Webservices on the other hand leverages mainly on its being xml based.Being XML based webservices are insulated from the implementation technology.Therefore in my opinion J2EE and webservices cater to different requirements.I is also likely that J2EE applications will expose a webserivce interface in an attempt the webservicize the applications. william
FYI, The next major change in J2EE will be suport for Web Services. Please read JSR 109 . EJBs,Servlets and MDB would be calibvrated as Web service components. J2EE containers would eventually become Web Service containers. Thanx Mandan
There are some pretty heavy issues here though. For example, what about transactions? I heard an interesting comment from Don Box at a .Net conference to the effect of "Do you really want to have a tx locking your database that will be going out over the internet in its graph?". Security is also a problem that has no current final spec for web services. Do you think IT is really going to want to use anything that has no security specification? I think there's a viable story right now for web services as a "poor man's EAI" but doubt that it will be anything more than a proxy/facade interface in production EJB use.