It is very easy to start developing your first XPages application in the same design template or database where your existing forms and views resides. In this short article we will see why is not a good idea and I will demonstrate this with a simple example.
We will start by creating a simple XPage with the following code in a database which resides on a Domino server:
This will show us the current session ID allocated to us by the Domino server when previewed in a web browser.
Create a local replica of this database, replicate and then go back to the browser and refresh the page. We will still notice that the session ID remains the same, but what about our scope values? Continue reading
In the previous installment of this series we began to build the Model layer described in the Model-View-Controller (MVC) architecture. In that article we covered low level database interaction classes as well as the representation of the data object for our sample Employee application. To recap, we designed the following classes four our Model layer:
- Employee: A base foundation class representing the employee data. The fields in this class, for our simple application, correspond to the fields on a Notes form.
- DominoEmplyeeDAO (and EmployeeDAO interface): The DominoEmplyeeDAO contains all of the code that processes the low level Domino database specific language for creating, reading, updating, and deleting an employee. The concrete class DominoEmployeeDAO implements the EmployeeDAO interface. The interface defines the generic method signatures that must be created by any class implementing that interface. This allows us to define a structured set of methods for working with any database without the requirement that client code have knowledge of the type of database implemented.
In a “real world” application there will be many “Employee” type Continue reading