View RSS Feed

All Blog Entries

  1. Establishing a Connection

    by , 04-27-2012 at 07:03 PM
    First, you need to establish a connection with the data source you want to use. A data source can be a DBMS, a legacy file system, or some other source of data with a corresponding JDBC driver. Typically, a JDBC application connects to a target data source using one of two classes:

    • DriverManager: This fully implemented class connects an application to a data source, which is specified by a database URL. When this class first attempts to establish a connection, it automatically
    ...
  2. JDBC: Query the Database

    by , 04-27-2012 at 07:03 PM
    Querying a database means searching through its data. You do so be sending SQL statements to the database. Once you have an open connection, you need to create a Statement object, like this:
    Java Code:
    Statement statement = connection.createStatement();
    Once you have created the Statement you can use it to execute SQL queries, like this:
    Java Code:
    String sql = "select * from people";
    
    ResultSet result = statement.executeQuery(sql);
    ...
    Categories
    Query
  3. The IDS Driver

    by , 04-27-2012 at 07:02 PM
    The IDS Driver is a type 3 driver with the IDS Server as its backend. Database queries and results are sent back and forth between the IDS Driver and the IDS Server. As it is a 100% Pure Java implementation, the driver guarantees the "Write Once, Run Anywhere" promise of Java. Indeed, it runs in all Java-enabled browsers, the Java Plug-in, and the JDK, plus all your favorite Java development tools.

    IDS Server supports Oracle (native OCI or ODBC), Sybase (native CT-Lib or ...
    Categories
    Driver
  4. Type 4: Native-protocol/all-Java driver

    by , 04-27-2012 at 07:01 PM
    The native-protocol/all-Java driver (JDBC driver type 4) converts JDBC calls into the vendor-specific database management system (DBMS) protocol so that client applications can communicate directly with the database server. Level 4 drivers are completely implemented in Java to achieve platform independence and eliminate deployment administration issues.

    Pros
    Since type 4 JDBC drivers don't have to translate database requests to ODBC or a native connectivity interface or to ...
    Categories
    Driver
  5. Type 3: Net-protocol/all-Java driver

    by , 04-27-2012 at 07:00 PM
    JDBC driver type 3 -- the net-protocol/all-Java driver -- follows a three-tiered approach whereby the JDBC database requests are passed through the network to the middle-tier server. The middle-tier server then translates the request (directly or indirectly) to the database-specific native-connectivity interface to further the request to the database server. If the middle-tier server is written in Java, it can use a type 1 or type 2 JDBC driver to do this.

    Pros
    The net-protocol/all-Java ...
    Categories
    Driver
  6. Type 2: Native-API/partly Java driver

    by , 04-27-2012 at 06:59 PM
    JDBC driver type 2 -- the native-API/partly Java driver -- converts JDBC calls into database-specific calls for databases such as SQL Server, Informix, Oracle, or Sybase. The type 2 driver communicates directly with the database server; therefore it requires that some binary code be present on the client machine.

    Pros
    Type 2 drivers typically offer significantly better performance than the JDBC-ODBC Bridge.

    Cons
    The vendor database library needs to be ...
    Categories
    Driver
  7. Type 1: JDBC-ODBC Bridge

    by , 04-27-2012 at 06:58 PM
    The type 1 driver, JDBC-ODBC Bridge, translates all JDBC calls into ODBC (Open DataBase Connectivity) calls and sends them to the ODBC driver. As such, the ODBC driver, as well as, in many cases, the client database code, must be present on the client machine. Figure 1 shows a typical JDBC-ODBC Bridge environment.

    Pros
    The JDBC-ODBC Bridge allows access to almost any database, since the database's ODBC drivers are already available. Type 1 drivers may be useful for those companies ...
    Categories
    Driver
  8. JDBC Driver Manager

    by , 04-27-2012 at 06:57 PM
    The JDBC DriverManager class defines objects which can connect Java applications to a JDBC driver. DriverManager has traditionally been the backbone of the JDBC architecture. It is quite small and simple.

    This is a very important class. Its main purpose is to provide a means of managing the different types of JDBC database driver. On running an application, it is the DriverManager's responsibility to load all the drivers found in the system property jdbc. drivers. For example, this ...
    Categories
    Driver
  9. What is a JDBC driver?

    by , 04-27-2012 at 06:13 PM
    The JDBC API defines the Java interfaces and classes that programmers use to connect to databases and send queries. A JDBC driver implements these interfaces and classes for a particular DBMS vendor.

    A Java program that uses the JDBC API loads the specified driver for a particular DBMS before it actually connects to a database. The JDBC DriverManager class then sends all JDBC API calls to the loaded driver.

    The four types of JDBC drivers are:

    • JDBC-ODBC ...
    Tags: jdbc driver Add / Edit Tags
    Categories
    Driver
  10. JDBC Architecture

    by , 04-27-2012 at 06:11 PM
    The JDBC API supports both two-tier and three-tier processing models for database access.

    In the two-tier model, a Java application talks directly to the data source. This requires a JDBC driver that can communicate with the particular data source being accessed. A user's commands are delivered to the database or other data source, and the results of those statements are sent back to the user. The data source may be located on another machine to which the user is connected via a network. ...
    Categories
    Tutorial
  11. JDBC Product Components

    by , 04-27-2012 at 06:10 PM
    JDBC includes four components:

    • The JDBC API — The JDBC™ API provides programmatic access to relational data from the Java™ programming language. Using the JDBC API, applications can execute SQL statements, retrieve results, and propagate changes back to an underlying data source. The JDBC API can also interact with multiple data sources in a distributed, heterogeneous environment.
    • The JDBC API is part of the Java platform, which includes the Java™ Standard Edition (Java™ SE
    ...
  12. JDBC Introduction

    by , 04-27-2012 at 06:09 PM
    The JDBC API is a Java API that can access any kind of tabular data, especially data stored in a Relational Database.
    JDBC helps you to write Java applications that manage these three programming activities:
    1. Connect to a data source, like a database
    2. Send queries and update statements to the database
    3. Retrieve and process the results received from the database in answer to your query
    The following simple code fragment gives a simple example of these three ...
    Categories
    Tutorial
  13. Using jBPM In An Architecture Based on Spring

    by , 04-27-2012 at 05:52 PM
    Spring itself needs only to have the Spring modules jar on the class path. See the included project's root pom.xml for the minutiae of our particular installation. I expect this project could be made to work with Spring 1.x, with some work. I'm using some of the fancy new name spaces, so it won't work directly.

    The beans jbpmConfiguration and jbpmTemplate (inside of services/services-engine/src/main/resources/service-context.xml) configure the jBPM integration. jbpmTemplate – provided ...
    Categories
    jBPM and Spring
  14. Configuring Delegations

    by , 04-27-2012 at 05:52 PM
    Delegation classes contain user code that is called from within a process execution, the most common example being an action. In the case of action, an implementation of the ActionHandler interface can be called on an event in the process. Delegations are specified in the processdefinition.xml file. One can supply any of these three pieces of data when specifying a delegation:

    1. the class name (required): this is the delegation class' fully-qualified name.
    2. configuration type
    ...
  15. The Process Class Loader

    by , 04-27-2012 at 05:51 PM
    Delegation classes are loaded through their respective process class loader. The process class loader has the JBPM class loader as its parent. It adds the classes deployed with one particular process definition. To add classes to a process definition, put them in the classes directory of the process archive. Note that this is only useful when one wishes to version the classes that have been added to the process definition. If versioning is not required, make the classes available to the JBPM class ...
  16. Migrating Process Instances

    by , 04-27-2012 at 05:50 PM
    An alternative approach to changing a process definition is to migrate each process instance to a new version. Please consider that migration is not trivial due to the long-lived nature of business processes. There is a clear distinction between definition data, execution data and logging data. Because of this distinction, a new version of the process has to be deployed first, and then process instances are migrated to the new version. Migration involves a translation if tokens or task instances ...
    Categories
    jBPM Process
  17. Process Versioning

    by , 04-27-2012 at 05:50 PM
    Process instances always execute on the same process definition as that in which they were started. However, the JBPM allows multiple process definitions of the same name to co-exist in the database. Typically, a process instance is started in the latest version available at that time and it will keep on executing in that same process definition for its complete lifetime. When a newer version is deployed, newly created instances will be started in the newest version, while older process instances ...
    Categories
    jBPM Process
  18. Deploying a Process Archive

    by , 04-27-2012 at 05:48 PM
    One can deploy a process archive in any of three different ways:
    • via the Process Designer Tool
    • with an ant task
    • programatically
    To deploying a process archive with the Process Designer Tool, follow this step. (This process is supported in the starter's kit.)

    1. Right-click on the process archive folder and select the Deploy process archive option.
    The starter's kit server contains the JBPM application, which has a servlet to upload process ...
    Categories
    jBPM Process
  19. Downloading JBoss jBPM

    by , 04-27-2012 at 05:47 PM
    The JBoss jBPM starter kit contains everything needed to execute JBoss jBPM, with the exception of a JDK. The JBoss Application Server in the JBoss jBPM starter kit requires J2SE 1.4 or a more recent version.
    After you have downloaded the starter kit, unzip it to a directory of your choosing. Once you have unzipped the starter kit, you will have a directory structure similar to the following:

    • Jbpm-starters-kit-3.1

    o jbpm: Contains the source code for the JBoss
    ...
    Categories
    Tutorial
  20. Deploying JBoss jBPM

    by , 04-27-2012 at 05:47 PM
    JBoss jBPM stores process definitions in a database. Therefore, deploying a process into JBoss jBPM involves parsing the process-definition.xml and storing it in the JBoss jBPM database. This can be done by:

    • Using the par Ant task supplied with JBoss jBPM to create a process archive.
    • Using the deploypar utility. This utility also creates a process archive and deploys the process archive to the jBPM database. The deploypar utility takes a jBPM.properties file as an attribute.
    ...
    Categories
    Tutorial
  21. Overview of the JBoss jBPM architecture

    by , 04-27-2012 at 05:45 PM
    In jBPM, process definitions are packaged as process archives. A process archive is passed to the jPDL process engine for execution. The jPDL process engine traverses a process graph, executes defined actions, maintains process state, and logs all process events.

    • Process engine: This component executes defined process actions, maintains process state, and logs all process events via the following delegate components:


    o A request handler
    o A state manager
    ...
  22. jBPM5

    by , 04-27-2012 at 05:44 PM
    jBPM5 is the latest community version of the jBPM project. It is based on the BPMN 2.0 specification and supports the entire life cycle of the business process (from authoring through execution to monitoring and management).

    The current jBPM5 snapshot offers open-source business process execution and management, including

    • embeddable, lightweight Java process engine, supporting native BPMN 2.0 execution
    • BPMN 2.0 process modeling in Eclipse (developers) and ...
    Tags: jbpm5 Add / Edit Tags
    Categories
    Tutorial
  23. What does jBPM do?

    by , 04-27-2012 at 05:43 PM
    A business process allows you to model your business goals by describing the steps that need to be executed to achieve that goal and the order, using a flow chart. This greatly improves the visibility and agility of your business logic, results in higher-level and domain-specific representations that can be understood by business users and is easier to monitor.
    The core of jBPM is a light-weight, extensible workflow engine written in pure Java that allows you to execute business processes ...
    Categories
    Tutorial
  24. What is JBoss Web

    by , 04-27-2012 at 05:42 PM
    JBoss Web Server is an enterprise ready web server designed for medium and large applications, based on Tomcat.

    JBoss Web a component of the JBoss Application Server, there are no more standalone version of JBoss Web you need the Application Server to get the Servlet/JSP container.,

    JBoss Web Server provides organizations with a single deployment platform for Java Server Pages (JSP) and Java Servlet technologies, PHP, and CGI. It uses a genuine high performance hybrid ...
    Categories
    JBoss Web
  25. The Need for JBoss Seam

    by , 04-27-2012 at 05:41 PM
    Let us exactly define what JBoss seam is. JBoss Seam provides a Light-weight Container for J2EE standards and it addresses the long-standing issues in any Typical Web Application like State Management and Better Browser Navigation. It also neatly provides an integration between the two popular technologies, Java Server Faces (in the UI tier) and Enterprise Java Beans (EJB 3 in the Server Side). Before getting into the various details about JBoss Seam let us see the common set of problems that are ...
  26. JBoss Seam: A Deep Integration Framework

    by , 04-27-2012 at 05:40 PM
    Software frameworks are very useful tools for enterprise Java developers. They are widely used to package reusable software components and services. Each framework provides a set of design patterns, APIs, and component models, which can be used in applications built on top of the framework. Examples of popular Java EE frameworks include both open source projects such as Hibernate, Spring, Struts, etc., and standard-based products such as various implementations for Servlet/JSP, JSF, EJB, JMS, Web ...
    Categories
    JBoss Seam
  27. Seam - Avoid XML Abuse

    by , 04-27-2012 at 05:39 PM
    As you probably noticed, Java annotations play a crucial role in expressing and managing Seam configuration metadata. That is done by design to make the framework easier to work with.

    In the early days of J2EE, XML was viewed as the "holy grail" for configuration management. Framework designers throw all kinds of configuration information, including Java class and method names, in XML files without much thought about the consequence to developers. In retrospect, that was ...
    Categories
    JBoss Seam
  28. Seam - Configuration by Exception

    by , 04-27-2012 at 05:38 PM
    The key design principal that makes Seam so easy to use is "Configuration by exception". The idea is to have a set of common-sense default behavior for the components. The developer only needs to configure the component explicitly when the desired behavior is not the default. For instance, when Seam injects component A as a property of component B, the Seam name of component A defaults to the recipient property name in component B. There are many little things like that in Seam. The overall ...
    Categories
    JBoss Seam
  29. Seam - POJO Services via Dependency Bijection

    by , 04-27-2012 at 05:38 PM
    Seam is a "lightweight framework" because it promotes the use of POJO (plain old Java objects) as service components. There are no framework interfaces or abstract classes to "hook" components into the application. The question, of course, is how do those POJOs interact with each other to form an application? How do they interact with container services (e.g., the database persistence service)?

    Seam wires POJO components together using a popular design pattern ...
    Categories
    JBoss Seam
  30. Seam - Web 2.0 Ready

    by , 04-27-2012 at 05:37 PM
    Seam is fully optimized for Web 2.0 style applications. It provides multiple ways for AJAX (Asynchronous JavaScript And XML, a technology to add interactivity to web pages) support -- from drop-in JavaScript-less AJAX components, AJAX-enabling existing JSF components, to a custom JavaScript library that provide direct access to Seam server components from the browser as Javascript objects. Internally, Seam provides an advanced concurrency model to efficiently manage multiple AJAX requests from the ...
    Categories
    JBoss Seam
Page 6 of 48 FirstFirst ... 4567816 ... LastLast