[Opensource] JoinedDataObject DBMaint paging problem.

[maxxam at inetfreemail.co.za]

Hi,

I’m using JoinedDataObject and the javadoc says this class is still under
development and not to use it in production code. I guess this is still
the case.

When editing my JoinedDataObject with DBMaint, I cannot ever get to the
second screen of records. DBMaint always shows the first screen, even if I
press Next or the screen number. I’m not sure if this is a bug in
JoinedDataObject or perhaps it has something to do with the fact that I am
not using a xml definition file (which my compiler cannot see into and
check, and additionally I don’t know where the hell to put it so that
JBuilder sees the darn thing – why are people so xml trigger happy these
days???) so I have put the following code together:

public class ProspectJoinDB extends JoinedDataObject {

  public void setDefinitionName(String definitionName) throws DataException {
    JoinedDigesterBean definition = new JoinedDigesterBean();
    definition.addDataObject(CustomerDB.class.getName(), "ProspectJoinDB",
"CustomerDB");
    definition.addDataObject(DefaultUserInfo.class.getName(),
"ProspectJoinDB", "DefaultUserInfo");
    //definition.addDataObject(ListingDB.class.getName(),
"ProspectJoinDB", "ListingDB");
    definition.addRelation("CustomerDB", CustomerDB.FLD_CUSTOMER_ID,
"DefaultUserInfo", DefaultUserInfo.EXPUID, null);
    //definition.addRelation("CustomerDB", CustomerDB.FLD_CUSTOMER_ID,
"ListingDB", ListingDB.FLD_CUSTOMER_ID, null);

    definition.setDistinct(true);
    definition.setDescription("Prospect Join DB");

    thisDefinitionName = "ProspectJoinDB";
    initWithBean(definition, "ProspectJoinDB");
  }
}

The commented out lines of code are there because I was trying to put
together a 3-way table join, but the third table just wasn’t behaving
correctly for all sorts of things so I took it out. This seems to work OK
now for everything else except the DBMaint issue above.

Thanks,
Max