Showing posts with label Bug. Show all posts
Showing posts with label Bug. Show all posts

Saturday, February 26, 2011

Bug: Boolean Accessors Prefixed with "is" not recognized as attribute in JDeveloper 11.1.1.4

The biggest fail that I noticed in JDeveloper 11.1.1.4.0 (aka Patch Set 3) is the inability to recognized boolean properties that are prefixed with "is" like isActive() as property in the entity xml files. My disappointment is that- this is properly recognized in earlier releases. We wanted to jive with the most recent release, so we have a lot of refactoring to make.
Below is a sample entity class and the corresponding entity xml file that was generated by JDev:
package model;

public class Employee {
    private Long id;
    private Boolean active;
    private String firstName;
    private String lastName;

    public void setActive(Boolean active) {
        this.active = active;
    }

    public Boolean isActive() {
        return active;
    }

    public void setId(Long id) {
        this.id = id;
    }

    public Long getId() {
        return id;
    }

    public void setFirstName(String firstName) {
        this.firstName = firstName;
    }

    public String getFirstName() {
        return firstName;
    }

    public void setLastName(String lastName) {
        this.lastName = lastName;
    }

    public String getLastName() {
        return lastName;
    }
}
Generated xml:
<?xml version="1.0" encoding="UTF-8" ?>
<JavaBean xmlns="http://xmlns.oracle.com/adfm/beanmodel" version="11.1.1.59.23"
          id="Employee" Package="model" BeanClass="model.Employee"
          isJavaBased="true">
  <Attribute Name="id" Type="java.lang.Long"/>
  <Attribute Name="firstName" Type="java.lang.String"/>
  <Attribute Name="lastName" Type="java.lang.String"/>
  <MethodAccessor IsCollection="false" Type="void" id="setActive"
                  ReturnNodeName="Return">
    <ParameterInfo id="active" Type="java.lang.Boolean" isStructured="false"/>
  </MethodAccessor>
  <MethodAccessor IsCollection="false" Type="java.lang.Boolean" id="isActive"
                  ReturnNodeName="Return"/>
  <ConstructorMethod IsCollection="true" Type="model.Employee"
                     BeanClass="model.Employee" id="Employee"/>
</JavaBean>
Notice that isActive() is not part of the attributes.

Monday, February 15, 2010

ADF Model: java.lang.NullPointerException at oracle.adf.model.binding.DCIteratorBinding.getSortCriteria

If you encountered this error though your code was running good before, then welcome to the club! :D
Here are some of our colleagues:
ADF webapp deployment problem...
JDBC connection for ADF
Both of them have resolve their case by recreating their application and build it from scratch. Yaiks! We sure cannot afford that on an app that we build for months.

Luckily, I was able to resolve my case by doing the steps below, but in your case, I don't know, so good luck!

It could be resolved by doing the following:
  1. Open the page definition of the target page that cause this error
  2. Find the method action that supports the page like ("findEmployeeById")
  3. Copy it to notepad for later reference
  4. Delete it. delete it even though that it is properly defined
  5. Recreate the method action above (i did it thru the overview tab)
  6. Run

Did it work?
Can somebody explain this for me?!!

Cheers!

Saturday, January 9, 2010

EJB and ADF: BUG! JPQLEntity.getAliasName() NullPointerException (EJB @Embedded Objects)

The title above is my posting on OTN Forum. I also filed a corresponding Service Request in Oracle Support to report such behavior.

I got an update that the corresponding bug was reproduced on there side. I am still waiting for the resolution of this and will update this post for any developments.

13 January 2010: I received the confirmation from Oracle Support that they filed (bug#9281552) for this issue.

Tuesday, January 5, 2010

Oracle UI Shell: java.lang.InstantiationException TabContext$TabSelectionActionListener

The title above is my posting on OTN Forum and was noted to be a known issue. Please see Richard Wright response here.

Update: March 08, 2010. I receive an email that the fix will be available thru Check for Updates in the next two weeks.