[JAVAEETUTORIAL-20] Advanced Composite Components chapter has error, needs enhancement Created: 20/Apr/11  Updated: 01/Aug/13  Resolved: 01/Aug/13

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

Type: Bug Priority: Major
Reporter: jendrock 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



 Description   

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

Error:
I think there is a mistake in chapter 13 of the Java EE 6 Tutorial (Advanced Composite Components), within the fourth section of that chapter (The compositecomponentlogin Example Application), in the first subsection of that section (The Composite Component File): I think there is a composite:attribute clause missing (<composite:attribute name="myloginBean" required="true"/>, or something like that).

Enhancement:
Moreover, from my point of view the contents of the next subsection (The Using Page) would be clearer if the subsection The Composite Component File of Chapter 13 started saying something like "The composite component file is an XHTML file called LoginPanel.xhtml." and a reference was added to the Composite Components section of Chapter 5 (Introduction to Facelets), where the use of Facelet libraries and prefixes for composite components is introduced.



 Comments   
Comment by jendrock [ 27/Apr/11 ]

Removed name of user who reported the issue.

Comment by jendrock [ 05/Feb/13 ]

The "error" was fixed quite some time ago. The required="true" portion is not included, as I believe it is the default. The verbiage requested in the "enhancement" section was included as well.

The cross reference back to the Composite Components section in the Introduction to Facelets chapter would be helpful. We'll add that in for the 7.0.0 release.

Comment by Ian Evans [ 24/Jun/13 ]

Reassigning Chinmayee's issues.

Comment by jendrock [ 01/Aug/13 ]

We will defer this fix until the next update, just prior to JavaOne. For that release, we are looking at replacing the compositecomponentlogin example with a more appropriate example.

Comment by Kim Haase [ 01/Aug/13 ]

Actually, there is a cross-reference to the Facelets chapter intro to composite components, right at the beginning of he Advanced Composite Components chapter. I don't think another one is needed.

So I think this issue can be closed now.

Comment by jendrock [ 01/Aug/13 ]

Actually, Kim is right. I will close the issue and open a new issue for replacing the compositecomponentlogin example with a more appropriate composite component example.





[JAVAEETUTORIAL-226] Error in code example in advanced security chapter Created: 30/Jul/13  Updated: 31/Jul/13  Due: 30/Jul/13  Resolved: 31/Jul/13

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

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


 Description   

A user reports that there is an error in the code example in the advanced security chapter in this section: http://docs.oracle.com/javaee/7/tutorial/doc/security-advanced003.htm#BABIFJGI.

The corrections are indicated by the comments at the end of the lines that contain the errors.

@Stateless
@ManagedBean // add annotation
public class LoginBean {
private String username;
private String password;

public String getUsername()

{ return this.username; }

public void setUserName(String username)

{ this.username = username; }

public String getPassword()

{ return this.password; }

public void setPassword(String password)

{ //add String password this.password = password; }

 Comments   
Comment by Ian Evans [ 30/Jul/13 ]

I don't agree that it should be @ManagedBean in the code sample. Currently it is @Named, the replacement for JSF obsolete @ManagedBean annotation.

If the user had problems that were solved by replacing @Named with @ManagedBean I suspect there might be an issue with CDI scanning. But that's a different issue.

Comment by jendrock [ 31/Jul/13 ]

Ian's comment is correct. @Named should be used instead of @ManagedBean. The general recommendation is to use @Named regardless. Therefore, I will leave the existing annotation (@Named) as is.

I did, however, make the second correction in the source. The correction should be visible when we publish the next update, very soon.

Comment by jendrock [ 31/Jul/13 ]

The change has been made in the source and the correction will be visible at the next update.





[JAVAEETUTORIAL-227] Incorrect package name in "Using the Timer Service" Created: 30/Jul/13  Updated: 30/Jul/13  Resolved: 30/Jul/13

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

Type: Bug Priority: Minor
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:

http://docs.oracle.com/javaee/7/tutorial/doc/ejb-basicexamples004.htm#BNBOY



 Description   

From the feedback alias:

A quick one that freaked me out for a moment, under:

Part IV Enterprise Beans

24. Running the Enterprise Bean Examples

Using the Timer Service

In the second paragraph the package names for schedules and schedule are wrong, as I understand it is javax.ejb not java.ejb
I know it's pedantic, but it might throw a few new people, the error appears to be there for ee6 and ee7



 Comments   
Comment by Ian Evans [ 30/Jul/13 ]

Updated in source. Fix will appear in the next update to the Tutorial.





[JAVAEETUTORIAL-211] Servlet chapter references old Java SE book Created: 03/Jul/13  Updated: 30/Jul/13  Resolved: 30/Jul/13

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

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


 Description   

At the end of http://docs.oracle.com/javaee/7/tutorial/doc/servlets003.htm#BNAFS is a reference to "The Java Tutorial, Fourth Edition, by Sharon Zakhour et al. (Addison-Wesley, 2006)." Since there's a link to the online tutorial section anyway, I think this can just be cut.



 Comments   
Comment by jendrock [ 30/Jul/13 ]

Fixed in source. Will appear in update.





[JAVAEETUTORIAL-215] Update Faces Flows example to use appropriate naming conventions Created: 10/Jul/13  Updated: 30/Jul/13  Resolved: 30/Jul/13

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

Type: Improvement Priority: Minor
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   

Ed Burns (the JavaServer Faces spec lead) wrote an article for the German Oracle users website recommending some naming conventions for Faces Flows applications. The example in the tutorial should be modified to use these.



 Comments   
Comment by Kim Haase [ 30/Jul/13 ]

Created new example (simple-flow) to illustrate points made in Ed's article, and updated jsf-configure chapter.





[JAVAEETUTORIAL-186] Make sure "jump lists" are correct Created: 10/Jun/13  Updated: 30/Jul/13  Resolved: 30/Jul/13

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

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


 Description   

Now that we have to manually update the "jump list" at the beginning of each chapter when we add a section, there is at least one mismatch – section 2.7 is not in the jump list at the beginning of Chapter 2. There may be more. This is a placeholder for all such fixes.



 Comments   
Comment by jendrock [ 20/Jun/13 ]

Fixed in source. Will go into update for 7.0.1.

Comment by Kim Haase [ 30/Jul/13 ]

Fixed again for 7.0.2.





[JAVAEETUTORIAL-219] Formatting problem in Concurrency chapter Created: 16/Jul/13  Updated: 30/Jul/13  Resolved: 30/Jul/13

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

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

http://docs.oracle.com/javaee/7/tutorial/doc/concurrency-utilities002.htm



 Description   

In section 53.2 the description in the bullet point for ManagedThreadFactory is mostly in monospace font.



 Comments   
Comment by jendrock [ 30/Jul/13 ]

Fixed in source. Will appear in the next update.





[JAVAEETUTORIAL-213] Create a simple inbound connector example Created: 10/Jul/13  Updated: 30/Jul/13  Resolved: 30/Jul/13

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

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   

The mailconnector example, while very complete, is very complex and mixes two use cases (inbound vs. outbound) that are better understood separately. JCA would be easier to explain and understand with a basic outbound example and a basic inbound example.

This issue represents creating a basic inbound example.



 Comments   
Comment by rcervera [ 30/Jul/13 ]

The example is now available under connectors/inboundconnector and is also described in the Connector Examples chapter.





[JAVAEETUTORIAL-212] Create a simple outbound connector example Created: 10/Jul/13  Updated: 30/Jul/13  Resolved: 30/Jul/13

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

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   

The mailconnector example, while very complete, is very complex and mixes two use cases (inbound vs. outbound) that are better understood separately. JCA would be easier to explain and understand with a basic outbound example and a basic inbound example.

This issue represents creating a basic outbound example.



 Comments   
Comment by rcervera [ 30/Jul/13 ]

The example is now available under connectors/outboundconnector and is also described in the Connector Examples chapter.





[JAVAEETUTORIAL-225] Typos and syntax errors in the security chapters Created: 30/Jul/13  Updated: 30/Jul/13  Due: 31/Jul/13  Resolved: 30/Jul/13

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

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


 Description   

A tutorial user points out 2 errors in http://docs.oracle.com/javaee/7/tutorial/doc/security-advanced003.htm#BABIFJGI.

1. Typo. The HttpServetRequest classes shown below should be HttpServletRequest.

public String login () {
FacesContext context = FacesContext.getCurrentInstance();
HttpServetRequest request = (HttpServletRequest)
context.getExternalContext().getRequest();
try

{ request.login(this.username, this.password); }

catch (ServletException e)

{ ... context.addMessage(null, new FacesMessage("Login failed.")); return "error"; }

return "admin/index";
}

public void logout() {
FacesContext context = FacesContext.getCurrentInstance();
HttpServetRequest request = (HttpServletRequest)
context.getExternalContext().getRequest();
try

{ request.logout(); }

catch (ServletException e)

{ ... context.addMessage(null, new FacesMessage("Logout failed.")); }

}

2. Syntax errors in XML due to missing single quotes (one occurrence) and curly closing braces (3 occurrences) are indicated with an asterisk per occurrence in the XML code below.

<h:form>
<h:outputLabel for="usernameInput">

  • # {bundle['login.username']}

    :
    </h:outputLabel>
    <h:inputText id="usernameInput" value="#

    {loginBean.username}

    "
    required="true" />
    <br />
    <h:outputLabel for="passwordInput">

  • # {bundle['login.password']}

    :
    </h:outputLabel>
    <h:inputSecret id="passwordInput" value="#

    {loginBean.password}

    "
    required="true" />
    <br />

  • <h:commandButton value="$ {bundle['login.submit']}

    "
    action="#

    {loginBean.login}

    " />
    </h:form>

Lines indicated with an asterisk include the corrections.



 Comments   
Comment by jendrock [ 30/Jul/13 ]

Both sets of errors have been fixed in source and will appear in the next tutorial update.





[JAVAEETUTORIAL-222] Section 'Declaring Welcome Files' would be better placed in 'Configuring' than in 'Example' Created: 29/Jul/13  Updated: 29/Jul/13  Resolved: 29/Jul/13

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

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


 Description   

Section "6.4.4 Declaring Welcome Files" seems misplaced inside Chapter "6.4 The hello2 Example".
It would be better placed inside Chapter "6.5 Configuring Web Applications"



 Comments   
Comment by Kim Haase [ 29/Jul/13 ]

Thanks for noticing this. Not only is it misplaced, but it is outdated and could use some reworking.

Comment by Kim Haase [ 29/Jul/13 ]

Moved welcome files section from 6.4.4 to 6.5.2 and revised it slightly.





[JAVAEETUTORIAL-179] Add some .css to the following examples: jsonpmodel, jsonpstreaming, duketf, dukeetf2, webserverlog, phonebilling, websocketbot Created: 06/Jun/13  Updated: 25/Jul/13  Resolved: 25/Jul/13

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

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   

Add some style to the examples above, since they look a little rough right now with no styling at all.



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

What about making a resource library example for JSF with common CSS files that these examples depend on? That way, we'd have one project to maintain for style and accessibility issues, etc.

Comment by rcervera [ 07/Jun/13 ]

That sounds like a good idea.

Some of these projects do not have JSF pages, just plain HTML and JavaScript. Maybe I should convert them to simple JSF pages for using such a common resource and still use the same JavaScript?

Comment by rcervera [ 25/Jul/13 ]

Ian, I added the default.css from other projects to these projects for the time being.

If we go with a JSF resource library for all projects, I'll modify these. They just did not look good without any style at all.





[JAVAEETUTORIAL-86] Explanation of contexts is confusing and unclear in JEE6 Tutorial Created: 25/Apr/12  Updated: 25/Jul/13  Resolved: 25/Jul/13

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

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


 Description   

Here is the definition of 'context' given in the CDI section of the JEE6 Tutorial:

Overview of CDI

"Contexts: The ability to bind the lifecycle and interactions of stateful components to well-defined but extensible lifecycle contexts"

This is a circular definition. What is a context. How is it different from a 'lifecycle context'? If it isn't different then it really is a circular definition which isn't really a definition. If they are different things, why do they have the same name?

This is probably a good definition for someone who who knows the subject; but not for someone who really needs the tutorial.



 Comments   
Comment by jendrock [ 25/Apr/12 ]

This passage was not meant to be a definition of the term "contexts" but was intended to describe the services provided by the technology (CDI) in this area. This is indicated by the text that introduces the bullet list. In fact, the term isn't defined in the CDI specification or anywhere else that we could find! If you can find a valid definition, we would be glad to include it in the tutorial.

Comment by jendrock [ 30/May/12 ]

I suggest that you look at this issue and then use the definition provided by Paul Davies in the first section of Chapter 9, "Using Contexts and Dependency Injection for the Java EE Platform", in the Oracle Fusion Middleware Developing Applications for Oracle WebLogic Server 12c Release 1 book. The meaning is essentially the same, but the grammar is slightly improved.

Comment by Ian Evans [ 24/Jun/13 ]

Ricardo: reassigning Chinmayee's CDI issues to you. This may have been fixed in the Java EE 7 Tutorial.

Comment by rcervera [ 25/Jul/13 ]

Fixed this issue in the source using Eric's suggestion.





Use JDK 7 language features whenever we can (JAVAEETUTORIAL-200)

[JAVAEETUTORIAL-202] Use type inference for generic instantiation Created: 24/Jun/13  Updated: 25/Jul/13  Resolved: 25/Jul/13

Status: Resolved
Project: javaeetutorial
Component/s: examples
Affects Version/s: None
Fix Version/s: 7.0.2

Type: Sub-task Priority: Major
Reporter: Ian Evans Assignee: rcervera
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


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

See the following tech note:
http://docs.oracle.com/javase/7/docs/technotes/guides/language/type-inference-generic-instance-creation.html

Comment by Ian Evans [ 24/Jun/13 ]

According to the following grep regex:

grep -r "new\s[a-zA-Z0-9]*<[a-zA-Z0-9]." *

all the examples except for mailconnector are using the correct diamond operator per JDK 7. The above command will show matches in rsvp, but that is because the entity type for collections must be explicitly set.

Comment by rcervera [ 24/Jun/13 ]

I'm working on adapting the new mailconnector sample to our tree. I'll watch out for these instances and fix them.

Comment by rcervera [ 25/Jul/13 ]

I have removed the mailconnector example from the tree.





[JAVAEETUTORIAL-187] Adapt the mailconnector sample project from the GF samples Created: 10/Jun/13  Updated: 25/Jul/13  Resolved: 25/Jul/13

Status: Resolved
Project: javaeetutorial
Component/s: doc, examples
Affects Version/s: 7.0.0
Fix Version/s: 7.0.2

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

 Description   

The GF samples include a modified version of the mailconnector example used in the EE 6 tutorial. We need to change the following to incorporate it to the tutorial:

1. Replace JSP pages by Servlets.
2. Adapt the sample to our POM example tree.
3. Other changes we may want to make to this example.
4. Document the example.

1. is done and 2. is in progress.



 Comments   
Comment by rcervera [ 25/Jul/13 ]

We are replacing the mailconnector example by two separate new examples. See issues JAVAEETUTORIAL-212 and JAVAEETUTORIAL-213.





[JAVAEETUTORIAL-217] Use clearly user-specific names for destinations Created: 12/Jul/13  Updated: 19/Jul/13  Resolved: 19/Jul/13

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

Type: Improvement Priority: Minor
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 JMS spec lead suggests that calling the example destinations "Queue" and "Topic" is "a bit confusing as the reader doesn't know whether this choice of name is significant. I prefer a name like "MyQueue".

I will make this change.



 Comments   
Comment by Kim Haase [ 19/Jul/13 ]

Fixed in documentation and examples.





[JAVAEETUTORIAL-171] Add info on JMS resource-definition annotations and use in some examples Created: 05/Jun/13  Updated: 19/Jul/13  Resolved: 19/Jul/13

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

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   

Nigel Deakin (JMS spec lead) pointed out that Java EE 7 supports two new annotations that need to be documented. These allow resources to be configured by the developer rather than the administrator. They should also be used in some of the JMS examples.

Examples:

@JMSDestinationDefinition(
name = "java:global/jms/tutorialQueue",
description = "Queue to use in tutorial",
interfaceName = "javax.jms.Queue"
destinationName = "MyQueueForTutorial"
)

@JMSConnectionFactoryDefinition(
name="java:global/jms/tutorialConnectionFactory",
description="ConnectionFactory to use in tutorial"
)



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

After some experimentation (the namespace seems to be java:app rather than java:global), I was able to use @JMSDestinationDefinition in two examples and to describe the annotation feature in the tutorial.

Comment by Kim Haase [ 12/Jul/13 ]

Committed doc and example fixes.

Comment by Kim Haase [ 17/Jul/13 ]

There's still more work to do, based on comments from Nigel on the fixed examples.

Comment by Kim Haase [ 19/Jul/13 ]

Committed fixes for both docs and examples.





Add section on method validation using Bean Validation (JAVAEETUTORIAL-218)

[JAVAEETUTORIAL-220] Add information on using method validation in a type hierarchy to Advanced Bean Validation chapter Created: 16/Jul/13  Updated: 16/Jul/13  Resolved: 16/Jul/13

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

Type: Sub-task 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


 Description   

Add documentation on how to correctly apply validation constraints to a type hierarchy. This is, in my opinion, an advanced feature, and should be in the Bean Validation: Advanced Topics chapter.



 Comments   
Comment by Ian Evans [ 16/Jul/13 ]

Added section to advanced chapter.





[JAVAEETUTORIAL-214] Revise the Interceptors chapters with new features in Interceptors 1.2 Created: 10/Jul/13  Updated: 16/Jul/13  Resolved: 16/Jul/13

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

Type: Improvement 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


 Description   

Interceptors 1.2 has several new features, including:

  • @AroundConstruct interceptors
  • @Priority annotation for determining interceptor order
  • Rules for specifying interceptor order

Add sections on these to the Interceptors chapters.



 Comments   
Comment by Ian Evans [ 16/Jul/13 ]

Added material to Interceptors chapter.





[JAVAEETUTORIAL-216] Missing name of the role assembling Java EE components Created: 12/Jul/13  Updated: 12/Jul/13  Resolved: 12/Jul/13

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

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


 Description   

The name of the role assembling Java EE components is missing from the text (as if it was replaced with blank in a search&replace operation).

Seen in:
Chapter 1.7 introduction text
Chapter 1.7.4 header
Chapter 1.4.7 text
(possibly more)



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

Thank you very much for catching this error. I'm sure you are right about how it happened. We will fix it.

Comment by Kim Haase [ 12/Jul/13 ]

Found and fixed several occurrences in Chapter 1 and single occurrences in Chapters 26 (ejb-intro), 46 (security-javaee) and 49 (resources), by finding all occurrences of "assembler" in the EE 6 Tutorial and inserting the missing work in the EE 7 chapter. If anyone added any new text for EE 7 containing this word, though, I haven't found it.





[JAVAEETUTORIAL-168] Revise 3 advanced JMS examples to use multiple app clients instead of a single multithreaded one Created: 05/Jun/13  Updated: 11/Jul/13  Resolved: 11/Jul/13

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

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 durable subscription, acknowledgement mode, and local transactions examples use a single multithreaded program to demonstrate the associated features. The JMS spec lead suggests in his review that these will be easier for users to understand if the various classes are broken into separate source files and run separately. The fix should go into the July or September update depending on how difficult it is to do.



 Comments   
Comment by Kim Haase [ 11/Jul/13 ]

Fixed in code and chapters.





[JAVAEETUTORIAL-205] Content of Java EE 7 Tutorial PDF file does not match contents of Java EE 7 Tutorial HTML files Created: 28/Jun/13  Updated: 10/Jul/13  Resolved: 10/Jul/13

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

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


 Description   

A user reports that http://docs.oracle.com/javaee/7/tutorial/doc/javaeetutorial7.pdf is not as up to date as its HTML counterpart.

The first difference can easily be seen on this page : http://docs.oracle.com/javaee/7/tutorial/doc/overview001.htm#GIQVH and its pdf counterpart.

To match the HTML docs that are in the latest IPS package in the Update Center, the online HTML files for the Java EE 7 Tutorial were updated and pushed out. The individual that pushed the HTML files out, however, did not have ownership of the PDF file, nor was he in the correct group, nor were the permissions set in such a manner that he was able to effect any changes, so this matter will have to rest as is until the original owner returns from vacation and either resets the file so it can be updated or updates the file from the doc directory in the branches/javaeetutorial-7.0.1 repository herself.



 Comments   
Comment by Kim Haase [ 10/Jul/13 ]

The correct PDF is now provided on the docs.oracle.com site.





[JAVAEETUTORIAL-203] rsvp example's welcome-file and Faces servlet mapping not being respected Created: 26/Jun/13  Updated: 08/Jul/13  Resolved: 08/Jul/13

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

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


 Description   

In jaxrs/rsvp, we have the following web.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
    <context-param>
        <param-name>javax.faces.PROJECT_STAGE</param-name>
        <param-value>Development</param-value>
    </context-param>
    <servlet>
        <servlet-name>Faces Servlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    <session-config>
        <session-timeout>
            30
        </session-timeout>
    </session-config>
    <welcome-file-list>
        <welcome-file>faces/index.xhtml</welcome-file>
    </welcome-file-list>
</web-app>

However, if you go to the context root (say, http://localhost:8080/rsvp/) you get a 404 error. The welcome-file setting isn't being respected.

If you change the Faces servlet mapping and welcome-file to:

    <servlet-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>*.xhtml</url-pattern>
    </servlet-mapping>
...
    <welcome-file-list>
        <welcome-file>index.xhtml</welcome-file>
    </welcome-file-list>

You get nothing but 404 errors at any URL.

After investigating, Ed Burns suspects a bug in the GlassFish 4 web container.



 Comments   
Comment by Ian Evans [ 08/Jul/13 ]

The problem was a conflict between the JAX-RS application path in RsvpApplication ("/") and the FacesServlet mapping in web.xml. The 404 was being sent by the JAX-RS runtime. Evidently, if there is a conflict between a JAX-RS annotation and servlet mapping, the annotation wins.

I changed the application path in RsvpApplication to "/webapi" and the target URIs in the client code. Now everything works.





[JAVAEETUTORIAL-206] Improve information about JSF API reference details Created: 01/Jul/13  Updated: 03/Jul/13  Resolved: 02/Jul/13

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

Type: Bug Priority: Minor
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   

A user has pointed out that it is not clear in Section 10.2 where to find information about the tags and attributes described there. Links to this information should be added to this section.



 Comments   
Comment by Kim Haase [ 02/Jul/13 ]

Checked in fix to section 10.2.





[JAVAEETUTORIAL-209] Tables need to use HRuleFormal role Created: 02/Jul/13  Updated: 03/Jul/13  Resolved: 02/Jul/13

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

Type: Bug Priority: Minor
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   

I seem to have used the default (I think) "Formal" role when creating some new tables in JSF and JMS chapters, instead of the correct "HRuleFormal" role. I am fixing any I find in my chapters and will note any I find in others. They all look the same in PDF, but in HTML the Formal ones have shaded contents while the HRuleFormal ones don't.



 Comments   
Comment by Kim Haase [ 02/Jul/13 ]

Nope, I'm the only idiot. Fixed table roles in JMS Examples and Facelets chapters.





[JAVAEETUTORIAL-210] Debug options need correcting Created: 02/Jul/13  Updated: 03/Jul/13  Resolved: 02/Jul/13

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

Type: Bug Priority: Minor
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   

In the section "Using a Debugger" (http://docs.oracle.com/javaee/7/tutorial/doc/usingexamples009.htm#BNADN), two default debug options are shown, with a bad line break:

-Xdebug -
Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009

I thought I'd better check on them before fixing the line break (JAVAEETUTORIAL-176).

Neither option actually appears in the Debug Options field currently. What does appear is

-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=9009

Do others see this too? I will make the correction if someone confirms the change.



 Comments   
Comment by jendrock [ 02/Jul/13 ]

I also see this for the Debug Options field:

-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=9009

Please feel free to make the correction.

Comment by Kim Haase [ 02/Jul/13 ]

Thanks, Eric. I've made the fix.





[JAVAEETUTORIAL-204] Broken links in the Java EE 7 Tutorial Created: 28/Jun/13  Updated: 02/Jul/13  Resolved: 02/Jul/13

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

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


 Description   

A user reported that links, such as http://docs.oracle.com/javaee/7/javaserverfaces/2.2/docs/renderkitdocs/, in http://docs.oracle.com/javaee/7/tutorial/doc/jsf-page001.htm
are not working.

After rerunning LinkChecker 8.4, the following links have been found to be broken (HTTP 404 error):

In http://docs.oracle.com/javaee/7/tutorial/doc/jsf-ajax013.htm, https://javaserverfaces.java.net/nonav/docs/2.2/jsdocs/symbols/jsf.ajax.html.

In http://docs.oracle.com/javaee/7/tutorial/doc/jsf-configure005.htm#BNAXB, http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt.

In http://docs.oracle.com/javaee/7/tutorial/doc/jsf-facelets004.htm#GIQXP, http://docs.oracle.com/javaee/7/javaserverfaces/2.2/docs/vdldocs/facelets/.

In http://docs.oracle.com/javaee/7/tutorial/doc/jsf-page001.htm#BNARB, http://docs.oracle.com/javaee/7/javaserverfaces/2.2/docs/renderkitdocs/.

In http://docs.oracle.com/javaee/7/tutorial/doc/preface.htm#GEXAF, https://glassfish.java.net/nonav/docs/v4/api/.

There were two URLs that resulted in a HTTP 301 error (moved permanent) and should be updated:

In http://docs.oracle.com/javaee/7/tutorial/doc/jaxrs004.htm#GILIZ, http://oreilly.com/catalog/9780596529260/ is redirected to http://shop.oreilly.com/product/9780596529260.do

In http://docs.oracle.com/javaee/7/tutorial/doc/jsf-configure002.htm#BNAWP, http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd is redirected to http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/web-facesconfig_2_2.xsd

There are also several http URLs that are redirected to https URLs and should be updated:

In http://docs.oracle.com/javaee/7/tutorial/doc/jaxrs003.htm#GIPZZ, http://www.netbeans.org/kb/docs/websvc/rest.html is redirected to https://netbeans.org/kb/docs/websvc/rest.html

In http://docs.oracle.com/javaee/7/tutorial/doc/jaxrs003.htm#GIPZZ, http://netbeans.org/kb/docs/websvc/twitter-swing.html is redirected to https://netbeans.org/kb/docs/websvc/twitter-swing.html

In http://docs.oracle.com/javaee/7/tutorial/doc/jsf-facelets004.htm#GIQXP, http://netbeans.org/kb/docs/web/jsf20-intro.html is redirected to https://netbeans.org/kb/docs/web/jsf20-intro.html

In http://docs.oracle.com/javaee/7/tutorial/doc/preface.htm#GEXAF, http://www.netbeans.org/kb/ is redirected to https://netbeans.org/kb/

In http://docs.oracle.com/javaee/7/tutorial/doc/usingexamples001.htm#GEXAJ, http://www.netbeans.org/downloads/index.html is redirected to https://netbeans.org/downloads/index.html



 Comments   
Comment by Kim Haase [ 01/Jul/13 ]

Fixed in doc source (except the jcp.org one, which should be left as is).

Comment by Kim Haase [ 02/Jul/13 ]

Found a bad link that the linkchecker missed, from http://docs.oracle.com/javaee/7/tutorial/doc/jsf-custom008.htm.

Are there more?

Comment by Kim Haase [ 02/Jul/13 ]

Fixed bad link in jsf-custom chapter. Please reopen if more are found.





[JAVAEETUTORIAL-208] Unused JMS example mistakenly included in bundle Created: 02/Jul/13  Updated: 02/Jul/13  Resolved: 02/Jul/13

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

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   

I forgot to remove the webrequestreply example from the workspace, though it was not included in the tutorial examples in the end. I will remove it from the trunk and branch.



 Comments   
Comment by Kim Haase [ 02/Jul/13 ]

Removed jms/webrequestreply directories from trunk and 7.0.1 branch at revision 1463.





[JAVAEETUTORIAL-170] Many links to Java EE 6 API and VDL docs within the Tutorial Created: 05/Jun/13  Updated: 01/Jul/13  Resolved: 01/Jul/13

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

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


 Description   

The following files have links to the EE 6 API/VDL docs:
ejb-basicexamples004.htm
jaxrs002.htm
jaxrs003.htm
jsf-page-core004.htm



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

Fixed in EJB and JAX-RS chapters.

Comment by Ian Evans [ 05/Jun/13 ]

Reassigning to Kim for JSF fix.

Comment by Kim Haase [ 05/Jun/13 ]

Fixed in JSF chapter.

Comment by Kim Haase [ 05/Jun/13 ]

Ian, did you commit the EJB and JAX-RS chapters? They don't come in when I update.

Comment by Ian Evans [ 05/Jun/13 ]

Source files checked in.

Comment by jendrock [ 01/Jul/13 ]

Update Java SE 6 API doc URLs in webi18n001.htm to Java SE 7 locations.

Comment by jendrock [ 01/Jul/13 ]

Updated Java SE 6 API doc links in webi18n001.htm to Java SE 7 URLs.





[JAVAEETUTORIAL-196] Make the automatic timeout shorter for timersession Created: 21/Jun/13  Updated: 24/Jun/13  Resolved: 24/Jun/13

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

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


 Description   

The automatic timeout in ejb/timersession is pretty long. It can be 20 seconds or so.



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

Fixed in source. The new automatic timeout will occur every minute.





[JAVAEETUTORIAL-198] Wrong usage of type in @Resource Created: 23/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.2

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

Tags: annotations

 Description   

Examples to the use of @Resource are wrong.
Example, 6.5.3.1:

@Resources ({
    @Resource(name="myDB" type=javax.sql.DataSource),
    @Resource(name="myMQ" type=javax.jms.ConnectionFactory)
})

Just to be syntactically correct, the type value either has to be between double quotes, or .class needs to be appended to return the actual Class object. As per the specification, type is defined as "public abstract Class<?> type". Correction of above would look like:

@Resources ({
    @Resource(name="myDB" type=javax.sql.DataSource.class),
    @Resource(name="myMQ" type=javax.jms.ConnectionFactory.class)
})

I would suggest to extend this case by means of a regex search through the documentation.



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

Fixed in source. I did a grep through the documentation, and this was the only instance of a class-level @Resource with a type attribute.





[JAVAEETUTORIAL-159] ajaxguessnumber: possible solutions without js-hack Created: 28/Feb/13  Updated: 24/Jun/13  Resolved: 24/Jun/13

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

Type: Improvement Priority: Minor
Reporter: swiss-chris Assignee: Ian Evans
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 30 minutes
Time Spent: Not Specified
Original Estimate: 30 minutes

Tags: jsf2, render, rendered, scope, tutorial, validation

 Description   

When reading the chapter on the ajaxguessnumber example app and analysing the code, I was surprised at the choice of writing a custom js-function "msg" to get rid of the stale result. Certainly, this allows the demonstration of the h:commandButton's onevent attribute, but:

  • it doesn't seem like a clean solution to me (it doesn't seem very refactoring-friendly because of the 2 getElementById("hard-coded HTML element ID") calls),
  • it doesn't explain the inclusion of the commented-out code <f:ajax execute="userNo" render="result errors1" /> within the code AND the tutorial chapter.

It looks more like a quick fix by one person (developer) that was later commented on by another person (who wrote the tutorial chapter).

If one were to want to rewrite the code as it was perhaps originally intended (as is perhaps still visible in the commented-out code aforementioned), I could think of the following two possibilities:

  1. Only render the outputText if there was no validation error.
  2. Change the scope of the ManagedBean from @SessionScoped to @RequestScoped


The first solution would look something like the following. For it to work with Ajax, the outputText would need to be wrapped in a container such as h:panelGroup and the f:ajax render attribute would need to refer to the panel's ID ("outputGrid"):

ajaxgreeting.xhtml
<h:commandButton id="submit" value="Submit" >
    <f:ajax execute="userNo" render="outputGrid" />
</h:commandButton>
<h:panelGroup layout="block" id="outputGroup">
    <h:outputText id="result" style="color:blue"
                  value="#{userNumberBean.response}" rendered="#{!facesContext.validationFailed}"/>
    <h:message id="errors1" showSummary="true" showDetail="false"
               style="color: #d20005;
               font-family: 'New Century Schoolbook', serif;
               font-style: oblique;
               text-decoration: overline" 
               for="userNo"/>
</h:panelGroup>

The second solution changes the design altogether. I'm not sure why you would want @SessionScoped for this example in the first place. @RequestScoped seems more appropriate and solves the problem of hiding the "stale output" of the "result" outputText element.



 Comments   
Comment by swiss-chris [ 28/Feb/13 ]

After posting my original proposals, I realized that simply changing the scope from @SessionScoped @RequestScoped wouldn't suffice. While the userNumber could be @RequestScoped, the randomInt needs to be @SessionScoped for the guessing game to give the user a second chance.

Off hand all I can think of to make this work as I had intended is to create a second dukesNumberBean, also a managed bean that contains the randomInt as well as the minimum and maximum values. I used @ManagedProperty(value="#

{dukesNumberBean}

") to inject it into userNumberBean

by the way, the value 10 was hardcoded into the userNumberBean constructor. Alternatively, randomInt could be created the following way:

long range = maximum-minimum+1;
randomInt = (int)(minimum + randomGR.nextDouble()*range);
Comment by Ian Evans [ 24/Jun/13 ]

UserNumberBean was changed to request-scoped, and a new session-scoped backing bean, DukesNumberBean, was added. A new panel group was added to display the results or the validation error. These changes eliminate the need for the separate ui.js Javascript file, as stale data should not be a problem.

These changes probably better reflect how we want users to use the f:ajax tag, but we no longer have an example that uses onevent or shows how to add custom Javascript. Perhaps we need an advanced example?

Comment by Ian Evans [ 24/Jun/13 ]

Fixed in source and rewrote doc source. The fixes will appear in the next Tutorial update.





[JAVAEETUTORIAL-183] Chapter 2 section "2.6 Tutorial Example Directory Structure" needs fixes Created: 10/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.2

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


 Description   

The first bullet list in this section needs to have the last two items corrected from "web" to "webapp".

The second bullet list should have "example-name-common" added to it, since several EAR examples have a common directory. How should this be described?



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

Fixed the web -> webapp issue, and added the following bullet:

example-name-common: library JAR containing components, classes, and files used by other modules

Comment by Ian Evans [ 24/Jun/13 ]

Fixed in source. Will appear in the next update of the Tutorial.





[JAVAEETUTORIAL-197] Archetypes should generate stand-alone pom.xml files Created: 21/Jun/13  Updated: 21/Jun/13  Resolved: 21/Jun/13

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

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


 Description   

Currently the archetypes in First Cup and the Java EE 7 Tutorial have the parent set. This can cause errors if the parent pom hasn't been installed yet.

Since these archetypes are presumably going to be used by developers for their own applications, it's better to make the generated project's pom.xml standalone, with the necessary dependencies and configuration all in the pom.xml file, not inherited from our project's pom.xml file hierarchy.



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

Fixed in the source. Will appear in the 7.0.2 release.





[JAVAEETUTORIAL-191] pom.xml generated by jaxrs-service-archetype use incorrect version Created: 14/Jun/13  Updated: 14/Jun/13  Resolved: 14/Jun/13

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

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


 Description   

The parent <version> string in the archetype-generated pom.xml file uses 7.0.1-SNAPSHOT. This should be 7.0.1.



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

The workaround is to edit the generated pom.xml and replace the parent definition with:

<parent>
    <artifactId>firstcup</artifactId>
    <groupId>org.glassfish.javaeetutorial.firstcup</groupId>
    <version>7.0.1</version>
</parent>

That is, delete -SNAPSHOT from <version> in the generated pom.xml.

Comment by Ian Evans [ 14/Jun/13 ]

Fixed the source in trunk. The fix will appear in the next update to the Tutorial package in the Update Center.





[JAVAEETUTORIAL-188] Minor error in code example in "Ordering Results" section of Criteria chapter Created: 12/Jun/13  Updated: 12/Jun/13  Resolved: 12/Jun/13

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

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


 Description   

There is a small error in the last code example at http://docs.oracle.com/javaee/6/tutorial/doc/gjivm.html#gjiwo

 
cq.orderBy(cb.asc(owner.get(Owner_.lastName), owner.get(Owner_.firstName)));

CriteriaBuilder.asc does not accept such arguments. It should probably be:

cq.orderBy(cb.asc(owner.get(Owner_.lastName)), cb.asc(owner.get(Owner_.firstName)));


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

Fixed in source, and it will appear in the next update of the Tutorial.





[JAVAEETUTORIAL-181] Multiple para elements inside a bullet point in an ItemizedList do not render properly in HTML (See 52.1.1) Created: 06/Jun/13  Updated: 10/Jun/13  Resolved: 10/Jun/13

Status: Resolved
Project: javaeetutorial
Component/s: None
Affects Version/s: 7.0.0
Fix Version/s: 7.0.2

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

Attachments: PNG File figureInListCssFix.png     PNG File ListPara.PNG     PNG File paragraphsInListsCssFix.png    
Tags: html, template

 Description   

They look fine on the PDF. In the HTML, the paragraphs and an image are not separated by any space. I don't know whether to reorganize the content or try to fix the template.



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

See the attachment for what it looks like if I add the following CSS to javaee-darb-fonts.css:

ul .figure {
    padding-top: 10px;
}
Comment by rcervera [ 07/Jun/13 ]

Thanks Ian, that fixes the figure in this case. I am unsure if that change would have unintended consequences elsewhere.

Still the paragraphs inside the same bullet list item do not render properly, there is no space between them (see attachment). The easiest thing may be for me to rewrite this part without multiple paragraphs inside a bullet point if there's no other solution...

Comment by rcervera [ 07/Jun/13 ]

Paragraphs inside a list item not rendered properly.

Comment by Kim Haase [ 07/Jun/13 ]

I wouldn't change anything in the source, Ricardo – lots of chapters have lists (numbered as well as ordered) with multiple paragraphs, and we should really have a fix if possible.

Comment by Kim Haase [ 07/Jun/13 ]

The fix for figures looks good!

Comment by Ian Evans [ 07/Jun/13 ]

See the paragraphsInListsCssFix.png attachment for a fix for these by altering the following CSS style:

.javaee #mainContent li p {
    line-height:1.5em;
    padding: 0em 0em .5em 0em;
    margin:auto;
}
Comment by rcervera [ 07/Jun/13 ]

That's a great solution - thank you!

Comment by jendrock [ 10/Jun/13 ]

Since the fix looks good, could you please check it in, Ian? And then can you close the issue, since the problem is no longer there? Kim propagated the fix to the online docs on docs.oracle.com. Thanks.

Comment by Ian Evans [ 10/Jun/13 ]

Fixed online, and will be included in 7.0.2.

I'm tracking our local changes to the post-processor template files in the project wiki here:
https://java.net/projects/javaeetutorial/pages/JavaEEPostProcessorBugFixes





[JAVAEETUTORIAL-184] Packaging chapter should mention that ra.xml is optional Created: 10/Jun/13  Updated: 10/Jun/13  Resolved: 10/Jun/13

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

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


 Description   

Section 5.4, Packaging Resource Adapter Archives, has the following bullet item:

  • A META-INF/ directory that stores the ra.xml file and optionally an additional deployment descriptor that can be used for configuration purposes.

The ra.xml file is also optional, so this needs to be rephrased.



 Comments   
Comment by jendrock [ 10/Jun/13 ]

Rewrote passage to say the following:

An optional META-INF/ directory that can store an ra.xml file and/or an application server-specific deployment descriptor used for configuration purposes.

That should do it.





[JAVAEETUTORIAL-185] Webapp chapter begins with some xref problems Created: 10/Jun/13  Updated: 10/Jun/13  Resolved: 10/Jun/13

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

Type: Bug Priority: Minor
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   

At the beginning of chapter 6, the range of chapters that cover presentation-oriented web apps is too small; it should go up to chapter 17. Also, some of the cress-reference formats need tweaking.



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

Fixed in source.





[JAVAEETUTORIAL-32] html tags in examples must have lang attribute Created: 03/Jun/11  Updated: 21/Feb/13  Resolved: 21/Feb/13

Status: Resolved
Project: javaeetutorial
Component/s: examples
Affects Version/s: 6.0.4
Fix Version/s: 7.0.2

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

Issue Links:
Related
is related to JAVAEETUTORIAL-40 Internationalize the dukes-forest cas... Closed

 Description   

All HTML tags in our examples must have the LANG attribute set.

It appears that for the simple case where the example is English-only, hardcoding the LANG attribute in the HTML tag may be the way to go:

<html lang="en"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core">
...

However, it appears that for the case studies, where the locale can change dynamically, we need to do some coding so that the current locale can be retrieved. I don't know how well something like this would actually work, but maybe one of you can try it out:

http://stackoverflow.com/questions/4830588/jsf-locale-is-set-per-request-not-for-session

Our apps are different in that they get the locale from the browser setting instead of having the user set it in the app; that might simplify things.

I can check in fixes for the simple cases and then un-assign myself so the case study authors can work on those.



 Comments   
Comment by Kim Haase [ 09/Jun/11 ]

I've completed this work for all but the case studies.

Comment by Kim Haase [ 09/Jun/11 ]

Unassigning so case study authors can do this work – though I can do it, if you prefer.

Comment by Kim Haase [ 08/Jul/11 ]

Ian, thanks for picking this up. While you are fixing this for dukes-tutoring you might also add a summary attribute to the h:dataTable element in any files that use one. Or would you rather I filed a separate issue for table summary problems?

Comment by Ian Evans [ 27/Jul/11 ]

Re-assigning to William for Duke's Forest.

Comment by Kim Haase [ 17/Aug/11 ]

This task is really part of the task of internationalizing dukes-forest. It will probably involve creating a locale bean like the one used by dukes-tutoring, and setting the lang attribute to the value of the locale bean's language property.

Comment by Kim Haase [ 05/Jun/12 ]

A couple of mailconnector pages are missing the lang attribute. Will fix.

Comment by William Markito [ 21/Feb/13 ]

This issue has been fixed on Duke's Forest since we've applied i18n. The templates pages (shipment & store) has the following syntax:
<html lang="#

{localeBean.language}

"...

Comment by William Markito [ 21/Feb/13 ]

This issue has been fixed on Duke's Forest since we've applied i18n. The templates pages (shipment & store) has the following syntax:
<html lang="#

{localeBean.language}

"...





[JAVAEETUTORIAL-150] Validation messages must get moved from dukes-resources to the default package of the main project Created: 05/Feb/13  Updated: 21/Feb/13  Resolved: 21/Feb/13

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

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


 Description   

The validation messages (Spanish and English-language bundles) need to be moved from dukes-resources/src/java to the default package of the main project. The validation messages cannot be found when they are in the dukes-resources project.



 Comments   
Comment by jendrock [ 05/Feb/13 ]

This issue needs to be fixed when we update the tutorial case studies to EE 7. That won't happen until 7.0.2.

Comment by jendrock [ 05/Feb/13 ]

This issue is present in 6.0.8. We are not planning to release the case studies with 7.0.0 or 7.0.1, so we will defer fixing the issue until 7.0.2. The docs are not impacted, the source is.

Comment by William Markito [ 21/Feb/13 ]

Fixed by revision http://java.net/projects/javaeetutorial/sources/svn/revision/1179





Generated at Thu Sep 29 10:15:56 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.