Mark Hapner talks about J2EE 1.4 new features
For the development direction of Sun J2EE technology, Mark Hapner is a key person: Mark is the leader of J2EE technical specifications, and the representative of Sun in WS-I (Web Service Interoperability) organized, he has participated in JDBC. The formulation of Technical specifications such as EJB, JMS. When receiving an interview with the THSERVERSIDE website recently, Mark Hapner talked about some technical issues related to J2EE 1.4.
In this interview, Mark mentioned: J2EE 1.4 The most important new feature is integrated in servlet and EJB, which is integrated with Web services, which can be seen that the level of the Web service is visible. But Mark believes that Sun has provided similar functions in the J2EE Web service development package. This time just integrates it more closely into the core of J2EE. The developers who are familiar with J2EE should be able to adapt to this change quickly. To make better use J2EE development web services.
J2EE 1.4 There are also some improvements in other respects, including connectors, management and deployment, identity authentication. But these aspects of improvements are seamlessly integrated with previous APIs. Ordinary developers can enjoy it.
In JSP 2.0, in addition to the previous JSP flag extension (Tag Extension Facility), it also provides something called "Simple Tag Extension Facility" to support relatively simple marking subset. Expand. Developers can extend tags in two ways of JSP and Java classes so that more developers can enjoy the power of custom tags. JSP 2.0 is a function called "JSP fragment" allows developers to write their own JSP tags.
In J2EE 1.4, Deployment Descriptor, DD will no longer use DTD, but use XML Schema. At the same time, Sun also plans to include JSR 175 - Java programming language metadata tools - J2EE. Some tools have been used to use attribute content in Javadoc to process Java source code, such as xDoclet, while JSR 175 is desirable to provide a standardized approach. This metadata will be very useful. The simplest is: You can automatically generate deployment descriptors from Javadoc with metadata tools to avoid trouble of writing XML files; complicated, and can even perform macro replacement features similar to C with metadata tools, or implement Design By The pre-compiled function of Contract. If JSR 175 can be included in the Java specification, I expect Design by Contract.
According to Mark, the Sun One Application Server and J2EE 1.4 Reference implementation share some code. J2EE 1.4 Blueprint Sample Application will no longer be a famous "Pet Store", but a application called "Adventure Builder". Especially interesting is that Adventure Builder will not use EJB. I remember that many people attack EJB is "the most embarrassing people in J2EE", I don't know if SUN is suggested to people? Of course, Sun also provides an application example of J2EE using EJB.
Until now, Mark is unclear when there will be lack of applying the J2EE 1.4 application server product. According to the context, I believe this time will not be too long. However, Sun provides such a comprehensive, so in-depth support in J2EE 1.4, so as soon as the propaganda is, it is obviously to compete for the market with its upstream status and application server manufacturers. In my opinion, IBM and BEA will support J2EE 1.4, which will be an event worthy of attention. Please see the full text of this interview:
http://www.theserverside.com/events/videos/markhapnertext/interview.jsp
Another related report:
Sun plans to rely on Sun One Application Server to take back Java / XML integrated server market
