This document provides a snapshot of the supported specifications and the latest features that have been added to Pramati Server in this release, along with all the enhancements and modifications made to the product.
| Version | Release Notes | Platform Certification |
|---|
| Server 6.0 SP1 | Release Notes | Platform Certification |
| Server 6.0 GA Release | You are here! | Platform Certification |
This section provides a snapshot of the specifications supported by Pramati Server in this release.
| Specification | Version |
|---|---|
| Enterprise JavaBeans (EJB) | 3.0 |
| Servlet | 2.5 |
| JavaServer Pages (JSP) | 2.1 |
| JavaServer Faces (JSF) | 1.2 |
| JavaServer Pages Standard Tag Library (JSTL) | 1.2 |
| Java Database Connectivity (JDBC) | 3.0 |
| Java Transaction API (JTA) | 1.1 |
| Java EE Connector API | 1.5 |
| Java Mail | 1.4 |
| Java EE Management | 1.1 |
| Java Management Extensions (JMX) | 1.2 |
| Java EE Deployment | 1.2 |
| Java API for XML Processing (JAXP) | 1.3 |
| Java API for XML Binding (JAXB) | 2.0 |
| Streaming API for XML Parsing (StAX) | 1.0 |
| Web Services for Java EE | 1.2 |
| Java API for XML Web Services (JAX-WS) | 2.0 |
| Java API for XML based RPC (JAX-RPC) | 1.1 |
| SOAP with Attachments API for Java (SAAJ) | 1.3 |
| Java API for XML Registries (JAXR) | 1.0 |
| Java Authentication Contract for Containers (JACC) | 1.1 |
| Common Annotations for Java Platform | 1.0 |
| Web Services Metadata for Java Platform | 2.0 |
| WS-Basic Profile | 1.1 |
| WS-Security | 1.0 |
| WS-SecurityPolicy | 1.1 |
| WS-Addressing | 1.0 |
| WS-ReliableMessaging | 1.1 |
| WS-Policy | 1.2 |
Web | [TOP] | ||
Key bug fixes | |||
| Fix For | Description | Server Configuration Impact | Application Configuration Impact |
|---|---|---|---|
Clarified behavior for session attribute in Page directive with conflicting values. |
As per the JSP specification, only one occurrence of any attribute/value pair defined by Page directive is allowed in a given translation unit, unless the values for the duplicate attributes are identical. This validation has been done for session attribute. |
No Impact. |
No Impact. |
The 'q' value specified for locales in Accept-Language header was ignored. |
The 'q' value for locales in Accept-Language was not parsed properly. As a result, the default value '1' was assigned for all the locales. This has been fixed. |
No Impact. |
No Impact. |
Clarified behavior for the taglib directive appearing after its usage. |
It is a fatal translation error for the taglib directive to appear after actions using the prefix introduced by it. This has been fixed to throw a translation error in such cases. |
No Impact. |
No Impact. |
Clarified behavior for the buffer attribute in Page directive. |
The value for the buffer attribute must have suffix kb. The suffix kb is mandatory or a translation error must occur. This has been fixed. |
No Impact. |
No Impact. |
Clarified behavior for the dynamic attribute having the same name as the tag attribute. |
The dynamic attribute cannot have the same name as tag attribute. If it has the same name as tag attribute, a translation error has to be thrown. This has been fixed. |
No Impact. |
No Impact. |
Fix for Single Sign-On (SSO) when session is not yet created. |
During SSO, if a user who was already authenticated in one application makes a request to another application having no session created for that user, the authentication fails. This has been fixed. |
No Impact. |
No Impact. |
Fix for enabling range requests. |
Download accelerators makes multiple range requests to accelerate downloading. Some of the browsers does this only when the 'Accept-Ranges: bytes' header is sent in the response. This has been fixed to send the header when static content is requested. |
No Impact. |
No Impact. |
EJB | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Slow deployment of JARs with huge ejb-jar.xml. |
The XML processing has been optimized to reduce the time taken to deploy archives with huge XMLs. |
No Impact. |
No Impact. |
Clarified transaction Re-entrancy for No lock entity beans. |
CMPs deployed with Isolation level Optimistic Repeatable Read or Read Committed and No Lock BMPs are checked for re-entrancy only when the bean re-enters the same transaction. This has been fixed. |
No Impact. |
No Impact. |
Offline generator to pick up super classes. |
Super classes and super interfaces of the Bean artifacts needed at the EJB client-side were not being included in the client jar created using the Offline generator utility. This has been fixed to include super classes and super interfaces of return types, method arguments, remote interface, and remote home. |
No Impact. |
No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Pessimistic locking support for JPA Entity beans. |
JPA Entity beans can be configured to use pessimistic locks within a transaction. Database Queries fired as a result of EntityManager API methods, NamedQuery invocations and Relationship access would take a pessimistic lock for the configured Entity. |
No Impact. | Property pessimistic-lock-entities needs to be specified under vendor specific properties in persistence.xml with the value as a comma separated list of entities to be locked pessimistically. |
Statistics for JPA entities. |
The status jpa command of server command shell displays the entity-wise statistics. The statistics include Cache Hits, Conflicting transaction Rollbacks and Database Loads, Inserts, Deletes, and Updates. |
No Impact. | No Impact. |
Separate configuration file for EJB Container. |
All the EJB container related configuration have now been moved from server-config.xml to ejb-config.xml. |
A new schema for ejb-config has been added. | No Impact. |
Enhanced BMP concurrency options. |
More options have been added to control locking and loading behaviour for BMP entity beans: no-lock, lock-with-cache-enabled, and lock-and-load-in-transaction. |
A new tag bmp-locking-option has been introduced to take the above options for BMP Entity beans. For backward compatibility reasons, we still support the older configuration through lock-bmp tag and the new configuration through bmp-locking-option tag. The lock-bmp tag takes precedence over bmp-locking-option tag if both are specified. One to one correspondence between older and newer options: true => lock-with-cache-enabled, false => no-lock, pre50 => lock-and-load-in-transaction. | The bmp-locking-option tag has been added to pramati-j2ee-server.xml, with the same semantics as that in ejb-config.xml, but this takes precedence over the values of the same tag in ejb-config.xml. |
Transactions | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Hibernate to use Pramati's Transaction Service for JTA. |
Hibernate relies on the uniqueness of the Transaction object returned from TransactionManager for JTA-based transaction management. Implemented hashCode and equals methods for the Transaction wrapper returned by Pramati's TransactionManager implementation. |
No Impact. |
No Impact. |
Clusters | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
EJB home lookups with com.pramati.naming.cacheLookups property is set to false. |
If the InitialContext is created with com.pramati.naming.cacheLookups property set to false, lookup of an EJB home used to go into an infinite loop in cluster. This has been fixed. |
No Impact. |
No Impact. |
NPE while dynamically adding a node to a cluster. |
When a node is dynamically added to an existing cluster and while this node is coming up, there could be cases where the existing nodes have partial information of the new node and results in an NPE. This is due to improper synchronization of the node sync-up mechanism. This has been fixed. |
No Impact. |
No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Cluster node sync up after network interruption. |
We now support re-establishment of cluster handshake after a cluster node comes back into the network after a temporary network outage. After the node comes again into the network, transparent auto recovery mechanism makes it ready for servicing requests after session sync-up and replication. |
Number of times the network recovery mechanism should attempt to check if the node has again become part of the network can be configured through recovery-attempts-on-network-failure tag in cluster-config.xml. | No Impact. |
Server Administration Console | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Fix for Node Creator with -force option. |
When a node is created with -force option with DB-based cluster persistence, existing tables with the same name as the one that is used in the current config topology were not dropped. This has been fixed. |
No Impact. |
No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Deployment of Admin application on a virtual host. |
Admin Console WAR applications can now be deployed and accessed on any virtual host. Virtual host should have been already configured on the server. |
A new attribute vhost-name has been introduced under the admin-console tag of management-config.xml to configure virtual host of admin console application. | No Impact. |
Configuring Admin login information through Node Creator. |
Server admin user, credentials, and realm can be configured through the topology.xml file during Node Creation. |
A new tag login-info has been introduced to provide admin user login configuration under each node element in the case of standalone nodes and under cluster element for cluster. The currently supported login properties are username, password, realm, and mask. If the password is specified in encrypted format, then the mask property must be specified as true, otherwise password is considered to be non-encrypted by default. |
No Impact. |
Logging | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Redirecting server startup messages to stdOut log file with -redirect option. |
When the server was started with -redirect option, server startup messages were not redirected to the log files, instead, they showed up on the console. This has been fixed. |
No Impact. |
No Impact. |
New Features and Enhancements | |||
| Feature | Description | Server Configuration Impact | Application Configuration Impact |
Java Logger configuration file for each application. |
Each application deployed within the Server VM can have its own Java logging configuration file for specifying Log Level and Log Handlers when using Java logging API. |
No Impact. | No Impact. |
Deploy | [TOP] | ||
Key Bug Fixes | |||
| Fix for | Description | Server Configuration Impact | Application Configuration Impact |
Conflicts due to DOM and SAX parsers bundled with the application. |
If the SAX/DOM parsers shipped with the JDK/Server were not same as those bundled with the application, it sometimes resulted in errors. The parsers are now isolated such that the server and the application use their respective XML parsers. |
No Impact. |
No Impact. |