I J2EE and. NET understand that humble
INTRODUCTION
====
Two months ago, another company for the development group based on J2EE (BEA WebLogic) platform to re-develop the original system, in the selection meeting, on enterprise development, I may have to deal with the various issues Advisory BEA's technology staff because I did not have the platform based on J2EE development experience, it can only against themselves. NET development experience and the experience in J2EE to question whether there is a similar building blocks for the support, of course, this is the development of two different platform, it is impossible to totally one-to-one thing, but the same is the development of enterprise-class platform, in fact, I think from the point of view framework, the development framework should be roughly the same. Following is that I took part in the selection after consulting with a number of experience, as I understand shallow Java platform, there are omissions and biases of readers also requested correction.
1, the COM + EJB
EJB and COM + There are too many similarities, are based on the specific binary agreement RMI and DCOM are distributed component technology. Because they need to complete the same functional requirements, they have decided too much the same as the need containers management, the state context, the Panel model, serial technology, object instance management, threads, long-distance calls, message queues, security and role , whether oral or entities Bean Bean, and regardless of the CMP or BMP, COM + can be found in a similar concept. In short, they like one pair of brothers.
EJB is a normative standard, and COM +, more people think that it is a product, perhaps this is Microsoft people stop feeling, because we can choose a different EJB containers server products, BEA, IBM or other open source , and only this one COM +. But the fact COM / DCOM / COM + is a norm or standard, like EJB, as long as you achieve the minimum standards in the COM + interface can be certain registered as a COM + components in Visual Basic 6 in the preparation of a COM + components is very easy.
2, JDBC on ADO
JDBC and ADO is somewhat similar, but拿它and ADO.net do some comparison seems unfair, after all, is late ADO.net. In the data object, I am most concerned about is that their data processing and caching, a long time, has been using the three-tier / multi-application framework to build enterprise applications, so the data sets / results-processing and remote transmission must be first of all the problems facing us.
Based on the traditional three-tier ADO.Recordset record set in the application, people usually through DCOM / CORBA agreement to transmit these data can be persistent object, data layers in the client received the revised data object, and then through these records focus on the meta-data to include mapping of SQL-related operations, in a multi-storey structure of the enterprise applications, such long-distance transmission, the client cache data sets and data connectivity fault mode technology is essential. JDBC in the ResultSet is not directly do, and this is perhaps the various data processing, mapping, as well as similar Hibernate EJB components such technology in the development of the Java platform in the cause of flourishing stop!
3, O / R Mapping
In fact I am not a type of data object or object-relational mapping (O / R Mapping) technology supporters, at least in the case at this stage. For ObjectSpace (It is said that in ADO.net 2 of the publication of the technology) or in Java Hibernate has no interest, I think the O / R Mapping it is not as wonderful as publicity, I would like to use this ADO.net DataSet " Table Module "[See" enterprise application framework "- Martin Fowler in technology transfer and operation of data in the O / R Mapping attributes normally used in the mapping field, they claimed that the pre-bonding technique can be compiled during inspection out on the field after the error detection and value types, and may be in the development environment IDE to provide more convenient and coding features (such as the list of members), but it will add to the development of tasks and difficulties, it may be necessary to many such mapping to mapping and operation of a table in the database, and I prefer to use a common data storage class to extract and store the various tables in the database, all this only through unified XML (such as the DataSet ADO.net) packaging for sheet data (including the linkages between these tables, constraints, etc.), this simplifies data storage and mapping and provide sufficient flexibility.
What kind of choice is the data model, which is not easy on this issue "enterprise application framework", a book on a dedicated (Chapter II). "Table module" more gentle on the workload and the complexity of the balance between, in view of "the application of 'Table Module' to a large extent depends on the environment on the structure of GM record set support. If development environment has a significant number of records set tools (such as. NET or Visual Studio), 'Table Module' it is very attractive. "[See" enterprise application framework "P22] and past experience, I said at the beginning when contact JDBC always entangled in the" Table Module "and the confusion among other models, because I really can not understand why no off-the-shelf J2EE on the" Table module "standard. In the Jishitian doubts, I have seen the "form-oriented programming strength (on Butler)," a text, and finally exclaimed: Java camp on the original "Table Module" mode is also very interesting! I believe this will promote the development of Java applications have a very positive role.
4, Web Services / SOAP
Microsoft is the XML and Web Services to advocate and to promote. Some people think that Microsoft's Web Services respected even suppress their own Remoting technology development, but the industry on the future of Web Services and support are unprecedented unity and strength. Based on the XML standard SOAP protocol so that we have a more clear on the prospects of reunification, this is an exciting and encouraging. On the support of the Web Service. NET has indisputable advantages, both for Web Services development efficiency and scalability aspects of the case, Microsoft released a WSE (Web Service Enhancement) 2.0 development kit after more elevated. NET In this regard advantage.
In the enterprise applications for long-distance data transmission and object caching is the basis of all, if the data object is an XML-based standard is very valuable, but unfortunately, this is full of competing interests in the business community, whether ADO.net the DataSet or Java in the JDO, Hibernate in the current exchange can handle, despite the possibility of using XSLT to convert, but to build a more unified communication standard has always been our good wishes.
5, user interface and reporting user interface technology always seems to be the strengths of Microsoft, Java camp appears to be mainly respected client is a Web browser technology, and. NET is now more popular and respected the fat client SmartClient technology, the two technologies You are missing, but the relative complexity of enterprise applications, I tend to use more fat client interface technology. In fact, the GUI interface in Java is getting better and better, for example, OpenOffice is such a good project that, and. NET in ASP.net is very innovative, especially ASP.net 2.0 is even more full of hope on these. NET technology in the development of Microsoft's speed and strength are respected, and the open-source Java community and also give them the strength achieved remarkable progress and results.
In the user interface technology, there is a very cool feature is the "bonding" technology. . NET you can easily target any one of the attributes of a GUI components bind to a certain attributes, and you can also bind themselves to the process of conversion and processing performance without worrying about multi - tied together the data synchronization display tedious details, because you only need Supervisor reconnaissance data sources can be good. In the use of "Table Module" data mode of operation, the bundled technology will greatly reduce the complexity of dealing with the interface, what is even more surprising is that I no longer believe that the data from operational interface development is a depressed Rongfan affairs.
In J2EE does not seem to have statements standards. In statements printing Crystal Report seems to have been the first choice of these two platforms, but did Crystal Report development of the Crystal Report friends will definitely be the product defects and Chinese support often complained, and Microsoft has also reached and product bundling Crystal Report But in fact, Microsoft has not abandoned its own separate statements, the development of the engine / service efforts, but he has been in this regard has been made very good results, has been to a Microsoft Reporting Service, we use most of the time, is to develop production of Crystal Report statements. Reporting Service I am really encouraged by the fact that its RDL (Report Definition Language), hope that one day, we pass the standardization of XML-based standard definition language statements to the exchange and system performance data statements!
6, other Microsoft always will be the design and realization of一手包办and made products, these products are rarely open-technology standards, and as far as possible, these products and technologies will be limited to the Windows platform, which hinders the realization of other accession but Microsoft has consolidated control of the technology platform, and this is perhaps Microsoft is a strategic decision to stop. Like. NET slogan "a platform, multi-lingual", the Windows operating system has always been the core of their relative Java "language, multiple platforms", This is obviously completely different strategic thinking . Some say that Microsoft is now pushing the smart-client (SmartClient) technology is the hope to promote the rich client to achieve better use of the Windows operating system dependent, but I do not fully agree with you.
Talking about. NET, I always could not help but pay attention to this exciting under the Mono open source projects. I am more and more anxious to different platforms in the running of our business applications, and this is increasingly common, and strong demand (particularly in the Government sector clients, in more and more strict copyright control in China, it will also have corporate clients demand more some platform of choice to reduce system costs), although I can choose the J2EE platform to develop business applications to achieve the purpose of cross-platform, but I am. NET infatuated with love and made me difficult to abandon it, like Miguel (Miguel de Icaza is Gnome, Ximian Mono and one of the founders) said that "When Microsoft introduced. NET, we it was love at first sight, started the Mono" and that the sentiment is undoubtedly contradictions and painful, and the emergence of Mono released to us is very exciting! At present, we intend to use the first Mono our enterprise application and data access layer WebService successful migration to Linux, and will support Oracle, PostgreSQL these two databases, with the development of Mono, when the WinForms completion of the basic support , then even better! ! ! All this is how people look forward to uh ~
Finally, I hope that this paper will try to avoid too much involved in the design of these two development platforms details of the difference (in fact, I also do this. Oo ^ ^), but also do not want to see the supporters of the two camps have this Some radical antagonism.
0 Comments to “I J2EE and. NET understand that humble”
No Comments. Send your comment.
Leave a Reply
You must be logged in to post a comment.