SCA has recently looked at norms and OSGI specifications. After reading again to make a comprehensive comparison between the two.
First, the two normative starting point and the mind is not the same. SCA specification is for enterprise application integration and development, OSGI specification is the original purpose of computing for mobile devices drawn. Since the two different starting point, leading to the focus of two different specifications. SCA specifications version now is 0.95, relative OSGI specification 4.0 version also appears to be somewhat immature.
SCA specification focuses on solving the existing call between enterprise applications and enterprise applications to service-oriented thinking on how to build and deploy. However, the realization of the component requirements in respect of the container is some lack of standing on the user's perspective simply describes the specifications of the client API.
The OSGI specification as the initial starting point is the computing environment for mobile devices, so more consideration to the run-time framework and services in the run time of the dynamic matching problem. In addition, the application provides a run time of hot deployment, analysis, operation, unloading capacity. It should be said, OSGI specification 4.0 has been developed to a relatively well regulated.
SCA SCA specifications now on the realization of the container, not one of guiding ideas, but OSGI standard in this area have done very refined. OSGI specification defines a Framework, Start Level, Package Admin, Security, a detailed description of the dependence between different components of the rules (static dependency, dynamic import), between the different components of the class name using a separate space.
As the SCA specifications for enterprise application integration, the implementation of SCA components can be Java, BPEL, EJB, WebService. The implementation of OSGI only for Java language. This is also the starting point because the two different result.
The SCA and OSGI the assembly model, the two are similar. Both are outside services (Service), but the SCA is more emphasis on design time component assembly, and the definition of a flexible component assembly model, the smallest atomic components can be assembled into a large system.
Has been achieved from the existing products of view, OSGI more be used as a single product of the overall structure, SCA specifications are more business-oriented components used in the assembly specification, as the structure of how the SCA products SCA specification is not a concern.
From the comparison on top can see the obvious shortcomings of the two separately, SCA specifications too much emphasis on integration, but the running time of the SCA component behavior description is too weak, all the components are designed to achieve time bound. Perhaps the product can be achieved in the SCA runtime dynamic binding, but as a norm, this is what it lacks. OSGI standard description of the components of the running time is complete, but all components must run in the same virtual machine, virtual machine service component interoperability is slightly insufficient.
Recommended links:
High-quality C + + / C Programming Guide - Chapter 11 references the experience of other programming
How To Identify Real And Can Automatically Create Index Index
Procurement Of Essential Personnel Of The Five Quality
HR staged STAR Wars
Expert Help TOOLS
Win2000 Registry
WMV to Zune
Eclipse to improve productivity
YouTube to WMV
Comment CONVERTERS And Optimizers
d3dx9 dll is missing EASY repair
European 3G camp stepped up lobbying of China
3DS MAX introduced the essence of materials and textures
QuickTime TO MPG
No comments:
Post a Comment