BEA EWORLD Site Report: First Day
12
15th
Shanghai sunny, outdoor temperature 17 degrees. The BEA EWORLD meeting will open tomorrow. The high level of this conference is coming to China, visible to the level of attention to this conference. There are three topics in this conference. First, DIABLO; Second, SOA; third, developer relationship.
Diablo is not a game of Diablo, is the code of WebLogic Server 9.0 that will be released tomorrow.
December
7th
In San Francisco, BEA pulled a group of speakers in the Oracle Openworld Conference to a hotel and showed them Diablo's beta version, which also caused great interest in these technical experts. According to sporama from all aspects, the new version of the WebLogic application server supports J2EE 1.4 specification, and is said to have special optimization of SOA. In fact, the WS-ReliableMessaging specification is implemented with JMS-based messaging and forwarding mechanisms - - This is a Web Service specification about "providing reliable asynchronous messages". According to the Executive Vice President of the BEA Product, the Enterprise Service Bus, ESB) of the Enterprise Service Bus (ESB) built on this message mechanism is less than three to four times more efficient than previous versions. It is because there is such a reliable and efficient message bus, and the SOA, which has been respected, can be its reality, which is why Diablo applied servers especially for SOA.
In addition, BEA emphasizes the thermal deployment capability of this server. In this propaganda information of this eWorld Conference, the author saw a material entitled "fluid computing), which pointed out that BEA responds to rapid changes in enterprises, and Diablo strong thermal deployment capabilities should be important. Technical link. As is well known, the WEBLOGIC handler EJB has used "pre-transder" approach, that is, the first use of the ANT script to generate EJB necessary for the HOM object according to the service code, and then deployed to the application server, this implementation strategy is unable to implement Effective thermal departments. The BEA focused on Diablo's thermal deployment capabilities, coupled with the previous BEA recruiting the two core developers of AspectWerkz, which could not help but believe in AOP technology, and thoroughly abandoned the pre-translational approach. This conjecture is about to be confirmed in the next two days.
In addition to Diablo's release, SOA application is also a key topic of this conference. In 2004, the concept of SOA has been fried in all major manufacturers, but developers are generally in the wait-and-see stage, hoping to see an example of architecture of SOA in actual projects. In the next two days, BEA will show developers to the SOA application examples of telecommunications, finance, government applications.
In addition, the BEA developer day event will be one of the highlights of the conference. BEA has always had a good reputation in the developer group. In addition to the founder and CEO Zhuang Sihao, the BEA high-rise, the Global Product Executive Vice President Huang Weiwen is also the Chief Technology Expert Michael Smith, CTO Office. And technical people such as Scott Regan responsible for developers. The 9CBS website will discuss the two technical experts to conduct exclusive interviews, discussions on the new generation of application server technology architectures, BEA China Developer Activity Strategy, and BEA China Talent Program. Please 9CBS netizens continue to pay attention to the follow-up reports of the reporter.
Develop your Rich Client: IBM supports Laszlo open source rich client platform
The IBM AlphaWorks website has recently released an integrated development environment for developing a Laszlo application (actually an Eclipse plugin) that allows J2EE developers to quickly develop Laszlo-based Rich Client applications in their familiar Eclipse environments. You can download the plugin at the following address: http://alphaworks.ibm.com/tech/ide4laszlo
In addition, the AlphaWorks website also provides an example application developed by Laszlo, showing the process of developing a Laszlo application in an Eclispe environment. The address of Demo is as follows:
Http://dl.alphaworks.ibm.com/technologies/rcb/demo.html
Laszlo is an open source Rich Client development environment. When using the Laszlo platform, the developer only needs to write a description language named LZX (where XML and JavaScript) are integrated, and the Laszlo platform running on the J2EE application server will compile it into a Flash file and transfer it to the client. Laszlo and XUL, XAML are very similar to the operation principle. But its biggest advantage is that it compiles the description language into flash, and Flash is a display form supported by any browser, so that the browser is solved with the browser. Moreover, in the future plan, Laszlo can also compile LZX into Java or .NET local code, greatly improve operational efficiency. Recently, Laszlo's CTO David Temkin has accepted an interview and made more introductions to Laszlo's strategic and development:
Http://news.com.com/david vs. goliath vs. goliath/2008-7344_3-5457982.html
JSP 2.1 and JSF 1.2 specification release preview version
J2EE's two important performance layer technologies JSP and JSF released a preview version of the new technical specification, and the most important point is that both of them are part of the Expression Language, EL. In the near future, these two techniques may be further integrated with each other to become a unified performance layer technology. However, in the universal view of the J2EE community, if the JSP is not the best choice, the JSP is not the best choice, and Velocity and XSLT, etc. Template-based view technologies are usually more convenient than JSP; and component-based JSF is also facing extensive Crisis of Confidence. Whether the combination of the two can be recognized by the industry, and it takes time to test.
The following is an official announcement
We are very happy to announce, JavaServer Pages, JSR-245 Developed Faces.javaserver Pages (JSP) 2.1 and JavaServer Faces (Faces) 1.2 developed under JSR-252.
JSP 2.1 outputs Expression Language (EL) to its own separate document, in technology, these documents are sub-documents of JSP specifications. These unified EL specification define a higher-level Java package, Javax.el. This package is completely independent between this technology and allows this technology to insert itself into the EL processing. Changed JSP specification complies with standardized EL specification.
This specification has no new feature for the JSR-252 mentioned earlier. Faces 1.2 supports new standardized EL, which also contains some of the relevant specifications for bug fixes.
Faces and JSP brought some new features in JSRS, and also lay a solid foundation for future development. For example, in a web application of Faces and JSP simultaneously, the web page is only possible to use JSP (excluding any Faces content) to access Managed Beans. Details of changing content can be seen in the preface to the Appendix E in JSP Specification and Faces Specification. JSP 2.1 EDR (JSR-245) http://jcp.org/aboutjava/communityprocess/edr/jsr245/ Faces 1.2 EDR (JSR-252) http://jcp.org/aboutjava/communityprocess/edr/jsr252/
Google Digits into Java Talent BEA Chief Architects
Not long ago, Google had just dug into Joshua Bloch, he is the author of Effective Java, the Collections framework he designed is one of the most well-received class library frameworks. At the same time, he is a chief expert in JSR175 (a metadata facility for the javatm programming language.
Then, Google also puts the Chief Architect of the BEA to Adam Bosworth into its own. Bosworth has been widely respected in the software industry as a technical executive. Before working for new enterprises Crossgain (acquired by BEA), Bosworth once served in Microsoft and successfully engaged in some project development, such as Microsoft's Access database.
His hopping is too sudden. Two months ago, he also served as an important role in the supplier's "year eWorld show", and introduced the Alchemy project in his keynote ---- a next-generation mobile browser plan.
Google's recruitment to buy a horse program has been in an orderly manner, a David Stoutamire working in Sun Microsystem, now working in Google. Just last week, NEAL GAFTER, Sun's Javac, also left Sun to go Google.
Not only the Java, Greg Stein, was a Collabnet project manager, managing the Subversion project and released their Sourcecast products, and now work in Google's blog software; Rob Pike, once is one of the first UNIX team members of Bell Laboratory, participation The development of the Plan 9 and Inferno operating system is now going to Google.
Google has been craving for talents. For developers, Google is also an attractive place. He only hires the best, smartest, almost genius, and only Microsoft can compare with it in the cage talent. Recently, Java talents have been pouring into Google is coincident, or Google is ready to try to do something based on Java, we will wait and see.
