If one of your goals is Spring Boot, a question you should make to yourself is that do you really want to deploy to jboss anymore. Spring Boot supports way better the jar packaging than war packaging and jBoss don’t really provide anything extra if you are moving to Spring Boot stack. You will for example be using Hibernate via Spring Boot dependency instead of using it via jBoss.
Thank you again. I’ve been through quite a loop of trying things and running into stack traces, including previous attempts involving the addition of the configure() method as shown in the page you’ve linked here, and the addition of a “Tomcat exclusion” entry and a “Tomcat dependency” entry. Since you’re recommending it here, I’ll try it again today just to confirm. Per your recommendation above, I’m also trying CDI and getting CRUD weirdness, which I think has to do with the annotation and scope requirements being different somehow, but I have another thread for that. To answer your “why JBoss?” question, we’re a smaller tool, piggybacking on the runtime environment of a larger system, so for now, it’s Java 8 and JBoss 7.1.
To me it sounds like you should NOT be using Spring Boot at all. That is a gret platform and easy to get starterd, but for you I think it offers nothing. Via jBoss you get CDI to replace Spring DI, Hibernate via Java EE APIs and so on.