Geronimo! Part 4: Mode

As you prepare for the next expedition in the software wilderness, one thing will become clear: without a good plan, the path of adventure will not go too far. You need to know when you do something worthwhile: what you want to achieve in the end and plan for that goal will always be guided by ultimate success, as you have said, and then carefully identify milestones in the process of achieving this goal. Ultimately, the thrill of creating a well-functioning system is quite satisfying.

Apache Geronimo fully supports compliant database systems. But no matter how good your tools are, there is no good plan to define how to achieve your goals, and these tools are useless.

Tip 1: Focus on ultimate success. Don't forget the target.

Geronimo contains a large set of Java™ classes that are designed to create useful applications by sticking different tools together into one functional whole. One of the most important tools is the database. The database is complex and requires an effective plan to create and manipulate the database.

Programmes and Models

The plan is varied. Some are loose and broad; they omit a lot of detail and pursue some simple goals, such as maximizing benefits. Others are compact and concrete; In terms of accuracy, they are like computer programs. A loose plan is often considered a scheme, with some bad meaning-that is, the scheme should be avoided. But a good, compact, detail-rich plan is considered a model, which reflects a lot of ideas and efforts.

Modern database technology borrows this term to name data modeling under different database technologies. You can see examples of using this term in a programming world that uses Extensible Markup Language (extensible Markup Language, XML) schemas, database schemas, object schemas, and so on. A database schema is a plan that defines the tables of a database and the fields of each table, and gives special emphasis to key fields that are used to find additional information in other tables.

Good patterns don't fall from the sky. Construction patterns require detailed research, careful thinking, and orderly processes. This all starts with defining goals and targeting them throughout the project.

Communicate regularly and clearly

With that in mind, the best starting point is the information that you and your customers expect to see--defining forms for how systems are used and WEB pages that convey information. Geronimo faithfully executes application code, manages session data, and database connections, while dynamically generating the pages that customers (and their customers) expect to see. It is important to look at the appearance and behavior of future product systems in a shared perspective. By using JavaServer pages (JSP) to develop a page prototype, you can present your ideas to your customers, and customers can provide feedback about modifying their skins.

I know it's a cliché to say, but if you haven't clearly defined the goals ahead, it's easy to carve out a path to a good plan. Take the time to define and refine the view that the customer will see. This will ultimately make you look good in everything.

For example, suppose you are designing a Geronimo WEB application for a college student resume that covers personal information, work experience, and other information about the students, including their hobbies and interests. When you show your students the form to enter all of this information, it is wise to keep the form brief and to place the main concepts on the page: General student information pages (such as name and contact information), hobbies and interests pages, work pages, and more. One rule is that people don't like to fill out large forms with a large number of input fields, so you should minimize the number of input fields as much as possible.

Tip 2: Avoid clutter. Keep everything brief.

When dealing with large concepts, you should look closely at the relationship between the records and see a one-to-many model-for example, a student corresponding to multiple jobs or multiple clubs. This is a clear signal separating the table that holds the student's contact information from the table that holds the work experience or club experience.

Avoid moving targets

It is also important to have customers confirm the final version of these views, which avoids the constant change in the goals you are chasing. If you don't spend enough time on the original design of the forms and views that Geronimo generates, you'll inevitably get into trouble. In Geronimo, forms and views can be designed as a series of JSP pages that are embedded in Java code in a Hypertext Markup Language (HTML) page that is used to input, output, and compute the values when they are processed and displayed by the system.

Tip 3: Ask the customer to confirm all the input and output forms. Avoid moving targets.

Collect a good, long list of fields, and then proceed to the next stage, the conceptual model, in which the concept of the system is defined. The conceptual model of the student resume system should include some abstract things, such as work, profession, school, student, club and hobby.

Keep in mind the building blocks of the database and their inheritance relationships: The database consists of tables, and the tables are made up of fields. In the first phase of the construction pattern, the primary design of the input form and output report was created using key concepts such as student and work, and the goal was to create a list of the elements of the smallest unit in the database, the Information field. Examples include student ID, total average score (GPA), student's major, his or her school, and so on.

Later, the fields are grouped into the appropriate tables, and standardized rules are applied to compress the pattern. Now, just collect a list of the fields that will be used in these tables.