Home / Articles / Adobe ColdFusion / Developing a ColdFusion/J2EE Solution

Developing a ColdFusion/J2EE Solution

Chapter Description

This article kicks off in the midst of fictional Sonic Systems' web project. It shows how the aim in creating a project blueprint was to eliminate the possibility for changes in the architecture during development, and to help development go as smoothly as possible.


In beginning development, the first step was to determine the overall architecture, including the folder structure, component usage, and styles to use. The largest part of this was for

Victor to determine what component and application elements would be used for what part of the application. This would determine how modular the application would be, and who would develop what and in what order.

Component and Application Elements

ColdFusion MX brings a number of new possibilities to the design of this application. It had always been Project Omega's practice to develop applications that were as modular as possible. This allowed for easy changes in the future as needs changed and new ideas arose. One of the challenges was to determine where to use what types of modular components. Victor could now choose from Enterprise JavaBeans, regular JavaBeans, Cold-Fusion components (CFCs), custom tags, or included files. That doesn't even include non-J2EE (such as COM objects) and ColdFusion possibilities. But even before he determined what technology to use, he needed to determine how to break up the application.

Victor decided that he would have low-level components for accessing basic information, such as XML registries. Above that, he would use custom tags to perform tasks that should be modular but at the same time accessed SESSION or APPLICATION variables. In general, these custom tags wouldn't contain too much layout; anything that had more than a modicum of user interface included should be developed as an included file.

At this point, Victor's objective wasn't to decide exactly what components, custom tags, etc. the team would need to create, but rather to determine what types of information would need to be done using what types of elements. Here is what he concluded:


User information component(s) will need to return information about a user but not set it to SESSION scope or otherwise interact with the application.

User PSML component(s) would be responsible for reading a user's PSML file and returning relevant information, as well as writing and saving any changes to the appropriate XML files.

Registry component(s) would be responsible for retrieving information stored in the PSML registries.

Custom Tags

Authentication. This will allow for "locking down" secure information.

Session storage. Custom tags will be needed to write user information to session. This will include the design information highlighted by Ernie as well as other information that the user will need to access.

Portlet generation. The actual generation of portlets would probably best be done using custom tags.

Included Files

Static page drawing. Any templates that will participate in drawing the page but not contain substantial dynamic information. This section would include headers/footers and style sheets, as Ernie suggested.

Dynamic page drawing. Other templates will need to be created in order to "draw" a page dynamically for the user. This can include laying out the numerous portlets on a page or drawing any dynamic navigation elements that may be included in this application.


The portal application itself will allow a new component type, the port-let. This will be used for providing the add/edit/delete interfaces.

After determining all this, Victor had Rhonda send a memo to the development team outlining the details of what needed to be created and what the directory structure would be.

Application architecture for Sonic Systems portal

Date: June 3

To: Project Omega Development Team

From: Rhonda

Subject: Application architecture for Sonic Systems portal

We're off! It's time to begin development on the Sonic portal project. You should all have a copy of the blueprint. This memo will define how things will be done and who should do them. If you have any questions about functionality, contact Victor; about design, contact Ernie. I can field any other questions, or even serve as intermediary for design and functionality programs—just let me know what you need.

The following directories and templates will be used for the portal application (where Y is the Web root directory):


The root directory of the application. This will contain the Application.cfm and the index.cfm templates—the controller pages of this application.


This directory will contain the components of the application.


This directory will contain the style sheets of the portal. Default.css will be the default.


This directory will contain all images—subdirectories can be created, if necessary.


This protected directory will contain the database and XML registries.


This protected directory will contain dynamic templates that are included, such as the log-in and the administrative menu template.


This protected directory will contain portlets—subdirectories can contain whole portlet applications.


This protected directory will contain users' PSML files, in the appropriate subdirectory.

This protected directory will contain design information, such as includes, in the appropriate subdirectories.


This protected directory will contain any custom tags for this application.

The following tasks will be done in the following order:

  1. Create CF_PORTLET custom tag for rendering individual portlets, and registry.cfc to read PSML registry entries.

  2. Create demo information for testing, including demo portlets, anon user PSML, and demo registry.

  3. Create component to read user PSML files.

  4. Create writer(s) to set user preferences to SESSION.

  5. Create page-drawing mechanisms—the Controllers.

  6. Attach into full application.

  7. Create Administrator and single-sign-on portlets.

  8. Create "real" portlet registry and user to test.

And so, development began...

7. Portlet Rendering | Next Section Previous Section

Adobe Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Adobe Press and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Adobe Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email ask@peachpit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.adobepress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020