Re: [jaxrs-dev] [External] : Re: Jakarta REST 4.0 - Brainstorming

["Markus Karg" <markus@xxxxxxxxxxxxxxx>]

>> * Is @Inject really needed for @*Param, or can we tell CDI that @*Param shall *imply* @Inject? 
> I think so, as long as @*Param are qualifiers. It may possible for implementations to provide shortcuts without @Inject, but I’m not sure we should encourage that.

Maybe we should ask the CDI team to extend their spec so any annotation's defition can be annotated itself with @Inject to make make it *imply* @Inject? This feels rather straightforward to me.

>> I also would like to add one more general topic to the 4.0 list: Supporting modern Java. This means, we should be able to run on JRE 17 as this is the next LTS version, and we should clarify with the Jakarta EE team what the minimum JRE for Jakarta EE 10 is. We also should discuss whether records and sealed classes needs special support in Jakarta REST 4.0 as I assume both become rather popular in the next months.
> This is more of a community decision IMO. I’m not sure how to do some of the things you mention here while requiring support for a minimum JRE. Perhaps you can explain this a bit more.

Let me turn it this way: In case the Jakarta EE team decides that the minimum supported JRE is 17, programmers will use records and sealed classes. I am not an expert for either, but I could imagine that questions will arise how to use it with JAX-RS. For example: Can I use record with @BeanParam, or do we need @RecordParam? Will we officially allow record as return type of method, and what is the impact on entity providers? So I think it would be a good thing to have "Modern Java" *discussed* for 4.0 to be aware of the possible implications.

>> And finally, we should discuss if we adopt the var keyword in (new / legacy / no) source code, as it makes the code less verbose and easier to read.
> Where? In our API classes?

I think it makes sense in the API classes, examples, and within the printed examples inside the spec doc.

— Santiago

> -----Ursprüngliche Nachricht-----
> Von: jaxrs-dev [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] Im Auftrag von Santiago Pericasgeertsen
> Gesendet: Freitag, 21. Mai 2021 16:49
> An: jaxrs developer discussions
> Betreff: [jaxrs-dev] Jakarta REST 4.0 - Brainstorming
> 
> Hi All,
> 
> I put together some slides with thoughts about Jakarta REST 4.0 and CDI. Also created a branch in my fork that includes all the necessary changes to build a small sample. 
> 
> Hope you find this useful to get us started.
> 
> — Santiago
> 
> [1] https://urldefense.com/v3/__https://github.com/spericas/jaxrs-api/blob/release-4.0/JakartaRest40.pdf__;!!GqivPVa7Brio!OshpQsm5nBJS7QDYyOv1nf4DvZ-7ef9ExV6xokgLKFWQ62lBgwaYSDwggEjGs7RYFSZVJs9wdQ$ 
> [2] https://urldefense.com/v3/__https://github.com/spericas/jaxrs-api/tree/release-4.0__;!!GqivPVa7Brio!OshpQsm5nBJS7QDYyOv1nf4DvZ-7ef9ExV6xokgLKFWQ62lBgwaYSDwggEjGs7RYFSYEKkUKsA$ 
> 
> 
> _______________________________________________
> jaxrs-dev mailing list
> jaxrs-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jaxrs-dev__;!!GqivPVa7Brio!OshpQsm5nBJS7QDYyOv1nf4DvZ-7ef9ExV6xokgLKFWQ62lBgwaYSDwggEjGs7RYFSaAvObFdA$ 
> 
> _______________________________________________
> jaxrs-dev mailing list
> jaxrs-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jaxrs-dev__;!!GqivPVa7Brio!OshpQsm5nBJS7QDYyOv1nf4DvZ-7ef9ExV6xokgLKFWQ62lBgwaYSDwggEjGs7RYFSaAvObFdA$ 

_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxrs-dev