[JAVAEETUTORIAL-257] JAX-WS tutorial chapter doesn't match what is in the code examples Created: 23/Dec/13  Updated: 15/Sep/14  Resolved: 23/Dec/13

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

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   

Actually this applies to both the doc and the examples; some fixes are needed to both.

The example source code for the JAX-WS web service, app client, and web client examples has been updated, but the code shown in the tutorial has not been updated to match it. Also, the WSDL URL in the source code is incorrect, so the clients do not run.



 Comments   
Comment by Kim Haase [ 23/Dec/13 ]

Checked in code fixes at revision 1713. Also checked in fixes in FrameMaker source.





[JAVAEETUTORIAL-256] Update Tag Libraries Supported by Facelets section Created: 15/Dec/13  Updated: 16/Dec/13  Resolved: 16/Dec/13

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

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


 Description   

Tag Libraries Supported by Facelets section(Under what is facelets?) need to be corrected considering the below points

1. Passthrough by elements and passthrough by attributes tablibrary namespaces respective Prefix and Example column values need to be interchanged each other.

2. Composite tab library need to be added

http://xmlns.jcp.org/jsf/composite

Regards,
Sudheer



 Comments   
Comment by Kim Haase [ 16/Dec/13 ]

Thank you very much for pointing out these errors. We will correct them in the next version of the Tutorial.

Comment by Kim Haase [ 16/Dec/13 ]

Fixed in Facelets chapter source.





[JAVAEETUTORIAL-255] Invalid integer converter example in Java EE 7 tutorial chapter 11.1.1 Created: 20/Nov/13  Updated: 15/Sep/14  Resolved: 27/Nov/13

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

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


 Description   

http://docs.oracle.com/javaee/7/tutorial/doc/jsf-page-core001.htm#JEETT00931

It mentions:

<h:inputText converter="javax.faces.convert.IntegerConverter" />

However, this is wrong, it should have been:

<h:inputText converter="javax.faces.Integer" />

See also http://stackoverflow.com/q/20081207



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

Thank you for pointing this out. The error has been corrected, and some additional fixes have been made in that section for the next respin.





[JAVAEETUTORIAL-254] Wrong version of beans.xml file in example Created: 22/Oct/13  Updated: 22/Oct/13  Resolved: 22/Oct/13

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

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   

For the encoder example in Section 26.1 of "Running the Advanced Contexts and Dependency Injection Examples," the instructions tell the user to run the example, then edit the beans.xml file and rerun the example. The version checked into the workspace is actually the edited version (I forgot to return it to the original state after testing), so the current instructions will confuse users.



 Comments   
Comment by Kim Haase [ 22/Oct/13 ]

Committed fixed version at revision 1675.

Am also correcting some instructions in the advanced CDI examples chapter to make them consistent with the ones in the simple CDI examples chapter.





[JAVAEETUTORIAL-246] Duke's Forest: order list not updated in admin interface after Approve Shipment process Created: 19/Sep/13  Updated: 19/Sep/13  Resolved: 19/Sep/13

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

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

Both Firefox and Chrome on Windows 7; Firefox on Solaris



 Description   

If I return to Duke's Store as admin after approving the shipment of a couple of items, and then click on List of Orders, the list is exactly the same as when I left it. The orders that shipped are still marked "Ready to ship". When I click View on an individual item, the status on that page is the same.

When I log in as the user who placed the orders, they are indeed shown as "Order shipped". And when I log out again and log in again as the admin, the orders are also shown as "Order shipped". It's only immediately after the status change that the incorrect status appears.

One wrinkle: If as the admin I deny a shipment, and then return to the list as admin, the status seems to have changed from "Ready to ship" to "Validating payment". This was the second item the user purchased, not the first, so this isn't the previous problem with the first order being perpetually in a "Validating payment" state (though that did happen the first time I tried using Chrome for Duke's Forest).



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

This may have to do with cached data in the browser – but telling them to clean their browser before they return to Store from Shipment seems a bit much.

Comment by Ian Evans [ 19/Sep/13 ]

Assigning to William.

Comment by Ian Evans [ 19/Sep/13 ]

Ricardo has checked in a fix for this.





[JAVAEETUTORIAL-245] Validation error message for malformed password can't be found (Duke's Forest) Created: 18/Sep/13  Updated: 19/Sep/13  Resolved: 18/Sep/13

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

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

Attachments: JPEG File password.jpg    

 Description   

If I try to sign up as a new user and enter "1234" as the password, I get an error message that says just "

{person.password}

", indicating that the error message can't be found. I think this means that validation messages have to stay in dukes-store and can't be moved to dukes-resources after all?

Image attached.



 Comments   
Comment by rcervera [ 18/Sep/13 ]

This is now fixed in the source. The ValidationMessages had to be moved one level up in dukes-resources.

Comment by Kim Haase [ 19/Sep/13 ]

Thanks, Ricardo, for fixing this! I can confirm that the validation message now appears:

Password must be between 7 and 100 characters and not empty.





[JAVAEETUTORIAL-244] Update Duke's Tutoring pages to use new namespaces Created: 18/Sep/13  Updated: 19/Sep/13  Resolved: 19/Sep/13

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

Type: Task 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 namespace in the Facelets files should be changed from java.sun.com to xmlns.jcp.org. For example,

xmlns:h="http://java.sun.com/jsf/html"

should be

xmlns:h="http://xmlns.jcp.org/jsf/html"



 Comments   
Comment by Kim Haase [ 18/Sep/13 ]

I should add: there are bugs in some areas. You can't use the new namespace for composite components (http://java.sun.com/jsf/composite) or for pages that use f:metadata with viewparams. See the web/jsf/bookmarks example and web/jsf/compositecomponentexample. You can use the namespace for other kinds of components. Sorry.

Comment by Ian Evans [ 19/Sep/13 ]

Fixed in source.





[JAVAEETUTORIAL-243] CDI Part needs to be moved forward in the book Created: 05/Sep/13  Updated: 06/Sep/13  Due: 13/Sep/13  Resolved: 06/Sep/13

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

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


 Description   

Need to reorganize the structure in the beginning of the tutorial. The CDI part needs to be moved to between Part III, Web Tier, and Part IV, Web Services.



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

Moved CDI part/chapters and updated book. This means all files changed, so if you were working on anything please move it to a safe place before doing an svn update.

Also took advantage of the opportunity to fix some capitalization inconsistencies in figure and table titles (and column titles in tables).

Comment by Kim Haase [ 06/Sep/13 ]

Reopen for edit





[JAVAEETUTORIAL-241] Add section on URL mapping to JAX-RS chapter Created: 02/Sep/13  Updated: 16/Sep/13  Resolved: 16/Sep/13

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

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   

The JAX-RS chapter needs a section on mapping URLs to javax.ws.rs.core.Application, and alternately how to extend Application and use @ApplicationPath to set the URL mapping programmatically.



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

Added section on configuring JAX-RS resources with information on setting the mapping via annotations as well as in the deployment descriptor.





[JAVAEETUTORIAL-240] dukes-forest: Payment web service does not work Created: 28/Aug/13  Updated: 29/Aug/13  Resolved: 29/Aug/13

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

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


 Description   

The payment web service does not work in the current state of the application. Follow these steps to reproduce the issue:

1. Start Glassfish Server

2. Build and deploy the application:
(this enables principal-to-role mapping and creates the required resources)
mvn install

3. Open a web browser:
http://localhost:8080/dukes-store/

4. Register as a new user

5. Log in as the new user
The log is successful on the page, but you get the following error message on the log:
SEVERE: SEC1111: Cannot load group for JDBC realm user [ricardo@gmail.com].

6. Add some products to the cart

7. Check out
You get the following errors on the log:


WARNING: Following exception was thrown:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
[...]
Caused by: javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://RCERVERA-LAP:8080/dukes-store/PaymentService/__container$publishing$subctx/null?WSDL. It failed with:
Server returned HTTP response code: 502 for URL: http://RCERVERA-LAP:8080/dukes-store/PaymentService/__container$publishing$subctx/null?WSDL.
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:249)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:230)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:193)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:162)
at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:359)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:321)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:230)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:212)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:208)
at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:112)
at javax.xml.ws.Service.<init>(Service.java:92)
at services.payment.forest.com.PaymentService.<init>(PaymentService.java:58)
... 36 more
Caused by: java.io.IOException: Server returned HTTP response code: 502 for URL: http://RCERVERA-LAP:8080/dukes-store/PaymentService/__container$publishing$subctx/null?WSDL
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
at java.net.URL.openStream(URL.java:1037)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:983)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:384)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:215)
... 46 more

SEVERE: EJB5070: Exception creating stateless session bean : [PaymentHandler]
WARNING: EJB5184:A system exception occurred ...


Possible cause: the JDBC realm is not working properly.
Possible line of investigation: New Password Encryption Algorithm field that we are not specifying. See the last comment on the following link:
http://stackoverflow.com/questions/12067410/glassfish-3-1-2-jdbcrealm-configuration

(digestrealm-password-enc-algorithm property if we want to add it in glassfish-resources.xml)



 Comments   
Comment by rcervera [ 29/Aug/13 ]

The payment web service works properly. The problem was the proxy configuration in GlassFish. Remove the http.proxyHost and http.proxyPort properties from your server, then the payment works fine.

We made changes to the installation process. Verify as follows:

1. Remove any previous authentication realms:
asadmin delete-auth-realm jdbcRealm

2. Configure resources and realms on dukes-forest/
mvn exec:exec

3. Build and deploy the application:
mvn install

4. Test normally and look at the server log. Payments less than $1000 are processed.





[JAVAEETUTORIAL-239] Refer to JAVA SE 7 security pages instead of SE 6 Created: 28/Aug/13  Updated: 28/Aug/13  Resolved: 28/Aug/13

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

Type: Improvement Priority: Trivial
Reporter: DLambers Assignee: jendrock
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

N/A



 Description   

At the end of paragraph 44.2.1 the following sentence is found:
"For more information on Java SE security, visit http://docs.oracle.com/javase/6/docs/technotes/guides/security/."

The link should be updated to Java SE 7:

http://docs.oracle.com/javase/7/docs/technotes/guides/security/



 Comments   
Comment by jendrock [ 28/Aug/13 ]

Fixed in source. Fix will appear in the bundle when update 7.0.3 is pushed to the Update center and will appear online when the next update is pushed out.

Thank you, @DLambers, for noticing the error and for filing the issue.





[JAVAEETUTORIAL-237] Fix leftover Solbook conversion errors regarding line breaks Created: 21/Aug/13  Updated: 21/Aug/13  Resolved: 21/Aug/13

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

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 four Frame files, the Solbook conversion process replaced line break directives with the word "linebreak" or "preflinebreak" (the name of the directive in Solbook). (There may originally have been more, but we must have caught them before.)

The files are jsf-facelets.fm, jaxrs.fm, persistence-basicexamples.fm, and security-javaee.fm. I just happened to notice one in the Facelets chapter and found the rest by searching for "linebreak" in the tutorial PDF.

I'm checking in fixed versions.



 Comments   
Comment by Kim Haase [ 21/Aug/13 ]

Checked in four Frame files.





[JAVAEETUTORIAL-235] Title "Java EE 6 Tutorial" is baked into PDF Created: 14/Aug/13  Updated: 14/Aug/13  Resolved: 14/Aug/13

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

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   

An alert reader has pointed out that the title of the Java EE Tutorial that appears in File->Properties in Adobe Reader, or in a browser title tab in some browsers (notably on the Mac), is "The Java EE 6 Tutorial".

This turns out to be something we have to fix in the FrameMaker .book file. The keywords there are also a bit sparse and could use improvement.



 Comments   
Comment by Kim Haase [ 14/Aug/13 ]

Checked in fix to book file. The fix will appear in the next update.





[JAVAEETUTORIAL-234] h:selectManyRadio doesn't seem right Created: 11/Aug/13  Updated: 13/Aug/13  Resolved: 13/Aug/13

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

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   

In section 12.2.1.4 the element h:selectManyRadio is mentioned as an example. I do not think this element exists but it would be better to replace it with h:selectManyCheckbox.



 Comments   
Comment by AnnTea [ 11/Aug/13 ]

Sorry, this should not have priority Major. I don't see how (or if) I can change that.

Comment by Kim Haase [ 13/Aug/13 ]

Whew, thanks very much for catching that! That's embarrassing, since selectManyRadio is a contradiction in terms.

I'll change the priority to minor (I think Major is the default) and fix it for the next rev of the Tutorial.

Comment by Kim Haase [ 13/Aug/13 ]

Fixed in documentation source.

Comment by AnnTea [ 13/Aug/13 ]

You are very welcome. I find the tutorial to be a great asset.





[JAVAEETUTORIAL-233] Describe Configuration instances in the WebSocket chapter Created: 09/Aug/13  Updated: 19/Aug/13  Resolved: 19/Aug/13

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

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

 Description   

Describe how to obtain a Configuration instance for WebSocket endpoints.

This is related to the question that Ian found here:
http://stackoverflow.com/questions/18097334/how-can-i-get-a-cookie-value-inside-websocket-end-point



 Comments   
Comment by rcervera [ 09/Aug/13 ]

Another relevant question that should be addressed:

http://stackoverflow.com/questions/17936440/accessing-httpsession-from-httpservletrequest-in-a-web-socket-socketendpoint

Thanks Ian for finding these.

Comment by rcervera [ 19/Aug/13 ]

Added a description and (tested) code snippets of endpoint configurator classes in websocket.fm.





[JAVAEETUTORIAL-232] Wrong URL given for guessnumber-jsf Created: 02/Aug/13  Updated: 09/Aug/13  Resolved: 09/Aug/13

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

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   

Section 8.3.3.3, "To Run the guessnumber-jsf Example", gives the URL as

http://localhost:8080/guessnumber

This gives an error 404, however. The URL should be

http://localhost:8080/guessnumber-jsf



 Comments   
Comment by Kim Haase [ 09/Aug/13 ]

Fixed in jsf-facelets.fm chapter.





[JAVAEETUTORIAL-231] Replace the inboundconnector example as discussed with the JCA engineers Created: 01/Aug/13  Updated: 18/Sep/13  Resolved: 18/Sep/13

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

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   

Siva suggested to replace the inboundconnector example for a future tutorial release to showcase an asynchronous communication use case between the EIS and the MDB/RA.



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

When you redo this example, you may want to use the naming conventions (with hyphens) described in http://docs.oracle.com/javaee/7/tutorial/doc/usingexamples006.htm#GEXAP. It's not very important, so no one mentioned it for the August release – it's great just to have the examples.

Comment by rcervera [ 18/Sep/13 ]

The example is now updated in the source tree and in the book.





[JAVAEETUTORIAL-230] Use JSON messages in the Connector examples Created: 01/Aug/13  Updated: 11/Sep/13  Resolved: 11/Sep/13

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

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   

Use JSON messages in the inbound and outbound connector examples.



 Comments   
Comment by rcervera [ 11/Sep/13 ]

The connectors/traffic example uses JSON processing now.





[JAVAEETUTORIAL-229] Use EIS-specific API in the outboundconnector example Created: 01/Aug/13  Updated: 11/Sep/13  Resolved: 11/Sep/13

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

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   

Replace the CCI implementation by a custom EIS-specific interface and implementation to access the resource adapter from the web application, as recommended by Siva and Jagadish from JCA. Update the Connector Examples chapter accordingly.



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

When you redo this example, you may want to use the naming conventions (with hyphens) described in http://docs.oracle.com/javaee/7/tutorial/doc/usingexamples006.htm#GEXAP. It's not very important, so no one mentioned it for the August release – it's great just to have the examples.

Comment by rcervera [ 02/Aug/13 ]

Thanks Kim, I'll fix that for the next release.

Comment by rcervera [ 11/Sep/13 ]

Replaced the Common Client Interface (CCI) by a simpler, EIS-specific, custom client interface.





[JAVAEETUTORIAL-228] guessnumber-jsf example: implementation of range differs from descriptions Created: 31/Jul/13  Updated: 09/Aug/13  Resolved: 09/Aug/13

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

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


 Description   

In the guessnumber-jsf example, as described by chapter 8.3, the described functionality is that Duke will pick a random number between 0 and 10, while the implementation will give a random number between 0 and 9.

Changing code line
randomInt = new Integer(randomGR.nextInt(10));
to
randomInt = new Integer(randomGR.nextInt(11));
would make the implementation match the description.

It is a minor issue that has no effect on what the example intends to demonstrate, but still might want to have it aligned.



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

Thanks for catching this. We'll make sure the language fits the implementation.

Comment by Kim Haase [ 09/Aug/13 ]

Updated guessnumber-jsf and guessnumber-cdi examples to generate a random number that includes the maximum value. Also updated the code in the jsf-facelets.fm and cdi-basicexamples.fm chapters.





Add section on standardized schema generation to Persistence chapter (JAVAEETUTORIAL-223)

[JAVAEETUTORIAL-224] Add section on specifying schema generation scripts to advanced JPA chapter Created: 29/Jul/13  Updated: 16/Sep/13  Resolved: 16/Sep/13

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

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   

An advanced feature that is part of standardized schema generation in JPA 2.1 is the ability to either have the provider generated create/drop scripts, or to specify custom create/drop scripts within an archive.

Add a section on this feature to the advanced JPA chapter.



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

Added a section in the intro chapter, as it keeps the information together.





[JAVAEETUTORIAL-223] Add section on standardized schema generation to Persistence chapter Created: 29/Jul/13  Updated: 16/Sep/13  Resolved: 16/Sep/13

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

Type: Improvement Priority: Major
Reporter: Ian Evans Assignee: Ian Evans
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-224 Add section on specifying schema gene... Sub-task Resolved Ian Evans  

 Description   

A new feature in JPA 2.1 is standardized schema generation on deployment. This replaces and standardizes the vendor-specific options used previously.

See section 9.4 of the JPA 2.1 spec for details.



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

Added new section on standardized database artifact creation/deletion and data-loading.





[JAVAEETUTORIAL-218] Add section on method validation using Bean Validation Created: 16/Jul/13  Updated: 16/Sep/13  Resolved: 16/Sep/13

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

Type: Improvement Priority: Major
Reporter: Ian Evans Assignee: Ian Evans
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-220 Add information on using method valid... Sub-task Resolved Ian Evans  

 Description   

Section 12.4:

JavaBeans Validation (Bean Validation) is a new validation model available as part of Java EE 7 platform [sic]. The Bean Validation model is supported by constraints in the form of annotations placed on a field, method, or class of a JavaBeans component, such as a managed bean.

We need to fix the grammar of the first sentence, but this is the only mention of method validation in our chapters. We need to add a section here.

We can add it to chapter 12. But I think we might need to do some reorganization of the chapters so:

  • the Bean Validation material is more prominent
  • we clarify the relationship is between Bean Validation and JSF validators
  • we clarify that Bean Validation constraints can be applied to more than just JSF backing beans


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

You are quite right that Bean Validation needs to be more prominently showcased than it is. Right now the intro to the topic is buried in Chapter 12 (Developing with JSF Technology). Please move it to its own chapter or wherever seems appropriate.

Comment by Ian Evans [ 29/Jul/13 ]

Completely refactoring the Bean Validation information will take more work and review time than we can accomplish in the 7.0.2 time-frame. Deferring to 7.0.3.

Comment by Kim Haase [ 03/Sep/13 ]

I'm going to make a start on this by pulling Section 12.4 (Using Bean Validation) out of Chapter 12 and making it a separate chapter, probably right after Chapter 10. Bean Validation is mentioned in Chapter 11, so it'd be a good idea to introduce the topic ahead of time.

I'll mention that this is not just a JSF facility and put in a forward cross-reference to the Chapter 25 section. Then I will leave it to you (Ian) whether you want to put the advanced material into this chapter or leave it where it is.

Does this make sense?

Comment by Ian Evans [ 03/Sep/13 ]

Sounds good to me.

Comment by Kim Haase [ 03/Sep/13 ]

Thanks, Ian. I've been working on it.

Note to all: I'm going to have to check in all the files, since they are now renumbered. If you are working on a chapter you should probably copy it to a safe place before your next svn update.

Please holler if this is extremely inconvenient. I'll wait an hour or so before doing the commit. Then Ian, feel free to make any additional changes to the chapter.

Comment by Kim Haase [ 03/Sep/13 ]

I committed the book with the new chapter. All yours, Ian.

Comment by Ian Evans [ 16/Sep/13 ]

Added new section to bean-validation chapter.





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

[JAVAEETUTORIAL-201] Use JDK 7 syntax for multiple exceptions Created: 24/Jun/13  Updated: 19/Sep/13  Resolved: 19/Sep/13

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

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


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

See the following tech note:
http://docs.oracle.com/javase/7/docs/technotes/guides/language/catch-multiple.html

Comment by Kim Haase [ 13/Aug/13 ]

The JMS, JSF (including dukes-bookstore), and CDI examples all use the new syntax where applicable. A couple of examples specify different handling for different exceptions, so they couldn't be updated.

Comment by Ian Evans [ 19/Sep/13 ]

I think we've updated the example tree with these language features.





[JAVAEETUTORIAL-200] Use JDK 7 language features whenever we can Created: 24/Jun/13  Updated: 19/Sep/13  Resolved: 19/Sep/13

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

Type: Improvement Priority: Major
Reporter: Ian Evans Assignee: Unassigned
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-174 Use try-with-resources (possibly othe... Sub-task Resolved  
JAVAEETUTORIAL-201 Use JDK 7 syntax for multiple exceptions Sub-task Resolved  
JAVAEETUTORIAL-202 Use type inference for generic instan... Sub-task Resolved rcervera  

 Description   

This is a general request to use JDK 7 language features in our examples. I will create subtasks for each language feature.



 Comments   
Comment by Ian Evans [ 19/Sep/13 ]

I think we've updated the example tree with these language features.





Augment information on starting app server (JAVAEETUTORIAL-173)

[JAVAEETUTORIAL-199] Add links back to Starting and Stopping the GlassFish Server/Java DB Created: 24/Jun/13  Updated: 19/Sep/13  Resolved: 19/Sep/13

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

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

Our instructions assume that the server has been started, so a cross-reference back to section 2.2, "Starting and Stopping the GlassFish Server" would be helpful. Something like:

To build and deploy the blahblah example, make sure GlassFish Server is started (see Section 2.2, 2.2, "Starting and Stopping the GlassFish Server") then do the following:
...



 Comments   
Comment by Kim Haase [ 21/Aug/13 ]

Fixed for JSF and JMS chapters.

Comment by Kim Haase [ 21/Aug/13 ]

Fixed for dukes-bookstore chapter; also, with Eric's okay, for servlet and security chapters.

Comment by Ian Evans [ 19/Sep/13 ]

Links have been added.





[JAVAEETUTORIAL-195] Update Duke's Forest for Java EE 7 Created: 21/Jun/13  Updated: 19/Sep/13  Resolved: 19/Sep/13

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

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


 Description   

Update the Duke's Forest case-study example to use the Java EE 7 APIs. Convert it to Maven format.



 Comments   
Comment by Kim Haase [ 18/Sep/13 ]

This should also involve changing the namespace in Facelets files from java.sun.com to xmlns.jcp.org. For example,

xmlns:h="http://java.sun.com/jsf/html"

should be

xmlns:h="http://xmlns.jcp.org/jsf/html"

Comment by Kim Haase [ 18/Sep/13 ]

I can try working on this if you like, William, since there are bugs involving composite components and bookmarks (viewparams in f:metadata).

Comment by William Markito [ 18/Sep/13 ]

Thanks Kim! I'd appreciate that since this I'll be traveling next week..

Comment by Kim Haase [ 19/Sep/13 ]

Committed namespace fixes at revision 1633. I think we're okay on this now, so I'm resolving.





[JAVAEETUTORIAL-194] Update Duke's Tutoring for Java EE 7 Created: 21/Jun/13  Updated: 12/Sep/13  Resolved: 12/Sep/13

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

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   

Update the Duke's Tutoring case-study to use Java EE 7 APIs. Migrate the code-base to Maven format.



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

Updated chapter and example with Java EE 7 features.





[JAVAEETUTORIAL-193] Add section on entity graphs to Advanced JPA chapter Created: 21/Jun/13  Updated: 12/Sep/13  Resolved: 12/Sep/13

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

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   

Entity graphs is a new feature in JPA 2.1. Add a section describing it to the advanced JPA chapter.



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

Entity graph chapter needs more material, and needs to be reviewed. Changing target to 7.0.3.

Comment by Ian Evans [ 12/Sep/13 ]

New chapter added to book.





[JAVAEETUTORIAL-176] Sample code lines should be shorter whenever possible to avoid line-wrapping in the HTML output Created: 06/Jun/13  Updated: 21/Aug/13  Resolved: 21/Aug/13

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

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

Tags: examples, html

 Description   

The HTML output seems to fit around 70 characters in one line for code examples. Line wrapping with CSS has been a great improvement, but the code is still difficult to read when it has more than a few long lines.



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

Fixed bad breaks in jsf-advanced-cc.fm.

Comment by Kim Haase [ 03/Jul/13 ]

Bad break in usingexamples.fm (Section 2.9.2.1) fixed as a result of JAVAEETUTORIAL-210.

Comment by Kim Haase [ 03/Jul/13 ]

webapp.fm: Fixed bad break in web.xml servlet-class subelement; also fixed in hello1 example trunk and branch files. Fixed two bad breaks in GreetingServlet.java; also fixed in hello2 example trunk and branch files.

Comment by Kim Haase [ 03/Jul/13 ]

jsf-intro.fm: fixed bad line breaks.

jsf-facelets.fm: fixed bad line breaks in Frame file as well as in guessnumber-jsf and reservation example files (trunk and branch).

Comment by Kim Haase [ 03/Jul/13 ]

jsf-el.fm: Fixed duplicated item (and bad line break) in Table 9-2.

jsf-page.fm: Fixed bad line breaks, and some table formatting as well.

Comment by Kim Haase [ 03/Jul/13 ]

jsf-develop.fm: Fixed bad line break, table formatting.

jsf-custom.fm: Fixed bad line breaks. Experimented with specifying "wide" as role for informal example. Fixed jsf-config.xml to reduce line lengths.

Comment by Kim Haase [ 03/Jul/13 ]

jsf-configure.fm: Fixed bad line breaks.

Comment by Kim Haase [ 03/Jul/13 ]

jms-concepts.fm, jms-examples.fm: fixed bad line breaks (also in producer, shareddurablesubscribererexample, websimplemessage examples).

Comment by Kim Haase [ 09/Aug/13 ]

Now that the font for code examples is smaller, we can probably go back to having lines that are as long as the FrameMaker source will allow.

Comment by rcervera [ 09/Aug/13 ]

Kim, should we close this issue then?

Comment by Kim Haase [ 09/Aug/13 ]

Hm! Yes, maybe that's the best choice. We'd have to retitle it to something like "Code lines should fit on a FrameMaker line", which seems like a no-brainer.

It is unfortunate that our nightly RSB builds don't use the new stylesheets, so we can't test our fixes. I wonder if they could be changed to use them?

Comment by Kim Haase [ 21/Aug/13 ]

Now that the nightly builds use the new stylesheets, maybe you could close this issue as "Works as Designed", Ricardo? That seems to be closest to the actual situation. I have reverted my "fixes".

Comment by rcervera [ 21/Aug/13 ]

Works as designed with the new style sheets.





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

[JAVAEETUTORIAL-174] Use try-with-resources (possibly other JDK 7 features) where we can Created: 06/Jun/13  Updated: 19/Sep/13  Resolved: 19/Sep/13

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

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


 Description   

NB provides a hint when it would be useful to wrap code in a try-with-resources block. GreetingServlet.java (in hello2) should implement this fix for the PrintWriter that it uses. Other older examples may need such fixes too.



 Comments   
Comment by jendrock [ 06/Jun/13 ]

Fixed GreetingServlet.java (in web/servlet/hello2), and MoodServlet.java (in web/servlet/mood).

Comment by Ian Evans [ 24/Jun/13 ]

See the following tech note:
http://docs.oracle.com/javase/7/docs/technotes/guides/language/try-with-resources.html

Comment by rcervera [ 05/Sep/13 ]

Fixed in the connector examples.

Comment by Ian Evans [ 19/Sep/13 ]

I think we've updated the example tree with these language features.





Generated at Sat Feb 13 22:48:41 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.