Answers to Java ee 5's SOA capabilities

Kevin Schmidt, executive director of Sun Microsystems's SOA product, answered some questions about SoA capabilities on the Java ee 5 platform.

Those critics believe that the Java ee 5 platform for Web developers and SOA designers is too complicated, but this is not the case. In the first part of this Q & A, Kevin Schmidt (CEO of Sun Microsystems's SOA product) talked about the convenience the Java ee 5 platform brings to SOA developers. In the second part, he answered some criticism about the platform.

Critics believe that Java ee 5 introduces more complexity than it reduces. In this platform, what complexity is reduced, and those parts are still complicated?

Kevin Schmidt: there are some significant improvements in EJB, and ejb3.0 and annotations play a simplified role. Netbean makes it easier to create elements. Netbean provides a variety of different design types and solver, allowing you to create whatever element you want, through annotations, tools can help you simplify writing in the creation TemplateCodeAnd logic. Tools can be used to create Servlets, JSP, and Web application software.

What are the benefits of annotation for Web Service Development?

SCHMIDT: Annotations allow you to specify the metadata required to create applications in the source file. In the past, users had to know a lot of details and use descriptors to define the metadata of the entire application software. Annotations allow you to specify the metadata in the source file under explicit guidance, so that you do not have to worry about too much details. Annotations can provide you with keywords and structures to define information under clear guidance, and tools can help you automatically generate comments. Therefore, developers do not need to know all the comments to be input. We provide them, but they can also be modified as needed. Annotations and tools can simplify the developer development process.

How do you think about the value of Ruby and spring in service directing to design and development?

SCHMIDT: many people see their values, and many developers use them to illustrate their values. They provide a different way, some of which can reduce the workload. So they are still valuable. However, I still think that Java EE stands at an important position and should work better than other languages.

In Java ee 5, the portability of Virtual Machine activation is considered by some analysts as a disaster and is considered useless for the SOA central interface because it does not need to be portable. Do you think that in the next round of platforms in the future, portability will not be emphasized, or will it still be an important concept in IT infrastructure?

SCHMIDT: I think portability is a very important concept. It is a basis for standardization. Portability allows more buyers to execute regulations and create better products for the society and customers through competition. The portability is consistent with the standard, which is the basis of Java ee.

What is the important difference between Enterprise SOA and traditional web design? How does Java ee 5 support such unnecessary features?

SCHMIDT: Speaking of enterprises, the Java ee 5 platform is required to have a storage device and transfer a large amount of data due to its nature. Traditionally, enterprises require confidentiality, ease of management, and management of services and resources. These are the very important points that Java ee 5 can provide to enterprises.

Is the Java ee 5 web service too API-centric?

SCHMIDT: when using JAX-WS, services built through Java ee 5 can be easily connected to services created using other technologies and languages. Compared with other languages, Java ee 5 does not introduce harsh connection conditions. Your service is only related to how you define the WSDL, the granularity of service formulation, and the structure of the interface that you use in the service. Therefore, whether it is easy to connect is irrelevant to Java ee 5 itself.

On the other hand, some people advocate Ruby and rails. Is it necessary to integrate them into Java ee 5 or let them do their own thing?

SCHMIDT: Of course, we can integrate them into various API levels, potential network usage, or a more friendly interface. There may be ways to link these two blocks.

You have mentioned glassfish many times. How is the progress of glassfish?

SCHMIDT: There are a lot of actions about glassfish. Java ee5 DSK was updated in October 30. This is an update released on javaone earlier this year. This update provides improved performance and stability. The most important thing we do is to publish the jbi runtime and the BPEL service engine. Another update of the Java ee 5 SDK will add the jbi service engine and binding components. We don't have more details yet, but we are committed to modularizing Java ee 5 to make it easy for people to use its various parts.

Are you going back to tango for updates?

SCHMIDT: we are still working on JAX-WS projects, collaboration capabilities, and support for the WS-Star specifications. At the same time, the study of collaboration capabilities with. NET network services and other technologies is also underway.

In addition to. net, what technologies and tools do you pay attention?

SCHMIDT: Of course, axis (APACHE project) is also quite common. It is used as the basis for WebSphere and WebLogic to create network services and SOA application software.

In combination, what capabilities does Java ee 5 provide for SOA development?

SCHMIDT: Java ee 5 does provide the ability to build services and applications. I know that the company wants to use other languages for collaborative programming. In the jbi engine of Java ee 5, we provide a unified interface with other languages to compile larger application software and balance Java ee with other languages, place them in the most appropriate place.