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.

Portal Log-in

The log-in would be another challenge within this project, though Victor didn't want to waste too much energy on it, as it wasn't a key factor of the application—the application could function without it. While Victor was focusing on Jetspeed, Jim was investigating the use of <CFHTTP> for the log-in. He had a knack for quickly seeing if something would work, and soon sent Victor this email:


Date: May 28

To: Victor

From: Jim

Subject: Log-in

Hey Victor—

I'll get right to the point: CFHTTP won't work. It acts more as a proxy between the user and the site—cookies aren't set on the user's machine. There's just no way to do it with that tag.

I was thinking that instead, we could list the applications a user would need to log in for (maybe in a portlet interface), then by simply clicking a button, a new window would open and post the log-in—the user could interact with the application right there, or close it and interact with it from within the portal. We could store the log-in information (user names and passwords) so users don't have to re-enter it. It's not a complete single-signon solution, but it would work and keep it within the current budget.

Let me know what you think.


4. The Database and Data Model | Next Section Previous Section