Now here is where the problems start. In JBoss 6 it worked fine using the @SecurityDomain annotation on our EJB from org.jboss.ejb3.annotation which since has been removed from JBoss AS7.
That's not right. @org.jboss.ejb3.annotation.SecurityDomain is still available in AS7 and infact that's what should be used. Why do you think it's removed?
Sorry for the later reply, been away on annual leave. Using Eclipse with JBoss tools and the JBoss 7 Runtime the class cannot be resolved, what jar can I expect to see it in?
It's in jboss-ejb3-ext-api-2.0.0-beta-1.jar.
The Maven GAV is org.jboss.ejb3:jboss-ejb3-ext-api:2.0.0-beta-1.
It seems that the JBoss 7.x Runtime that gets added to Eclipse when using JBoss Tools with a Dynamic Web Project doesn't include this jar as part of the runtime. So the import doesn't work during compilation. I made a custom User Library which did include the jar mentioned above and the project then compiles correctly and deploys into JBoss 7.
Seems the JBoss 6.x Runtime class library in eclipse already included it so I didn't have these compilation issues.
Thanks for your help.
It seems that the JBoss 7.x Runtime that gets added to Eclipse when using JBoss Tools with a Dynamic Web Project doesn't include this jar as part of the runtime.