| Re: [jakartaee-platform-dev] Release profiles independently |
It’s a valid point, that the term „Cloud“ is probably not the best and final Codename for that Kind of profile, but I really don’t think those sorts of integrations with Cloud Vendors belong to Jakarta EE as such. Either yet another MicroProfile spec or (not sure, if that is purely a lliaison with MicroProfile and the CNCF or more) this „Cloud Native Java WG“. Werner Von: Markus KARG The question is whether "Cloud" wouldn't involve more API - such which do not even exist yet, e. g. deploment and migration between different cloud vendors, or interacting with the provisioning SPIs those vendors provide? -Markus Von: jakartaee-platform-dev [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von arjan tijms Hi, On Tue, Mar 16, 2021 at 6:50 PM Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Tiny, tiny, correction; it's just "Faces", not "Server Faces" ;) Regarding the cloud profile, with "Dependency Injection", do you actually refer to the JSR 330 fork? As that's actually a dependency of CDI, and not something the platform suggests to use on its own (correct me if I'm wrong), maybe the picture can be simplified by omitting it? Maybe half offtopic here, but maybe not. What about folding JSON Processing and JSON Binding into just JSON? Then rename Jakarta Restfull WebService to Jakarta REST and Bean Validation to Validation. If (big if) the current Dependency Injection can be folded into CDI, then CDI Lite could use the simple name Dependency Injection. The Cloud Profile could then be: REST JSON Validation Security Dependency Injection Config Annotations IMHO, just by those names alone, makes it look a lot smaller, simpler and easier to comprehend what it does. Kind regards, Arjan Tijms |