shortbut key for Jdev IDE

  1. Go to file in navigator : Alt+Home
  2. Find Usages Ctrl+Alt+U
  3. Go To Java Type Ctrl+Minus
  4. Go To File Ctrl+Alt+Minus
  5. Show Overview Ctrl+Shift+ Back Quote
  6. Extract Method Ctrl+Alt+X
  7. Introduce Variable Ctrl+Alt+V
  8. Run Project F11
  9. Debug Project Shift+F9
  10. Quick JavaDoc Ctrl+D
  11. Reformat Ctrl+Alt+L
  • Search
  • Code Highlight Ctrl+Alt+H
  • Clear Code Highlight Ctrl+Alt+K
  • Auto Code Highlight (this makes the code always highlighted)
  • View
  • Structure Ctrl+Shift+S
  • Property Inspector Ctrl+Shift+I
  • Component Palette Ctrl+Shift+R
  • Break Point Ctrl+Shift+R
  • Miscellaneous
  • Copy Path Ctrl+Shift+C
  • Go To Line Ctrl+G
  • Go To Window Ctrl+F6
  • Go To File Ctrl+Alt+Minus
  • Build
  • Make Project Ctrl+F9
  • Rebuild Project Alt+F9
  • Run
  • Resume F9
  • Step Over F8
  • Step Into F7
  • Step Out Shift+F7
  • Java Editing
  • Organize Imports Ctrl+Alt+O
  • Select in Navigator Alt+Home

Jdeveloper On Linux



Here some quick tips for Jdeveloper running on linux as it might not as convienetn as the windows version, so you do not need to check the install guide pages.

1. start jdev —


2. To access the quick start –


From quick start you can start jdev, can also go to config page to create/extend your jdev’s domain servers.

3. uninstall  –


4. page to get all the jdev extenstions by manually download.

The reason you should know this – because of sometimes you can not access the jdev update site to get all the downloads for your jdev extension.

Such as SOA editor extension or webcenter extension from oracle internall site, you can go to this page to manually download zip file and to extend your jdev.

Problem: unable to initialize credential store

By W.ZH  Jan 2009



when I migrate a sample project from 10g or 11g to my version 11g jdev, every thing looks fine and project migrated, but when you try to run it, you will see the JDBC connection error in log (password null), and also you will see that if you change or even open the DB connection and then try to save it, get an error of “unable to initialize credential store.”

Possible solutions from OTN forum:


This looks like a corrupted cwallet.sso file. It happens sometimes that this file, which holds the credentials of the connections and roles.

This file is located in the src/META-INF folder. It can be recreated if you close JDev, delete (or rename) the file and start JDev again. Then you have to add the connection to the applications again. This should recreate the cwallet.sso file.(W.Zh: I found there are two sso  and
jps-config.xml files in my project. i think this is a migration issue.)

To my knowledge this should not happen in JD11. This cwallet.sso problem was first discovered in TP4 (frequently), where the file got corrupted when you interrupt starting the embedded server.

This has not happened to me since JDev I just remember this when I saw you error.



I’ve figured a solution for this bug.

– Creating a new application

– Creating a new connection in the app ressources (now it’ll work : no “Unable to initialize credential store”)

– Copying Model and ViewController project from previous application




Hi. I recently got JDev and when I opened my current project, it was migrated from JDev and I got the same problem. I solved this checking
jps-config.xml file, fixing the security context. I don’t know why it was incorrectly set after migration. After I fixed and set up correctly the security context, I just tested my connection, retype password and save. That’s all. I think it doesn’t have relation with cwallet.sso file in this case.

Hope this resolution be usefull for somebody.


W.ZH:  I slove my problem by method 2 (This time OTM forum can have answers ;-)).  Jdev 11g seems need some time to get mature.

How to install the JDeveloper 11g

By W.ZH Oct 2008

  • Please note Project in Jdev 10g can not migrate to 11g except the JDeveloper only. So you have to migrate to version first, then migrate to 11g.
  • ADF 11g applications require a Java EE 5 container. To date, only Oracle WebLogic Server 10g (10.3) is certified, and we plan to support JBoss and Tomcat as well. Note, OC4J 10.1.3 and/or OAS 10.1.3 is not fully Java EE 5 compliant, and ADF 11g applications will not work in that environment.