While tunnning your Spring application with Basic Authentication security you can notice that you are receiving Basic Aithentication window in your browser.
The problem is with BasicAuthenticationEntryPoint that sends header
WWW-Authenticate: Basic realm="nmrs_m7VKmomQ2YM3:"
So, if you don’t want to receive this window in your browser, just create Custom Entry Point:
###ivanursul.elance.com On this page I put projects, where I was involved.Some of the projects were just backend web services, some were full stack applications.Anyway, if you are interested in hiring me as a frelance developer, you should learn about this projects: ###Online Booking system for restaurants #####www.egogso.com To be honest, this was my first project, where I was as a developer.I remember, that I was just a junior java developer with some contradictory skills. The real issue was with my team - actually, nobody could review me, because I didn’t have senior developers on the project.So, it was a risky project for me. Anyway, I finished him. Later, I switched to another company, so I don’t much about this project for now. I use: Java 1.7 Spring 3.0 Hibernate(Can’t remember version) Twitter bootstrap Backbone.js Digital Ocean as a cloud server ###Accountant system. #####as.egogso.se This was my second project, on which I worked as a backend developer.This was a project, where I started to use unit tests, database migrations, maven multi-module structure, and so on.This also was a project, where I realized why I should use JSR and specifications I use: Spring 4.0 JPA(Hibernate) Maven 3 Jenkins PostgreSQL Liquibase ###Simple Save...
It’s been a long period since Java 8 was introduced.New Java comes with a lot of new features. One of these features is the complete removal of the Permanent Generation (PermGen) space which has been announced by Oracle since the release of JDK 7. Interned strings, for example, have already been removed from the PermGen space since JDK 7. The JDK 8 release finalizes its decommissioning. This article will share the information that I found so far on the PermGen successor: Metaspace. The final specifications, tuning flags and documentation around Metaspace should be available on Java 8 official documentation. Metaspace The JDK 8 HotSpot JVM is now using native memory for the representation of class metadata and is called Metaspace; similar to the Oracle JRockit and IBM JVM’s. The good news is that it means no more java.lang.OutOfMemoryError: PermGen space problems and no need for you to tune and monitor this memory space anymore…not so fast. Instead of java.lang.OutOfMemoryError: PermGen you are now able to receive java.lang.OutOfMemoryError: Metadata space .While this change is invisible by default, we will show you next that you will still need to worry about the class metadata memory footprint. Please also keep in mind that...
Few weeks ago I started to work with JHipster - Java Framework for rapid development.I am not going to write a review of this framework - I hope, I will find time to do it later, but today I am going to write some useful information about pitfalls, that you can reach during your work with JHipster. #####Jhipster project unable to start itself on digitalocean Just FYI, Jhipster is built on top of Spring Boot Framework + Angular JS, so to start application, you need just to execute single command mvn spring-boot:run That’s a convenient way for deploying application - no separate application servers, only embedded, only hardcore. That’s why Spring Boot stores some embedded tomcat server, which contains all properties. So, the problem is that sometimes, when you deploy your application on Digital Ocean cloud server - you need to wait for a long time to finish deploying process. In my case, the problem with long deploy is that Tomcat loves to use /dev/random function, instead of /dev/urandom. To get a good example of how random and urandom works, just go to terminal and type cat /dev/random Then try to move your mouse, you will receive additional values. Then...
Agenda
</br>
Description of rules
@Rule vs @ClassRule
Some useful rules
Writing your own rule
Description of rules
Rules allow very flexible addition or redefinition of the behavior of each test method in a test class. Testers can reuse or extend one of the provided Rules below, or write their own.
This mean, that you can controll the behavior of your test case, you can catch exceptions, write before-after methods, etc.
I would recommend to read more about rules here
https://github.com/junit-team/junit/wiki/Rules
@Rule vs @ClassRule
There is a difference between @Rule and @ClassRule in JUnit.We can differ them similiar as @Before and @BeforeClass. If you will annotate field ,that implements org.junit.rules.TestRule with @Rule annotation, then it will run in each method. But, if you will annotate this field as @ClassRule, then it will run once.
Useful rules examples
Writing your own rule
We will write custom TestRule, that will log actions. We will have two
We will get
before: global
before: local
after: local
after: global
