Examples

JED (Java Editor for DataTables) performs on the server side handling the business logic of our web applications. The examples provided here are focused on variations of server side setups to meet the requirements for most scenarios. These examples are by no means the only examples. For other examples that are more focused on the client side involving DataTables, we recommend you visit SpryMedia's website for DataTables and Editor.

All examples on this website adhere to the latest version of DataTables v1.10.# and Editor v1.5.# series. Two new features, multi-row editing and file uploads, are supported by JED.

If you're relatively new to web application development and are looking for a quick "Getting Started Guide" on setting up a web application using JED, click the book icon: java datatables examples and getting started guide

JED has been designed to provide extra versatility allowing the programmer to access their database without involving DataTables on the client side. There are times when you have a web page that has form fields that you want to populate with data from your database. Below are a number of examples that demonstrate how you can use JED in more general use case scenarios.

As you browse through each example, note that there is a separate tab labelled simply Java which references the controller Java Server Page. In a production environment you will likely want to use a Servlet instead. Java Server Pages are used as our controller scripts for demonstration purposes only so that the source code can be viewed under the Java tab.

NOTE: The example descriptions provided on this website are intended for an audience familiar with programming languages: HTML, JavaScript/JQuery, and Java. The general viewing audience may be unfamiliar with some of the terminology discussed. However, you are still welcome to experiment with the examples, as they may suite your needs for any project you may have in mind. Note also, that all examples involving Server Side Processing will work on an Oracle database but on the minimum version release 12c. Prior to version 12c, Oracle did not support the limiting of records as MySql does with the "LIMIT" clause in their SQL syntax. The ability to filter for a limited number of records is integral in Server Side Processing, so we are happy to see that Oracle has finally provided us with this important feature.

Please note that the database which is used for these examples is reset after every Session closes.