Historical errata for Stripes

Perhaps there is a better example than the Display Tag table? The text doesn’t mention it, but it brings along a ton of cruft from apache commons.

It looks like using a type converter/formatter for Contact introduces a regression.

To reproduce:

- deploy the “email_06” and “email_07” examples

- click on “Update” for “Ballou”

- replace his last name by “B”

- click on “Cancel”
- for “email_06”, the app behaves as expected: nothing has changed. For “email_07” though, the last name has unfortunately been changed (it is “B” now). Same for “email_08” and “email_09” at least.

Environment:

- Java 1.5.0_15

- Apache Ant 1.7.1

- Apache Tomcat 5.5.26
- Stripes 1.5 SNAPSHOT 950

The book says, “To install the JSTL, copy the following
two JARs from the Stripes distribution to your WEB-INF/lib directory: jstl.jar, standard.jar”

But those files don’t appear to be in the Stripes 1.5 distribution! I downloaded them from http colon slash slash jakarta.apache.org/site/downloads/downloads_taglibs-standard.cgi

“Stripes is mostly present the Controller and View parts” should read “Stripes is mostly present in the Controller and View parts”

You have in the book’s code listing but never mention ViewSourceActionBean.java. A few words on View Source would have been nice.

On page 328, just under “brown box”, with title “Stripes never ceases to amaze me”,
there is a closing tag , which should be above brown box (I think)..

“To use the Display Tag, add its required JAR files to the /WEB-INF/lib
directory, and declare the library in taglibs.jsp:”

It would be nice if you listed exactly what jar files are required in the book and where they are located in the code provided rather than having to go to an external website.

Love the book though. Nice job.

Stripes treats an event handler as the default when
* the event handler is annotated with @DefaultHandler, and
* the event handler is the only one defined in the action bean.

Should the “and”, at the end of the first bullet, be an “or” ?

/WEB-INF/classes/translations/fieldNames.properties
/WEB-INF/classes/translations/fieldNames_fr.properties

must be …

/WEB-INF/classes/translations/fieldLabels.properties
/WEB-INF/classes/translations/fieldLabels_fr.properties

LoginInterceptor.java has compilation error without comment closing properly.

in code section (before section 3.3 )
“” should use font’s color ‘red’ instead of ‘blue’.

in section ‘2.2 Hello, Stripes!’ the line shown in the example file structure:
WEB-INF/classes/stripesbook/action/HelloActionBean.class
should be:
WEB-INF/classes/stripesbook/action/HelloActionBean.java

The line in the example jsp (contact_list.jsp) at the bottom of the page that reads:

should be:

OOPS! tech error #38227 is NOT an error. my bad!! (please delete)

The line UrlBinding("/action/contact_list/${event}") should probably read UrlBinding(“/action/contact_list/{$event}”)

following line in getCurrentFolder()
int id=(c!= null)Integer.parseInt(c.getValue()):0;
should be:
int id=(c!= null)?Integer.parseInt(c.getValue()):0;
and maybe for the sake of readability:
int id = ((c!= null) ? Integer.parseInt(c.getValue()) : 0);

Book states “The formatType= attribute could also have been omitted to use the formatter’s default”.

Actually, ommitting the formatType attribute causes a null pointer exception. PhoneNumberFormatter does not set a default value for the formatType field.

Simple fix is to modify the init() method:

public void init() {
if (this.formatType == null) {
formatType = “dashes”;
}
}

Second sentence “sent” should be “have sent” or “send”

Excellent book. It’s been incredibly useful on my current project.

Bug in Ajax functionality to filter contact list. The column sort functionality does not work properly after the user has filtered the contact list. In this case the server only returns the contact list table, not the whole page. Cause is sort functionality in DisplayTag is sending the _evenName parameter. One resolution is to add the excludedParams=“_eventName” attribute to the tag.

The PDF version contains many non-fuctional page links throughout the index.

e.g. Aliases, 204, 205f, 210, 213

The page number entry “205f” is shown in black, and is not a functioning link.

The functioning page numbers 204, 210 and 213 are in red and work as expected.