Using Express when the database schema does not match theclass model

Question

We are working on a large pay/personnel management system and are
evaluating Forté Express and Sage Scaffolds. We need to answer some big
questions in the near future, and I was hoping that there may be someone
out there with the answers.
1. How different can the database schema and the class model be, before
Express becomes a bad choice of framework? What solutions exist for cases
where Express is still a viable option?
2. Assuming that we can get around the problem in question 1, will the
Application Model features still work afterwards? (i.e. how sensitive are
the client-side services to changes in the database services?)
3. Express seems to use domain classes everywhere, whereas we are always
being advised to use scalar attributes wherever possible. How badly does
this affect the performance of Express applications?
4. Has anybody out there used Sage Scaffolds on a large project recently?
How did it go? What problems should we watch out for? Doesn't its 'Chain
of Responsibility' pattern tend to produce a lot of unnecessary objects at
run-time?
5. Has anybody used the Born collection classes? How do they compare with
Brahma's Fortify?
Thanks to those who have already helped - all input gratefully received!
Tim Kimber
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

I did all that before posting the orignial post..
declare
  v_schema_exists varchar2(1) := 'N';
  res             boolean;
  schemaURL       varchar2(100) := 'T0090.xsd';
  schemaPath      varchar2(100) :=  '/prmt/xsd/T0090.xsd'; --'/public/T0090.xsd';
  xmlSchema xmlType := XMLTYPE(bfilename('DIR_PRMT_OUT_CVIEW','T0090.xsd'),NLS_CHARSET_ID('AL32UTF8'));
begin
  begin
    select 'Y'
      into v_schema_exists
      from sys.all_xml_schemas  -- changed from user_xml_schemas
     where schema_url = schemaURL;
    dbms_xmlSchema.deleteSchema(schemaURL,4);
    exception
      when NO_DATA_FOUND then
        null;
  end;
  if (dbms_xdb.existsResource(schemaPath)) then
    dbms_xdb.deleteResource(schemaPath);
  end if;
  res := dbms_xdb.createResource(schemaPath,xmlSchema);   
  dbms_xmlschema.registerSchema ( schemaURL, xdbURIType(schemaPath).getClob(), TRUE, TRUE, FALSE, TRUE );
end;
/ I guess my understanding was that I could grant another oracle user access to my registered schema just like I can grant a single user access to a table. Evidently I only have two options. Only the schema owner can use the schema or everyone can use the schema and I cannot grant access to a single user other than myself.
Edited by: Mark Reichman on Jul 2, 2010 9:08 AM
Edited by: Mark Reichman on Jul 2, 2010 9:09 AM