Oracle JDeveloper 12c Released

During last week, the Oracle JDeveloper 12c was publically released, finally joining the two branches of ADF back into a single framework - at least for the most part. JDeveloper 12c (12.1.2.0.0) is a major release, bringing support for an corresponding new Fusion Middleware release 12.1.2, as mentioned on the New Features Document Just to refresh our memory let's review the JDeveloper version history:

Back in june 2011, JDeveloper 11.1.2.0 - 11g R2 was released, and later updated up to version 11.1.2.4.
This branch was always a bit special and was considered "preview of what is to become 12c". It brought us many new features, such as:
  • JSF 2.0 support
  • improved hot deployment
  • improved IDE performance
  • ADF essentials
  • ADF Mobile
At the same time, R1 progressed as well with PS5 and PS6 releases in 2012 an 2013. It also included some really nice features, such as:
  • new skin
  • new data visualization components (treemap, suburts, timeline...)
  • paging in tables
  • support for oracle public cloud

The problem was, that developers could decide to either have the new features from one or the other branch, leaving some goodies behind. That finally ends with the 12c release for the most part. Let's review some scenarios and see which version should you use at the moment:

We are an ISV developing a stand alone ADF application, which is going to be deployed on premise.
In this case it makes sense to use JDeveloper 12c and get the best from both worlds. Even if you are extending your web application with ADF Mobile application later on, you will have no problems as ADF Mobile is only using standard SOAP/REST web services to communicate with your 12c ADF application.

We want to develop ADF Mobile application and deploy it on iOS and Android.
You need to use JDeveloper 11.1.2.4 for the ADF Mobile application. It does NOT mean your web/back-end application needs to be developed with this version though.

We are developing SOA/BPM/Portal application
In this case, you need to stay with 11.1.1.7 for a while, as Oracle Fusion Middleware 12c has not been released yet.

We want to develop an ADF application and host it on the Oracle Public Cloud
Oracle Public Cloud only supports ADF R1/PS5 at this time, so you should develop your application with JDeveloper 11.1.1.6

I am a developer and I would like to use ADF for my project, but I don't have the budget for WebLogic server
We have a free version of ADF called ADF essentials, and it has been updated to 12c. You can use that and deploy your application on GlassFish.

Here is a version map which can help you make the right decision:

jdev12c-vmap

Find out more on the new release of Oracle JDeveloper 12c checking out this brief Development Experience Demo and make sure to download for free at http://oracle.com/jdev

Provided by Oracle FMW Evangelist Jernej Kase jernej.kase@oracle.com

Bookmark and Share

Comments:

Hi Jernej,

Thanks for your sharing your experience and interesting important information. Regarding to hosting ADF applications in Oracle Public Cloud it is also possible to use JDeveloper 11.1.1.7. This JDeveloper Version has been included Cloud SDK. Consequently you don't need 11.1.1.6 any more.

Regards,
Volker

Posted by Volker on July 17, 2013 at 07:32 AM CEST #

Hi Volker,

Indeed the Oracle cloud SDK is included in 11.1.1.7 and even 12c. But beware - the ADF binaries on the Oracle Public Cloud are 11.1.1.6.

This means you should not deploy your 11.1.1.7 app to the cloud. This version brought some new components, such as sunburst and timeline, the new skyros theme and more.

What happens when you deploy 11.1.1.7 app using those components to the cloud? The application breaks. I've created a simple demo page with sunburst component and this is the result:

OracleJSP error: oracle.jsp.parse.JspParseException:
/helloWorld.jspx: Line # 14, <f:facet name="center">
Error: http://xmlns.oracle.com/dss/adf/faces:sunburst is not a registered tag in the specified namespace.

So, until further notice you should still use 11.1.1.6 for the Oracle Public Cloud.

Posted by Jernej on July 17, 2013 at 10:12 AM CEST #

Thanks Jernej,

"We are developing SOA/BPM/Portal application
In this case, you need to stay with 11.1.1.7 for a while, as Oracle Fusion Middleware 12c has not been released yet"

Maybe it should be "...as Oracle Fusion Middleware 12.1.3 has not been released yet" or "...as a full Oracle Fusion Middleware has not been released yet"?

Regards Peter

Posted by Peter Lorenzen on July 17, 2013 at 04:55 PM CEST #

Hi Peter,

you are correct, I should refer to "the full Oracle Fusion Middleware stack".

We have what is now called Cloud Application Foundation (WebLogic, Coherence, ...) 12c, but SOA, BPM & Webcenter 12c have not yet been released.

Posted by Jernej on July 26, 2013 at 09:04 AM CEST #

Hello i followed the instruction on this link to build Android App with Jdeveloper 12c .During my deployment on my emulator Jdeveloper gave me this error:

[05:57:57 PM] Signing application...
[05:57:57 PM] Command-line executed: ["C:\Oracle\Middleware\Oracle_Home\oracle_common\jdk\bin\jarsigner", -keystore, "C:\Program Files\Java\jdk1.7.0_11\bin\Omile.keystore", -storepass, madu123, -keypass, madu123, -digestalg, SHA1, -sigalg, MD5withRSA, "C:\JDeveloper\mywork\Employees\deploy\Omile\Employees.apk", Omile]
[05:57:57 PM] jarsigner: Certificate chain not found for: Omile. Omile must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.
[05:57:57 PM] Command-line execution failed (Return code: 1)
[05:57:57 PM] Command-line executed: "C:\Oracle\Middleware\Oracle_Home\oracle_common\jdk\bin\jarsigner" -keystore "C:\Program Files\Java\jdk1.7.0_11\bin\Omile.keystore" -storepass madu123 -keypass madu123 -digestalg SHA1 -sigalg MD5withRSA "C:\JDeveloper\mywork\Employees\deploy\Omile\Employees.apk" Omile
[05:57:57 PM] Deployment cancelled.
[05:57:57 PM] ---- Deployment incomplete ----.
[05:57:57 PM] Deployment failed due to one or more errors returned by 'C:\Oracle\Middleware\Oracle_Home\oracle_common\jdk\bin\jarsigner'. The following is a summary of the returned error(s):
Command-line execution failed (Return code: 1)

Posted by guest on September 23, 2014 at 12:47 PM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Oracle ECEMEA Partner Hubs Migration Center Team

We share our skills to maximize your revenue!
Rapidly and successfully assist you to adopt and implement the latest of Oracle Technology in your solutions.

Stay Connected
partner.imc
@
beehiveonline.oracle-DOT-com
Google+ Subscribe by Email

Search

Archives
« July 2015
SunMonTueWedThuFriSat
   
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
       
Today