Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!

jean-francois lepetitj

Greenhorn
+ Follow
since Sep 01, 2004
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by jean-francois lepetitj

Thank you very much Krzysiek* for your explanations.
For the question 9 p 563, the HFS page that you mentioned is p. 533.
So the same authors that you hail should have to fix it.

For all the other book errata there is the http://www.oreilly.com/catalog/headservletsjsp/errata/ html page.
So glance at it before publishing your discoveries.

However while reading this o'reilly errata page, some ambiguities stay.
Here is an example that I am just studying p 634 about <security-constraint> rules:

The book:
Hand written - if there were NO <http-method> elements, in the <web-resource-collection>, it would mean that NO HTTP Methods are allowed, by ANYONE in any role.
Key-point - if no HTTP Methods are specified then ALL Methods will be constrained.

Errata fix:
Hand written - if there are NO <http-method> elements, in the <web-resource-collection>, it would mean that ALL HTTP Methods are allowed, by ANYONE in any role.
Key-point - if no HTTP Methods are specified then ALL Methods are allowed.

Pretty different isn't it!

But NO new erratum has be written p 635 1 st paragraph for:
A resource is always constrained on an HTTP method by HTTP basis, although you CAN configure the <web-resource-collection> in such a way that ALL Methods are constrained, simply by not putting in ANY <http-method> elements.

So what is true!

Indeed is there a difference between
nothing and <http-method></http-method> (<http-method> does not seem to be a mandatory element),
as there is one between
nothing (all users are allowed)and <auth-constraint></auth-constraint> (no user is allowed)?

JF.


* Why Chris instead of Krzysiek or Krzys?
Hi,
- In the question 9 p 563, I don't understand why the answer C is wrong :

Given:
10. public class BufTag extends BodyTagSupport {
11. public int doStartTag() throws JspException {
12. // insert code here
13. }
14. }
Assume that the tag has been properly configured to allow body content.
Which if inserted at line 12, would cause the JSP code
<mytags:mytag>BodyContent</mytags:mytag> to output BodyContent?

C. return EVAL_BODY_BUFFERED

- In the question 17 p 567, by reading the JSP v20 7.1.6 specifications one can understand that the B and D answers are wrong. But I haven't found in the HFS custom tag development chapter that, in case of simple Tag, the TLD <body-content> "JSP" value has to be forbidden. Indeed if this rule is mentioned for the Tag File on page 498 (through the tag directive), it seems that nothing is said about this shared behaviour due to the Simple Tag & Tag File comon origin : the Simple Tag Extension. But I haven't read yet all the book...

Anyway this book is realy great especially for french guys who can "joindre l'utile a l'agreable" by learning also US english frickin' expressions as :
Boom, Gee, Dude, Uh-oh, Um, Uh, Yikes, Crap
[ December 08, 2004: Message edited by: jean-francois lepetitj ]
I am 48. Why this strange question? Does my difficulties with English has revealed my age?
15 years ago
Considerations: 91/100
Documentation : 58/70
O-O Design : 30/30
GUI : 28/40
Locking : 80/80
Data Store : 40/40
Network Server: 40/40

Thank you very much for all the ideas and solutions that I have found in this forum.

I was very anxious because English is not my mother language (it is french)
and it was a project inside the project to write an understandable documentation in English (50 % more time). So for all my french compatriots worrying about the language difficulty I tell them : Allez-y c'est possible!

A small advice for all the candidates: make a break of 7 days in your project especially at the end. After this break you could see a lot of small imprecisions in your design and documentation.
15 years ago