1) The user clicks on one of the navigator item, so Navigator invokes XmlForm Runtime to launch the corresponding XmlForm. 2) XmlForm Runtime deserializes the XmlForm file and initializes the corresponding Controller (Windows form) instance, then attaches the associated FormPlugin to the Controller instance. 3) Either Controller or FormPlugin invokes a service method through Service Proxy in order to response to the user's action on the form. 4) Service Proxy accesses the web service by using WCF. 5) Service Broker receives the web service request from client, then initializes a database transaction, and invokes the proper Manager method to proceed the business logic and catches all the unhandled exceptions in the Manager method. 6) Manager manipulates business entity through DAO object to finish the business logic. 7) DAO utilizes NHibernate component to execute the entity query. 8) NHibernate converts the entity query to the database query and then execute it through native SQL Client (for SQL Server) or ODBC driver (for ISAM File).
(1)generat service broker/ client proxy. (2)build all solution (3)utility pl scripts.
(1)Package Responsblility (2) Business Code ->Script, Script.Shared, Service implementation
Shared.sln, Entity, Model, Util
One of the best UI Presentation Framework Commercial but Complex, we wrapped to TcmEditors
OR Mapping Tool Relay on ADO.net
Prons, More OO, DataTable -> bug prone, Use Dot., Consistent way of people thinking, Easy Mnt
It’s library that can be used by to access data and data services. NHibernate also relies upon it, but sometimes we could simply use ADO.Net directly in application code to inquiry/update data, especially when we want to operate upon DataTable instead of entity