Yes, it is. But it's up to you to configure them to work properly. At least for JSF, JPA and CDI, you just drop the relevant jars in WEB-INF/lib and they will work.
– Luiggi MendozaJun 13 '15 at 17:12
Better think of TomEE instead (Tomcat's successor). Why do you want to avoid EJBs, by the way? EJBs not only provide transaction management but many more features like security, pooling, concurrency management...
– TinyJun 13 '15 at 17:46
Thank you @Tiny for your help. I just want to avoid using a heavyweight app server and instead use declarative and programmatic transactions and security. which I think is possible with tomcat. Also spring framework provides the same services without the need for an app server. I am wrong?
– Mohammed BounagaJun 13 '15 at 18:31
App servers are no longer heavy-weight. Take a look at WildFly or GlassFish and you're ready to go. Even when you go the hard way and add lots of libs to Tomcat, you'd be still missing the container glue code.
– Harald WellmannJun 13 '15 at 18:34