Archive from October 2017
Java EE Presentations at JavaOne 2017
Published on 26 Oct 2017
by Dominika Tasarz
Topics: Java EE, Microservices, MicroProfile | 0 Comments
Didn't get a chance to attend JavaOne 2017 earlier this month? You can now watch some of the conference talks online! See below for our selection of the most interesting and useful presentations about Java EE.
All JavaOne 2017 recorded talks can be found on the Oracle Java YouTube channel.
Payara Server 5 Alpha 2 release is here!
Published on 20 Oct 2017
by Arjan Tijms
Topics: What's New, Payara Server 5 | 1 Comment
We're excited to announce that the second Alpha release of Payara Server 5 is now available for download! We highly encourage you to give it a go, test it out and let us know what further improvements are needed.
Using HotswapAgent to Speed up Development
Published on 18 Oct 2017
by Ondro Mihályi
Topics: How-to, NetBeans, JVM, DevOps | 15 Comments
Improvements to SQL Logging in Payara Server 173
Published on 13 Oct 2017
by Fabio Turizo
Topics: What's New, How-to | 0 Comments
A crucial component in many web applications is the use of a database. The chances of using JDBC directly or indirectly to access a relational database (through JPA or other ORM frameworks) on these applications are quite high. A common problem when dealing with relational databases is dealing with SQL queries or statements that take too much time to resolve, thus causing your application to be considered slow in producing results to the user. It's usually better to detect these issues preemptively, before sub-par performance damages your application, and Payara Server has you covered!
New Arquillian Container for Payara Server
Published on 03 Oct 2017
by Fabio Turizo
Topics: What's New, Java EE, Arquillian | 5 Comments
One of the core steps in every continuous integration process is running integration tests for your application. Unlike vanilla unit tests, integration tests allow you to assess the state of your applications or systems by testing all of its components together (modules, databases, messaging, etc.) and verifying that they work correctly as a whole unit. Needless to say, integration tests are more complex that simple unit tests, have a larger footprint, take more time and are usually saved to test full releases or major changes to implementations.