Business Object Assumptions and Limitations

The current version of wwBusiness has the following assumptions and limitations:

• Flat hierarchy Business Object Framework
  For simplicity this business object framework is based on a very simple class hierarchy. For the most part you will be dealing with methods and properties on the wwBusiness object level, with only a few support objects attached to the business object. The end result of this layout is that it's very easy to create and use business objects without having to climb a learning curve.

• Uses DataAdapter for updates
  The current version uses the DataAdapter for generating Insert and Update statements which is less than optimal in many situations. However, the framework caches DataAdapter instantiations so that the adapter retrieves this information only once. The Web Store also demonstrates how to cache the DataAdapters globally so the load only occurs once per application start.

  You can of course use custom statements by creating a custom DataAdapter.

• Connections are always opened and released for every operation
  All SQL access occurs through temporary connections. This is the approach Microsoft recommends for data access in Web applications for scalability. Performance is good as long as connection pooling is not disabled in the Connection. The only exception to this implementation are transactions. When transactions are in use the connection is reused until the transaction finishes.

In addition if you're using SQL Server you should create a new database or run the wwBusiness_SqlServer.sql Sql script to add a couple of worker tables and stored procedure to the database.