I'm a +1 for Krazo, in fact I think MVC is now part of the spec so its needed. It _might_ have already been done. I'm a little more on the fence for Deltaspike. I really like it, and use it in my own projects. My question would be, what other dependencies does it bring in, and what is the overall impact in terms of the size of the distribution?
We can't ship Hibernate due to its license. > When I teach my students they add Spring to their Tomcat install to gain the automatic Repositories capabilities. I'm curious, is that being added as an application dependency, so directly to Tomcat (in the lib directory, for example)? I wonder if we're seeing a lot of Spring Initializr use, and whether something like that for TomEE may be useful? Jon On Tue, Oct 4, 2022 at 10:05 AM Swell <souheil.sul...@gmail.com> wrote: > Hello everyone, > > firstly thanks for the amazing work on microprofile. > > I would like to share some thoughts on the Plume flavor dedicated to > attract newcomers to TomEE. > > Is there room for us to include Krazo and DeltaSpike out-of-the-box, maybe > not in all flavors, but at least in Plume ? > > When I teach my students they add Spring to their Tomcat install to gain > the automatic Repositories capabilities. > Doing so they do not need the EJB container, nor Krazo and DeltaSpike. > since they gain Spring Controllers and Repositories with equivalent > features. > > When they must add a dependency to their app they prefer to add Spring, > which do not train the future IT pros to start using TomEE. > > Having Krazo, DeltaSpike and Hibernate included in Plume might attract more > devs towards Apache solutions. > > if given permission, i could start a PR with added dependencies. > > thanks for your time. > have a nice week, > Swell > -- >
