[JAVAEETUTORIAL-192] Bug in Tutorial PDF Created: 12/Jun/13  Updated: 24/Jun/13  Resolved: 24/Jun/13

Status: Resolved
Project: javaeetutorial
Component/s: doc
Affects Version/s: 7.0.1
Fix Version/s: 7.0.1

Type: Bug Priority: Major
Reporter: arungupta Assignee: jendrock
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Section 1.1 of Java EE 7 Tutorial PDF says:

New technologies, including the following:

  • Whatever gets in

Online version at http://docs.oracle.com/javaee/7/tutorial/doc/overview001.htm#GIQVH is correct.

Got the following comment from a community member "I wonder if somebody has done the QA of the tutorial?".



 Comments   
Comment by Ian Evans [ 24/Jun/13 ]

Fixed in 7.0.1-3 update.





[JAVAEETUTORIAL-182] Material missing from overview chapter Created: 07/Jun/13  Updated: 24/Jun/13  Resolved: 24/Jun/13

Status: Resolved
Project: javaeetutorial
Component/s: doc
Affects Version/s: 7.0.1
Fix Version/s: 7.0.1

Type: Bug Priority: Major
Reporter: Kim Haase Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The Platform Highlights section of the Overview is missing a list of new Java EE technologies, and the section on EJB technology that is cross-referenced from there has "TBA". New features for other technologies are missing (JMS should be mentioned).



 Comments   
Comment by Kim Haase [ 07/Jun/13 ]

Checked in some fixes to overview.fm. More may be needed. Please let me know.

Comment by Ian Evans [ 24/Jun/13 ]

Fixed in 7.0.1-3.





[JAVAEETUTORIAL-180] Fix/Redo tables 18-1 and 18-2 in the WebSocket chapter Created: 06/Jun/13  Updated: 11/Jun/13  Resolved: 11/Jun/13

Status: Closed
Project: javaeetutorial
Component/s: None
Affects Version/s: 7.0.0
Fix Version/s: 7.0.1

Type: Improvement Priority: Major
Reporter: rcervera Assignee: rcervera
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: html

 Description   

The tables don't look good on the HTML output.



 Comments   
Comment by rcervera [ 11/Jun/13 ]

Table 18-1 was redesigned to render properly in the HTML view.
Table 18-2 was converted to an itemized list to render properly in the HTML view.

Comment by rcervera [ 11/Jun/13 ]

Fixes will appear in the next nightly build. Fix for Table 18-1 is already incorporated into the latest nightly build.





[JAVAEETUTORIAL-178] 17.6 The mood example application, should go before 17.5 The fileupload example application Created: 06/Jun/13  Updated: 11/Jun/13  Resolved: 11/Jun/13

Status: Closed
Project: javaeetutorial
Component/s: None
Affects Version/s: 7.0.0
Fix Version/s: 7.0.1

Type: Improvement Priority: Minor
Reporter: rcervera Assignee: rcervera
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

mood is a more basic example, so it should come before the fileupload example.



 Comments   
Comment by rcervera [ 11/Jun/13 ]

Fixed in the book sources.





[JAVAEETUTORIAL-177] Fix/Redo tables 17-4, 17-5, and 17-6 (Servlets) - Description column is too narrow and hard to read Created: 06/Jun/13  Updated: 11/Jun/13  Resolved: 11/Jun/13

Status: Closed
Project: javaeetutorial
Component/s: None
Affects Version/s: 7.0.0
Fix Version/s: 7.0.1

Type: Improvement Priority: Major
Reporter: rcervera Assignee: rcervera
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

These tables need to be redesigned or fixed. The description column is too narrow and hard to read on the HTML output.



 Comments   
Comment by rcervera [ 11/Jun/13 ]

These tables have been redesigned in the sources.





[JAVAEETUTORIAL-175] 17.12.2 Waiting for a Resource - Replace the 'Resource' type in this example as it may get confused with @Resource Created: 06/Jun/13  Updated: 11/Jun/13  Resolved: 11/Jun/13

Status: Closed
Project: javaeetutorial
Component/s: None
Affects Version/s: 7.0.0
Fix Version/s: 7.0.1

Type: Improvement Priority: Major
Reporter: rcervera Assignee: rcervera
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

This sections shows how to use asynchronous processing in Servlet using the access to some resource as an example. The type of the resource should be changed from 'Resource' to 'MyResource' or similar to avoid confusion with @Resource.



 Comments   
Comment by rcervera [ 11/Jun/13 ]

Replaced Resource with MyRemoteResource.





[JAVAEETUTORIAL-173] Augment information on starting app server Created: 06/Jun/13  Updated: 24/Jun/13  Resolved: 24/Jun/13

Status: Resolved
Project: javaeetutorial
Component/s: doc
Affects Version/s: 7.0.1
Fix Version/s: 7.0.1

Type: Improvement Priority: Major
Reporter: Kim Haase Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
JAVAEETUTORIAL-199 Add links back to Starting and Stoppi... Sub-task Resolved  

 Description   

The section "Starting and Stopping the GlassFish Server" in Chapter 2 currently describes how to start the server from the command line first, then describes starting it from NB.

However, if a user starts the server from the command line but then goes on to use NB for most examples, there can be some awkwardness attaching NB to an already running server.

It would be better to reorganize this section to have a brief intro to the effect that you can start and stop the server using either NB or the command line, and then have two subsections the way we do for running the examples, with the first one on NB and the second on the command line.

Also, the instructions on running the first couple of web examples (at least) should mention as the first step that the server needs to have been started (with an xref to the section). Some writers are already very conscientious about doing that, but I have not been.



 Comments   
Comment by Kim Haase [ 06/Jun/13 ]

Checked in fixes to usingexamples.fm and webapp.fm. Leaving open for additional modifications as needed. Suggestions welcome.

Comment by Ian Evans [ 24/Jun/13 ]

Augmented starting/stopping instructions added in 7.0.1-3. Created subtask for cross-references to this section from example instructions.





[JAVAEETUTORIAL-169] Code copied and pasted into Frame does not show line breaks in the HTML output Created: 05/Jun/13  Updated: 05/Jun/13  Resolved: 05/Jun/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 7.0.1
Fix Version/s: 7.0.1

Type: Bug Priority: Major
Reporter: rcervera Assignee: rcervera
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

When you sometimes paste code from an editor into Frame, it looks good in the Frame view and the PDF, but the line breaks are not really new lines, and they do not show up correctly on the HTML output.

We have to ensure that each line in the example has its own ProgramListing structure element.

Examples of affected files:

servlets015.htm
websocket011.htm
batch-processing008.htm



 Comments   
Comment by rcervera [ 05/Jun/13 ]

Fixed in the doc sources.

Comment by Ian Evans [ 05/Jun/13 ]

Which code editor did you paste in from? I've pasted from NetBeans, TextPad, and emacs with no apparent problems.

Comment by rcervera [ 05/Jun/13 ]

I always pasted from NetBeans, and it worked fine 95% of the time. There were a few cases where it did not work properly. The line break characters appear on FrameMaker but several lines where grouped together in the same ProgramListing.

Comment by Kim Haase [ 05/Jun/13 ]

Ricardo's right. You have to be really, really careful how you paste from NB. I think pasting into a new, empty programlisting element works okay, but trying to overwrite existing code can produce strange results. You really have to look not only at the Frame page (where the newlines look fine) but also at the structure to make sure the new code isn't all in one programlisting element.





[JAVAEETUTORIAL-167] Modify JPA examples to use java:comp/DefaultDataSource instead of jdbc/__default Created: 03/Jun/13  Updated: 03/Jun/13  Resolved: 03/Jun/13

Status: Resolved
Project: javaeetutorial
Component/s: examples
Affects Version/s: 7.0.0
Fix Version/s: 7.0.1

Type: Bug Priority: Major
Reporter: Ian Evans Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

From Java EE 7 Platform Spec section EE.5.19:

The Java EE Product Provider must make the default data source accessible to the application under the JNDI name java:comp/DefaultDataSource.

jdbc/__default is not portable.



 Comments   
Comment by Ian Evans [ 03/Jun/13 ]

Fixed in source. Will be available in 7.0.1.





[JAVAEETUTORIAL-166] Misaligned text in the Creating Facelets Views section Created: 27/May/13  Updated: 28/May/13  Resolved: 28/May/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.8
Fix Version/s: 7.0.1

Type: Bug Priority: Trivial
Reporter: Michael Dobrovolsky Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Misaligned text in the Creating Facelets Views section. After the words The next section uses various tags to insert components into the web page: the alignment of opening and closing <head> tags is different:

<h:head>
    ...       
    </h:head>


 Comments   
Comment by Kim Haase [ 28/May/13 ]

Will be fixed in the Java EE 7 tutorial.





[JAVAEETUTORIAL-165] Broken link to Mojarra Release Notes Created: 27/May/13  Updated: 28/May/13  Resolved: 28/May/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.8
Fix Version/s: 7.0.1

Type: Bug Priority: Minor
Reporter: Michael Dobrovolsky Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Broken link to Mojarra Release Notes in the section Further Information about JavaServer Faces Technology. Should be https://javaserverfaces.java.net/2.1/releasenotes.html instead of http://javaserverfaces.java.net/nonav/rlnotes/2.1.4/.



 Comments   
Comment by Kim Haase [ 28/May/13 ]

We are removing links to this volatile location from the Java EE 7 tutorial.





[JAVAEETUTORIAL-164] Broken link to the terms of the License for tutorial examples source files Created: 27/May/13  Updated: 28/May/13  Resolved: 28/May/13

Status: Closed
Project: javaeetutorial
Component/s: examples
Affects Version/s: 6.0.8
Fix Version/s: 7.0.1

Type: Bug Priority: Minor
Reporter: Michael Dobrovolsky Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Comment sections of tutorial source files point to the terms of the License at: http://developers.sun.com/license/berkeley_license.html but this link redirects to http://www.oracle.com/technetwork/java/index.html.



 Comments   
Comment by Kim Haase [ 28/May/13 ]

The link in the Java EE 7 tutorial examples goes to http://java.net/projects/javaeetutorial/pages/BerkeleyLicense.





[JAVAEETUTORIAL-163] Different location of the Reload Enabled check box in GlassFish Server 3.1.2.2 Created: 27/May/13  Updated: 28/May/13  Resolved: 28/May/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.8
Fix Version/s: 7.0.1

Type: Bug Priority: Minor
Reporter: Michael Dobrovolsky Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

GlassFish Server Open Source Edition 3.1.2.2 (build 5)



 Description   

In the recent version of GlassFish Server (3.1.2.2) the Reload Enabled check box is located not in the Advanced tab of the GlassFish Server node as described in the section To Disable or Modify Dynamic Reloading but in the Applications Configuration tab of the Domain node instead.



 Comments   
Comment by Kim Haase [ 28/May/13 ]

The Java EE 7 tutorial will not provide instructions on disabling dynamic reloading, since this is an advanced task.





[JAVAEETUTORIAL-161] Fixes needed to section on CDI and resource adapters Created: 30/Apr/13  Updated: 30/Apr/13  Resolved: 30/Apr/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.8
Fix Version/s: 7.0.1

Type: Bug Priority: Major
Reporter: Kim Haase Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

We received the following request. In fact we had documented that you could not use a resource adapter as a managed bean, but the statement was not very clear. This will be fixed in the EE 7 tutorial.

-------- Original Message --------
Subject: Re: Injecting RA into a servlet?
Date: Thu, 25 Apr 2013 23:03:21 +0530
From: Sivakumar Thyagarajan <sivakumar.thyagarajan@oracle.com>
To: marina.vatkina@oracle.com
CC: RAMU,JAGADISH <jagadish.ramu@oracle.com>

Hi Marina

On Thursday 25 April 2013 06:25 AM, Marina Vatkina wrote:
> Siva, Jagadish,
>
> According to the Java EE Tutorial
> (http://docs.oracle.com/javaee/6/tutorial/doc/gmgjb.html) you can inject
> a RA. Are there a place to read more about it? Which API can be called
> on the injected ref? Are there any devtests that I can look at?

This appears to be an error. I will report this to the docs team to have
this fixed. Thanks for pointing this section to us.

In EE 6 the behaviour was undefined though the presence of a beans.xml
in rar would make the RAR a bean archive.

Section 21.5 in [1] now describes the new DI related requirements we
brought in the Connectors MR in EE 7. It is not recommended now to use
the ResourceAdapter class as a Bean as it is not portably supported.

Thanks
--Siva.
[1]
https://java.net/projects/connector-spec/downloads/download/connector-1_7-spec-with-change-bars-20130315-2.pdf.zip






[JAVAEETUTORIAL-158] dukesbookstore: Error in Messages_de.properties CartItemCount value Created: 27/Feb/13  Updated: 27/Feb/13  Resolved: 27/Feb/13

Status: Resolved
Project: javaeetutorial
Component/s: examples
Affects Version/s: 6.0.8
Fix Version/s: 7.0.1

Type: Bug Priority: Minor
Reporter: swiss-chris Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 5 minutes
Time Spent: Not Specified
Original Estimate: 5 minutes

Tags: properties

 Description   

Messages_de.properties contains the following line:

CartItemCount=Ihr Einkaufswagen enthält {0,choice,0#Ihr Einkaufswagen enthält keine Artikel|1#Ihr Einkaufswagen enthält einen Artikel|1< Ihr Einkaufswagen enthält

{0} Artikel}.

Output for a cart with exactly one element: "Ihr Einkaufswagen enthält Ihr Einkaufswagen enthält einen Artikel."

Proposed correction:

CartItemCount=Ihr Einkaufswagen enthält {0,choice,0#keine Artikel|1#einen Artikel|1<{0}

Artikel}.

Output for a cart with exactly one element: "Ihr Einkaufswagen enthält einen Artikel." (Correct also for 0 or 1< elements in cart).

p.s. I speak, read and write German perfectly (but I believe the correctness of my proposal can be deduced merely from understanding the Java MessageFormat syntax).



 Comments   
Comment by Kim Haase [ 27/Feb/13 ]

Thanks very much for catching this. If you find any more errors in those messages, please let us know.

Committed to EE 6 branch at revision 1182.

Committed to trunk at revision 1183.





[JAVAEETUTORIAL-121] technically unspecified default is unspecified not first item Created: 07/Jul/12  Updated: 24/Apr/13  Resolved: 24/Apr/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.7-5
Fix Version/s: 7.0.1

Type: Bug Priority: Major
Reporter: Brant Gurganus Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

In the second to last paragraph under the "Displaying a Menu Using the h:selectOneMenu Tag" section of the "Adding Components to a Page Using HTML Tags" page at http://docs.oracle.com/javaee/6/tutorial/doc/bnarf.html, it indicates that, "If you don't provide a value, the first item in the list is selected by default." However, this is inaccurate. I have tested this out, and it renders as a <select> element with nested <options>. No <option> is marked as selected. If you look at the HTML 4.01 specification under section 17.6.1 at http://www.w3.org/TR/html4/interact/forms.html#h-17.6.1, you will see that it indicates that "If no OPTION element has the selected attribute set, user agent behavior for choosing which option is initially selected is undefined."



 Comments   
Comment by Brant Gurganus [ 07/Jul/12 ]

This unspecified selection issue also occurs in the following "Displaying Components for Selecting Multiple Values" section as well.

Comment by Kim Haase [ 09/Jul/12 ]

I've tried this, and JSF does consider the first item as selected if you use a selectOneMenu tag – but not if you use selectOneListbox or selectOneRadio. (If you output the selected values on a response page, you can see the effect.)

Comment by Brant Gurganus [ 10/Jul/12 ]

JSF considering the first item as selected is incorrect. It is the browser making that judgment. If you look at the HTML specification excerpt, nothing requires the first option to be the selected one. Most browsers will do so though. Because of the implementation detail, the first item gets submitted as the value. It's not a blank value being submitted. However, that is not JSF doing so. That is the browser doing so. Some browsers might pick the third option instead. There's no requirement that it be the first item.

If you were correct, an <h:selectOneMenu> with no value would render as:
<select><option selected="selected">a</option><option>b</option></select>

Instead, it renders as:
<select><option>a</option><option>b</option></select>

That second rendering leaves you in unspecified territory for which item to select initially.

Comment by Kim Haase [ 11/Jul/12 ]

Thanks, Brant. I expect you are correct and am checking with the spec leads to confirm, since the misinformation has been in the tutorial since EE 5.

Comment by Kim Haase [ 24/Apr/13 ]

Fixed in 7.0.1.





[JAVAEETUTORIAL-118] note that since the IDs are generated the IDs may not match Created: 07/Jul/12  Updated: 24/Apr/13  Resolved: 24/Apr/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.7-5
Fix Version/s: 7.0.1

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


 Description   

There is an example at the end of the "Rendering a Hyperlink with the h:commandLink Tag" section of the page at http://docs.oracle.com/javaee/6/tutorial/doc/bnarf.html titled "Adding Components to a Page Using HTML Tags". It may be worth noting that the IDs are generated so they may not match. I believe there are also two JSF implementations. I'm sure MyFaces wouldn't generate calls to functions in a mojarra object.



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

We definitely need to point out that the generated IDs are implementation-specific and that the prefixes will probably not be the same as the ones shown.

I think there are even more than two JSF implementations around, but we assume that tutorial users are using only GlassFish.

Comment by Ian Evans [ 09/Jul/12 ]

I'm trying to understand why the generated IDs would matter to web developers, and I'm coming up empty.

It's true that the generated IDs in the HTML will vary by implementation, since the spec doesn't require them to match the IDs in the Facelets tags. But I can't think of a use-case where output HTML from one implementation would mix with output HTML from another implementation.

The only scenario I can think of where the IDs matter is for a custom Javascript library. However, if you're writing your own Javascript that uses the HTML tag IDs, you're going beyond the platform, and are relying on non-portable features.

Comment by Brant Gurganus [ 09/Jul/12 ]

I agree with Ian's statements. However, in the context of a tutorial, there can be an expectation that what is shown in output in the tutorial would match your own output. The issue is more about that expectation and managing that than about interoperating with the IDs.

Comment by Kim Haase [ 24/Apr/13 ]

I think that for anyone running GlassFish the output will be exactly that or something very similar, but I changed it to "HTML that looks something like the following".

Fixed for 7.0.1.





[JAVAEETUTORIAL-116] give example of binding Created: 28/Jun/12  Updated: 24/Apr/13  Resolved: 24/Apr/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.7-5
Fix Version/s: 7.0.1

Type: Improvement Priority: Major
Reporter: Brant Gurganus Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

In the section on "The value and binding Attributes" on the page entitled "Adding Components to a Page Using HTML Tags" at http://docs.oracle.com/javaee/6/tutorial/doc/bnarf.html, I'd like to see an example of the binding attribute. In ramping up on PrimeFaces and JSF in general, I've seen several components having the binding attribute, but I haven't seen any good documentation on its use yet. I think a little more description would be helpful in this part of the tutorial.



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

We need at least to provide a forward reference to where the binding attribute is discussed ("Writing Properties Bound to Component Instances" in Chapter 9), and possibly to improve the explanation in that section. The discussion of both the value and binding attributes belongs in Chapter 9 because it's more closely related to the writing of managed beans than to the writing of Facelets pages.

Comment by Kim Haase [ 24/Apr/13 ]

Fixed for 7.0.1.





Rework JSF lifecycle information (JAVAEETUTORIAL-88)

[JAVAEETUTORIAL-113] section depends on knowledge not yet covered (bad sequencing) Created: 28/Jun/12  Updated: 24/Apr/13  Resolved: 24/Apr/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.7-5
Fix Version/s: 7.0.1

Type: Sub-task Priority: Minor
Reporter: Brant Gurganus Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

This occurs in "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 section mentions the "force events, validations, and conversions to be processed when request parameter values are applied." However, the page request lifecycle that tells the ordinary sequencing of these activities has not yet been covered in the tutorial. At a minimum, it'd be good to link elsewhere in the tutorial where such things are covered, so you have the appropriate context to understand that section. Ideally, the tutorial would be sequenced with this section coming sometime after the section covering that request lifecycle.



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

Good point. I'm making this a sub-task of a larger issue on the JSF lifecycle documentation.

Comment by Kim Haase [ 24/Apr/13 ]

Fixed with JAVAEETUTORIAL-88.





[JAVAEETUTORIAL-108] VDL not crossreferenced Created: 27/Jun/12  Updated: 24/Apr/13  Resolved: 24/Apr/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.7-5
Fix Version/s: 7.0.1

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


 Description   

The page at http://docs.oracle.com/javaee/6/tutorial/doc/bnaia.html describing "Defining a Tag Attribute Type" brings up View Description Language (VDL) as the means by which custom tags are created. However, the creation of the custom tags is not covered nor is there a link to a page about custom tag creation. I think it is early to learn about custom tags in the tutorial sequence, so I'd say a link to elsewhere is most applicable.



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

Yes, we definitely need a forward cross-reference both here and in Chapter 4, where custom tags are first mentioned (http://docs.oracle.com/javaee/6/tutorial/doc/bnapk.html). Also, the terms "view" and "View Description Language" should be introduced earlier than they are, and "View Description Language" should be defined.

Comment by Kim Haase [ 21/Aug/12 ]

Actually, the EL chapter contains additional material that needs to be updated for JSF (instead of JSP). Custom tags are used much less in JSF than in JSP, so we really don't need to talk about them this early; but they are used as examples elsewhere in the chapter.

I think the whole "Defining a Tag Attribute Type" section does after all need to be moved, possibly as a subsection of http://docs.oracle.com/javaee/6/tutorial/doc/bnawn.html, "Defining the Custom Component Tag in a Tag Library Descriptor." The custom component tag in that advanced chapter doesn't even have any custom attributes, so the topic remains theoretical (and should – it was more relevant at EE 5).

Comment by Kim Haase [ 24/Apr/13 ]

The entire section "Defining a Tag Attribute Type" applies to JSP development but not to JSF, so I have removed it. I made a few more updates in the EL chapter to make it apply better to JSF.





[JAVAEETUTORIAL-90] Relationship between JSF tags and input components should be mentioned more Created: 17/May/12  Updated: 24/Apr/13  Resolved: 24/Apr/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.7-5
Fix Version/s: 7.0.1

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


 Description   

The tutorial should reverse its current practice of avoiding explicit mention of JSF components that underlie the Facelets tags.



 Comments   
Comment by Kim Haase [ 24/Apr/13 ]

Changed my mind about this. We can mention the existence of the underlying components in Using JSF Technology in Web Pages, but focus on the use of the tags. The components are more prominent in the Developing with JSF Technology chapter and can stay there.





[JAVAEETUTORIAL-89] Reintroduce concept of backing beans to JSF chapters Created: 17/May/12  Updated: 24/Apr/13  Resolved: 24/Apr/13

Status: Closed
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.7-5
Fix Version/s: 7.0.1

Type: Task Priority: Major
Reporter: Kim Haase Assignee: Kim Haase
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The term "backing bean" has been banished from the tutorial in favor of "managed bean." However, a backing bean is a specific type of managed bean. The term should be defined and used where appropriate.



 Comments   
Comment by Kim Haase [ 24/Apr/13 ]

Completed for 7.0.1.





Generated at Fri Sep 04 18:59:49 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.