At the end of 2003, the Beta version of J2SE1.5 will be released. The two updates of J2SE1.4, which have been released and now released 1.4.1 and 1.4.2 are all expected by the 2003 Javaone conference. If you don't participate in this conference, or if you want to recall, then the following is the brief content of this conference. J2SE 1.4.1 and 1.4.2 Releases When 1.4.1 (Development Code "Hopper") released in September 2002 and its follow-up version 1.4.2 (development code "Mantis") is released as scheduled in January 2003 More than 4,000 bugs have been repaired, and in the continued fixes. In J2SE1.5's new features, some people will add a long-awaited feature, such as full support for the iTenium CPU; Swing users will see two new built-in Look & Feels, one is Windows XP style, one GTK style; also has improved in start-up time. The enhancement of the server mainly includes two new GCs, a parallel marker cleaning algorithm and a similar young space collection (Parallel Young Space Collector). These two new GCs can be called by compilation: -xx: useconcmarksweepgc and -xx: useparallelgc. Next, how to use these parameters to adjust the best performance of the system is that we need to learn and understand in J2SE 1.5. J2SE 1.5 ReleaseJ2se 1.5 (Development Code "Tiger") is an important modification on the Java platform and language, mainly including 15 JSR requests and other similar updates. This Release mainly focuses on several key subject: mainly quality, monitoring and management, performance and scalability, easy development and desktop client. Ease of Development You may have heard the modifications on the Java language that mitigates the development difficulty. This J2SE implements the following JSR: JSR 201 contains four modifications based on JSR requirements; the core of JSR 175 is support metadata, while JSR 14 specifies generics. The metadata function provides a declarative development and replaces the code generation and maintenance of some tools. The generic upgrade has been reused without the need to manually transform (Manual Casting), usually some of the issues on type security. The other four modifications are:
Use the for loop to traverse the container (Collection Type) without the need for an explicit declared iterator; an enumeration type provides a type security that transcends similar to Final Static Int; when used in generics Autoboxing feature (the original type is not used in the original generic type); the Static Constants class is introduced to improve the explicit shared a static data;
