I'm definitely going to cover some design patterns/strategies related to Struts and EJB. I've been working on an a Struts/EJB application for over a year now and have learned a great deal about how to approach this, so this should be valuable to others. Brian Keeton and I just finished an EJB 2.0 for Que and I will include some ideas we discovered while writing that as well. Someone did point out to me however that obviously not everyone is using EJB and I should give focus to that as well.
The banking example is only used in chapter 3, which is an overview of Struts. From the point on, I plan to use other examples. Right now, I'm in the B2B world where orders, items, catalogs, and customers are important. So I might use that domain. Hopefully, I can use various "real" domains to bring something for everyone. Since I first posted the initial TOC, I've added several new chapters and taken away some. One of the ones that everyone has asked for is a chapter on alternatives to JSP. So a chapter on XML/XSLT or something along these lines will probably make it in. The new features like multiple sub-apps, workflow, role-based actions, etc... definitely will make it in. I'm not sure where at in the book, but for sure will be very important. Chuck -----Original Message----- From: Hertzel Karbasi - OPTinity eBusiness Solutions [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 05, 2002 10:11 AM To: Struts Users Mailing List Subject: Re: OReilly Struts book Great!! 1. IMO it's better to cover Struts 1.1 as I see in your TOC there is a just and appendix for changes in 1.1. 2. Are you going to cover some design patterns related to J2EE+EJB in reference to Struts? 3. An Order Entry/Shopping Cart application would be more usable and popular than Banking. 4. What about XML/Wap in view components? 5. What about extending Struts (Workflow, Service Manager, Data Formatting, ...)?
