Hi @Java Brains ....i have one question...please let me know if we use reactive programming so we should not use List or Map or Arrya.i know there is replacement of ExecutorService but is it like to use flux or Mono everywhere even for list ,array or Map set.please let me know
Java Brains, thank you very much for the excellent video. One question about Implicit Flow. You've mentioned that it's drawback is that anyone can use the access token that client received. Isn't it true for the Authorization Code Flow when anyone can get Authorization Token and then get an Access Token with it? From my point of view this is exactly the same problem just the "dance" gets one step longer. And you point that in the first flow client can get an access token in a more secure way is not convincing. Why not to make the same level of security while getting an access token without sending authorazition one first?
I have a wsdl file which has inputName=" " , outputName=" " , bindingOperationName= " " etc.. how is this one different from the one which I have . Where can I find more info on the format that I have .
Field authorRepository in io.springbootproject.betterreadsdataloader.BetterReadsDataLoaderApplication required a bean of type 'com.author.AuthorRepository' that could not be found. The injection point has the following annotations: - @org.springframework.beans.factory.annotation.Autowired(required=true) Action: Consider defining a bean of type 'com.author.AuthorRepository' in your configuration.
Got this error after adding the @EnableHystrixDashboard and properties: Caused by: java.lang.IllegalStateException: Failed to introspect Class org.springframework.cloud.netflix.hystrix.dashboard.HystrixDashboardConfiguration
any one who is watching this video make sure you know run command is deleted for versions after 3.0.0 so you can skip this video as or use `mvn spring:boot run` command
Good course (thanks!), but it misses to explain two points which I think most would stumble on. 1) By using a Mono (and delayElement), you're freeing up one thread, but it's still another thread in the JVM that must "delay" (except it's handled by Spring webflux). Same for real I/O operations. There's no magic going on here, I think the video should make that clear. If you have slow blocking code (i.e., a long-lived DB call), you will have a thread blocked somewhere at some point. And if you have 10 of these, you'll have 10 blocked threads (or worse, less than 10 but with subsequent requests queued) -- just for a crude example. 2) Nowhere in this video series did it cover the critically important fact that actually, you get no threading by default unless you specify it somewhere; all rails would be on the same thread. You in your example Fluxes happen to be getting parallel threading, perhaps unknowingly, by using delayElement() (look at the source: return delayElements(delay, Schedulers.parallel())). Without that, everything would be executed sequentially on the same thread that you created the Flux. In reality, nobody will be using anything like the example Fluxes in production code. Crucial methods like runOn(), publishOn(), subscribeOn(), etc., should have been covered -- the whole concept and benefits of Reactor is lost otherwise, IMO. See: projectreactor.io/docs/core/release/reference/#schedulers
I was doing well until session #29 when adding the embedded Derby DB. I get this on startup. Any clues on how to fix it? Thanks for a great tutorial!!! 2024-05-18T14:07:59.476-04:00 INFO 66638 --- [course-api-data] [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000489: No JTA platform available (set 'hibernate.transaction.jta.platform' to enable JTA platform integration) 2024-05-18T14:07:59.700-04:00 WARN 66638 --- [course-api-data] [ main] o.h.t.s.i.ExceptionHandlerLoggedImpl : GenerationTarget encountered exception accepting command : Error executing DDL "create table topic (id varchar(255) not null, desc varchar(255), name varchar(255), primary key (id))" via JDBC [Syntax error: Encountered "desc" at line 1, column 47.] org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL "create table topic (id varchar(255) not null, desc varchar(255), name varchar(255), primary key (id))" via JDBC [Syntax error: Encountered "desc" at line 1, column 47.] at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:94) ~[hibernate-core-6.4.4.Final.jar:6.4.4.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlString(AbstractSchemaMigrator.java:574) ~[hibernate-core-6.4.4.Final.jar:6.4.4.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlStrings(AbstractSchemaMigrator.java:514) ~[hibernate-core-6.4.4.Final.jar:6.4.4.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.createTable(AbstractSchemaMigrator.java:315) ~[hibernate-core-6.4.4.Final.jar:6.4.4.Final] at org.hibe
Hi, would really help if you could do a video on arrays, list, and arraylists private List<Topic> topics = new ArrayList<>(Arrays.asList( new Topic("Spring", "Spring Framework", "Spring Framework Description"), new Topic("Spring1", "Spring Framework1", "Spring1 Framework Description"), new Topic("Spring2", "Spring Framework2", "Spring2 Framework Description"), new Topic("Spring3", "Spring Framework3", "Spring3 Framework Description"))); The above is quite confusing for me. Appreciate your guidance. Tq
Funny you should mention Kissinger. It took a seasoned Indian diplomat to remind him of his heritage of being progeny of Jew refugees from WW2 and who was now turning a blind eye to the genocide in Bangladesh. You should look it up on the internet; he apparently pulled the table cloth from the breakfast table yelling he ain't a refugee. But the points you've mentioned are really good face savers when staring at an unknown problem. Good content, as usual.
This problem reminds me of a game i used to play when i was young with 3 and 7 with a group of friends. We were counting one by one and every time when someone missed the BUZZ ( in our country we would call it BOLTZ instead of BUZZ :D ) had to drink the BOOZE. Nice job anyway
Is using Method References a good practice for maintainable code? I see that the reader has to actually look into the parameters of the and keep both of them side by side.
We can also use Java Streams for this Step2 : personList.forEach(person -> System.out.println("lambda person : " + person)); Step 3 : personList.stream(). filter(person -> { return (person.getLastName().charAt(0) == 'C'); }).forEach(person -> System.out.println("stream person : " + person));
