As the largest Java platform conference in the USA and one of the leading technology events held annually around the globe. Devnexus is the premier conference for professional software developers who want to hear from and interact directly with internationally-acclaimed presenters and technologists while also connecting with like-minded developers who are mastering their craft in a range of relevant technologies.
Founded in 2004 by the Atlanta Java Users Group, Devnexus attendees can expect an experience that will span three days, beginning with an optional full-day of six hands-on workshop sessions, followed by two days of presentations and live demonstrations on the industry’s hottest topics. Offering 15 concurrent technology tracks and 150+ individual sessions, Devnexus brings attendees unparalleled opportunities for both learning about the latest technology trends and diving deep into technologies that interest them
it does not compile it show these error $ gradle install Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring root project 'spring-authorization-server'. > Could not resolve all files for configuration ':classpath'. > Could not resolve org.apache.xerces:xercesImpl:2.9.1. Required by: project : > io.spring.gradle:spring-build-conventions:0.0.38 > io.spring.gradle:docbook-reference-plugin:0.3.1 > Could not resolve org.apache.xerces:xercesImpl:2.9.1. > Could not get resource 'repo.spring.io/plugins-snapshot/org/apache/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.pom'. > Could not GET 'repo.spring.io/plugins-snapshot/org/apache/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.pom'. Received status code 401 from server: > Could not resolve org.apache.xerces:resolver:2.9.1. Required by: project : > io.spring.gradle:spring-build-conventions:0.0.38 > io.spring.gradle:docbook-reference-plugin:0.3.1 > Could not resolve org.apache.xerces:resolver:2.9.1. > Could not get resource 'repo.spring.io/plugins-snapshot/org/apache/xerces/resolver/2.9.1/resolver-2.9.1.pom'. > Could not GET 'repo.spring.io/plugins-snapshot/org/apache/xerces/resolver/2.9.1/resolver-2.9.1.pom'. Received status code 401 from server: * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. * Get more help at help.gradle.org BUILD FAILED in 30s 6 actionable tasks: 6 up-to-date A build scan was not published as you have not authenticated with server 'ge.spring.io'.
Good old Venkat, trying to make a political statement and virtue signal. It goes to show how everyone has their flaws and reaffirms the idea that people should generally stick to their expertise in public discourse.
"Moving towards async?" We've been there for almost a decade and in another ~5 years java will be ready... and by 'ready' i mean punt us back to Exceptions like it's the 1900s. Can't wait.
Will Loom make reactive stack obsolete then? They created reactive Spring in order to have non-blocking web stack. But now, if we can accomplish the same thing imperative style then I assume we can have "normal" Spring that is non-blocking.
Sure, in another 5 years you'll be able to make simple non-blocking calls. Any kind of aggregation will still be a good old java concurrency cluster fuck.
At 4:20 the Resource Owner Password grant was mentioned and it was going to be shown how to implement it ( 4:45 ). I guess there is a mention of it at 22:10 and at 27:45 by customizing tokenEndpoint customization but would like to understand how to implement it. I do understand it is not recommended but I am looking for it as a migration path to first wean off of the old library.
Sadly there are no much docu or examples. Hopefully this will change soon. I am trying to use it in my microservices app. No code on Github of this talk?
jPro implemented a Loadbalancer to solve the Problem with static variables. it's working fine for us. we can host our app for different users in the web