ADF and Jdeveloper

Use ADF logger in ADF application

noreply@blogger.com (Rohit Barthwal) — Mon, 08 Jul 2013 19:29:00 +0000

Description:

Oracle has provided a logging mechanism in ADF, so that a developer can use this logging feature to test the ADF applications. It's basically a thin wrapper around the java.util.Logging APIs with a few simple methods and, most importantly some specific features integrated into both JDeveloper and Enterprise Manager. It's preferable to use this built-in logger for these reasons, plus it can help you avoid the kind of class-loading issues if one uses some random version of something like Log4J.

Oracle Fusion Middleware components create diagnostic log files in the Oracle Diagnostic Logging (ODL) format. Log file naming and the format of the contents of log files conform to an Oracle standard. By default, the diagnostic messages are in text format.

You can also set up the Java logger to display Java diagnostic messages. Whichever logging format you choose, you can set several levels of logging to control the level and number of messages that are displayed.

You configure the logging session by editing the logging.xml file using the overview editor for Oracle Diagnostic Logging Configuration. You can set the logging level for both persistent and transient loggers and declare handlers for each logger. Logging configuration can be set at any time, even while the application is running in JDeveloper.

After you have created a log, you can view and filter the log messages with the Oracle Diagnostic Log Analyzer. This tool allows you to set filters for different log levels, define message time frames, and search on message text.

Configuration Steps :

Open logging.xml file :

In the Application Server Navigator, right-click IntegratedWebLogicServer and choose Configure Oracle Diagnostic Logging for server name.

Or, from the Log window Action menu, select Configure Oracle Diagnostic Logging.

In the overview editor, click the Overview tab, select ODL Log Levels or Java Log Levels for the logger types you want to view.

So what we see here is a hierarchy of all the packages in the running app server. Notice that some of the icons are green, these are packages or classes that have a presence in the logging.xml already and some are yellow. These latter groups are transient, that is, we can temporarily set up logging on that package or class for the duration of the application server, but once the application server shuts down, the entire logging configuration will be reverted. You'll notice the checkbox at the top of this screen that is labeled Hide Transient Loggers if you want to see persistent loggers only, select Hide Transient Loggers.

Setting up logging level:

You can use the overview editor for Oracle Diagnostic Logging Configuration to configure the logging levels specified in the logging.xml file. The file can be configured before and while the application is running in Integrated WebLogic Server. The changes will apply without the need to restart the server.

When Integrated WebLogic Server is running, you can define both persistent and transient loggers. When the Integrated WebLogic Server is not running, you only can define persistent loggers. The transient loggers will last only for the session and will not be entered in logging.xml. If the server is not running, you must explicitly save the configuration changes to logging.xml for the updates to take effect in the next server run.

To set level of a package or class just expand the corresponding package or class, go to the level column drop down the list and select the required level.

Now this class or package will show this level of message. If a package has a level set then all the sub package and classes under that package will show the same level of messages.

Add new logger :

To add a logger.

If the server is running, click the add icon dropdown menu, and choose add persistent logger or add transient logger . If the server is not running, click Add to add a persistent logger. You cannot add a transient logger.
In the Add Logger dialog, enter a logger name.
Select the logging level.
Click OK.

As well as the logging levels it is also possible to configure the handlers. In logging, the handler is the thing that takes your log message and does something with it - prints it to the console, writes it to a file etc. If you select the root logger in the editor here you will see that it defines three handlers listed in the Handler Declaration section of the screen at the bottom of the editor:

odl-handler
wls-domain
console

The first two would be the default for a standalone WLS instance, but the console we've automatically added for you in the case of the embedded WLS so that you will be able to see the output of your carefully placed logging commands in the log window of the IDE.

Logging.xml file

These changes are done from JDeveloper IDE in logging,xml file, which resides in following location:

C:\Documents and Settings\username\ApplicationData\JDeveloper\latest_system_ folder\DefaultDomain\config\fmwconfig\servers\DefaultServer

These customizations in xml file looks like :

<loggers>

      <logger name="oracle.adf" level="INFO"/>

      <logger name="oracle.adf.faces" level="FINE"/>

      <logger name="oracle.adf.controller" level="INFO"/>

      <logger name="oracle.bc4j" level="INFO"/>

      <logger name="oracle.adf.portal" level="INFO"/>

      <logger name="oracle.vcr" level="INFO"/>

      <logger name="oracle.portlet" level="INFO"/>

      <logger name="oracle.adfinternal" level="INFO"/>

      <logger name="oracle.adfdt" level="INFO"/>

      <logger name="oracle.adfdtinternal" level="INFO"/>

</loggers>

Use of ADF Logger

Using logger for model configuration :

In the Application Navigator, double-click the user interface project.
In the Project Properties dialog, click the Run/Debug/Profile node and create a new run configuration.
In the Run Configurations list, double-click the new run configuration to edit its properties.
In the Edit Run Configuration dialog, for Launch Settings, enter the following Java options for the default virtual machine:

-Djbo.debugoutput=adflogger

This option will now pick the settings from logging.xml file.

Using Logger for java classes

First define the logger itself - usually a static variable in a particular class - for example one of your managed beans:

private static ADFLogger _logger = 
            ADFLogger.createADFLogger(MainPageBackingBean.class);

• Next, throughout your code you can sprinkle logging statements at various levels which are (I hope) fairly self explanitory, for example in this constructor:

public MainPageBackingBean() {
        super();
        _logger.info("Creating a new instance");
        if (BindingContext.getCurrent() == null) {
            _logger.warning("Injected Data-Binding Reference is null");
        } else {
            try {
                doSomethingComplex();
            } catch
            weirdAppException waex;
            {
                _logger.severe("Unexpected exception doing complex thing",
                               waex);
            }
        }
    }

As you can see we generally just pass a String message to the logger, although in the error case we can pass a throwable exception as well. You can also grab your Strings from a resource bundle, rather than hardcoding them. This probably makes sense for error messages but may be overkill for programmers eyes only messages. To grab the resource bundle you simply call the getFormattedMessage() function on the logger, or you can also get hold of the resource bundle that it references using getResourceBundle().

_logger.severe(_logger.getFormattedMessage("errors.db_connection"));

Where the resource bundle contains something like:

errors.db_connection=Unable to establish connection with database!

You can pass parameters to inject into the resource string as well
The final thing to mention in this posting was the use of guard conditions. Although logging calls themselves are cheap if logging is not enabled, you may actually need to do quite a lot of work to prepare the stuff you want to log. For example, I have a standardized method that I use as a Task Flow Initializer to dump out the contents of the PageFlowScope for that taskflow. That's a pretty expensive operation so you want to bypass that whole thing if you know that every single log message within it will be ignored.
Therefore you can use the isLoggable() method to wrap the whole thing. Here's the example:

public void diagnosticInitializer() {
        //Only do the work if we need to
        if (_logger.isLoggable(Level.INFO)) {
            AdfFacesContext actx = AdfFacesContext.getCurrentInstance();
            FacesContext fctx = FacesContext.getCurrentInstance();
            //Gather key information to dump
            String windowName =  actx.getWindowIdProvider().getCurrentWindowId(fctx);
            String viewPort = ControllerState.getInstance().getCurrentViewPort().getClientId();
            Map pageflowScopeMap = actx.getPageFlowScope();

            _logger.info("TaskFlow Diagnostics for " + viewPort);

            if (!pageflowScopeMap.isEmpty()) {
                Iterator mapIter = pageflowScopeMap.entrySet().iterator();
                while (mapIter.hasNext()) {
                    Map.Entry entry = (Map.Entry)mapIter.next();
                    String varKey = entry.getKey().toString();
                    Object varValue = entry.getValue();
                    String varClass = "n/a";
                    if (varValue != null){
                        varClass = varValue.getClass().getName();
                    }
                    StringBuilder bldr = new StringBuilder();
                    Formatter formatter = new Formatter(bldr, Locale.US);
                    formatter.format("Key:\"%s\" Value:\"%s\" Type:[%s]", varKey, varValue, varClass);                    
                    _logger.info(bldr.toString());
                }
            } else {
                _logger.info("No PageFlowScope associated with this TaskFlow instance");
            }
        }
    }

References :

https://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part

https://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part2

http://docs.oracle.com/cd/E15523_01/web.1111/b31974/web_testdebug.htm#BABDBCGF

Use of Input Range Slider

noreply@blogger.com (Rohit Barthwal) — Fri, 30 Nov 2012 09:51:00 +0000

ADF has a long list of Rich look component. They are very easy to use and they give rich look to an application. One of these cool component is Range(selector).

This component is very use full to select two number values. It has some properties by which it is controlled. these are :

Minimum : Range start point.
Maximum : Range end point
Minimum Increment : The smallest possible increment or possible increment when user presses + or – button one time
Major Increment : Distance between two major ticks, major ticks has label.
Minor Increment : Distance between two minor ticks, minor ticks do not show label.

In image:
Minimum : 0
Maximum : 100
Minimum Increment :1
Major Increment : 10
Minor Increment : 5

The main property of this component is value. It contains two values maximum and minimum. Its contains value of form oracle.adf.view.rich.model.NumberRange object.

To get its value first bind this component to java bean class.

private RichInputRangeSlider range;

Get its value

NumberRange sliderValue =getRange().getValue();

To get minimum and maximum selected value :

Integer minVal = sliderValue.getMinimum().intValue(); 
Integer maxVal = sliderValue.getMaximum().intValue();

Now use these value as you need. Play with another component of ADF

Adios.

Create weblogic domain for production environment

noreply@blogger.com (Rohit Barthwal) — Thu, 29 Nov 2012 10:48:00 +0000

Fromlast post now its next step, to create a weblogic server domain. We can do this process through commands in Unix based operating system and in windows. Here I will use the domain creation wizard to create the domain.

Go to start menu → weblogic → weblogic server 11g r1 → tools → Configuration wizard.

On clicking configuration wizard will start it will ask for creation of weblogic domain or extend a already created weblogic domain. Select create a new weblogic domain and click next.

Next screen is to select product which your weblogic server will support . As weblogic server domain will be used for ADF application deployment so select Oracle JRF .

Now give your domain name and location of domain. Click next.

Assign Username password for weblogic administration.

Now select production mode for domain. This will set server for production environment. Select java sdk which already installed with weblogic server. Click next.

Check for optional configuration. Select admin server, managed server and deployments and services.

Configure admin server, select listen address and port on which server will run.

Create a new managed server, assign listen address and port for managed server. Port shoul be different from managed server's port. Creation of managed server can be done after domain creation from weblogic server console.

Skip cluster configuration.

Create machine for admin and managed server give node manger listen address and port. Node manager is used to start server remotely. Node manager can be installed as a windows service. I will show that later.

Assign machine to both admin and managed server by moving them to right part of shuttle. Go to next step.

This step shows libraries and applications which will be deployed on admin and managed server.

Select managed server o left side, now select library on the right side. These libraries are of supported technology here ADF libraries are included.

Skip next step.

Next step shows configuration summary.

Now configuration is complete.

Now start weblogic server from weblogic home /user_projects/domains/<Domain Name>/bin/startWebLogic.cmd . After running cmd file it will ask for username password

After authentication server will start after few seconds .

Admin server of this new domain now running , you can open server console in web browser at the address you have given at the time of domain creation. In production mode applications are deployed on managed server so next is to start managed server. In weblogic domain console all things are done through admin. To start managed server open cmd in windows. Go to bin location inside created domain.

Type startManagedWeblogic.cmd <managed server name> http://<admin serevr listen address: port>

After few seconds managed server will run.

You can see server status in weblogic admin console. Go to environment → servers.

Now domain is ready for deployment. In next post I will show how to deploy an application on Managed server.

Installation Of ADF Runtime Environment to Weblogic Server

noreply@blogger.com (Rohit Barthwal) — Fri, 02 Nov 2012 05:48:00 +0000

In previous post I show the Installation process of Weblogic server. This post is in continuation.
Now to run ADF application on weblogic server first we have to install ADF runtime in to Weblogic server. This will provide needed ADF library in weblogic server so that ADF application can be deployed in to the server. ADF run time is not installed in to weblogic server autometically, it is done manually.
To do this we need Jdeveloper installer. Run Jdeveloper Installer in welcome screen click next to start setup.

Go to next screen , this will show option to select existing middleware home or to create a new middleware home. Choose an existing home where weblogic server is installed. Here home for weblogic server is (C:\Oracle\Middleware). Then click next.

This screen shows Components this installer can install. Weblogic server component will come disabled as it is already installed in this middleware home, we just need ADF runtime, So we will select this option . No need to install jdeveloper. Click Next to proceed.

On JDK selection option, SUN SDK already selected as weblogic is installed with SUN SDK. So simply click next in this step.

Next step is for selection of installation directory. As this middleware home is created previously so skip this step and press next button.

Now screen is showing installation summary. Click next to proceed.

Now installation process is started .

At the end installation is complete message comes. Click on done button will exit the installation.

Weblogic server is now ready for ADF application Deployment. Next step is to Create a new domain in weblogic server for production mode.

Installation Of Weblogic Server

noreply@blogger.com (Rohit Barthwal) — Thu, 01 Nov 2012 05:52:00 +0000

Oracle have provided Weblogic Server to run ADF application created in Jdeveloper. when we install Jdeveloper Weblogic Server also get installed. This is our scenario for development. Now we need to install stand alone Weblogic Server to a machine for production purpose.

Here I will show the steps of installation of stand alone Weblogic Server.

Run setup for weblogic server.

A welcome window will come up to start installation of weblogic server. Click next button to start installation.

Next screen will ask for a middleware home. If you want to use existing home then select one of the appeared home or simply create a new one.

Click next to go to next step. Select custom installation type. In typical it installs Oracle coherence and Oracle Enterprise pack for Eclipse. We do not need them, so choose custom installation

Go to next step by clicking next. This screen shows components to install. Select Weblogic server and leave other option unchecked

Go to next step. There are two option for java installation first one is Sun SDK and other is Oracle JRockit . Choose Sun SDK and click next.

In next window it will show where weblogic server will be installing.

Now select no option for Node manager service. We will do this later manually.

Choose shortcut option for weblogic server. Click next.

Next window shows summery of installation.

Clicking next button will start process of installation.

After installation it shows complete message in window. Done will exit the process.

This is the process of weblogic server installation.

ADF Utility Classes

noreply@blogger.com (Rohit Barthwal) — Mon, 22 Oct 2012 07:14:00 +0000

Following files can be used in ADF to ease coding. These java files contain very useful methods.

Set Text Style in input text field

noreply@blogger.com (Rohit Barthwal) — Mon, 17 Sep 2012 14:38:00 +0000

In ADF application default style of input text is lower case. Whenever user types in input text he has to decide to type in lower case or upper case or first letter capital style. If a developer want to restrict the format of a input text to lower case or upper case or capitalized style then it can be done by changing style.
As this style property is set, this will give desired format regardless the user's keyboard's caps lock button is on or not.
To do this go to contentStyle property of input text and set one of the following values:

For Capatalized text
text-transform:capitalize

For Lowercase:
text-transform:lowercase

For UPPERCASE:
text-transform:uppercase

Get Current Date and time

noreply@blogger.com (Rohit Barthwal) — Tue, 21 Aug 2012 05:52:00 +0000

We usually need to get current date and time in java class. It is easy to get current date for java.util.Date class.

java.util.Date date = new java.util.Date();

This date object gives current date and time. To use this date and time this can be formatted in needed date format as follows:

DateFormat dateFormat = SimpleDateFormat("yyyy/MM/dd HH:mm:ss");
            java.util.Date date = new java.util.Date();
            String datetime = dateFormat.format(date);

This will give desired format to current date. Now to use this format in code we need to change this string to java.util.Date

        try{
                java.util.Date date2 = dateFormat.parse (datetime);
                }catch(ParseException pe){
                    pe.printStackTrace();}

Now to get current date in oracle.jbo.domain.Date class do the following

        java.sql.Timestamp datetime = new java.sql.Timestamp(System.currentTimeMillis());
        oracle.jbo.domain.Date daTime = new  oracle.jbo.domain.Date(datetime);

Or change java.util.Date to oracle.jbo.domain.Date

               DateFormat dateFormat = new SimpleDateFormat("yyyy/MM/dd HH:mm:ss");
                    java.util.Date date = new java.util.Date();
                    String dateStr = dateFormat.format(date);
         try{
                java.util.Date date2 = dateFormat.parse (dateStr);
                    java.sql.Date sqldate = new java.sql.Date(date2.getTime());
                    oracle.jbo.domain.Date daTime = new  oracle.jbo.domain.Date(sqldate);
                    System.out.println("Current Date Time : jbo " + daTime);
                }catch(ParseException pe){
                    pe.printStackTrace();}

To get only date use java.sql.Date and to get date with time use java.sql.Timestamp

Get value from task flow using Contextual Event

noreply@blogger.com (Rohit Barthwal) — Wed, 28 Sep 2011 12:07:00 +0000

Often a page or a region within a page needs information from somewhere else on the page or from a different region. Among the options for passing information to and from regions, Contextual Events is the most powerful and the option that does not make regions refresh or require the referenced bounded task flow to restart.

Contextual events have two parts:

A publisher (or producer), such as a button that raises a named event, with or without a custom payload.
A handler (or consumer) that listens for a specifically named event or a wildcard event, to process that event.

Create a Contextual Event:

Create a bounded task flow with page fragment and create a view inside it. Create a view object and place it as a tree table or tree in page.
To create a contextual event just select the tree and go to its properties. There go under the option publish event and click on add button to create a contextual event. Select create new event and press ok, this will create a contextual event. Here event type will be currency change event.

Get Contextual Event:

Create a adf jar file of this application. Add this library to a new application where you will use the task flow as a region.
Create a page and put a input text on it, give its value from a bean class.

public class NewBean {
    private RichOutputText newtext;
    String MyValue=null;

    public NewBean() {
    }

    public void setNewtext(RichOutputText newtext) {
        this.newtext = newtext;
    }

    public RichOutputText getNewtext() {
        return newtext;
    }

    public void setMyValue(String MyValue) {
        this.MyValue = MyValue;
    }

    public String getMyValue() {
        return MyValue;
    }
}

Now create a event handler class which will act as a consumer of event generated by a producer. In it create a function which will get the value from producer event. This function will take a parameter of currency change event type which is produce by the tree node selection event.

public class EventHandler  {
    public EventHandler() {
        super();
    }
   
    public void handleEventStringPayload(DCBindingContainerCurrencyChangeEvent customPayLoad) {

        this.setNewValue(customPayLoad.getSource().toString());
        FacesContext fctx = FacesContext.getCurrentInstance();
        ELContext elctx = fctx.getELContext();
        ExpressionFactory exprFactory = fctx.getApplication().getExpressionFactory();
        ValueExpression ve = exprFactory.createValueExpression(elctx, "#{NewBean}", Object.class);
        NewBean pageBean = (NewBean)ve.getValue(elctx);
        pageBean.setMyValue(customPayLoad.getSource().toString());
        AdfFacesContext adfFacesContext = AdfFacesContext.getCurrentInstance();
        adfFacesContext.getCurrentInstance().addPartialTarget(pageBean.getNewtext());

    }

To make this function available at the binding level, create this java class' data control. To do this right click on this java class and go to create data control. Select all 3 option if you are using release 2 of jdeveloper.
Now go to page , drag and drop task flow from library and make it a region or dynamic region. By this event will also be available in this page. Go to binding section of page and add new method binding to it. Add method from data control to it. By this, method can be accessed from this page.

Again go to binding tab of page and open contextual event tab. In this tab go to subscriber tab and click on add button. This will pop up a window. Click on the search button it will show available events in this page. Select previously defined event in task flow's page.

select the publisher or keep it any. Now go to handler option and click search button it will show available functions in bindings. Select the function created for event handling. Go to last part of subscriber parameter. Give parameter name same given in event handler function. Its value will be ${payLoad}.

Now run application it will show selected tree value in output box which is outside the region.

For sample application click here

UNSAVED DATA WARNING

noreply@blogger.com (Rohit Barthwal) — Tue, 23 Aug 2011 15:18:00 +0000

Introduction :

If You are working on a form or table and some of data is modified or added, on moving to other page of taskflow this data will remain in cache or it will show no warning for unsaved data

How to do it :

To show warning of unsaved data between page navigation just go to property of af:document and set Uncommitted data warning to true. Then whenever you move out of that page or close the browser it will show you a warning of unsaved data.

Warning Message

SHOW UNSAVED ROW HIGHLIGHTED

noreply@blogger.com (Rohit Barthwal) — Tue, 23 Aug 2011 14:49:00 +0000

Introduction :

This post to describe how to show a unsaved row of a table. There is a property of an entity which is entity state. This entity can be in 4 states:

New
Modified
Unmodified
Initialized

How to do it :

just copy the following code and paste in to inline style of column of table. This will highlight newly created row.

#{row.row.entities[0].entityState == 0? 'background-color:#ff9c31;':''}

To highlight modified row compare entity state to 2

0 for new unsaved row

1 for unmodified row

2 for modified unsaved row

-1 for initialized row

for showing unsaved rows whether modified or a new place both condition together.

#{row.row.entities[0].entityState == 2||row.row.entities[0].entityState == 0?'background-color:#ff9c31;':''}

CUSTOM VALIDATOR

noreply@blogger.com (Rohit Barthwal) — Thu, 04 Aug 2011 08:10:00 +0000

In my last post I included information about different validations available in ADF-BC. These validations are very easy to apply in Entity object and view objects. There are most of the possible validations are available. Still you may want to define your own custom validation, for this you will write code in your managed bean.

To apply a custom validator go to your jspx or jsff page and select the input text or other input component an go to its properties. Give a function name to validator.

This validator will look like :

public void NameValidation(FacesContext facesContext, UIComponent uIComponent, Object object) {

return true:

}

Now in this validator method you can write your own validation code. Such as I have written here validation of name input text, so that user can only insert capital letters, numbers and “_”. If validation fails it will show a error, else nothing.

public void NameValidation(FacesContext facesContext, UIComponent uIComponent, Object object) {
        String value = (String)object;
        if ((value == null) || value.length() == 0) {
            return;
        }
        String expression = "^[A-Z 0-9_]{2,100}$";
        CharSequence inputStr = value;
        Pattern pattern = Pattern.compile(expression);
        Matcher matcher = pattern.matcher(inputStr);
        String error = “Only upper case letter and _ allowd”;
        if (matcher.matches()) {
        } 
else {
            throw new ValidatorException(new FacesMessage(FacesMessage.SEVERITY_ERROR, error, null));
        }
    }

When you run application and validation fails you will get an error like this:

ADF-BC Validations

noreply@blogger.com (Rohit Barthwal) — Mon, 01 Aug 2011 08:31:00 +0000

This framework provides very good feature of validation. In ADF we can validate user inputs at different levels. Which are

Attribute level: Fires on value change.
Entity level: Fires on moving from one record to another.
Transaction level: Fires after attribute and entity level validations are complete. It validates Master-detail validations.

These validations are defined in Entity object and View object level. There are many rules of possible validations and ADF-BC provide lots of them. These validations rules are:

Compare: Attribute value compared with other attribute's value or an expression or a literal.
List: Value is validated against a list of values.
Key Exists: Its like a foreign key validator, it checks the value whether it exists or not. Like value for employee will check for the department to check whether it is present or not.
Regular Expressions: Value compared against provided regular expression. Like for email validation, Number Format validation.
Script Expression: Groovy expression are used to do validations.
Method Validator: When a method validator is created it adds a method in corresponding entityImpl calss. Like

public boolean validateEname(String ename) {  
return true;
}

ADF page refresh using java code

noreply@blogger.com (Rohit Barthwal) — Fri, 29 Jul 2011 06:49:00 +0000

This post will show the code for a full page refresh. Most of the time Partial page rendering do the work, still we need a full page refresh. For this easy way is to call a java method and refresh the page. This is needed when there is a change in database values and you want to refresh the form and table after operation.

So use following code for this:

public void refresh() {
      FacesContext facesContext = FacesContext.getCurrentInstance();
      String refreshpage = facesContext.getViewRoot().getViewId();
 ViewHandler  viewHandler =
facesContext.getApplication().getViewHandler();
      UIViewRoot viewroot =  viewHandler.createView( facesContext, refreshpage);
viewroot.setViewId(refreshpage);
facesContext.setViewRoot(viewroot);
}

Generate a XML file for a view object

noreply@blogger.com (Rohit Barthwal) — Thu, 07 Jul 2011 06:05:00 +0000

There is a need of generating a xml file from a view object. This is a very easy process as there is a method of view object class “writeXml” to write the content of view object to a xml format.

First generate Impl class for application module.
Write following code to create an object of view object, and generate xml content. Then write this generated xml to a file using output stream.

public String printXml() {

        Connection conn;
        FileOutputStream out;
        ByteArrayOutputStream outputStream = new ByteArrayOutputStream();
        try {
            AppModuleImpl am = (AppModuleImpl)resolvEl("AppModuleDataControl");
            conn = am.getDBTransaction().createStatement(0).getConnection();
            ViewObject vo = am.findViewObject("EmployeeView");
            ((XMLNode)vo.writeXML(4, XMLInterface.XML_OPT_ALL_ROWS)).print(outputStream);
            System.out.println(outputStream);
            out = new FileOutputStream("F://Employee.xml");
            PrintStream p = new PrintStream(out);
            p.println(outputStream);
            p.close();

        } catch (Exception e) {
            System.out.println(e.getMessage());
        }
        return null;
    }

  public Object resolvEl(String data){
    FacesContext fc = FacesContext.getCurrentInstance();
    Application app = fc.getApplication();
    ExpressionFactory elFactory = app.getExpressionFactory();
    ELContext elContext = fc.getELContext();
    ValueExpression valueExp = elFactory.createValueExpression(elContext, "#{data."+data+".dataProvider}", Object.class);
   return valueExp.getValue(elContext);
  }

Use database table for authentication in adf security

noreply@blogger.com (Rohit Barthwal) — Fri, 01 Jul 2011 08:08:00 +0000

To use sql authenticator in weblogic server security realm, read following blog post: SQLAuthenticator

Now go to application and apply adf security. You do not need to modify the role mapping in weblogic.xml. The default is perfectly fine:


  
    valid-users
    users

For each group in your SQLAuthenticator provider in weblogic console, create an equivalent application role in jazn.xml, and recreate those roles in the Enterprise Roles in jazn.xml. In jazn,xml make enterprise role as member of the appropriate application role. There is no need to create user in jazn.xml file. Crating role will do the work.

My ADF Presentation

noreply@blogger.com (Rohit Barthwal) — Wed, 22 Jun 2011 09:44:00 +0000

Application development framework

Refresh Resource Bundle

noreply@blogger.com (Rohit Barthwal) — Tue, 21 Jun 2011 06:08:00 +0000

Resource bundle can not be refreshed using ResourceBundle class. using following code do not clear the cache.

Class type = ResourceBundle.class;
Field cacheList = type.getDeclaredField("cacheList");
cacheList.setAccessible(true);
((Map)cacheList.get(ResourceBundle.class)).clear();

If you want to refresh resource bundle of your application you should need to use Resource bundle manager instead of Resource bundle class.

ResourceBundleManagerRT rt = (ResourceBundleManagerRT)ResourceBundleManagerRT.getResourceBundleManager();
 rt.flush();

Use external XML file for Resource Bundle

noreply@blogger.com (Rohit Barthwal) — Mon, 20 Jun 2011 07:06:00 +0000

Create list resource bundle file for default and supported locale. And read label value from xml file.
This approach gives a facility to change label or message value, without compilation and redeployment of application.
To do this first crate a xml file containing key and value pair, so that you can use label according to their key.



 
  home_greeting
  My Home application
   
 
  global_button_submit
  Press it
 
 
  global_button
  Enter value

This method also give an option to use single file for different application, which are used as a library.
Here you can write code to read xml file and assign key value pair to an object of resource bundle class.

public class MyResources extends ListResourceBundle {

    public MyResources() {
        super();
    }
  
  private static final Object[][] contents =
    { { "", "" }, { "", "" }, { "", "" } };

    protected Object[][] getContents() {
        try {
            File file = new File("C:\\Users\\admin\\Desktop\\locale\\Resource.xml");
            DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
            DocumentBuilder db = dbf.newDocumentBuilder();
            Document doc = db.parse(file);
            doc.getDocumentElement().normalize();
            NodeList nList = doc.getElementsByTagName("label");

            for (int temp = 0; temp < nList.getLength(); temp++) {

                Node nNode = nList.item(temp);
                if (nNode.getNodeType() == Node.ELEMENT_NODE) {

                    Element eElement = (Element)nNode;

                    contents[temp][0] = getTagValue("key", eElement);
                    contents[temp][1] = getTagValue("value", eElement);

                }
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
        return contents;
    }

    private static String getTagValue(String sTag, Element eElement) {
        NodeList nlList = eElement.getElementsByTagName(sTag).item(0).getChildNodes();
        Node nValue = (Node)nlList.item(0);

        return nValue.getNodeValue();
    }

}

Jdeveloper 11g release 2 , with lots of new features

noreply@blogger.com (Rohit Barthwal) — Fri, 10 Jun 2011 08:01:00 +0000

Oracle released a new version of Jdeveloper 11g, containing lots off new features and even rapid development of application. These new features take jdeveloper to another level and now can be compared with other J2EE IDE such as java bean and eclipse.

To download new jdeveloper go to following link: http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html

Main features of new jdeveloper are:

Hot deployment: There is no need now to run application after any change in application files. Now just save the changed file and refresh the page.
Skin Editor: This new editor for skin is very use full to create css for application. It made it easy to select different properties of a component and change their attributes.
For other features follow the link: http: //www.oracle.com/technetwork/developer-tools/jdev/jdev-11gr2-nf-404365.html

You can also get installation guides for this new release and for new skin editor in this link : http://www.oracle.com/technetwork/developer-tools/jdev/documentation/index.html

Check for the related documents: http://download.oracle.com/docs/cd/E16162_01/index.htm

Call Jasper report using a link

noreply@blogger.com (Rohit Barthwal) — Wed, 01 Jun 2011 10:05:00 +0000

In previous post jasper report is called with the help of java bean. Now we can use a link to call report as in previous method calling report from a .jsff page gives error.

To call report using link follow following steps:

Add a go link to page which will call servlet and also pass parameters.
Add a command button to assign value to parameters.
Add value in destination like “/jasperservlet?deptno=#{bindings.DepartmentId1.inputValue}&reporttype=#{bindings.Filetype1.inputValue}”.
Here deptno and reporttype are parameters passed from url and will be used in servlet.
To get parameter value in servlet use following code.

Integer code = Integer.valueOf(request.getParameter("deptno"));
String reporttype = request.getParameter("reporttype");

Jasper report in ADF aaplication

noreply@blogger.com (Rohit Barthwal) — Thu, 26 May 2011 17:00:00 +0000

This post is to create an application which will use to generate Jasper report as created with the help of iReport tool.

Next are the steps of creating that needed application.

In application create entity object, view object and application module use to database table employees and departments from HR user.
Go to employee view object and create List of values for department id. Create a transient attribute for file types in which report will be generated.
So create a list of values in this attribute and take static values from a static view object like pdf, xls, csv etc.
Before creating any page or java class, Jasper report related libraries should be imported in jdeveloper so that jasper related java classes can be used.

commons-beanutils-1.8.3.jar
commons-collections-3.2.1.jar
commons-digester-2.1.jar
commons-logging-1.1.1.jar
iText-2.1.7.jar
jasperreports-4.0.1.jar
jfreechart-1.0.13.jar
poi-3.7-20101029.jar

Now create a page to select report output file type and to pass the parameter to jasper report. Add both list of values to page for run time selection.

When user will select the values for department and file type and run the report, these values will be passed to servlet from java class. To get selected values in java class lov should be changed. Add a for each element in select one choice and get item value from this.
Bind these both list to bean class so that selected values will be passed to servlet.
Now create a servlet for request and response for report. For this go to new, select servlet from category and http servlet from items, click ok.
Give servlet name, its package, type to html, and select doget and doPost methods. Click next.
Now it will show created servlet on editor . Write code for jasper report in this servlet.
Write code in one of the method doGet() or doPost().

public void doPost(HttpServletRequest request,
HttpServletResponse response)
throws ServletException, IOException {

response.setContentType(CONTENT_TYPE);

Create a connection so that report will use this connection to get data from database.

try{ 
PreparedStatement st = null;

String amDef = "jasper.model.module.AppModuleAM";
String config = "AppModuleAMLocal";
AppModuleAMImpl am =
(AppModuleAMImpl)Configuration.createRootApplicationModule(amDef,
config);    
st = am.getDBTransaction().createPreparedStatement("select 1 from dual", 0);
Connection conn = st.getConnection();

Place jrxml file in public-html folder of application so that it will pick file from server location . To get this file input stream is created .

InputStream input = new FileInputStream(new File(getServletConfig().getServletContext()
.getRealPath("/reports/parReport.jrxml")));

JasperDesign design = JRXmlLoader.load(input);
JasperReport report = JasperCompileManager.compileReport(design);

Now get Attributes which are set at the time of servlet calling.

Integer code = (Integer)request.getAttribute("deptno");
String reporttype = (String)request.getAttribute("reporttype");

Set value for parameter of report. If you have more than one parameter in your report, then you have to call the put method for each parameter.

Map parameters = new HashMap();
parameters.put("DeptNo", code);
JasperPrint jasperPrint=JasperFillManager.fillReport(report, parameters, conn);

Now create a output stream to send file to client. Then Check file type and export file to client in right format.

OutputStream ouputStream = response.getOutputStream();
JRExporter exporter = null;

if( "pdf".equalsIgnoreCase(reporttype) )
{
response.setContentType("application/pdf");

response.setHeader("Content-Disposition", "attachement; filename=\"file.pdf\"");


exporter = new JRPdfExporter();

exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint);
exporter.setParameter(JRExporterParameter.OUTPUT_STREAM, ouputStream);
}
else if( "rtf".equalsIgnoreCase(reporttype) )
{
response.setContentType("application/rtf");
response.setHeader("Pragma", "no-cache");
response.setHeader("Content-Disposition", "attachement; filename=\"file.rtf\"");

exporter = new JRRtfExporter();
exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint);
exporter.setParameter(JRExporterParameter.OUTPUT_STREAM, ouputStream);
}
else if( "html".equalsIgnoreCase(reporttype) )
{
exporter = new JRHtmlExporter();
exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint);
exporter.setParameter(JRExporterParameter.OUTPUT_STREAM, ouputStream);
}
else if( "xls".equalsIgnoreCase(reporttype) )
{
response.setContentType("application/xls");
response.setHeader("Content-Disposition", "attachement; filename=\"file.xls\"");

exporter = new JRXlsExporter();
exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint);
exporter.setParameter(JRExporterParameter.OUTPUT_STREAM, ouputStream);
}
else if( "csv".equalsIgnoreCase(reporttype) )
{
response.setContentType("application/csv");
response.setHeader("Content-Disposition", "attachement; filename=\"file.csv\"");

exporter = new JRCsvExporter();
exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint);
exporter.setParameter(JRExporterParameter.OUTPUT_STREAM, ouputStream);
}

try
{
exporter.exportReport();
}
catch (JRException e)
{
throw new ServletException(e);
}
finally
{
if (ouputStream != null)
{
try
{
ouputStream.flush(); 
ouputStream.close();

}
catch (IOException ex)
{
System.out.println(ex.getMessage());
throw (ex);
}
}
}

}catch(Exception ex) {
ex.printStackTrace();
}

After writing servlet we have to call this servlet and pass dynamic values from page to servlet. For this write a function and call this function from a button on page.
To send request to servlet we will use http request and response cycle. In request we will set attributes, which we will need in servlet to pass to jasper report and to print report according to its format.

public void callServlet(ActionEvent actionEvent) throws Exception  {
FacesContext ctx = FacesContext.getCurrentInstance();
HttpServletRequest request = (HttpServletRequest)ctx.getExternalContext().getRequest();
HttpServletResponse response =(HttpServletResponse) ctx.getExternalContext().getResponse();

request.setAttribute("deptno", deList.getValue());
request.setAttribute("reporttype", fileTypeList.getValue());

request.getRequestDispatcher(response.encodeURL("/jasperservlet")).forward(request, response);   

response.flushBuffer();  
ctx.responseComplete();    

}