earlier this year i wrote an article describing how enterprise javabeans had impacted the application server market, causing a convergence between web application servers and distributed object and transaction servers. with the advent of the j2ee (java 2 enterprise edition) standard, were about to witness another seismic shift in this market.
its worth looking at what j2ee is -and isnt. j2ee builds on the java 2 standard, and adds specifications for most of the important programming interfaces in an application server. key interfaces are ejb for middle-tier logic, and servlets and java server pages (jsp) for dynamically generated html pages. other apis include jndi (naming and directories), jms (messaging), javamail, jta/jts (transactions) and rmi-iiop (remote communications protocol).
while the j2ee specification comes with a reference implementation and compliance tests, its important to understand that j2ee doesnt cover a number of apis and functions that are central to todays application servers. for example, there are no specifications for how to connect to legacy or nonrelational data sources; how to create applications that interact with other systems via xml; how to cluster, load-balance and fail-over a server; or how to manage a server.
benefits of standardizatio... 下一页