Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Jakarta EE in the future



On Wed, Jul 11, 2018 at 4:00 PM, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

On Wed, Jul 11, 2018 at 12:07 AM Reza Rahman <reza_rahman@xxxxxxxxx> wrote:
Personally speaking, other than JPA, these APIs are mostly feature complete. They perhaps only need some minor maintenance releases.

I do agree they are mostly feature complete, although for JSF we do plan a major new release (3.0), where we deprecate and remove a lot of stuff and streamline the entire model.

 

Not sure, if JSF 3 or above could ever get rid of that hardcoded project stage enum in favor of e.g. something similar to what DeltaSpike does?
Especially for integrating with other standards like the Config JSR or being anywhere near "Cloud Native" these 3 hard-coded stages feel very much outdated and insufficient.

Werner
 
The major work in JPA is more power, flexibility

I agree with this too. JPA is not only the most frequently used spec (according to several surveys and personal experience), it's also the one that needs exactly that work. From the top of my head, things like sub-queries, moving between JPQL and Criteria, first class support for the "paging-filtering-sorting" paradigm, and (IMHO) a streamlining of the Criteria AP.
 
and maybe standardizing something like the DeltaSpike Data module (on the other hand, maybe that too is fine as a third-party CDI add-on). The consensus on EJB is to move away from it in favor of CDI services in various specifications like JMS and Java EE Concurrency.

The work in Jakarta EE is mostly elsewhere such as what is going on in MicroProfile/JNoSQL as well as perhaps JPMS alignment/modularity/Java SE support + further reactive features. Other under-developed areas are more niche like JCA, JavaMail (maybe all this needs is a good CDI extension) and JCache. There is also MVC.

Security also needs some work still. JWT (available in MicroProfile) and OpenID + OAuth2 for instance are must-haves I think. Then there's a couple of gaps that still need to be addressed (multiple authentication mechanisms, and authorization annotations/modules mostly).

Kind regards,
Arjan


 

On 7/10/2018 4:11 AM, George Labuschagne wrote:

Good day

 

Just to get clarity on this conversation.

 

The following tech (in order of importance to myself) will still be available and ‘going strong’ in Jakarte EE / Java EE 11 LTS?

  • JSF (PrimeFaces + OmniFaces)
  • EL
  • CDI
  • JPA (Hibernate)
  • EJB

 

And then Red Hat based EAPs like WildFly 14+

 

Correct?

 

Kind regards,

 

George

 

From: jakarta.ee-community-bounces@eclipse.org <jakarta.ee-community-bounces@eclipse.org> On Behalf Of Emily Jiang
Sent: Monday, 09 July 2018 23:01
To: Jakarta EE community discussions <jakarta.ee-community@eclipse.org>
Subject: Re: [jakarta.ee-community] Jakarta EE in the future

 

Besides what the other people said, if you are writing Java-based microservice, please checkout microprofile programming model (microprofile.io), which is complementary to Java EE/Jakarta EE. To reiterate, Java for Enterprise (Jakarta EE) is undergoing a big transformation right now and will come out even stronger and nimble.

Thanks

Emily

 

On Mon, Jul 9, 2018 at 5:42 PM, Werner Keil <werner.keil@xxxxxxxxx> wrote:

Hi,

 

Thanks for the reply and clarification.

Expect more for aspects of Web development, especially Web Services from Jakarta EE. 

Getting familiar with the current Web Profile is a good start. And should have you prepared for other technologies or profiles that are specialized to a particular area, e.g. "headless" APIs without a Web UI or "Self-Contained Systems" which come with a Web UI of some sort.

 

Regards,

Werner

 

 

On Mon, Jul 9, 2018 at 6:24 PM, Aislan Nadrowski <aislan.nadrowski@xxxxxxxxx> wrote:

Hi all,

 

Thanks for the feedback! 

 

Werner, what I mean with “Java for web” is the set of specs used to develop backend and frontend like JSP, JSF, Servlet, CDI, JPA, etc. I do not mean Applets and Java Web Start :)

 

Kind regards,

 

 

On Mon, Jul 9, 2018 at 1:16 PM John Hogan <jhogan515@xxxxxxxxx> wrote:

Hello Aislan.

 

There's probably a better forum for this question, but since you're here ...

 

IMO, you are heading in the right direction.  I believe that the future of Jakarta EE is in good hands with the Eclipse Foundation and is on solid ground going forward.  I also believe that you would be making a very wise investment in the most open, widely used, standards based and powerful platform available.  There has always been plenty of noise and naysayers from competing camps regarding the supposed demise of Java EE/Jarkarta EE.  My recommendation would be to ignore the FUD and continue with Jakarta EE.

 

John Hogan

 

On Mon, Jul 9, 2018 at 9:46 AM, Aislan Nadrowski <aislan.nadrowski@xxxxxxxxx> wrote:

Hi,

I’m not sure if here is the right place to ask this question but maybe you can help me.

I’m a user of the Java SE and I really like this platform/language. In recent months I decided to study web things using Java, so: Java EE and now Jakarta EE.

When Oracle announced the Java SE support roadmap I started to hear from people of other communities (other platforms/languages) that with this roadmap the future of the Java for web is uncertain.

Roadmap: http://www.oracle.com/technetwork/java/javase/eol-135779.html

How do you see the future of the developer that uses Jakarta EE in 3 years? This thing of changing the release each 6 months can really reduce the use of Java for web?

Thanks!

Kind regards,

--

Aislan Nadrowski
Software Developer


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

 

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


 

--

Aislan Nadrowski
Software Developer


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

 


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




--

Thanks
Emily
=================
Emily Jiang
ejiang@xxxxxxxxxx



Disclaimer

The content of this e-mail message and all attachments thereto (`this message`) does not necessarily reflect the views of MegChem (Pty) Ltd (`MegChem`). Before acting on the contents thereof, the recipient should verify that the originator has the appropriate delegated authority. In the event that this message has not been appropriately authorised in terms of MegChem`s delegation of authority, or in the event of the personal usage of MegChem`s e-mail facility, MegChem will not be liable for the contents of this message.

1. This message may contain information which is confidential, private or privileged in nature and subject to legal privilege. If you are not the intended recipient you may not peruse, use, disseminate, distribute or copy this message or its attachments. Please notify the sender immediately by e-mail, facsimile or telephone and thereafter return and or destroy this original message.

2. Please note that the recipient must scan this message and any attachments for viruses and the like. MegChem accepts no liability, damage or expense resulting directly or indirectly from the access of any message or it`s attachments or the use thereof.

3. MegChem reserves the right to monitor, read, filter, block, delete, use and act upon any incoming or outgoing message or it`s attachments sent or received by the employee, including hyperlinks in such message attachments and files copied or saved, automatically or by the employee on MegChem`s equipment.

4. Please report email abuse / misuse to mailabuse@xxxxxxxxxxxxx

This email has been scanned for viruses and malware, and automatically archived by Mimecast SA (Pty) Ltd, an innovator in Software as a Service (SaaS) for business. Mimecast Unified Email Management ™ (UEM) offers email continuity, security, archiving and compliance with all current legislation. To find out more, contact Mimecast.



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


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

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



Back to the top