Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Eclipse is still behind the current state ofJava EE 8

I was a commercial customer of Exadel Studio before it was acquired by RedHat. They had one of the best support for Struts, HTML and JSF at that time. Only JDeveloper could have come close feature-wise. Sadly, haven’t seen any significant contribution to it by RedHat/JBoss post the acquisition.

 

From: reza_rahman
Sent: 25 February 2018 22:05
To: EE4J community discussions
Subject: Re: [ee4j-community] Eclipse is still behind the current state ofJava EE 8

 

With things moving to Eclipse, it would definitely be very beneficial for the IDE to start having much better support for Java EE. This is key to the success of EE4J. Hopefully major vendors already recognize this? Needing to install JBoss tools on top of Eclipse just for better Java EE support has always felt cumbersome.

 

Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

 

-------- Original message --------

From: arjan tijms <arjan.tijms@xxxxxxxxx>

Date: 2/25/18 8:58 AM (GMT-05:00)

To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>

Subject: Re: [ee4j-community] Eclipse is still behind the current state of Java EE 8

 

Hi,

 

This is indeed an issue. For JSF 2.3 another issue is that it actually throws an exception when a faces config with version 2.3 is used, despite JSF 2.3 now being almost a year old.

 

I wonder if Red Hat would be open to contribute its JSF (RichFaces) tooling to WTP. This is somewhat ahead of WTP, and JSF/RichFaces is likely not that important to Red Hat anymore (RichFaces was EOL'd a while back).

 

Locally I've been working on the last published version of GlassFish tools a little, adding a small extra feature (the ability to just choose the home directory where GF/Payara is installed, and not having to choose one of the internal folders). I'm now 'fairly' up to date with the code to be able to add some other features I had planned.

 

Of course, there's much more needed, especially indeed bringing everything up to date with Java EE 8, and then EE4J/Jakarta EE.

 

Kind regards,

Arjan Tijms

 

 

 

 

On Sun, Feb 25, 2018 at 11:37 AM, Alexander Salvanos <salvanos@xxxxxx> wrote:

Dear Colleagues,

 

the current version of "Java EE for Developers" (with Eclipse Oxygen) is still far behind the current state of Java EE 8.
This not only concerns the GlassFish tools, but also WTP.

Almost all technologies aren't referred updated.

E.g. When using JSF, still the deprecated "managed bean package" way is offered.

When using project facets, alsmost all the technologies are been offered in older versions.

We need to be vigorously and decidedly updating here, because not only does this endanger the Eclipse IDE,

but also the Java EE 8 standard, since Eclipse is the most widely used IDE for Java EE.

 

Best Regards,

Alex


Alexander Salvanos
Goebenstr.5
D-53113 Bonn
Telefon: +49 (151) 24296962


_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community

 

 


Back to the top