|Re: [jakarta.ee-community] Jakarta EE Blogging and Speaking Ideas|
Firstly, thanks so much for considering adopting some of the ideas I
have with regards to blogging and speaking on Jakarta EE topics. They
are below, I am happy to help in any way needed. I am also sending this
to the community aliases in case other folks are interested.
* I am updating this talk to Jakarta EE 10:
will add speaker notes and a recording so anyone can deliver it. I will
probably update the title to "Jakarta EE 10 and Beyond".
* I will update this talk to target Jakarta EE 11+:
In order to do that we first need to create a "Jakarta EE 11
Contributors Guide" from our current one:
I plan to drive that after Summer.
* This talk needs to be updated to Jakarta EE 8/10:
Specifically, an SSE case needs to be added as well as JSON Binding,
etc. The front end needs to be updated and in general the content too. A
stock ticker is what I had in mind as the SSE case. This could easily be
a workshop, a series of blogs a well as a contribution to the official
Jakarta EE examples.
* "Top __ Jakarta EE Features in __ Minutes". This could be just slides
or just live coding.
* "Using Records in Jakarta EE Applications", "Using Records in Jakarta
Persistence/JPA Applications". This could easily be a series of blogs a
well as a contribution to the official Jakarta EE examples. This could
be just slides or just live coding. This might end with finding some
gaps in Jakarta Persistence/Jakarta EE.
* "Running Jakarta EE Applications on Quarkus", "Running Jakarta EE
Applications on Helidon". This would be a somewhat
experimental/exploratory talk seeing to what extent these runtimes
actually support Jakarta EE APIs beyond the Core Profile and also
examining any critical gaps (other than some of the features still in
EJB today my hypothesis is actually there aren't many gaps).
Let me know your thoughts?
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community
member and do not reflect the views of my employer.
Back to the top