Unfortunately, this doesn’t really satisfy the “reusability” criterion for the approach I mention. You have to write your Java code for every separate stored function your application needs to call. The idea here is (unlike the method outlined in the JDev documentation) to eliminate this-case-only Java coding.

Also, and more importantly, this really only works to retrieve scalar values. This article is actually about data sink, and its sequel is about retrieving result sets, not scalar values (I do think something like what you suggest, possibly generalized in some way, would be a good way to retrieve scalar values from DB functions).

Finally, by bypassing view and entity objects, you lose a lot of what business components provides: Cache management (especially management of large numbers of sessions), declarative validation, the ability to have multiple query collections corresponding to different data filters, the ability to have multiple, synchronized iterators over data, and so on. By using existing component types, and simply changing the way they retrieve/sink data, you can retain all of this other functionality.

example of java method

AppModuleImpl.java
…
public class AppModuleImpl extends ApplicationModuleImpl …..
…

public String adf_test_func(int num, String varch){
try {
//Connection conn = this.getDBTransaction().
// createPreparedStatement(”begin null; end;”,1).getConnection();

CallableStatement cs = this.getDBTransaction().
createCallableStatement(”begin ? := ADF_TEST_FUNC(?,?); end;”,0);
cs.registerOutParameter(1, Types.VARCHAR);
cs.setInt(2,num);
cs.setString(3,varch);
cs.execute();
String retValue = cs.getString(1);
return retValue;
}
catch (SQLException ex){
throw new JboException(ex);
}
}

thanks,
Mark Malakanov

If you’re interested in setting properties per entity object definition per user, the easiest way is probably to store them, with a key that indicates both the definition and the property (e.g., the string “mypackage.MyEntityDefName_MyProperty”) on the Hashtable returned by ApplicationModuleImpl.getSession().getUserData() for your application module. Then, create a method on your EntityObjectImpl custom framework subclass (assuming you need to use this property within particular EO instances, even though you want to store it once) like so:

public (or protected) Object getCustomProperty(String propName) {
Hashtable properties = getDBTransaction().getSession().getUserData();
String propKey = getEntityDef().getFullName() + ‘_’ + propName;
return properties.get(propKey);
}