The following table describes the items changed with the purpose of improving the development productivity.

Table F-21 Changes made with the purpose of improving the development productivity

Item	Overview of changes	Reference manual	Reference location
Easy migration from other application server products	The use of the following functionality was enabled for smooth migration from other Application Server products: The upper limit of the HTTP sessions can now be determined using exceptions. If the JavaBeans ID is repeated and if the upper case/ lower case in the custom tag attribute name and TLD definition are different, the occurrence of translation errors can now be controlled.	Web Container Functionality Guide	2.3, 2.7.5
Provision of cosminexus.xml	By specifying attributes unique to Cosminexus Application Server in cosminexus.xml, the J2EE applications can now be started after being imported into the J2EE server without specifying the property settings.	This manual	11.3

The following table describes the items changed with the purpose of supporting the standard functionality.

Table F-22 Changes made with the purpose of supporting the standard functionality

Item	Overview of changes	Reference manual	Reference location
Supporting Servlet 2.5	Servlet 2.5 is now supported.	Web Container Functionality Guide	2.2, 2.5.4, 2.6, Chapter 6
Supporting JSP 2.1	JSP 2.1 is now supported.	Web Container Functionality Guide	2.3.1, 2.3.3, 2.5, 2.6, Chapter 6
JSP debug	JSP debug can now be performed in the development environment in which MyEclipse is used. #	Web Container Functionality Guide	2.4
Storing the tag library in the library JAR and TLD mapping	When the tag library is stored in the library JAR, the TLD file in the library JAR is searched by the Web Container when the Web application starts and is automatically mapped.	Web Container Functionality Guide	2.3.4
Omitting application.xml	application.xml can now be omitted in the J2EE application.	This manual	11.4
Combined use of annotations and DD	The annotations and DD can now be used together and the contents specified in an annotation can be updated with the DD.	This manual	12.5
Conforming annotation to Java EE 5 standards (default interceptor)	The default interceptor can now be stored in the library JAR. Also, DI can now be executed from the default interceptor.	This manual	11.4
Resolving the @Resource references	The resource references can now be resolved with @Resource.	This manual	12.4
Supporting JPA	The JPA specifications are now supported.	This manual	Chapter 5, Chapter 6

# In version 09-00 and later, you can use the JSP debug functionality in the development environment using WTP.

The following table describes the items changed with the purpose of maintaining and improving reliability.

Table F-23 Changes made for maintaining and improving reliability

Item	Overview of changes	Reference manual	Reference location
Persistence of session information	The session information of the HTTP session can now be saved in the database and then and inherited.	Expansion Guide	Chapter 5, Chapter 6
Controlling the full garbage collection	By deploying the object that causes full garbage collection outside the Java heap, the occurrence of full garbage collection can now be controlled.	Expansion Guide	Chapter 8
Client performance monitor	The time required for client processing can now be checked and analyzed.	--	--

Legend:

--: This functionality has been deleted in 09-00.

The following table describes the items that are changed with the purpose of maintaining and improving operability.

Table F-24 Changes with the purpose of maintaining and improving operability

Item	Overview of changes	Reference manual	Reference location
Improving the operability of applications on the management portal	The server management commands and management portal can now be interoperated for application and resource operations.	Management Portal User Guide	1.1.3

The following table describes the items that are changed for other purposes.

Table F-25 Changes due to other purposes

Item	Overview of changes	Reference manual	Reference location
Deleting the disabled HTTP Cookies	The disabled HTTP Cookies can now be deleted.	Web Container Functionality Guide	2.7.4
Detecting errors in the Naming Service	When an error occurs in a Naming Service, the EJB client can now detect the error faster.	This manual	2.9
Connection error detection timeout	A timeout value can now be specified for connection error detection timeout.	This manual	3.15.1
Supporting Oracle11g	Oracle11g can now be used as the database.	This manual	Chapter 3
Scheduling of batch processing	The execution of batch applications can now be scheduled using the CTM.	Expansion Guide	Chapter 4
Batch processing log	The retry frequency and retry interval can now be specified for the error in log file size, number of log files, and log exclusion processing of the batch execution commands.	Definition Reference Guide	3.6
snapshot log	The collected contents of the snapshot log are changed.	Maintenance and Migration Guide	Appendix A.1, Appendix A.2
Publication of the protected area of method cancellation	The contents of protected area list that is outside the scope of method cancellation are published.	Operation, Monitoring, and Linkage Guide	Appendix C
Pre-statistical garbage collection select functionality	You can now select whether to execute garbage collection before the class-wise statistical information is output.	Maintenance and Migration Guide	9.7
Functionality to output the age distribution information of the Survivor area	The age distribution information of the Java objects in the Survivor area can now be output to the JavaVM log file.	Maintenance and Migration Guide	9.11
Finalize retention cancellation functionality	The JavaVM finalize processing status can now be monitored and the retention of processing can be cancelled.	--	--
Changing the maximum heap size of the server management commands	The maximum heap size used by the server management commands was changed.	Definition Reference Guide	5.2, 5.3
Action for cases when un-recommended display names are specified	A message is now displayed when an un-recommended display name is specified in the J2EE applications.	Messages	KDJE42374-W

Legend:

--: This functionality has been deleted in 09-00.