The JavaEE Xperience

This is on JDeveloper 11.1.1.3. YMMV

1. ojdeploy does not understand “nocompile=false”

   If you have the nocompile property set, then ojdeploy does not compile your project no matter what the value of the property.

2. ojdeploy does not like relative paths in the properties

   For e.g., my workspace path was getting constructed as “C:\folder\build\..\MyApp\MyApp.jws”. That didn’t work – ojdeploy did not create the task-flow-registry file. I had to make sure that the workspace path was “C:\folder\MyApp\MyApp.jws”

3. Chris Muir reports on OTN that there is a bug cos of which ojdeploy is case-sensitive to Windows paths as well. http://forums.oracle.com/forums/thread.jspa?messageID=9119712#9119712. Come to think of it, this could’ve been the root cause for my point 2 failure.

Oracle’s technical preview of JDeveloper 11g has been out for sometime now. Having been using ADF, the first thing to do was to check out the new ADF Rich Client (RC) components. They are almost the same uber-cool Faces components but now with the “rich” experience. Ofcourse, you can choose to stick to the Trinidad (erstwhile ADF Faces) components if you don’t want the rich UI. After seeing the power and cool-factor of RC, I doubt you would want to do that though. Read the rest of this entry »