http://www.w3schools.com/html/default.asp
Wednesday, August 31, 2016
Tuesday, August 30, 2016
JBoss Data Virtualization
JBoss Data Virtualization is a data integration solution that sits in front of multiple data sources and allows them to be treated as a single source, delivering the right data, in the required form, at the right time to any application and/or user.
AGILE DEVELOPMENT
Rapid ways to deliver reusable and loosely coupled unified data views and data services using graphical tools. Hide data integration complexity from data consuming application developers and business users. Decouple consuming applications and data sources. Allow reuse and extension of logical data models, views and services.
Monday, August 29, 2016
How to Make Executable JAR file in Eclipse IDE - Java
If you are Java programmer then you know what is the purpose of JAR file, but for those who are unaware, JAR file is deliverables of Java application. Just like C and C++ application produce EXE files, Java produces JAR files.
In other words, A JAR (Java Archive) file is a ZIP format file that bundles Java classes into a single unit, it may contain all the resource needed by Java application as well. There are mainly two types of JAR file in Java:
Library JAR (normal JAR) files: JARs which are reusable libraries e.g. Apache commons JAR file, guava.jar itself or even JDBC drivers e.g. ojdbc6_g.jar.
Executable JAR files: JARs which can be executed as a standalone Java applications. The main
Using Dependency Injection with Java EE
Using Dependency Injection with Java EE
by samdhukate11@gmail.com
by samdhukate11@gmail.com
When Java EE 6 introduced the Contexts and Dependency Injection (CDI) specification, I was amazed that Java EE finally included dependency injection (DI) horizontally. In other words, any component can be injected into any other component, regardless of whether it's an EJB, a web service, or a POJO. Thus, you can inject a component from a Java EE container using the @Inject annotation, since the file named beans.xml is present in the WEB-INF/META-INF directory to indicate to the container which classes should be scanned.
Sunday, August 28, 2016
Saturday, August 27, 2016
JUnit cheat sheet
This post continues our series of the most useful and beautiful cheat sheets from which software engineers can learn the most frequently used commands, idioms, and best practices on various topics.
Today, we’re talking about unit tests and JUnit, one of the most popular unit test libraries in the JVM ecosystem, including some of the really useful updates in JUnit 5, which brings the library up to speed with the new features in Java 8. Now, it’s very tempting to just grab the image, print it out and start looking for a place on the wall to pin it up. By all means, do it! But make sure you stay with us, and continue reading this post, as we’ll explain the content of the cheat sheet in much more depth. The cheat sheet will then serve as a visual hint for your future testing.
JUnit cheat sheet
GET THE JUNIT CHEAT SHEET!
Building modern JavaScript applications on top of #JavaEE backends
Build modern JavaScript applications on top of Java EE backends. The Oracle JavaScript Extension Toolkit (JET) enables you to create complex enterprise JavaScript applications. But how do you connect those applications to a backend and can Java play a role?
HTTP/2 Client – Java 9
HTTP/2 Client – Java 9
The web has changed a lot since the 90’s, so in May 2015, a new version of the HTTP-Protocol was presented by the Internet Engineering Task Force (IETF). With Java 9, the developers also updated the HTTP-API in the JDK and came up with an entirely new API for HTTP/2 and Websocket. This new API will replace the old HTTPURLConnection API, which is as old as HTTP/1.1 itself.
Problems with HTTP/1.1
With HTTP/1.1, you had many Request-Response cycles which increased the latency and loading times of webpages. Additionally, you had the problem of head-line-blocking, which means that the line of packets is held up by the first packet. Because of that, an often used approach on optimizing was to open several TCP-Connections to the server and request the elements equally distributed over the connections and use workarounds like image sprites. But these multiple TCP-Connections put some additional load on the web servers and are pretty inefficient, because TCP-Connections are expensive. The goal of HTTP/2 is, to lower latency, loading times and server load, but still being backwards compatible to HTTP/1.1.
What is HTTP/2 about?
Friday, August 26, 2016
Subscribe to:
Posts (Atom)