Skip to main content

JRE vs. JDK

 

The JRE and the JDK are two terms you hear people mention very frequently in the Java world, and what they are the two parts that we need in order to run and create Java applications. The JRE is the Java Runtime Environment. JDK is the Java Development Kit. And so, the JRE is what you require in order to run Java applications, and end users normally install the JRE. They're the ones who are going to run our apps. The JDK provides the tools that we need to create Java apps. So, normally, developers are the ones who install the JDK on their machines. And in order to develop apps, you need to run them, so the JDK installation includes a JRE. So how does all this work together? If we sit down, and we type up a Java source file with our program code inside of it, and we want to go ahead and run that in some host environment, how do we do it? A host environment might be Windows, Linux. It could be Mac. It could even be a browser. It might be a phone running Android. How do we get from that source code we've typed up to something that can run on that other computer? Well, that's where the Java Development Kit comes in. Using the Java Development Kit, we can feed our source code into it, and it will produce our Java application. Now Java's does not like a lowlevel language like C. C, when you compile a C program, it produces an application that can run directly on the host computer. Java uses an abstraction called byte codes that's platform independent. It allows us to not be tied to a host environment, but we have something that can be run in different host environments. And that's where the Java Runtime Environment comes in. The Java Runtime Environment provides what we need for our Java app to display codes that execute in any host environment. So that's why end users install the Java Runtime Environment because they just need to run that code. We, as developers, install the JDK to give us the tools to produce that application.

Comments

Popular posts from this blog

Brief Overview of RPA

Brief Overview of RPA:     §   In short, it’s a way for machines to replace human workers in regular activities done across the organization.     §   It works on both Front End & Back End applications/operations.     §   BOT provides Virtual automation agents , it acts like MIMIC HUMANS .     §   BOT ’s available in Clouds/Servers     §   BOT is nothing but a configurable software set up, works only on rule-based triggers     §   It automates Non-Value –added works     §   It is a Sub Domain of BPMS (Business Process Management Software)

RPA Implementation Approach

RPA Implementation Approach: 1. Tool Selection o     Based on user requirements, features available in tools, you’ve to select TOOL from mentioned above         2. Process Prioritization o     After successful section of Tool, you’ve to consolidate & prioritize the all processes in current operation. Let’s start automating lowest first and most important to next

Types of Recording

Types of Recording: 4 types of recording modes are available Ø   Basic Ø   Desktop Ø   Web Ø   Citrix 2 ways of Recording Ø   Automatic Ø   Manual Basic – generates a full selector for each activity and no container, the resulted automation is slower than one that uses containers and is suitable for single activities. Desktop – suitable for all types of desktop apps and multiple actions; it is faster than the Basic recorder, and generates a container (with the selector of the top-level window) in which activities are enclosed, and partial selectors for each activity. Web – designed for recording in web apps and browsers (supported: Internet Explorer, Google Chrome), generates containers and uses the Simulate Type/Click input method by default. Citrix – used to record virtualized environments (VNC, virtual machines, Citrix, etc.) or SAP, permits only image, text and keyboard automation, and requires explici...