[JAVAEETUTORIAL-128] File paths wrong in Java EE 6 Tutorial from the UpdaterTool Created: 03/Aug/12  Updated: 16/Aug/12  Resolved: 03/Aug/12

Status: Resolved
Project: javaeetutorial
Component/s: examples
Affects Version/s: 6.0.7-5
Fix Version/s: 6.0.7-5

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

Mac OS 10.8, JVM 1.7_5, Java EE 6 SDK Update 4



 Description   

"To Obtain the Tutorial Component Using the Update Tool" on page 73 does not work properly on a Mac, at least not with the OS version I am running. The reason being is the update tool has the paths all wrong. If I look at the Files view of the Java EE 6 Tutorial version 6.0.7-4 they look like the example I have pasted below:

glassfish/docs/javaee-tutorial\doc\bnaac.html
glassfish/docs/javaee-tutorial\doc\bnaan.html
glassfish/docs/javaee-tutorial\doc\bnaaw.html
glassfish/docs/javaee-tutorial\doc\bnaax.html
glassfish/docs/javaee-tutorial\doc\bnaay.html
glassfish/docs/javaee-tutorial\doc\bnabo.html
glassfish/docs/javaee-tutorial\doc\bnabs.html

Everywhere there is a backslash () the folder structure is not created, you just get a file with the name "javaee-tutorial\doc\bnaay.html". As a result the file structure is completely missing on Mac OS and it is necessary to copy the tutorial from a Windows computer where either slash appears to work.



 Comments   
Comment by Ian Evans [ 03/Aug/12 ]

Looking into this right now. I don't know why the Update Center toolkit wouldn't handle Windows paths correctly when creating packages, but that's what this appears to be.

Comment by Ian Evans [ 03/Aug/12 ]

Changing priority to P1, as this package is broken on non-Windows platforms.

Comment by Ian Evans [ 03/Aug/12 ]

Created package 6.0.7-5 with correct file layout for Unix platforms. Release engineering will push it to the external repository soon.





[JAVAEETUTORIAL-126] javascript incorrectly described as object-oriented Created: 12/Jul/12  Updated: 16/Aug/12  Resolved: 25/Jul/12

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

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   

This issue occurs on "Overview of Ajax" page at http://docs.oracle.com/javaee/6/tutorial/doc/gkigr.html. The second paragraph describes JavaScript as object oriented. JavaScript does have objects, but it is prototype oriented. It does not have object oriented features like inheritance. Objects inherit from objects set as their prototype. There are no classes.



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

Thank you again for catching this error in terminology.

Comment by Kim Haase [ 25/Jul/12 ]

Checked in fix that removes the claim that Ajax is object-oriented.





[JAVAEETUTORIAL-124] technically incorrect statement in context of Java Created: 11/Jul/12  Updated: 16/Aug/12  Resolved: 25/Jul/12

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

Type: Bug 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 empty string is represented as "". It is a character array of zero characters. A null string is represented by null. It can be described as the absence of a string instance.' as the second paragraph after "Validating Null and Empty Strings" on the page named "Using Bean Validation" at http://docs.oracle.com/javaee/6/tutorial/doc/gircz.html. The second sentence is not correct in the Java context. A character array is mutable. A String is not. So a string in Java is not a character array. It may be more technically accurate to say "It is a character sequence of zero characters." As String implements CharSequence, this is technically correct as well as conceptually correct.



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

Thank you for catching this error.

Comment by Kim Haase [ 25/Jul/12 ]

Checked in fix that changes "array" to "sequence".





[JAVAEETUTORIAL-122] clarify UI restraint versus validation Created: 10/Jul/12  Updated: 16/Aug/12  Resolved: 27/Jul/12

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

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   

This issue occurs on the page titled "Using the Standard Validators" at http://docs.oracle.com/javaee/6/tutorial/doc/bnatc.html. Under the section titled "Using LongRangeValidator" you might clarify that size does not do any validation. Size only sets the size attribute on the rendered input field which, only in that rendered interface will restrict input to a certain length. There is nothing preventing an appropriate GET or POST request from specifying a field value that exceeds the set length. To actually validate the length, you'd need a validator.



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

Thanks for catching this misleading language.

Comment by Kim Haase [ 27/Jul/12 ]

Removed the irrelevant sentence about the size attribute of inputText.





[JAVAEETUTORIAL-73] Streamline NetBeans-generated navigation strings used by controllers in Duke's Forest Created: 21/Mar/12  Updated: 16/Aug/12  Resolved: 03/Apr/12

Status: Resolved
Project: javaeetutorial
Component/s: examples
Affects Version/s: 6.0.7-2
Fix Version/s: 6.0.7-5

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

Tags: case-study

 Description   

Remove all unnecessary navigation strings and replace with one bean that holds all navigation destinations of the application, thereby avoiding the duplicated strings that we have today in several places in the application. Now, all controllers have the same navigation cases: Create, Edit, List, Update). There should be one simple enum or class with final string objects (Create/Edit/List) instead of having "List", for example, in 4 different places in the same controller. Essentially rewrite this part of code that was generated by NetBeans wizards.



 Comments   
Comment by William Markito [ 03/Apr/12 ]

Solved by last commit.





[JAVAEETUTORIAL-53] Need to document that you can use EL resource references in JSF stylesheets and scripts Created: 22/Sep/11  Updated: 16/Aug/12  Resolved: 18/Oct/11

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

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


 Description   

If you are using <h:outputStylesheet> or <h:outputScript>, the referenced stylesheets/scripts can use the EL resource syntax. Developers may need to do this to make references to other resources in their stylesheets or scripts.

For example, if your resource library has a stylesheet that defines a background image, you can't refer to it by URL, since it's part of a resource library, and the image is also a resource. So you use a resource reference in the CSS:
background: #fff url(#

{resource['img:background.jpg']}

The JSF runtime will substitute the resource reference with the actual location in the application. E.g.:
background: #fff url(/dukes-shipment/javax.faces.resource/background.jpg.xhtml?ln=img)

Why background.jpg.xhtml? It's the extension specified by the JSF servlet in web.xml.

This section should be updated:
http://download.oracle.com/javaee/6/tutorial/doc/bnarf.html#gjgep

See section 2.6.1 of the JSF 2 spec for the resource reference syntax.



 Comments   
Comment by William Markito [ 22/Sep/11 ]

As an example, dukes-forest case study will use this feature.

When using the tags above, the whole stylesheet/javascript will be imported and processed by Faces Servlet through /javax.faces.resource/. Accessing the page source will show the complete url generated by JSF runtime.

The default pattern for resources usage is #

{resource['library:location']}

and JSF will replace with the right path.

Comment by Kim Haase [ 18/Oct/11 ]

Duke's Store uses this syntax in its default.css file. However, the actual location doesn't show up in the page source, only the reference to the CSS file. The images, of course, do appear.

Comment by Kim Haase [ 18/Oct/11 ]

I have added this information to the recommended section. Further suggestions welcome.





[JAVAEETUTORIAL-38] Change from DBAO to using JPA entity classes Created: 17/Jun/11  Updated: 16/Aug/12  Resolved: 14/Jul/11

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

Type: Task Priority: Major
Reporter: chinmayee_srivathsa Assignee: jendrock
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 2 weeks
Time Spent: Not Specified
Original Estimate: 2 weeks


 Comments   
Comment by jendrock [ 14/Jul/11 ]

Kim and I completed this task. We created and populated the database, ran the NetBeans Create Entities from Database wizard to create a new Book.java file in the dukesbookstore.entities package. We added the findbooks named query to it as well. We got rid of web/bookstore/src/java/com/sun/bookstore6/database/BookDBAO.java and migrated its functionality to dukes-bookstore/src/java/dukesbookstore/ejb/BookRequestBean.java, adding logging functionality and a named query.

Comment by jendrock [ 14/Jul/11 ]

The functionality has been ported to the revised example in web/dukes-bookstore. We tested it and it operates as before - no regressions.

Comment by jendrock [ 14/Jul/11 ]

It works as advertised, so I will close this issue. However, if further testing indicates a need to work on it again, the issue will have to be reopened.





[JAVAEETUTORIAL-16] Bean Validation null string comparison code snippet would throw NPE Created: 22/Dec/10  Updated: 16/Aug/12  Resolved: 11/May/11

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

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

http://download.oracle.com/javaee/6/tutorial/doc/gircz.html#gkcrg


Tags: bean, jsf, validation

 Description   

"In this case, the user input for the field is not required.

if (testString.equals(null)) {
doSomething();
} else {
doAnotherThing();
}

By default, the doAnotherThing method is called even when the user enters no data, because the testStringelement has been initialized with the value of an empty string."

This code is broken in that if testString actually were null, the code would throw a NullPointerException instead of correctly checking the comparison.

It should be:
if (testString == null) {
doSomething();
} else {
doAnotherThing();
}



 Comments   
Comment by devikag [ 11/May/11 ]

Code snippet modified as per user suggestion.

The chapter(9) is updated and the modified content will be visible after next publication.





[JAVAEETUTORIAL-10] Misleading link to AS download in Java EE 5 Tutorial Created: 30/Sep/10  Updated: 16/Aug/12  Resolved: 06/Dec/10

Status: Resolved
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.4
Fix Version/s: 6.0.7-5

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
Environment:

Operating System: All
Platform: All


Issuezilla Id: 10

 Description   

Reported to the Java EE Documentation mailing list from a user.

ON this page:
http://download.oracle.com/javaee/5/tutorial/doc/gexaj.html#gexab

You refer to “Sun Java System Application Server 9.1� and “download the
Application Server from�
Followed by a link to
http://www.oracle.com/technetwork/java/javaee/downloads/index.html.

The resulting page does not show any tag or text for “Sun Java System
Application Server 9.1�.

What are we supposed to download?

I am trying to follow the “Java EE 5 Tutorial�.

Do not put my email address on any list!!!!

We are clarifying this point in the Java EE 5 tutorial, pointing to the correct
download page for AS 9.1



 Comments   
Comment by Kim Haase [ 30/Sep/10 ]

Will fix in next docarch update.

Comment by Ian Evans [ 06/Dec/10 ]

Fixed in current update:
http://download.oracle.com/javaee/5/tutorial/doc/gexaj.html#gexab

Comment by jendrock [ 27/Apr/11 ]

Removed the name of the user that reported the issue.





[JAVAEETUTORIAL-9] Redundant line in JAX-RS chapter Created: 30/Sep/10  Updated: 16/Aug/12  Resolved: 06/Dec/10

Status: Resolved
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.4
Fix Version/s: 6.0.7-5

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
Environment:

Operating System: All
Platform: All


Issuezilla Id: 9

 Description   

Reported to the Java EE Documentation mailing list from a user.

Hello!
On page http://download.oracle.com/javaee/6/tutorial/doc/gilik.html in the
'Extracting Request Parameters' section describing the acceptable Java types for
@QueryParam and @PathParam one of these two lines is redundant:

  • Any class with a constructor that accepts a single String argument
  • Any class with a constructor that takes a single String as a parameter
    Keep up the good work,
    Laszlo

This is in the JAX-RS chapter. we will fix it.



 Comments   
Comment by Kim Haase [ 30/Sep/10 ]

Will fix in next docarch update.

Comment by Ian Evans [ 06/Dec/10 ]

Fixed in the latest update:
http://download.oracle.com/javaee/6/tutorial/doc/gilik.html#gipyw

Comment by jendrock [ 27/Apr/11 ]

Removed the name of the user that reported the issue.





[JAVAEETUTORIAL-8] Need to add web.xml before you can add a context parameter Created: 17/Sep/10  Updated: 16/Aug/12  Resolved: 06/Dec/10

Status: Resolved
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.4
Fix Version/s: 6.0.7-5

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

Operating System: All
Platform: All
URL: http://download.oracle.com/javaee/6/tutorial/doc/bnaeo.html#gjsfj


Issuezilla Id: 8

 Description   

The instructions for adding a context parameter need an additional step to
create a web.xml file, as there isn't one by default now in Java EE 6.

These steps should come after step 1 above:
2. Highlight the project in the Project Pane and select File -> New File.
3. Select the Web category, then Standard Deployment Descriptor under File
Types, click Next, then Finish.

This will create an empty web.xml file in web/WEB-INF/.



 Comments   
Comment by Kim Haase [ 21/Sep/10 ]

I was inclined just to put in a statement that the steps apply generically and
not specifically, but maybe we also need a separate task on creating a web.xml
file to which the following tasks would point:

To Add a Context Parameter Using NetBeans IDE
To Add an Initialization Parameter Using NetBeans IDE
To Set Up Error Mapping Using NetBeans IDE

I'll check something in to the tutorial workspace and you can see what you think.

Comment by Kim Haase [ 30/Sep/10 ]

We will fix this in the next docarch update.

Comment by Ian Evans [ 06/Dec/10 ]

Fixed in current update:
http://download.oracle.com/javaee/6/tutorial/doc/bnaeo.html#gjsfj





[JAVAEETUTORIAL-3] loginform.html missing body tags Created: 22/Feb/10  Updated: 16/Aug/12  Resolved: 19/Jan/11

Status: Resolved
Project: javaeetutorial
Component/s: examples
Affects Version/s: 6.0.4
Fix Version/s: 6.0.7-5

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

Operating System: All
Platform: All


Issuezilla Id: 3

 Description   

javaee6 tutorial bundle – examples/web/hello2_formauth project

loginform.html file needs to be fixed to not have html syntax errors.

easy fix – just add <body> </body> tags



 Comments   
Comment by Ian Evans [ 22/Feb/10 ]

Reassigning to Kim.

Comment by Kim Haase [ 19/Jan/11 ]

We no longer ship hello2_formauth; instead we provide hello1_formauth, which uses Facelets.





[JAVAEETUTORIAL-1] Getting Started with Enterprise Beans has incorrect description of EJB converter example Created: 22/Jan/10  Updated: 16/Aug/12  Resolved: 06/Dec/10

Status: Resolved
Project: javaeetutorial
Component/s: doc
Affects Version/s: 6.0.4
Fix Version/s: 6.0.7-5

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

Operating System: All
Platform: All


Issuezilla Id: 1

 Description   

In the intro to Ch 15, Getting Started with Enterprise Beans, it says the
converter example contains both a web client and an application client, but the
description is just of the web client.



 Comments   
Comment by Ian Evans [ 01/Oct/10 ]

Fixed in source for chapter.

Comment by Ian Evans [ 06/Dec/10 ]

Fixed in latest update.
http://download.oracle.com/javaee/6/tutorial/doc/gijre.html





Generated at Wed Jun 03 15:34:34 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.