5 JDeveloper Tips February 6
Here is an unsorted list of 5 simple JDeveloper tips to help speed things up and prevent unexpected problems.
1. After updating your code from a repository, do a clean and a rebuild, especially if changes are made to the JPR files.
Example: We started getting a JAZN Runtime exception:
oracle.security.jazn.JAZNRuntimeException: JBO-25002: Definition com.demo.model.MyView of type View Definition not found
As it turned out, the views had been updated and JDeveloper had not picked up on all of the changes, after a clean, a rebuild and another test, everything worked as expected.
2. After changing a property in the properties panel, click on another property or press enter so that JDeveloper recognizes the change. If you just move on to another file with changing the field you are on and causing a value change event to occur, it will not register the change you made.
This problem is actually resident in many web and Java based systems mostly because the events provided by JSF and Swing never recognize value changes if you leave the component that caused the change.
3. Use the BC Browser. I wrote an earlier blog post about it and why it is important. Basically it allows you easily test the ADF BC layer in your project. Since the Model layer is the basis for the rest of the application, it’s an important tool.
4 . Log out of the Version Control repository you are using. JDeveloper is constantly rechecking the server to see what has changed and update the “Pending Changes” list in the project. This can cause a lot of unnecessary overhead if you aren’t waiting around for a particular update to be made. Logging out fo the Version Control server will prevent that from happening.
5. Increase the memory allotted to the embedded OC4J server. Often you will be testing your application using the embedded server and it’s default settings are not adequate for most real projects. You can increase the default memory allocation by right-clicking on your ViewController project, select “Project Properties”, “Run/Debug/Profile”, Edit the existing profile or add a new profile to select. In the profile, select “Launch Settings” and in the input box for Java Options add the options “-Xmx512m -XX:MaxPermSize=256M” or whatever you deem appropriate.