How to package an application into a ear file

This is for those who want to know the ideal and most common way an application is packaged in the form of an ear file. Here's how the application structure will look like:

myApp.ear
 |
 |--------- META-INF
 |            |
 |            |---------- application.xml
 |
 |--------- myEJB.jar
 |            |
 |            |--------- META-INF
 |            |            |
 |            |            |-------- ejb-jar.xml  
 |            |
 |            |------ org
 |            |         |----- myApp
 |            |                 |------- ejb
 |                                        |-------- *.class
 |
 |---------- myWeb.war
 |              |
 |              |----- WEB-INF
 |                      |------ web.xml
 |                      |
 |                      |------ jsp
 |                               |---- *.jsp
 |
 |---------- commonUtil.jar
               |
               |--------- org
                           |----- myApp
                                    |------ common
                                             |----- *.class

The application.xml present in the META-INF folder of the ear will contain the following:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application>
 <display-name>helloworld</display-name>
 
 <module>
  <java>commonUtil.jar</java>
 </module>
 
 <module>
  <web>
   <web-uri>myWeb.war</web-uri>
   <context-root>/myWeb</context-root>
  </web>
 </module>
 
 <module>
  <ejb>myEJB.jar</ejb>
 </module>
 
</application>

inverse attribute in Hibernate - What does it mean?

This is the best explanation, that i have seen till date, about Hibernate's "inverse" attribute:
Meaning of "inverse" in Hibernate

Evict collection from Hibernate second level cache

Hibernate allows persistent objects to be cached in its second level cache(The first level cache in Hibernate is the Session object which is ON by default). Applications can switch on the second level cache. When a object is being retrieved by the application through Hibernate, Hibernate first checks in its Session cache and then the Second level cache to see if the object has be retrieved already. If it finds it either the Session cache or the Second level cache, it will NOT fire a query to the database.
While configuring second level cache, the object can be cached and also the collections contained in the object can be cached. Have a look at the following example:

<hibernate-mapping default-lazy="false" > 
 <class name="org.myapp.ho.Parent" table="Parent"> 
    <b><cache usage="read-only" /> </b>
    <id name="id" type="Integer" column="ID" /> 
  <set name="myChildren"> 
     <b> <cache usage="read-only"/> </b>
     <one-to-many class="org.myapp.ho.Child"/> 
  </set> 
 </class> 
</hibernate-mapping>

<hibernate-mapping default-lazy="false" > 
   <class name="org.myapp.ho.Child" table="Child">
      <b><cache usage="read-only" /></b>
      <id name="id" type="Integer" column="ID" /> 
   </class> 
</hibernate-mapping>

Note that we have used the cache setting at 3 places:
1) The org.myapp.ho.Parent object
2) The "myChildren" collection in the org.myapp.ho.Parent object
3) The org.myapp.ho.Child object
When you configure a collection to be second level cached in Hibernate, it internally maintains a SEPERATE cache for these collection than the one which it uses to cache the parent objects. So in the example above, the “myChildren” will be cached separately than the org.myapp.ho.Parent object.
There might be cases where applications would want to evict objects from the cache. If its the Session cache from which the application has to evict the object then the call to Session.evict will cascade even to collections and will evict the collection from the *Session cache*. However, if the object(and the collections contained in it) have to be evicted from the second level cache, then the application has to *explicitly* call the evictCollection method on the SessionFactory to remove the *collection* contained in the Parent object. The reason behind this is, as already mentioned, the collections are cached separately, than the parent objects, in the second level cache.
So, in our example above, if we have to evict the Parent with id 500 and its collection from the second level cache, then here’s what has to be done:

SessionFactory sf = MyUtil.getSessionFactory();
//this will evict the Parent Object from the second level cache
sf.evict(org.myapp.ho.Parent.class,new Integer(500)); 
//this will evict the collection from the second level cache for the Parent with id=500
sf.evictCollection(org.myapp.ho.Parent.class.getName() +  ".myChildren", new Integer(500)); 

The first parameter to the evictCollection method is the ‘roleName’ of the collection. The roleName is formed as follows:

roleName = NameOfTheParentClass + "." + NameOfTheCollectionInsideTheParent

The second parameter the evictCollection method is the id of the parent object, to which this collection belongs.