As long as Tomcat doesn't release the integration as part of their core build we can stop the whole discussion!
-1 on dropping webbeans-tomcat7 Once there is a good alternative in the main build in tomcat we can discuss this again. LieGrue, strub > Am 01.07.2020 um 12:01 schrieb Romain Manni-Bucau <rmannibu...@gmail.com>: > > Le mer. 1 juil. 2020 à 11:52, Gurkan Erdogdu <cgurkanerdo...@gmail.com> a > écrit : > >> CDI is the core spec for all other Jakarta EE specifications. I really dont >> know why Tomcat does not include it naturally. I think the home >> for such natural integration will be Tomcat. But, not under the modules, >> but integrated into the Tomcat core and release monthyl with Tomcat release >> > > Nop, EE always built each spec independently of the IoC - which is wrong I > agree but it is what has been done and why you have at least 5 concurrent > IoC in EE. > If we follow your reasoning, tomcat should also include EJB, JAXRS, > javax.security etc, not sure it would be sane and you just move the issue > which is that once you trivially integrated servlet+cdi you must integrate > servlet+cdi+security, then +jaxrs etc (Pareto law applies well there). > So at the end, CDI is based on servlet spec - since it is spec-ed like that > cause servlet spec rejected CDI integration at that time - then CDI is > built on top on tomcat and not the opposite and in terms of build > dependency, OWB consumes servlet spec, not the opposite so strictly > speaking it is more logical to keep it in OWB. > Lastly you still ignore that we integrate with jetty too and if we keep > jetty we must keep tomcat for consistency of our deliveries and user facing > artifacts so IMHO there is no need to only do half of the discussion which > can only lead to half a decision which means it would not be applicable at > the end IMHO. > > >> >> Remy, >> Is it possible to open a discussion in tomcat dev list to discuss more on >> this topic? >> >> Gurkan >> >> On 1 Jul 2020 Wed at 12:45 Romain Manni-Bucau <rmannibu...@gmail.com> >> wrote: >> >>> Hmm, sounds close to what we deliver ( >>> http://openwebbeans.apache.org/owbsetup_tomcat.html ). >>> I agree we Gurkan we should be able to converge but today I don't see why >>> Tomcat is a saner home, factually it is worse since it is not ready to >> use >>> for end user compared to owb distro and fact it is in tomcat/modules is >> not >>> that encouraging to me (and I assume tomcat will not release it in its >>> monthly release, right?). >>> >>> Romain Manni-Bucau >>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>> <https://rmannibucau.metawerx.net/> | Old Blog >>> <http://rmannibucau.wordpress.com> | Github < >>> https://github.com/rmannibucau> | >>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book >>> < >>> >> https://www.packtpub.com/application-development/java-ee-8-high-performance >>>> >>> >>> >>> Le mer. 1 juil. 2020 à 11:27, Gurkan Erdogdu <cgurkanerdo...@gmail.com> >> a >>> écrit : >>> >>>> Thanks Remy. >>>> Is it possible to merge these 2 efforts to single one under Tomcat >>> coebase? >>>> I dont see any reason to maintain two different implementation with the >>>> same aim >>>> >>>> >>>> >>>> On 1 Jul 2020 Wed at 11:14 Rémy Maucherat <r...@apache.org> wrote: >>>> >>>>> On Tue, Jun 30, 2020 at 10:35 AM Gurkan Erdogdu < >>>> cgurkanerdo...@gmail.com> >>>>> wrote: >>>>> >>>>>> Sorry but not understand why both Tomcat and OWB doing the same >> think >>>>> with >>>>>> nearly same classes >>>>>> >>>>>> @Remy >>>>>> Just wonder why did you introduce such a module in tomcat modules? >> Do >>>> you >>>>>> have any specific purpose? >>>>>> >>>>> >>>>> The idea is to provide a different packaging, with specific easy to >>>> follow >>>>> instructions that allow adding CDI support to the Tomcat container. >>>>> >>>>> Rémy >>>>> >>>> -- >>>> Gurkan Erdogdu >>>> http://gurkanerdogdu.blogspot.com >>>> >>> >> -- >> Gurkan Erdogdu >> http://gurkanerdogdu.blogspot.com >>
