with so many exciting changes in this release, you may be wondering where you should start. as in previous releases, the comprehensive list of all changes is available in the release notes guide. this article, from the j2se team, will take you through the major changes so that you have a grasp of what j2se 1.5 has to offer, before diving into the api docs. 【程序编程相关:在ASP.NET FORUMS中一种存储】
java 2 platform, standard edition (j2se) version 1.5 ("tiger") is the next major revision to the java platform and language; it is currently slated to contain 15 component jsrs with nearly 100 other significant updates developed through the java community process (jcp). 【推荐阅读:优化代码,看看哪个执行速度更快!!!】
ease of development scalability and performance monitoring and manageability desktop client【扩展信息:劝创业者——别拿自己当回事 】
the j2se 1.5 release is focused along certain key themes:
there are a small number of features that are just as important but didn´t neatly fit in with the themes; they are listed at the end:
miscellaneous featuresease of development
you may have already seen reports about some of the new java language changes that comprise the ease of development theme. the changes include generic types, metadata, autoboxing, an enhanced for loop, enumerated types, static import, c style formatted input/output, variable arguments, concurrency utilities, and simpler rmi interface generation.
jsr-201 contains four of these language changes; enhanced for loop, enumerated types, static import and autoboxing; jsr-175 specifies the new metadata functionality, while jsr-14 details generic types.
the new default language specification implemented by the javac compiler is version 1.5, you do not need to supply the option -source 1.5 as required in beta1.
metadata
the metadata feature in j2se 1.5 provides the ability to associate additional data alongside java classes, interfaces, methods, and fields. this additional data, or annotation, can be read by the javac compiler or other tools, and depending on configuration can also be stored in the class file and can be discovered at runtime using the java reflection api.
one of the primary reasons for adding metadata to the java platform is to enable development and runtime tools to have a common infrastructure and so reduce the effort required for programming and deployment. a tool could use the metadata information to generate additional source code, or to provide additional information when debugging.
... 下一页