Oracle JDeveloper and Oracle ADF Blog

  • September 18, 2012

Help Improve Oracle Products Usability at OOW

Shay Shmeltzer
Director of Product Management - Oracle

We already wrote about all the great ADF related activities at OOW. But we wanted to also let you know about an additional activity you can participate in at OpenWorld:

Oracle Middleware User Experience team will be conducting
focus groups and customer feedback activities at Oracle
OpenWorld 2012 (Oct. 1st - Oct. 3rd). Customer participation
helps Oracle develop outstanding products and solutions.

of all types are invited to participate: Directors,
& Product Managers,
Sales, Human Resources, Marketing, Recruiters, Budget
Managers,  and more.

participate in these sessions you do not have to be
registered for Oracle OpenWorld.**

you or someone you know is interested in participating, please
email muxtesting_us@oracle.com
with the following information:





Number (work, mobile, include country code):

Join the discussion

Comments ( 2 )
  • guest Sunday, November 25, 2012

    If you're interested in JDeveloper usability, it would be a good idea to start with the User's Manual and the JDeveloper download package so I don't have to spend countless hours discovering where the installation put the Java EE kernal files and how to get JDeveloper to recognize them. Then you can stream line and improve your user interface.

    Why do you have multiple places to manage libraries and why is the interface for Managing Libraries so unintuitively designed, including choice of names. For example, the user's manual says I can add extentions. Do they mean JAVAX? After all this is a Java EE dev tool.

    The manual goes into great detail about adding libraries out of project scope and I don't see equivalent sections for adding libraries within project scope. When I attempted to add an external (evidently this means to all users and applications), JDeveloper puts the jar into the User folder instead. At least the developer could have put up a message saying why it did that.

    Here is what someone wrote on the following website:


    "Although JDeveloper provides loads of libraries out-of-the-box, you often need other libraries in your application. You can easily add these libraries via the project properties. This provides two options: ‘Add Library’ and ‘Add Jar / Directory’. We normally us the Add Library option because it allows to include the JavaDoc and the source code. However make sure that you check the ‘Deployed by Default’ checkbox or else the library will not be included on the classpath and the application will fail with a java.lang.ClassNotFoundException. By the way, we never use Tools -> Manage Libraries because we only use project libraries and never the user or system libraries, because they introduce local dependencies that need to be maintained at every workstation seperately."

    Evidently they don't think too much of managing libraries outside project scope.

    Notice they call extension files 'system files'. While I wouldn't have named it this, it makes a lot more sense than "extension".

    Why does the sample app included with JDeveloper (MyFirstApplication) throw up errors saying it can't find the faces.bean files. Evidently the JDeveloper installer didn't put the J2EE kernal files in the correct place so this didn't happen.

    The user's guide is supposed to be the safety net and it appears the design team didn't sit down with some JDeveloper greenhorns to do a USEABILITY STUDY on how well they did.


  • Shay Monday, November 26, 2012

    guest - The tools-Manage libraries allow you to create libraries that you'll be using in multiple projects. This way you only need to define them once and then you can just add them to every project that requires them.

    Those libraries can be on shared drives so to not create machine specific location dependencies.

    Can you clarify what do you mean by "Java EE kernal files and how to get JDeveloper to recognize them." and also - what step in the tutorial failed for you? We do test the tutorials and make sure they work if you follow all the instructions in them. Could it be that when you created the project you didn't add the JSF as project features (step 4)?

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.