Q&A
| Q1: | I have a monolithic program that I would like to transition into an n-tier application. How do I do this? |
| A1: | First, you need to identify from the specification what sort of target architecture is required. If your application is to be Web-enabled, you will need to provide Web-oriented functionality in the presentation layer. If you are working with persistent data, you will need data access through a data access layer. You should map out your target architecture based on the services available under the J2EE platform.
Next, you will need to sift through the monolithic code separating out the code belonging to the logical layers. This code might need to be rewritten in such a way as to make it maintainable and extensible. Introduce modularity by adopting object-oriented programming and design classes. Package these classes and design components to have maximum cohesion and loose coupling wherever possible. To implement and deploy your J2EE application, read the rest of the book and follow the examples. |
| Q2: | What is the difference between Microsoft's .NET Framework and J2EE? |
| A2: | You can build enterprise applications with both platforms. Both J2EE and .NET Framework applications can provide good levels of scalability, availability and so forth. The essential difference is largely one of choice. J2EE lets you use any operating system, such as Windows, UNIX, or a mainframe. J2EE's development environment can be chosen to suit developers from a variety of Integrated Development Environment (IDE) and J2EE application server vendors. The .NET Framework is essentially limited to the Windows family of operating systems. This allows it to be more cleanly integrated with the operating system, but reduces the choice of target platforms. |
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.