OraNA :: Oracle News Aggregator

In this blog I will show you what you need to do to make this work. You need to know a litte bit about MDS and ADF security, for more info read my previous blog.
The ADF Query panel not only displays the attributes of the viewobject but also the viewobject criteria's. For this I created a new criteria called SalaryCriteria. To do this yourself we have to open the viewobject, go to the query part and there we see the defined criteria's.
In this editor you can create a complex where clause. The bind variables you use in this criteria are displayed as search attributes in the ADF Query Panel.

When we press save in the Query Panel we get a dialog where we can save the search

In the top right of the Query Panel you can select your own saved searches or the view criteria's

Here you see what is happening when you save a search. ADF creates a persdef folder and in this folder ADF makes a copy of the used viewobject and adds the new search criteria to it. ADF does the same thing as we did manually in the viewobject.

Now that BEA and WebLogic are part of Oracle, what is going to happen to the yearly conference BEA held for developers?

Well it got merged into the Oracle Develop conference this year at OOW.

Last month when I posted my previous entry on this year's Oracle Develop conference, I said we have 135 sessions in the conference - turns out we actually have 188 sessions according to the content catalog.

Most of the sessions that got added have to do with WebLogic/BEA products.
A quick search on "WebLogic" brings back over 25 sessions and hands-on labs and seraching for JRockit will bring more.

So if you are a WebLogic developer, we hope you'll join us this year at Oracle Develop and OOW.

The ROWTYPE example will have to wait a bit, as i got a question for an example using an object type parameter when calling a stored procedure. So here goes…

I’ll admit upfront, i haven’t gotten this working the way i want it yet. I would like iBatis to map my object to the oracle object, but i couldn’t get that working. Instead i have kind of a workaround: i’ll instantiate the object type in some plsql code in my sqlMap configuration.

Here’s the sql code i’m going to execute. First the object type:

CREATE OR REPLACE type employee_obj
AS
  object (
    id             NUMBER(10)
  , name           VARCHAR2(100)
  , date_of_birth  DATE 
  )
/

The plsql stored procedure looks like this:

procedure save_employee_obj (
    p_emp in employee_obj
  ) is 
  begin
    insert into employees (
      id
    , name 
    , date_of_birth
    ) values (
      p_emp.id
    , p_emp.name
    , p_emp.date_of_birth
    );
  end;

The workaround in the sqlMap configuration file looks like this:

<procedure id="insertEmployeeObj"
             parameterClass="nl.iteye.ibatis.example1.Employee">
    <![CDATA[
      { call
          declare
            l_emp employee_obj := employee_obj(#id#,#name#,#dateOfBirth#);      
          begin
            employee_pkg.save_employee_obj(l_emp);
          end
      }
    ]]>
  </procedure>

I use iBatis’ # notation to map to parameterClass properties to a new object type instance.

Now i can call the stored procedure in my java application like this:

Employee emp = new Employee(
    new Long(5)
  , "Stefan"
  , (new GregorianCalendar(1992,Calendar.JUNE,15)).getTime()
  );
sqlMapper.insert("insertEmployeeObj", emp);

Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Java, Database, Oracle, ORM, Open Source

Oracle ADF Business Components

The first version of Oracle ADF Business Components say the light of the world with JDeveloper 3. It was created to address the deficiencies of the EJB 1.1 specification. Although named Business Components this is a framework to create Business Components (for Java). ADF Business Components are usually referred ADF BC or BC4J. I will try be consistent but bear with me if I mix both.

Entities and Views and Application Modules

Like any other ORM framework ADF BC has its own names for the same concepts. The primary concepts are Entities, Views and Application Modules. Entities are usually considered as the representation of a table row in the database, while Views are manipulating the Entities (creating, updating, retrieving, and deleting). While Views work on Entities you need an Application Module to work with the Views and with the data in the database. The Application Module contains all the Views that are need for this module and the necessary information of the underlying database.

Implementing the ADF BC Model Layer

As in the two previous model layers we are reusing the data model created in the database. This is also a strength of ADF BC, working with existing database model instead of creating it from scratch. (As both approaches have their pros and cons, a seperate entry to show these is quite likely.) Like before we're following the same order of steps for JDeveloper 10.1.3 and 11g:

• Create a Model Layer Project
• Import the Database Objects

Steps for JDeveloper 10.1.3

Step 1: Create a Model Layer Project

• To create a new Model Layer Project select OnlineSurvey in the Application Navigator, open the Context Menu and chose the New Project... menu entry.
• In the New Gallery select an Empty Project and click on OK.
• In the Create Project window set the Project Name to ModelBC and click on the OK button.
• Select the newly created ModelBC project in the Application Navigator and open the Project Properties window with a double-click.
• In the Project Properties window, check the values of Project Content and make sure that the Default Package is set to demo.survey.model.bc. Click OK to close this window.
• Click on the Connections Navigator. Expand the Database folder, select the survey entry and open the Context Menu. From it select the Properties... entry to open the Edit Database Connection window. Click on the Authentication tab and check whether the Deploy Password check box is checked. If not, make sure that it is checked! ADF BC relies on it.

Step 2: Import Business Components from Tables

Select the ModelBC project in the Application Navigator. Open the New Gallery from the Context Menu -> New .... In the New Gallery expand the Business Tier and select ADF Business Components. On the right-hand side select Business Components From Tables and click on the OK button.

• In the Initialize Business Components Project window select the survey connection and accept the default values for the SQL Flavor and Type Map (both should be Oracle). Click OK and the OK button on the Login window.
• In the Create Business Components From Tables wizard step 1, click on the Query button to get all available tables. Once the table names appear, select all of them. Move all entries from Available to Selected, by clicking on the >> button. Like in the other model projects we change the names from plural to singular names. Best is to do it right now by selecting each line in the list and change the appearing value in the Entity Name text field, eg Answers to Answer.
• Click Finish to end this wizard.

The wizard will now create the Entities and Association files in a single package. This is quite good at the first sight but really tedious if return to the project in three weeks. The naming for the Associations is hardly readable or memorable. Therefore we need to do two things:

1. Move the Associations and the Entities in separate package.
2. Rename the Associations with better readable names.

Move the files in separate packages is quite easy. Select all Entities, the ones without the Assoc suffix (Click on the file while holding the Ctrl-key). From the Context Menu select Refactor->Move... and type in the name demo.survey.model.bc.entities. After clicking on OK all files will be moved in the new package. You might be asked for creating the new package directory. This is perfectly OK. Repeat this for the Associations and move them into the package demo.survey.model.bc.links.

Warning! In JDeveloper 11g TP4 this might not finish. If this happens to you, the easiest bet is to kill JDeveloper 11g TP 4 and continue where it stopped.

Renaming the Associations to better readable names is as simple as moving the files. Only difference is that must do it file by file. In the demo.survey.model.bc.links package we select an Association, open the Context Menu, select Refactor, select Rename..., enter the new name and click on OK. We repeat this for all entries in the package and rename them according to the table below.

Steps for JDeveloper 11g

Note: During the course of this series a new version of the JDeveloper 11g has been released on OTN. I will follow every official release and you should do the same. If you've created the projects with an earlier version of JDeveloper 11g and reopen them in a newer release, it is possible that the project files have to be migrated. if JDeveloper asks you to do this, simply accept it.

Step 1: Create a Model Layer Project

• To create a new Model Layer Project select OnlineSurvey in the Application Navigator, click on the Applications Menu on the right-hand side select the New Project... menu entry.
• In the New Gallery select an Empty Project and click on OK.
• In the Create Project window set the Project Name to ModelBC and click on the OK button.
• Select the newly created ModelBC project in the Application Navigator and open the Project Properties window with a double-click.
• In the Project Properties window, check the values of Project Content and make sure that the Default Package is set to demo.survey.model.bc. Click OK to close this window.
• Expand the Application Resources accordion, expand the Connections folderm andexpand the Database folder, select the survey entry and open the Context Menu. From it select the Properties... entry to open the Edit Database Connection window. Check whether the Deploy Password check box is checked. If not, make sure that it is checked! ADF BC relies on it.

Step 2: Import Business Components from Tables

Select the ModelBC project in the Application Navigator. Open the New Gallery from the Context Menu -> New .... In the New Gallery expand the Business Tier and select ADF Business Components. On the right-hand side select Business Components From Tables and click on the OK button.

• In the Initialize Business Components Project window select the survey connection and accept the default values for the SQL Flavor and Type Map (both should be Oracle). Click OK and the OK button on the Login window.
• In the Create Business Components From Tables wizard step 1, click on the Query button to get all available tables. Once the table names appear, select all of them. Move all entries from Available to Selected, by clicking on the >> button. Like in the other model projects we change the names from plural to singular names. Best is to do it right now by selecting each line in the list and change the appearing value in the Entity Name text field, eg Answers to Answer.
• Click Finish to end this wizard.

The wizard will now create the Entities and Association files in a single package. This is quite good at the first sight but really tedious if return to the project in three weeks. The naming for the Associations is hardly readable or memorable. Therefore we need to do two things:

1. Move the Associations and the Entities in separate package.
2. Rename the Associations with better readable names.

Move the files in separate packages is quite easy. Select all Entities, the ones without the Assoc suffix (Click on the file while holding the Ctrl-key). From the Context Menu select Refactor->Move... and type in the name demo.survey.model.bc.entities. After clicking on OK all files will be moved in the new package. You might be asked for creating the new package directory. This is perfectly OK. Repeat this for the Associations and move them into the package demo.survey.model.bc.links.

Renaming the Associations to better readable names is as simple as moving the files. Only difference is that must do it file by file. In the demo.survey.model.bc.links package we select an Association, open the Context Menu, select Refactor, select Rename..., enter the new name and click on OK. We repeat this for all entries in the package and rename them according to the table below.

The final step in JDeveloper 11g is click on the Save All button in the button bar to save all the modified files.

It contain a whole bunch of updates from the JavaOne'08 version. In particular a section on rolling your own version of part of the @AsyncWebService proposal using the RI.

Ok, one more basic example before we get into the interesting oracle specific stuff. In the previous example i illustrated how to call a plsql stored procedure using ibatis, in this example i’ll show you how you can call a stored function.

Here’s the plsql function that we’re going to call:

create or replace package body employee_pkg
is
  ...
  function get_name_by_id (
    p_id in number
  ) return varchar2 is
    l_name varchar2(100);
  begin
    select name
    into   l_name
    from   employees
    where  id = p_id;
    return l_name;    
  end;
  ...
end;

The sqlMap configuration entry you need for this is as follows:

<parameterMap id="parameters1" class="map">
    <parameter property="name" jdbcType="VARCHAR" javaType="java.lang.String"
               mode="OUT"/>
    <parameter property="id" jdbcType="NUMERIC" javaType="java.lang.Long"
               mode="IN"/>
  </parameterMap>
  <procedure id="selectNameByIdFunc" parameterMap="parameters1">
    <![CDATA[
    { ? = call employee_pkg.get_name_by_id( ? ) }
    ]]>
  </procedure>

Using this bit of configuration, you can now call the plsql function in your java program as follows:

Long id = new Long(3);
Map pars = new HashMap();
pars.put("id", id);
sqlMapper.queryForObject("selectNameByIdFunc", pars);
System.out.println("Query by id " + id + ": " + pars);

The next example will be a bit more interesting, it will demonstrate a way to handle ROWTYPE parameters returned by a stored function.

Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Java, Database, Oracle, ORM, Open Source

For the past several years we've been running the OTN Developer Days across the US and Canada with great success.
Well the time has come for an update of the material, so Lynn from our team did an update of the content to be based on the upcoming 11g version - and we ran the first pilot event here in HQ last week - and now we are ready to roll it to the rest of the world.

The workshop is built from two half days - the first half consist of presentations and demos that will introduce you to the concepts of development used for Fusion Applications development. In the second half of the day you'll be running through hands-on labs and actually experience building a complete application.

We are covering the ADF stack used by the Fusion Applications inside Oracle (ADF Business Components, ADF Controller and ADF Faces Rich Client Components).

This workshop is a great introduction to the future of application development in the Oracle world.
Beyond our regular Java audience, we expect to see also Apps customers (EBS, PeopleSoft, Siebel etc), Forms customers and of course BEA customers who won't to see a more productive approach to Java based application development.

Check out the current schedule here.

If you don't see an event coming to your town - contact your local Oracle office and ask them to make sure this roadshow comes to your location. (They can call me if they need details on how to get this going).

I'll be doing the event in Pennsylvania on July 22nd - drop by and say hello.

In the previous example, Simple delete and insert statements with iBatis, i already demonstrated how you can call a oracle stored procedure. That example used a class to specify all the procedure parameters. Ibatis is often smart enough to know how to map the class properties to the parameters in your sql call. But sometimes you need to do the mapping between the properties and the sql parameters yourself. I’ll illustrate this here.

The following plsql procedure queries the employee with the specified id, and returns the employees name and date of birth:

procedure get_employee_by_id (
    p_id   in out number
  , p_name in out varchar2
  , p_date_of_birth in out date
  ) is 
  begin
    select name
    ,      date_of_birth
    into   p_name
    ,      p_date_of_birth
    from   employees
    where  id = p_id;
  end;

Using a parameterMap element in my sqlMap i can specify that the sql parameters are INOUT parameters:

<parameterMap id="parameters0" class="nl.iteye.ibatis.example1.Employee">
    <parameter property="id" jdbcType="NUMERIC" javaType="java.lang.Long"
               mode="INOUT"/>
    <parameter property="name" jdbcType="VARCHAR" javaType="java.lang.String"
               mode="INOUT"/>
    <parameter property="dateOfBirth" jdbcType="DATE" javaType="java.util.Date"
               mode="INOUT"/>
  </parameterMap>
  <procedure id="selectEmployeeById" parameterMap="parameters0">
    <![CDATA[
    { call employee_pkg.get_employee_by_id( ?, ?, ? ) }
    ]]>
  </procedure>

Now i can call my stored procedure as follows:

Long id = new Long(4);
  Employee emp = new Employee();
  emp.setId(id);
  sqlMapper.queryForObject("selectEmployeeById", emp);
  System.out.println("Query by id " + id + ": " + emp);

In the next example i’ll show an plsql packages function call.

Permalink | No comments | del.icio.us | Technorati | digg | dzone | StumbleUpon | Java, Database, Oracle, ORM

We have to enable Enable User customations then Across Sessions using MDS and at last Enable Seeded Customizations. Across sessions will store the changes in the mds repository, so the next time the user still sees the changes.
Step 2 is the configuration of the adf-config.xml file

In this file we have to add three things. The first thing we have to do is to define a mds repository. Make sure that you add the following folders ViewController/public_html , ViewController/adfmsrc and Model/src to the metadata-path property.
The second thing are the customizations classes. You can use different classes at the same time. I use in this blog only one ( UserCC ) . You can also use SiteCC or SecurityRoleCC.

Now we only have to define which changes are stored in the mds repository

<?xml version="1.0" encoding="windows-1252" ?>
<adf-config xmlns="http://xmlns.oracle.com/adf/config"
            xmlns:sec="http://xmlns.oracle.com/adf/security/config">
  <sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
    <CredentialStoreContext credentialStoreClass="oracle.adf.share.security.providers.jps.CSFCredentialStore"
                            credentialStoreLocation="../../src/META-INF/jps-config.xml"/>
    <sec:JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
                             jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
                             authorizationEnforce="true"
                             authenticationRequire="true"/>
  </sec:adf-security-child>
  <app-config type="MDS" name="default"
              xmlns="http://xmlns.oracle.com/adf/mds/config">
    <mds-config version="11.1.1.000" xmlns="http://xmlns.oracle.com/mds/config">
      <persistence-config>
        <metadata-namespaces>
          <namespace path="/" metadata-store-usage="one"/>
        </metadata-namespaces>
        <metadata-store-usages>
          <metadata-store-usage id="one">
            <metadata-store name="mymetadatastore"
                            class-name="oracle.mds.persistence.stores.file.FileMetadataStore">
              <property name="metadata-path"
                        value="D:/projecten/workspace/11g/mds_user_cc/ViewController/public_html;D:/projecten/workspace/11g/mds_user_cc/ViewController/adfmsrc;D:/projecten/workspace/11g/mds_user_cc/Model/src"/>
            </metadata-store>
          </metadata-store-usage>
        </metadata-store-usages>
      </persistence-config>
      <cust-config>
        <match>
          <customization-class name="oracle.adf.share.config.UserCC"/>
        </match>
      </cust-config>
    </mds-config>
  </app-config>
  <adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">
    <persistent-change-manager>
      <persistent-change-manager-class>
        oracle.adf.view.rich.change.MDSDocumentChangeManager
      </persistent-change-manager-class>
    </persistent-change-manager>
    <taglib-config>
      <taglib uri="http://xmlns.oracle.com/adf/faces/rich">
        <tag name="column">
          <attribute name="displayIndex">
            <persist-changes>true</persist-changes>
          </attribute>
          <attribute name="width">
            <persist-changes>true</persist-changes>
          </attribute>
        </tag>
      </taglib>
    </taglib-config>
  </adf-faces-config>
</adf-config>