JavaOne 2012: JavaOne Technical Keynote

1) Java's enhanced for loop will be replaced by forEach() method and they will include this method in all the collections via default implementation interface approach.

2) JMS 2.0 taking the help of java's Annotations and resource injection to send a message.

3) Java focusing on increasing the JavaFX Libraries (Adding new component like Combo Box in JavaFX).

4) Scene Builder with Netbeans for Developing JavaFX Apps.
Main UI thread to be separated from background threads, allowing it to take advantage of multiple CPUs in JavaFX.

5) The "Angry Bids" example application was demonstrated. It is based on Avatar and runs on GlassFish and uses standard Java EE 7 components.

6) Netbeans 7.3 will be coming this week with HTML5 as a New Project Type in it.
Also Netbeans is going to Support JQuery.

Comments

Post a Comment

Popular posts from this blog

Hashicorp Configuration Language - HCL

Installing Terraform What is Terraform and Why do we need it? Terraform Commands Here, we will cover the basics of the Terraform configuration language, as well as explore providers and resources. Continuing what we started in Terraform Commands, we will modify main.tf so we can deploy a Ghost container to Docker. The syntax of Terraform configurations is called HashiCorp Configuration Language (HCL). It is meant to strike a balance between being human-readable and editable, and being machine-friendly. For machine-friendliness, Terraform can also read JSON configurations. For general Terraform configurations, however, we recommend using the HCL Terraform syntax. Terraform code files The Terraform language uses configuration files that are named with the .tf file extension. There is also a JSON-based variant of the language that is named with the .tf.json file extension. Terraform Syntax Here is an example of Terraform's HCL syntax: resource "aws_instance" "example...
Read more

Terraform - Input Variables

Installing Terraform What is Terraform and Why do we need it? Terraform Commands Hashicorp Configuration Language - HCL Tainting and Untainting Resources Terraform Console and Output Input variables serve as parameters for a Terraform file. A variable block configures a single input variable for a Terraform module. Each block declares a single variable. Syntax: variable [NAME] {   [OPTION] = "[VALUE]" } Arguments Within the block body (between { }) is configuration for the variable, which accepts the following arguments: type (Optional): If set, this defines the type of the variable. Valid values are string, list, and map. default (Optional): This sets a default value for the variable. If no default is provided, Terraform will raise an error if a value is not provided by the caller. description (Optional): A human-friendly description for the variable. Using variables during an apply: terraform apply -var 'foo=bar' Set up the environment: cd terraform/basics Edit main...
Read more

Terraform - Tainting and Updating Resources

Installing Terraform What is Terraform and Why do we need it? Terraform Commands Hashicorp Configuration Language - HCL We are going to take a look at how to force a redeploy of resources using tainting. This is an extremely useful skill for when parts of a deployment need to be modified. Tainting and Untainting Resources Terraform commands: taint: Manually mark a resource for recreation  untaint: Manually unmark a resource as tainted Tainting a resource: terraform taint [NAME] Untainting a resource: terraform untaint [NAME] Set up the environment: cd terraform/basics Redeploy the Ghost image: terraform apply Taint the Ghost blog resource: terraform taint docker_container.container_id See what will be changed: terraform plan Remove the taint on the Ghost blog resource: terraform untaint docker_container.container_id Verity that the Ghost blog resource is untainted: terraform plan Updating Resources Let's edit main.tf and change the image to ghost:alpine. Open main.tf: vi main.tf ma...
Read more