OK, that's not so bad; cuts it down to a single warning, which could be eliminated
with a @SuppressWarnings inside getCache(). Accessing a field via a getter isn't a
bad practice anyway.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028403#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...