TBH, I don't see why @Cache needs to be in an ext-api jar at all. It's a specification of what impl of an SPI to use, which is probably not the sort of thing we should be encouraging, and definitely isn't something that we need to make totally painless. The only reason a user would need to use this annotation is if they write a custom Cache impl. And if they do that they are going to have to have the full ejb-core jar on their classpath anyway. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102756#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...