This section describes features that were supported in earlier versions of EAServer but are not supported in version 6.0.
ActiveX ActiveX components are no longer supported. ActiveX CORBA clients running with EAServer 5.x can access EAServer 6.0. Use EAServer 5.x to generate .tlb and .reg files to use with your ActiveX-enabled IDE.
.NET clients will be supported in a future EAServer version.
Component creation support Unlike EAServer Manager in earlier versions of EAServer, the Management Console does not support manual creation of standard J2EE components such as EJBs or Web applications. Instead, use industry standard development tools such as PowerBuilder, NetBeans, IntelliJ, Eclipse, and JBuilder to package these components in J2EE archives, then deploy them to EAServer with the Management Console, the command-line tools, or Ant.
CORBA clients The initial context factory implementation class com.sybase.jaguar.jndi.CosNaming.JaguarInitialContextFactory is no longer supported.
J2EE module property sheets Property sheets for J2EE modules are no longer supported. You can use the tools described for component creation support to edit J2EE deployment descriptors.
Management API The com.sybase.jaguar.management.* API package is no longer supported.
MASP The EAServer Methods As Stored Procedures (MASP) interface is not supported in EAServer 6.0.
MASP will be supported in a future EAServer version.
OCI 7 and 8 EAServer 6.0 does not support OCI 7 or OCI 8 native connection caches.
OTS and DTC transaction models The transaction manager no longer supports either the OTS or DTC transaction models.
Static page caching In earlier versions of EAServer, static page caching was used to improve JNI access from a C-language Web server to servlets and JSPs. All EAServer 6.0 code is Java-based, so you need no longer optimize JNI calls.
