JADE (programming language): Difference between revisions
m Reverted edits by 203.131.156.2 (talk) to last revision by 202.124.123.107 (HG) |
m Minor copy edits. Templates added: reflist, official website. Links: decapitalized non-proper nouns, removed needless piping, updated, added. External links: removed 3 references to same website. |
||
| Line 1: | Line 1: | ||
[[Image:Jadelogo.PNG|thumb|The JADE logo]] | [[Image:Jadelogo.PNG|thumb|The JADE logo]] | ||
'''JADE''' is an [[object-oriented]] software development and deployment platform. It has its own programming language that exhibits a seamlessly integrated [[application server]] and | '''JADE''' is an [[object-oriented]] software development and deployment platform. It has its own programming language that exhibits a seamlessly integrated [[application server]] and [[object database]] management system. It is designed to be an end-to-end development environment, which allows systems to be coded in one language from the [[database server]] down to the [[client (computing)|clients]]. It also provides APIs for other languages, including [[.NET Framework]], Java, [[C (programming language)|C]]/[[C++]] and [[Web service]]s. | ||
As a programming language, its main competitors are [[Java (programming language)|Java]] and [[C Sharp (programming language)|C#]], while as a database it competes with other object-oriented databases and [[post-relational database]]s such as [[Versant corporation|Versant]], [[Caché (software)|Caché]] and [[Matisse (DBMS)|Matisse]] as well as traditional relational database software packages such as [[Oracle database|Oracle]] and [[Microsoft SQL Server]]. | As a programming language, its main competitors are [[Java (programming language)|Java]] and [[C Sharp (programming language)|C#]], while as a database it competes with other object-oriented databases and [[post-relational database]]s such as [[Versant corporation|Versant]], [[Caché (software)|Caché]] and [[Matisse (DBMS)|Matisse]] as well as traditional relational database software packages such as [[Oracle database|Oracle]] and [[Microsoft SQL Server]]. | ||
Using the JADE platform requires per-process fees to be paid. A free limited licence is available for development. | |||
==Language== | ==Language== | ||
In | In syntax, JADE is very similar to [[Pascal (programming language)|Pascal]]; its syntax is based on the language [[Modula-2]], which was derived from Pascal. As a newer language, JADE includes innovations lacking in Pascal or Modula-2, however it lacks certain features of other modern object-oriented languages such as C# and Java. | ||
===Programming model=== | ===Programming model=== | ||
Like all of the other popular programming languages used to create database-driven software, JADE is [[object-oriented programming|object-oriented]] | Like all of the other popular programming languages used to create database-driven software, JADE is fully [[object-oriented programming|object-oriented]]. JADE was designed to have all the most important features of object-oriented programming, but it was also designed to make programming simple, and so does not exhibit the full range of tools that some other languages do. For example, JADE does not support the overloading of methods or operators. This may seem like a big loss to some programmers, but for programming database applications which is what JADE is designed for, the parts that are left out do not end up being major drawbacks, as they are almost never needed. One notable feature that JADE lacks is parameterised constructors and this leads to some dangerous consequences in that one can never know if an object has been properly initialized. | ||
Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespace (computer science)|namespaces]] in .NET, but they are much different in the fact that schemas have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[ | Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespace (computer science)|namespaces]] in .NET, but they are much different in the fact that schemas have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[model-view-controller]] methodology, as model classes can be put in one schema, then the controller and view classes can be built on top of the model classes in a subschema. | ||
===Program structure=== | ===Program structure=== | ||
JADE applications are structured quite differently from most programming languages in the fact that JADE programs are ''not'' developed by writing code into long files and then compiling all the files together | JADE applications are structured quite differently from most programming languages in the fact that JADE programs are ''not'' developed by writing code into long files and then compiling all the files together at once. JADE programs are actually developed using a user interface that allows programmers to visually create [[class (computer science)|classes]] and define their properties and methods. Instead of locating methods in large files, programmers select the method they would like to edit and only the code for that particular method is displayed. Also instead of compiling all the code of a program at once, in JADE, each method is compiled individually as soon as the method is completed, meaning code can be checked immediately. | ||
All the code for a JADE application is stored in its object-oriented database. This has | All the code for a JADE application is stored in its object-oriented database. This has several advantages. First, it allows for multi-user development, as the database maintains concurrency control. Second, with each piece of the code being a separate object in the database, in a lot of the cases it is possible to recode the system while it is live and online as long as the parts of the system being changed are not in use. | ||
==Features== | ==Features== | ||
| Line 27: | Line 27: | ||
There are very few differences between manipulating transient and persistent objects. It has been said that JADE makes it ''appear'' to the programmer as if all the objects in the entire database were in local memory. Most of the time, JADE's object-oriented database is used in a multi-user system, and so this statement could be extended to say that JADE makes it appear to the programmer as if all the objects in the database were stored in some shared memory that all users connected to the system could access, even from different computers. | There are very few differences between manipulating transient and persistent objects. It has been said that JADE makes it ''appear'' to the programmer as if all the objects in the entire database were in local memory. Most of the time, JADE's object-oriented database is used in a multi-user system, and so this statement could be extended to say that JADE makes it appear to the programmer as if all the objects in the database were stored in some shared memory that all users connected to the system could access, even from different computers. | ||
With all of the program code centralised on the database server as well the data, JADE achieves its goal of an end-to-end system, as JADE presents such a level of abstraction that all | With all of the program code centralised on the database server as well the data, JADE achieves its goal of an end-to-end system, as JADE presents such a level of abstraction that all client nodes can be programmed as if they were running on the database server. This is very desirable to most database programmers as they don't have to take several different technologies and link them together, they just create one application for everything. | ||
JADE's database is also inherently object-oriented, and so it eliminates the performance loss in an [[object-relational mapping]] system where objects must constantly be converted from | JADE's database is also inherently object-oriented, and so it eliminates the performance loss in an [[object-relational mapping]] system where objects must constantly be converted from object-oriented form to relational form. Like all other commercial database products, JADE is ACID-compliant and has all of the standard features such as atomic transactions, locking, rollback, crash recovery and the ability to keep one or more [[secondary database server]]s synchronised with the main database for backup, disaster recovery and performance reasons. | ||
JADE also provides a Relational Population Service that enables | JADE also provides a Relational Population Service that enables automatically replicating objects from the main database to one or more [[relational database]]s. This allows JADE systems to interoperate with relational databases for reporting, [[business intelligence]] and [[data warehouse]] purposes. As of 2010, the relational databases supported by this feature are Microsoft SQL Server 2000/2005/2008. | ||
===Three-tier model=== | ===Three-tier model=== | ||
Often for database-driven software, the [[ | Often for database-driven software, the [[three-tier (computing)|three-tier]] methodology is followed. This involves applications being split into three tiers — data storage, processing and presentation. In the data storage and processing tiers, JADE systems are a collection of co-operating servers, called [[node (networking)|nodes]], and multiple nodes may be involved in each tier. Each type of node has a different name and all are capable of manipulating objects and executing business logic. A collection of nodes can be deployed across one or several machines. Database servers handle data storage and can also execute business logic, while application servers handle processing. In a three-tier model, presentation clients provide the user interface. JADE also provides a two-tier client that combines the abilities of an application server and presentation client. Traditionally, these three tiers would be created by combining three programs and having them communicate to form one system. Having the different programs separate like this has many advantages, the main one is that the system becomes scalable, that is, raising the power of the system involves simply adding more nodes. | ||
Designing a system like this gives the programmer a decision to consider every time they want to code in a particular function. They need to decide whether the function would run best on the database server, application server or presentation client before they begin coding as it will be difficult to change that decision once the functionality is coded into one of the tiers. | Designing a system like this gives the programmer a decision to consider every time they want to code in a particular function. They need to decide whether the function would run best on the database server, application server or presentation client before they begin coding as it will be difficult to change that decision once the functionality is coded into one of the tiers. | ||
| Line 49: | Line 49: | ||
====JADE Forms==== | ====JADE Forms==== | ||
JADE Forms applications are made up of forms, as the name suggests. Clients need to connect through the JADE | JADE Forms applications are made up of forms, as the name suggests. Clients need to connect through the JADE Smart [[thin client|Thin Client]] or Standard Client to be able to run applications that use JADE Forms. | ||
The | The Smart Thin Client works by connecting to an Application Server which generally does all the processing on behalf of the Smart Thin Client, meaning the thin client only needs to be responsible for displaying forms and taking input. This means the computer running the thin client does not have to be a very powerful computer, and it does not require a fast network connection as it is not loading data from the database — JADE thin clients are often run over a dial-up connection. This is the reason they are called thin clients, as there is not a heavy requirement on computational power to run these clients. | ||
The | The Standard Client is just the Smart Thin Client combined with the Application Server on one machine. In this case, the node running the client does all of the processing as well as the presentation. Standard clients have greater demands on computational power than thin clients, as they must load data from the database as well as do their own processing. | ||
The advantages of using JADE Forms include: | The advantages of using JADE Forms include: | ||
| Line 63: | Line 63: | ||
* Cannot reach a worldwide audience as is possible on the World Wide Web. | * Cannot reach a worldwide audience as is possible on the World Wide Web. | ||
JADE Forms have an interesting twist to them though. It is actually possible to run a JADE Forms application through a web browser by changing its mode to | JADE Forms have an interesting twist to them though. It is actually possible to run a JADE Forms application through a web browser by changing its mode to ''web-enabled''. When this happens, JADE automatically generates HTML code to make pages that resemble the forms and [[widget (computing)|controls]], without any modifications to the code. This is a very quick way for programmers that are not competent with HTML and other web technologies to deliver a program through the web. | ||
====HTML documents==== | ====HTML documents==== | ||
| Line 76: | Line 76: | ||
====Web services==== | ====Web services==== | ||
[[Web | [[Web service]]s are used to allow different programs to communicate with each other from remote locations in an object-oriented form. Web services cannot be accessed directly by human users. One of the uses of Web services with JADE is to allow other technologies such as .NET or Java to use JADE as the backend object-oriented database. Web services also allow JADE systems to interoperate with services provided by other non-JADE systems. | ||
====Interoperability==== | ====Interoperability==== | ||
In addition to Web services, JADE is also capable of interfacing with other programs through language APIs (including .NET, Java, C/C++), DLL calls, ActiveX/COM objects and .NET assemblies. This allows other programs to access objects and execute methods, and can be used to provide a different interface to a JADE application. JADE 6.2 provided a Java API, .NET Assembly integration and the ability to run Smart Thin Clients on Windows Mobile devices. JADE 6.3 provides an API for .NET languages. | In addition to Web services, JADE is also capable of interfacing with other programs through language APIs (including .NET, Java, C/C++), DLL calls, ActiveX/COM objects and .NET assemblies. This allows other programs to access objects and execute methods, and can be used to provide a different interface to a JADE application. JADE 6.2 provided a Java API, .NET Assembly integration and the ability to run Smart Thin Clients on Windows Mobile devices. JADE 6.3 provides an API for .NET languages. | ||
===Multilingual | ===Multilingual abilities=== | ||
JADE natively supports [[multilingual]] programs. It does this in several ways: | JADE natively supports [[multilingual]] programs. It does this in several ways: | ||
* Strings can be marked as | * Strings can be marked as ''translatable'', which means they will be change depending on the current language. | ||
* Many versions of the same form can be created to suit each language. This means interfaces can look entirely different from one language to the next. | * Many versions of the same form can be created to suit each language. This means interfaces can look entirely different from one language to the next. | ||
* The developer has methods available to access the current [[locale]] of the system and so they can implement their own language-dependent features. | * The developer has methods available to access the current [[locale]] of the system and so they can implement their own language-dependent features. | ||
| Line 113: | Line 113: | ||
==History== | ==History== | ||
JADE was originally conceived by [[Gilbert | JADE was originally conceived by Sir [[Gilbert Simpson]] and is currently developed by the Jade Software Corporation.<ref>[http://www.jadeworld.com Jade Software Corporation]</ref> | ||
The first version of JADE was JADE 3, released September 1996. | The first version of JADE was JADE 3, released September 1996. | ||
| Line 123: | Line 123: | ||
* [[Object-oriented programming]] | * [[Object-oriented programming]] | ||
* [[Object database]] | * [[Object database]] | ||
==References== | |||
{{Reflist}} | |||
==External links== | ==External links== | ||
* {{official website|http://www.jadeworld.com}} Jade Software Corporation | |||
* | |||
===Tutorials and resources=== | ===Tutorials and resources=== | ||