I agree that things get a bit confusing with the renaming of Java EE to Jakarta EE. If this wasn't the case I wouldn't like any renaming at all. As far as I can tell the current separation of "Java Web" and "Java EE" hasn't caused any confusion among NetBeans users.
I'm not sure I like the words "Legacy" or "Vintage", as some may interpret these as having negative connotations. There are still many projects out there that use EAR files and EJBs. EJBs in particular suffer from the bad rep EJB 2 had, where EJB 3 is a whole different beast, very easy and simple to use. Moving EJBs to a "Legacy" or "Vintage" category may reinforce the bad reputation from EJB 2. Additionally, I still see a fair amount of projects using EAR Files (mostly maintenance of existing code). I like Ondro's idea of using "Java Enterprise", which would cover both Java EE and Jakarta EE. On Wed, Jan 30, 2019 at 4:08 AM Ondro Mihályi <ondrej.miha...@gmail.com> wrote: > Hi, > > I agree with Eric. EJB and EAR is still part of Java EE, will be part of > Jakarta EE and there are no plans to deprecate it. I heard some ideas to > create a new "modern" profile in Jakarta EE but it's only ideas and we're > far away from that happening. Therefore all this should be supported by > Netbeans at least via a plugin if we already have that functionality. I > know that a lot of companies still maintain their older applications that > use EJB and EAR and they're not going to remove it even when using Docker > or other modern technology. > > I propose (reasoning below): > > - leave "Jave Web" category as is > - rename "Java EE" category to "Java Enterprise" category (which to many > would sound like "legacy" anyway) > > Reasoning: > > I thought that the "Java Web" category is for web apps in general, for WAR > projects, which can be also deployed to servlet containers like Tomcat. > Although the project creation dialog refers to Java EE in one select box, > it allows choosing Tomcat and only adds dependencies present in Tomcat. In > addition, if there was a plugin for generating Ant-based Spring Boot apps, > it could also be in this category, as it would be a Java Web project, > although a separate SpringBoot type packaged as JAR. > > On the other hand, the "Java EE" category is for legacy enterprise > constructs in Java EE, like EARs, EJBs and EJB clients. Here the name "Java > EE" for the category is wrong, because Java EE is no longer used only in > enterprise and with EARs. I would rename this category to "Enterprise > Java".This could be extracted into a separate plugin and only installed if > needed. Later if these constructs are deprecated in Jakarta EE we could > just make the plugin deprecated too. > > A bonus is we wouldn't need to rename anything to Jakarta EE later. > > - Ondro > > > > > > st 30. 1. 2019 o 5:19 Eric Bresie <ebre...@gmail.com> napísal(a): > > > I’m a little bit of an outsider looking in but give the older > technologies > > are still Java EE why confuse things with Vintage and Legacy and just > leave > > them there with the new Jakarta EE category when available. > > > > Then just make sure to have a Version attribute to configure the setup of > > the project? > > > > I thought recent Java EE has different profiles ( Web Profiles, Full > > Profiles,etc.). Would linking with these profiles work better? Or is the > > Java Web not necessarily related to Java EE Web Profiles? Is the Java Web > > more of a micro service? > > > > Would having an Enterprise category work better maybe and allowing > > different flavors under that? > > > > Eric Bresie > > ebre...@gmail.com > > > On January 28, 2019 at 11:50:02 PM CST, Josh Juneau < > juneau...@gmail.com> > > wrote: > > > I certainly agree that we need to keep this functionality within the > > IDE. Regarding naming and/or breaking it out into an extension: I would > be > > in favor of keeping this functionality under a "Vintage Java EE" > category. > > That is what it is, correct? I think we will need a "Jakarta EE" category > > in the near future, and this new category will not contain older > > functionality. I would prefer going straight to "Jakarta EE" as a > category, > > rather than use "Modern Java EE". Jakarta EE 8 is due out soon and it > will > > be in alignment with Java EE 8. > > > > > > Older (deprecated) functionality should go into the "Vintage Java EE" > > category. As Ken had mentioned, these technologies have not been > > deprecated, but these older EAR wizards would certainly be vintage in my > > opinion. If the day comes where most of the necessary EJB functionality > is > > moved into other APIs, then maybe it can be broken off as an add-on > > extension...but not until then. > > > > > > Hope this makes sense. Thanks for all of the work that has gone into > > moving the IDE forward. > > > > > > Josh Juneau > > > juneau...@gmail.com > > > http://jj-blogger.blogspot.com > > > https://www.apress.com/index.php/author/author/view/id/1866 > > > > > > > On Jan 28, 2019, at 3:41 PM, Brett Ryan <brett.r...@gmail.com> > wrote: > > > > > > > > Geertjan’s article is not about removing EE support it’s what to do > > about the old Java EE which is deprecated in favour of Jakarta EE in the > > future being the modern EE variant. > > > > > > > > For those that do not know, yes; Java EE 8 is the last version of > Java > > EE, Jakarta EE while not being a replacement it is the new way forward > for > > enterprise web applications. Removing legacy support in favour of new > > technologies is certainly not suicide it is moving with the times. > > > > > > > > Spring support has always been brilliant in NetBeans with bean > > navigation suppirt and now a lot of bootstrap support, but that’s the > > modern current focus. > > > > > > > > > On 29 Jan 2019, at 08:33, Tomas Poledny <salja...@gmail.com> > wrote: > > > > > > > > > > NetBeans had the best support of JEE from all IDE. Support for > > Spring is > > > > > very poor. I think remove of support part of JEE is suicide for > > NetBeans. > > > > > This is main reason why I am using NetBeans. > > > > > Tomas > > > > > > > > > > > On Mon, Jan 28, 2019, 22:24 Brett Ryan <brett.r...@gmail.com > > wrote: > > > > > > > > > > > > It’s always a sensitive topic whenever considering to remove > > something, > > > > > > however; I am in favour for removing classic JavaEE support in > > favour of > > > > > > concentrating on modern java web technologies such as spring and > > Jakarta. > > > > > > > > > > > > It becomes an enormous task to support everything. We can always > > provide > > > > > > support in the form of a plugin though I feel that those using > > classic Java > > > > > > EE may not benefit from the additions being added to NetBeans IDE > > and may > > > > > > continue to use 8.2. > > > > > > > > > > > > > > On 29 Jan 2019, at 06:05, Geertjan Wielenga > > > > > > > <geertjan.wiele...@googlemail.com.invalid> wrote: > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > Especially to Java/Jakarta EE people out there, e.g., Ivar, > > Josh, David, > > > > > > at > > > > > > > least -- please advise what should be done with the EAR and EJB > > support, > > > > > > as > > > > > > > described here: > > > > > > > > > https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache > > > > > > > > > > > > > > And, hurray, thanks Matthias especially, and Vikas, Arunava, > > Sarvesh, and > > > > > > > Reema, for a lot of work on relicensing, for getting the > > enterprise > > > > > > cluster > > > > > > > integrated! > > > > > > > > > > > > > > Gj > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: > > dev-unsubscr...@netbeans.incubator.apache.org > > > > > > For additional commands, e-mail: > > dev-h...@netbeans.incubator.apache.org > > > > > > > > > > > > For further information about the NetBeans mailing lists, visit: > > > > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > dev-unsubscr...@netbeans.incubator.apache.org > > > > For additional commands, e-mail: > > dev-h...@netbeans.incubator.apache.org > > > > > > > > For further information about the NetBeans mailing lists, visit: > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > > > > > -- http://ensode.net - A Guide to Java, Linux and Other Technology Topics My Books: https://www.packtpub.com/books/info/authors/david-r-heffelfinger <http://www.packtpub.com/authors/profiles/david-heffelfinger> My Video Training: http://www.packtpub.com/java-ee-development-with-netbeans-7/video Follow me on Twitter: https://twitter.com/ensode
