this looks quite impressive.

Some thoughts...

The examples that you give should be more than just a
banking application I think.  

I believe you should have some value-add in the book. 
For example -- when to use session storage vs request
storage.

I know there are new featues such as forwarding
actionforms (I think there is something mentioned
about this.)  It would be nice to know a practical
example of using this.

I like what you are doing with security and
exceptions.

two other people mentioned having something about
tiles and something about using ide's.  This has my
vote as well.  

I think that you should have as many references to
other complimentary books.  

Is the EJB section as complete as it can be?

How about team based development.  Setting up
sandboxes, issues with config files.

Are you using tomcat for examples?  How about some
configuration issues with other containers.  I am
thinking of weblogic...

Which tools to use for developing with custom tags (I
have hear of ultradev and it's add-ons is good). 
Other tools -- There have been numerous mentioned in
this list -- there was one today about tables and
another about struts code generators etc.


I also think you should keep in close contact with who
the developers are -- I bet they have some great ideas
on what to document -- what to expect etc.

just some thoughts


Sandeep

--- "Jesse Alexander (KADA 12)"
<[EMAIL PROTECTED]> wrote:
> Hi,
> 
> sounds good...
> 
> Chapter 1 + 2: hopefully short, as they appear in
> (almost) every Java-server-related book
>                keep them to what Struts does
> differently
> Chapter 8: Is this an introduction into using a
> taglib (then make it short) or an intro
>            into writing a taglib (does it fit into
> the O'Reilly focused and small approach?)?
> Chapter 9: Where is the Struts-related part? That
> chapter can cover books on its own...
> Chapter 13: Make it a bit more general: Separating
> Struts (Presentation) from EJB or 
>             plain Javabeans (business logic). Almost
> the same rules apply to JavaBeans
>             as well as EJB's. Samples could also be
> EJB only...
> Chapter 18: Logging is important also for the
> Business-Logic, so it should be 
>             separated from Struts...
> Chapter 20+21: Important for people learning Struts,
> so do them well
> 
> Appendix A: Depending on the format could fill up
> the book without aiding to much.
>             Explain how one can find them after
> having installed Struts on his
>             development machine.
> Appendix C: Tends to be old before the book is
> published...A pointer to [Struts_Home]
>             might be enough
> 
> regards
> Alexander
> 
> -----Original Message-----
> From: Chuck Cavaness
> [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, January 27, 2002 7:58 PM
> To: [EMAIL PROTECTED]
> Subject: OReilly Struts book
> 
> 
> I just wanted to let everyone know that I just
> signed a contract to write a 
> book on Struts for O'Reilly. The book just got
> underway, so
> it will not be out until the late summer or early
> fall.
> 
> I've included a rough working outline here, but
> realize that it's a work in 
> progress and I will continue to flush out the
> details over
> the coming days. If you have any suggestions for
> things to add, please feel 
> free to send them to [EMAIL PROTECTED] so as
> to not flood the newsgroups.
> 
> I've used Struts since the beginning and watched it
> evolve into a the great 
> framework that it is today and for sure will be
> when all of the 1.1 functionality gets rolled in. I
> intend to cover both 
> 1.0 and 1.1 functionality, although I haven't
> figured out the
> cleanest way to handle the envoling functionltiy.
> I've started a dialog 
> with Ted and he's given me some good ideas.
> 
> I just finished co-authoring "Special Edition EJB
> 2.0" and "Special Edition 
> Using Java 2" and I'm planning on the book
> having a heavy focus on EJB and J2EE, since that is
> my current use of the 
> framework.
> 
> The working outline follows...
> Chuck
> 
> 
> O'Reilly Struts Working Outline
> 
> Chapter 1.    Introduction to Struts
>    Brief History of the Web
>    What are Servlets?
>    JavaServer Pages Technology
>    JSP Model 1 and Model 2 Architectures
>    Why is Model - View - Controller So Important?
>    Creation of the Struts Framework
>    Alternatives to Struts
> Chapter 2.     The Web Server/Servlet Container
> Relationship
>    An Understanding of the Physical Architecture
>    The Request/Response Phase Explained
>    The HttpRequest, HttpResponse, and HttpSession
> Objects
>    Using a Get Versus a Post (Where does this
> belong?)
>    Redirecting Versus Forwarding
>    Using URL Parameters
>    Available Web Servers and Servlet Containers
> Chapter 3.    Overview of the Struts Framework
>    Looking at the Big Picture
>    A Banking Account Example
>    Struts Controller Components
>    Struts Model Components
>    The Struts View Components
>    Life Cycle of a Struts Request
>    Summary
> Chapter 4.    Configuring web.xml and struts-config.xml
> Chapter 5.    Struts Controller Components
> Chapter 6.    Struts Model Components
> Chapter 7.    Struts View Components
> Chapter 8.    Custom Tag Libraries
> Chapter 9.    Building a Web Tier Framework
> Chapter 10.   Exception Handling
> Chapter 11.   Externalizing the Struts Validation
> Chapter 12.   Internationalization and Localization
>    What is Internationalization and Localization?
>    Internationalizing your Struts Applications
>    Determining the User Locale
>    Configuring the Struts Resource Bundle
>    Performing Localization with Struts
>    Supporting Multiple Currencies
>    Internationalizing a Database
> Chapter 13.   Struts and Enterprise JavaBeans (EJB)
>    Struts and Enterprise JavaBeans
>    EJB Home and Remote References
>    What is a Proxy?
>    The RemoteProxy Pattern
>    Building a RemoteProxy Object for Your Web
> Application
>    Using JNDI in a Struts Application
>    Developing a RemoteProxy Framework
>    Using Dynamic Proxies
>    Using Debug Proxies
> Chapter 14.   Security in your Struts Web Applications
>    Web Application Security Features
>      Authentication
>      Authorization
>      Audit Trails
>      Repudiation
>    Dealing with Session Timeouts and Invalid Login
> Attempts
>    Performing Page-Level Security
>    Modifying the struts-cfg.xml for security
>    Using HTTPS/SSL with Struts
> Chapter 15.   Building Dynamic Menus
> Chapter 16.   Paging and Sorting
> Chapter 17.   Navigation Trails
> Chapter 18.   Logging in a Struts Application
>    Logging in a Web Application
>    System versus Application Logging
>    Using the Servlet Container for Logging
>      Using Filters
>      Using Event Listeners
>    Struts Internal Log Messages
>    Traditional Buy versus Build Analysis
>    Using the log4j Logging Framework
>      Brief look at Java Class Loaders
>      What do Class Loaders have to do with log4j?
>    Integrating log4j with Struts
>      What are Loggers?
>      Configuring log4j Appenders
>      Initializing log4j
>      Log file Rollover
>      Setting the Log file location
>      Logging within the Struts Framework
>    Protecting your application from change
>    Using the Log4j Tag Library
>    Creating an Email Appender
>    The Performance impact of Logging
>    Third-Party log4j Extensions
>    Java 1.4 Logging API
> Chapter 19.   Addressing Performance
> Chapter 20.   Struts Design Strategies
> Chapter 21.   Packaging your Struts Application
> Chapter 22.   Co-Branding and Personalization
> Appendix A. Struts API
> Appendix B. Downloading and Installing Struts
> Appendix C. Struts Resources
> Appednix D. Changes in Struts 1.1
> 
> 
> --
> To unsubscribe, e-mail:  
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> --
> To unsubscribe, e-mail:  
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 


__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to