Chris Siemback

In the March issue of JDJ (Vol. 6, issue 3) we discussed the basics behind J2EE security, including coverage of role-based security for both the Web and EJB tiers. In Part 2, we provide an example of implementing J2EE security in the WebLogic Server. While this article and the examples contained within are specific to WebLogic 6.0, all of the deployment code and standard descriptors should be portable to any J2EE-compliant server. We won't cover encryption and SSL this month, as they're articles in their own right. Trader Application How many securities trading examples have you seen to date? Too many, I bet you'd say. Well, we decided airline reservation systems and "hello, world" programs are way too overused. Even though the stock market is not a hot topic these days, in an effort to spend more time explaining J2EE security and less time talking about business re... (more)

The Decision Process: Moving to WebLogic Platform 7.0

BI, a company that specializes in business improvement programs for a wide range of companies, leverages J2EE for many of its software solutions. In fact, we've had several J2EE-based applications in production for years. Our flagship online media redemption vehicle is one such application, and is one of our largest. The application is an online catalog, which participants can use to redeem media for products. This application was the catalyst for our move to WebLogic 7.0. In this article, I'll discuss the following: Why we decided to change application servers How we came up wi... (more)