What will be the best practice with-in seam framework, will L2 cache, Named query help..

Scenario :
We are sending Ajax request (using suggestionBox) to fetch itemNames when user enters text.
We have list of approximately 5000 item names, corresponding entity is Item.

What will be the best practice option to get list of itemNames on the basis of text entered in suggestion box by user (we want to query result only for the text entered)

a) Define framework:entity-query in components.xml, call this to fetch itemNames when user enters text.

b) Use built-in ejbql in corresponding itemList.java (default generated by seam)
@Override
public String getEjbql() {
return “select item from Item item”;
}

c) Create separate query using enityManager in some bean class, add where clause passing the text entered by user.
public List getItemsList(String itemName) {
List itemLst = entityManager.createQuery(“select item from Item item…. where
item.itemName=”).getResultList();
return itemLst;
}

Is it still worth the effort to design and implement a 2nd level cache for my read-only/read-mostly entities? We have a 2 node horizontal JBoss AS cluster in prod with state replication turned off. thx.

The @NamedQuery can then be retrieved through the createNamedQuery() method in the EntityManager API.

entityManager.createNamedQuery will return Query object from JPA which doesn’t not support setCacheable(true). Since this is a hibernate feature, I believe cacheable queries are possible with hibernate session, correct me if I am wrong.

Is there an ehcache.xml that I need to configure first?

Yes, you should configure an ehcache.xml. For Ehcache, this specifies the cache eviction policies I mentioned in the posting.

Is there an ehcache.xml that I need to configure first?

Thanks in advance,
Dennis