Skip to main content

Home/ Java Development/ Group items tagged java standard edition

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Rinav G

JDBC 4.0 Enhancements in Java SE 6 - 0 views

www.forteach.net/...33689.html

JDBC4.0 JDBC java

shared by Rinav G on 04 Oct 10 - No Cached
  • In JDBC 4.0, we no longer need to explicitly load JDBC drivers using Class.forName(). When the method getConnection is called, the DriverManager will attempt to locate a suitable driver from among the JDBC drivers that were loaded at initialization and those loaded explicitly using the same class loader as the current application.
  • Auto-loading of JDBC driver class
  • Service Provider mechanism (SPM).
  • ...4 more annotations...
  • META-INF/services directory.
  • META-INF/services/java.sql.Driver.
  • java.sql.Driver.
  • the META-INF/services/java.sql.Drive
  • Rinav G on 04 Oct 10
     
    JDBC 4.0 Enhancements in Java SE 6 Java Platform, Standard Edition (Java SE) version 6 (code name Mustang), is currently in its second beta release and is scheduled to be delivered in October of this year. Java SE 6 includes several enhancements to the Java Database Connectivity (JDBC) API. These enhancements will be released as JDBC version 4.0. The main objectives of the new JDBC features are to provide a simpler design and better developer experience. This article provides an overview of the JDBC 4.0 enhancements and what benefits they offer to enterprise Java developers. We will explore the new JDBC features with the help of a sample loan processing application using Apache Derby as the back-end database.
enderson james

Sturdy Business with Java SE - 0 views

technology.ezinemark.com/dard-edition-7d2d42c92f26.html

java standard edition java se

shared by enderson james on 18 Feb 11 - No Cached
  • enderson james on 18 Feb 11
     
    Java SE is main platform for developing application for your business. The main reason behind use of Java SE is the capability of running same code run on different types of platform. Aegis Software offering java solution for latest Java SE to their customer.
Hendy Irawan

Scout/Overview - Eclipsepedia - 0 views

wiki.eclipse.org/Overview

project eclipse framework SDK platform business application overview eclipsepedia scout

shared by Hendy Irawan on 24 Apr 11 - No Cached
  • Hendy Irawan on 24 Apr 11
     
    The goal of the Eclipse Scout project is making it easy to build distributed enterprise applications based on the Eclipse platform. It consists of a runtime framework providing transparent service communication between the client and backend part and is shipped with a rich set of common user interface components. The user interface is not built for a particular rendering technology but it encapsulates the core functionality into a headless model. GUI factories are available for rendering the client model into a particular target UI platform. SWT and Swing are supported out of the box and an AJAX GUI factory could be easily added. Developing Scout applications is supported by the Scout SDK, a plug-in set built on top of Eclipse PDE and Eclipse JDT. The Scout SDK works directly on the bare Java resources and assists the development task by providing an augmented view on the underlying Java code. Additionally, it comes with a rich set of wizards and operations for modifying the Scout application project just by editing the underlying Java code. There is no meta-data required. Hence a developer can switch between editing resources using Eclipse's standard editors and leveraging the features of Scout SDK at any point in time. Eclipse Scout can be used to create multi-tier client/server applications, standalone client applications or OSGi-based server applications. Basically, there are three main advantages when choosing Scout as your framework for building such applications. First, the Scout runtime is service oriented by design. Almost every functionality is provided as an OSGi service. Every OSGi bundle may make use of them. Second, Scout provides a rich set of UI elements being uncoupled from a particular GUI technology. And third, building distributed client/server applications is as easy as if both parts would run within the same local JVM.
1 - 3 of 3
Showing 20▼ items per page