One of the most heard questions is what is the different from Oracle JET with Oracle ADF? Will the one replace the other? Or will they coexist next to each other? All very valid questions, for now they will coexist next to each other. Oracle supports and invests in both products, focusing on a different kind of developer and a different kind of tool. You can see this in their own product as well, as a rule of thumb Oracle builds their SaaS application with the ADF and their PaaS applications with JET.
The biggest difference between the two is that ADF protects you from the underlying technology, works in a declarative way and is a server side framework. Oracle JET is more on the edge, as you would expect, from a JavaScript toolkit, more code centric and a pure client-side toolkit.
They share a lot of the same components and the Oracle DVT components work also in JET, this means the same DVT components work in Oracle ADF, MAF & JET. JET is based on libraries such as JQuery, JQuery UI & KnockOut, therefore you can use the key features (like 2 way binding) out of these libraries in JET as well. Behind the scenes Oracle has worked on this project for over 2 years, with the same development teams as the teams that work on ADF Faces & DVT’s.
JET is a modular toolkit in which you can pick ‘n mix your own JS libraries to extend more capabilities. Oracle has also build in support for internationalization & accessibility.
For now the use of Oracle JET is only for “the lucky few”, it comes with a Restrictive Use License (RUL) if you are using one of the few Cloud products (MCS, JCS, DevCS, ABCS: more on these in later blogs) Oracle offers today. However, they are looking for open source possibilities under the Apache 2.0 license. That they are working on open sourcing, but they did not give a timeframe on this yet. The release cycle of JET will be aimed at a minor release every two months and a major release every six.
So where do you start? First of all, make sure you check out the Oracle JET page for more cool stuff. Here you can find explanations, tutorials and code samples, there are cookbooks where you can check out the JET components and see the JavaScript and HTML code for these components. This tool works both ways, so you can copy and paste your JET component code in there as well to see the component it would generate!
You can use any code editor you prefer, whether this is Agnostic, NetBeans or some other IDE. They do however have build in support in the latest release of NetBeans, so it might be wise to let that be your weapon of choice.
Last but not least, Oracle Application Builder Cloud Services (ABCS) is fully build in Oracle JET, but it also produces Oracle JET code. So when you use the ABCS to create user interfaces, you can get the underlying JET code and continue working on that as a developer.
No comments:
Post a Comment