Bug in ADF 11g R2- Transient and Bind Valiable of Timestamp type

This is a bug in ADF 11g R2, and sometimes so much annoying for developer.

Bug Is-

• Suppose you have created business components for Employees table of HR Schema, there is HireDate in Employees table , see it in EntityObject-

• Now go to source and see, it is of type oracle.jbo.domain.Timestamp (default java representation of Timestamp database data type )

• Now go to Employees ViewObject and create a transient variable for DOB(Date Of Birth)  and select it as Timestamp

•  Now after this if developer tries to get or set value of this transient variable, it shows a exception (java.sql.Timestamp can not be cast to oracle.jbo.domain.Timestamp)

•  To solve this error go to Employees ViewObject and select transient attribute and go to source, se it is of type java.sql.Timestamp

 

• Change it to oracle.jbo.domain.Timestamp  and then run it
• So this is a bug when developer creates new Transient or Query bind variables of Timestamp type, ADF automatically assign it java.sql.Timestamp

Always check it when using Jdveloper 11gR2

Cheers... happy debugging

Using af:inputNumberSlider and af:inputRangeSlider for good UI in Oracle ADF

Hello All,
This tutorial is about slider component
Slider is cool and interesting component in ADF to select a single number or to select a range
there is two types of slider available in ADF Faces

1. af:inputNumberSlider (to select single value)
2. af:inputRangeSlider (to select range)

Follow steps to learn how to use slider in ADF

• Go to Component Palette and search slider and drop it  into page

• look in property inspector of slider , there are many properties to customise this component, you can change min-max values,orientation etc

•  See Horizontal and Vertical slider-

• Now to get its value in bean , bind both slider to managed bean, using binding property





    private RichInputNumberSlider numberSliderBind;
    private RichInputRangeSlider rangeSliderBind;


    public void setNumberSliderBind(RichInputNumberSlider numberSliderBind) {
        this.numberSliderBind = numberSliderBind;
    }

    public RichInputNumberSlider getNumberSliderBind() {
        return numberSliderBind;
    }

    public void setRangeSliderBind(RichInputRangeSlider rangeSliderBind) {
        this.rangeSliderBind = rangeSliderBind;
    }

    public RichInputRangeSlider getRangeSliderBind() {
        return rangeSliderBind;
    }



• now to get value of inputNumberSlider simply use binding.getValue()



 Number numberVal = (Number)numberSliderBind.getValue();



• To get Range of inputRangeSlider use this



        NumberRange sliderVal = (NumberRange)getRangeSliderBind().getValue();
        Number minVal=sliderVal.getMinimum();
        Number maxVal=sliderVal.getMaximum();



• Now Run your page and see how is it-

You can use slider for custom search, fixed range interval etc

Avoiding JBO-27101: DeadEntityAccessException, Attempt to access dead entity -Oracle ADF

JBO-27101-DeadEntityAccessException
As Per Oracle docs- JBO-27101: DeadEntityAccessException

Cause: Trying to refer to an invalid/obsolete entity. This could occur if some business logic has held on to an entity reference which was removed and the transaction has been posted or committed. It could also occur if a reference entity has been removed from the cache and any ViewRow is attempting to access it.

Action: Use findByPrimaryKey to find a valid entity of the desired key instead of holding on to a reference to an entity instance.

oracle.jbo.DeadEntityAccessException: JBO-27101: Attempt to access dead entity in DepartmentsEO, key=oracle.jbo.Key[10 ]
 at oracle.jbo.server.EntityImpl.setAttributeValueInternal(EntityImpl.java:3649)
 at oracle.jbo.server.EntityImpl.setAttributeValue(EntityImpl.java:3599)
 at oracle.jbo.server.AttributeDefImpl.set(AttributeDefImpl.java:3193)
 at oracle.jbo.server.EntityImpl.setAttributeInternal(EntityImpl.java:1936)
 at exception.model.entities.DepartmentsEOImpl.setManagerId(DepartmentsEOImpl.java:142)
 at exception.model.entities.DepartmentsEOImpl.doDML(DepartmentsEOImpl.java:229)
 at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:6721)
 at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:3264)
 at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:3067)
 at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:2071)
 at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2352)
 at oracle.adf.model.bc4j.DCJboDataControl.commitTransaction(DCJboDataControl.java:1590)
 at oracle.adf.model.binding.DCDataControl.callCommitTransaction(DCDataControl.java:1415)
 at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1428)
 at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2169)
 at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:731)
 at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:402)
 at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:252)
 at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:185)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.sun.el.parser.AstValue.invoke(Unknown Source)
 at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)

This exception mainly occurs when developer/User removes a row from ViewObject and try to access it again to set any value or to commit transaction .
if entity(object of a row in table) is removed and then accessed from cache throws this exception
So Always check code that you have written to remove a row from entity and do check your doDML() method in EntityImpl class as it executes during commit after any DML Operation (Update, Delete).

Steps to reproduce DeadEntityAccessException-

• here i am using default HR Schema (Departments table)
• Create business components using Departments table

• create a page and drag Departments viewObject from data control as a table on page and also drop delete and commit operation on page

• Now go to EOImpl class of Departments Entity Object and just set any attribute's value in doDML(); method



    /**
     * Custom DML update/insert/delete logic here.
     * @param operation the operation type
     * @param e the transaction event
     */
    protected void doDML(int operation, TransactionEvent e) {
        setManagerId(1800);
        super.doDML(operation, e);
    }

• Now just run your application and delete any row then press commit, in this case doDML(); method try to set managerId in deleted row that is not in cache, in this case you will see DeadEntityAccessException