[JAVAEETUTORIAL-114] create actual examples instead of inviting user to imagine Created: 28/Jun/12  Updated: 19/Jul/13  Resolved: 19/Jul/13

Status: Closed
Project: javaeetutorial
Component/s: doc, examples
Affects Version/s: 6.0.7-5
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Brant Gurganus Assignee: Kim Haase
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

This issue is in the "The immediate Attribute" section of the page entitled "Adding Components to a Page Using HTML Tags" at http://docs.oracle.com/javaee/6/tutorial/doc/bnarf.html. The third paragraph in this section starts with "Assume that you have a page with a button and a field for entering the quantity of a book in a shopping cart." Why are we assuming here? This is a tutorial, so have readers open an existing example of this scenario or code it up and see what happens. This also relates to other feedback on the sequencing of describing how immediate works without describing the ordinary request lifecycle. The user doesn't yet have the context to imagine what would happen.



 Comments   
Comment by Kim Haase [ 06/Jul/12 ]

This is a good suggestion, and we should do something with this section. We have been hoping to add some simpler examples along with the large case study. I'm not absolutely certain that the immediate attribute is the best candidate for such an example, but I'll certainly try.

JAVAEETUTORIAL-88, when fixed, should help provide more lifecycle context at this point.

There's also a subject-verb agreement typo ("occurs" in the 4th paragraph) that should be fixed.

Comment by Kim Haase [ 24/Apr/13 ]

Deferring to an update release later in the year.

Comment by Kim Haase [ 19/Jul/13 ]

Since the lifecycle information is now provided before this chapter, users have the information needed to understand the hypothetical situation presented. The section does describe in detail an example from the case study that provides a more realistic use case.

Generated at Sun Apr 19 03:27:15 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.