While demonstrating the new features of SOA-Web 2.0, using 2.0 of Web pages can bring more sweetness, in addition, the development path based on commercial operations may show more advantages for casual group services. The service content mainly focuses on data processing and application.
However, alas, such a perfect institution does not actually exist. Stephen Maryka, CTO from ICEsoft Technologies, does not believe in the Java company version-the SOA platform selected by many companies-is suitable for installation to operate on web pages of 2.0. In a comment posted on a search page, he pointed out: "In terms of usage, it may indeed show that it supports 2.0 web pages, however, in most processes, Java scripts that are equivalent to Ajax technology are mostly used for running."
Despite this, Java EE was designed earlier than Ajax technology while 2.0 web pages grew mainly in Ajax technology, which indeed touched many fields. As Maryka points out:
"In the Java EE manual, the Java public service staff will provide detailed content, but the previous revisions circulating show more about Ajax technology and the concept of 2.0 web pages. Its Extended building components in JSF prove that it is more suitable for being integrated into Ajax technology as leveraged components. However, the problem is that the Ajax lever component exists in a small communication warehouse, which damages the JSF's life cycle. Now we need a comprehensive approach to integrate Ajax technology without compromising the life cycle of JSF ."
Maryka recommends that you improve the communication model requirements of Java EE users and add update instructions. "Currently, the user communication model that is circulating is only a foundation in JSF. The technology is still rough in displaying the rich features of web pages 2.0 ."