Jakarta EE JakartaOne Livestream German 2022, 9 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: CN4J STUDIO - INTERVIEW MIT JÜRGEN HÖLLER

Description

JakartaOne Livestream is a one-day virtual conference for developers and technical business leaders that brings insights into the current state and future of Jakarta EE and related technologies focused on developing cloud-native technologies for enterprise Java applications.

Featuring Speakers: Hendrik Ebbers, Jürgen Höller, Falk Sippach, Jan Westerkamp

05:45-06:00 GMT-04

A

We'll see each other later at Penny,. Thank you very much for your presentation.

A

And we're coming back to our studio,, so in our studio we always invited interview partners during the breaks and we're very happy that Jürgen Höller will be able to appear in the picture soon.

A

It may be that it is still tired. We still have pasta time, but I hope that he will appear soon, hello, hello, look there. I can hear him already hello. Jürgen greet you greet you very nice now. Some are probably wondering what is Jürgen Höller doing, he is that is, but the one from the Spring Framework here at a Jakarta EE event, but we want to talk about it a bit in the next 10 15 minutes that we also have some intersections.

A

You are also part of the working group of jakarta.de, and that would be my first question: where do you work actively in which specifications in which parts of the chakrai world? Where do you have your cutting point? Kte? Where are you active even up to date? Jürgen tell me.

B

So, first of all, thank you for the invitation for the interview. I am pleased to be able to contribute here from our side, because we actually have specific interest in a whole range of specifications which now also in Turkey in 9 and i10, so in the E10 will be further developed in the E9. The next, but, of course, still that and for the for the future of the primary Epi in the whole series of interesting and and also others for us can of course include the same dpi for tomcat for jelly.

B

It is the primary integration for for webcontainer and tomke, and shady are already at the forefront here with the integration with jacket. We assume that there are no new features now only in jakarta, i10, the epi, but also in the related versions.

B

Generations of tomkit and jacky will come here, so for u ns is basically these epis are an integration point for providers that we not only want to see through the epi, but also as a product,, so to speak,, integrate Tomcat and Shelly are the two typical candidates for also in webcontainer are in springtood, of course,. That too System so JPA we have traditionally the optics relational web in parallel between JP and are guided, but of course, now with halbernet.

B

Yes at a point, even that has consolidated the system 0 to the primary and only etial with that you can communicate with, because of that ca, n't and shouldn't use, there's no, no classic natives.

B

Of course, also a typical integration point: we call we call trigger invalitation order. The.

B

Services then typically made available, who, who.

B

Supported the tomcat namespress, so it's very important to us that he that not only the first available but also ei A generation of providers suitable for production, with which we can also take over management here, and we have decided to make this leap for springton for sprinton 3.

B

Primarily with spaceland ATI 9,, the main reasons are that we also want to take the portfolio with us,. We assume that we, namely at the end of the year when our date comes in November. We assume that dungeon index 10 providers will be common or will be available, so we will not artificially restrict here. We see this as a new phase Part of the lifecycle of this, this spec and this provider a a breaking point. It may be right here with Space, but from there we'll see more revolution again with regular new releases.

B

Offering the option of basically being able to use this aneur version of Tank Jenny right away so.

A

That means, then, from autumn with springfood 3. You can then probably program against the Jakarta i10 Epis in spring in order to be able to.

B

Work platform-neutrally, so to speak,. We assume that this will be possible depends on the pastures,. So at the moment it is this chakartei 9. We we are playing here with the.

B

6.0 we test, even if there is still the Jakarta adapter. We are actually primarily interested in the product generations that are now really quasi native as the only appialkati 9er card and and and and and support the following, where there is not just one adapter somewhere in between sitting and accommodating an older en older product generation. That always makes sense for a transition,, but strategically we are actually interested in the product generations that will follow and have.

B

Already shown that with half nations here, we are also actively pursuing an active vision, has an active roadmap for this new product generation, which can only be integrated via Chakra Systems,.

B

So here is also a breaking point in the administrators with existing generations up to 27,. So you don't get 5x essentially and bounce tone. 3 will probably not be the primary provider, Hyper 6.x I, say now deliberately six and nothing because we pick them up the way they are released there, that doesn’t necessarily have to fit our life cycle. Our own release cycle, our my generation, but that doesn’t matter because it’s in the classic spring tradition and the conscience Degree. Also in the spring food tradition. Well, a user has a choice.

B

You can use the version that now comes with this product generation. You can normally upgrade it yourself individually. So it's like an opt-in to a newer version, one for partydependency, and we definitely see that that this is also done.

B

Classically all stay here, where you do that. You.

A

Can tell we want to answer that you're really into this whole topic,, so streaming, isn't that far away from Jakarta anyway, it has a lot of intersection points,. So it's very exciting what you said there,. You also have that an interesting question. Jan.

C

Or yes, exactly what is your relationship with Java, SE and version for current releases,, for example, of springboot and sprung? And what does it look like with the upcoming major release.

B

That the topic is perhaps even more difficult to accommodate in in our community, because we deliberately take a very unusual step. The existing spring company, 3x generation, springton 2 generation, still has many places with Java 8 used but of course allows the use of Java 11 from Java 17, actually from every Java version. Since eight we distinguish here not so strong girl.

B

You the the fault line, we introduce it now or actually use it, because there is one that will be there anyway or.

B

Consciously decided to demand a very high minimum version here, because with Springform 3, we not only.

B

Offer zero there,, that is point 0,. It is here in November, but see it as a generation, one new generation of the framework for the coming years and in the coming years,. So if we now take a perspective in mid-2023 or 2024,, hopefully, Java 17 will be the common Java version that we will find in productive use and we are preparing for that.

B

I think 17 is also going to be our release- and in November it's already more than a year, old, there's already 18,, but there will be 19 after that, and there will also be a few interesting new trigger features,, at least in Java 19,, which we'll also have somewhere I want to pick up with. 17 will remain the basement for this generation.

B

You can always go to Java 17 ETS release as a basis,, but we also see this as an invitation to take up newer, Java versions beyond 17 right away,, be it 19, be it the 21 LTS release that will come next year in September, 2023. We, assume that if we jump sexually and three users will follow these JDK upgrades quite actively, or at least a certain part of our community, a certain part that will bring good 3 users will want to do that.

B

We would also like to actively support that those who want to stay on the baseline will, of course, also feel comfortable there. We try to cover both with one product generation.

C

Yes, so for the background for Jakarta E10, the release was also discussed, which minimum daverse version is allowed so for respect those who come in and have corresponding requirements. 17 was in discussion, but the majority decided so minimum should still be compatible with Java SE 11, its one of the arguments, was, however, at the time when the decision was made that was about a year ago that 17 had not even appeared that could have been delayed from today's point of view, 11 is minimal.

C

Compatibility may no longer be the optimal decision with the subsequent manager release that will definitely change, because with Rest 4.0, it says using records, for example,. The bar is then also set at 17,, but of course you can also qualify posters at 17 and let them run,.

C

There was 18,, which.

C

Offers a breaking change with the Security Manager there Of course. There is a bigger problem in the house,. So how do you deal with that?, The elimination of the security man on the.

B

Edge,, actually in the depths, yes,, we have now decided to take out all the security people,, as it was already marked at the time more of an implementation decision, not so much an epa decision, because that security is only relevant to people in very few places,.

B

But we have to. With such a framework generation that is planned for several years. In.

B

Advance, you have to take such steps as early as possible. Now. You may somehow get away with it with the 17 baseline, but we assume that in the future the new test release will also become dominant and that Springform,, whatever version, a feature release, will also run primarily for 21,. So we actually anticipate such decisions quite early and prepare the code basis early on,, so to speak,, because we assume that this will be urgent, that it will be urgent it in the planned life cycle that we have planned for this framework generation.

B

It is unavoidable that the 17 baseline is also partly motivated by this. We also want EPA is the infizite existi eren. These are new flaction epis records, reflection and all these things that we would like to be able to use as a federal parliament foundation in the framework- and there are some very interesting language- videos in the Java 17 language level that also make our life easier internally,.

B

So we have, we modernize,. We also have it Actually,. We have already pulled through. We, have completely modernized the frameboard code base to the Java 17 language level,, which of course also internally.

B

Represents the starting point for a generation now and makes maintenance easier in the next few years and simply produces code that is easier to read,. So we want this added value ourselves that Java has created, this progress. That Java has created in the language in which koalpress can also be used in our code base and in some places it will also shine through as a user app,. But it's actually primarily about the firmware code,, which it is itself.

C

Very interesting, yes,.

A

C

Unfortunately,.

A

The time is already up: again. It's, really exciting. To talk to you. You can really learn a lot from you and we're really excited to hear what's to come and what's coming up soon and also Spring Boot 3.0. If that's in the fall I'm. Also really looking forward to it, nice that you were there,.

B

A

B

Other projects,, the providers are also involved here,, but most of it is already there,, so I'm not worried, they've all already done their job,. So we'll do it with the edges. We try to bring these things together into one into one. Springfood, 3, I, hope.

A

We'll see each other again soon live at a conference also, so, first of all many greetings to Austria to Linz until you're in Linz, I. Think or thank you.

B

Exactly you were there.

A

And see you soon, bye, bye thanks.

B

For the conversation bye.