Glad it's working. :) As for the query cache, if you set it to true on the client side, then you are going to have to set up JBoss Cache as the second level cache on the client side.
I was briefly thinking maybe you could get away with using some other cache provider (ehcache, etc.) on the client side for your query caching, but the problem is if the client side case isn't a cluster-aware one that knows how to communicate with the server side cache you could get this: 1) Do a query on the client side that returns beans A, B, C. Cache the result. 2) Do something on the server side that changes B such that it would no longer match the query. 3) Do the query again on the client side. Client side query caching layer doesn't know about the change to B, so the out-of-date cached result of A, B, C is returned. Invalid. Same problem applies in reverse as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048686#4048686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048686 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
