JavaExp: Java and Open Source Technology

This document will explain the steps that should be followed to configure the Day Communique 4.2 dev. Environment with Weblogic as the app server Instead of the default Servlet engine provided by Communique. For this paper, I have used the sample application and its domain for porting the Day Communique. Weblogic domain is a logically related group of WebLogic Server resources. Domains include a special WebLogic Server instance called the Administration Server , which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional WebLogic Server instances called Managed Servers . You deploy Web applications, EJBs, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only. Day Communique comes with five war files, they are crxauthor.war,crxpublisher.war,author.war,publish.war and ROOT.war. crxauthor.war: The repository of the

Hibernate Caching Hibernate uses two different caches for objects: first-level cache and second-level cache. First-level cache is associated with the Session object, while second-level cache is associated with the Session Factory object. By default, Hibernate uses first-level cache on a per-transaction basis. Hibernate uses this cache mainly to reduce the number of SQL queries it needs to generate within a given transaction. For example, if an object is modified several times within the same transaction, Hibernate will generate only one SQL UPDATE statement at the end of the transaction, containing all the modifications. To reduce database traffic, second-level cache keeps loaded objects at the Session Factory level between transactions. These objects are available to the whole application, not just to the user running the query. This way, each time a query returns an object that is already loaded in the cache, one or more database transactions potentially are avoided. In addition, y