Re: Tomcat 8.5 documentation question

[Thad Humphries]

On Tue, Apr 5, 2016 at 2:53 AM, Mark Thomas  wrote:

> On 04/04/2016 23:10, Thad Humphries wrote:
> > In docs/config/http.xml, lines #1430 and #1648 use
> "certificateValidation".
> > However when I go to "#SSL_Support_-_SSLHostConfig" I find the attribute
> > "certificateVerification", *not *"certificate*Validation*".  I think one
> or
> > the other is an error (and I think "certificateVerification" is the
> correct
> > attribute based on the "certificateVerificationDepth" attribute name).
>
> Thanks for pointing that out.
>
> I've fixed this for 9.0.x and 8.5.x and it will be included in the next
> release of both.
>
> For the record, certificateVerification was the correct one.
>
> Mark
>

You're welcome. I would have put it in a pull request, but I was unsure
which was which.

-- 
"Hell hath no limits, nor is circumscrib'd In one self-place; but where we
are is hell, And where hell is, there must we ever be" --Christopher
Marlowe, *Doctor Faustus* (v. 121-24)

Re: Tomcat 8.5 documentation question

[Mark Thomas]

On 04/04/2016 23:10, Thad Humphries wrote:
> In docs/config/http.xml, lines #1430 and #1648 use "certificateValidation".
> However when I go to "#SSL_Support_-_SSLHostConfig" I find the attribute
> "certificateVerification", *not *"certificate*Validation*".  I think one or
> the other is an error (and I think "certificateVerification" is the correct
> attribute based on the "certificateVerificationDepth" attribute name).

Thanks for pointing that out.

I've fixed this for 9.0.x and 8.5.x and it will be included in the next
release of both.

For the record, certificateVerification was the correct one.

Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 8.5 documentation question

[Thad Humphries]

In docs/config/http.xml, lines #1430 and #1648 use "certificateValidation".
However when I go to "#SSL_Support_-_SSLHostConfig" I find the attribute
"certificateVerification", *not *"certificate*Validation*".  I think one or
the other is an error (and I think "certificateVerification" is the correct
attribute based on the "certificateVerificationDepth" attribute name).

-- 
"Hell hath no limits, nor is circumscrib'd In one self-place; but where we
are is hell, And where hell is, there must we ever be" --Christopher
Marlowe, *Doctor Faustus* (v. 121-24)

Re: Documentation Question

[David kerber]

On 2/22/2012 3:50 PM, Jim Showalter wrote:

Hmm.  Am I to understand this is fixed now?  I tried it and it still seems
to have problems.  However, the other versions (  7.0) seem to be working
much better (I thought they too had problems when I tried in the past).
Also, I appreciate everyone jumping in quickly to fix this.

Jim

-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: Wednesday, February 22, 2012 10:44 AM
To: Tomcat Users List
Subject: Re: Documentation Question


The worst offender (in my opinion) is
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.


By the way, for the page in question, my HTML-checker lists 147
errors (not warnings), the few first of which being :

line 59 column 5 - Error: end tag for element P which is not open
line 78 column 11 - Error: end tag for element P which is not open
line 111 column 10 - Error: end tag for element P which is not open
line 137 column 5 - Error: end tag for element P which is not open
line 154 column 5 - Error: end tag for element P which is not open



Fixed.



If VirtualWebappLoader is updated to trim each value in
virtualClasspath, then that example could be wrapped into several
lines.


That seems like a very reasonable thing to do, as long as it's just
trimming-off leading and trailing whitespace.

I noticed while I was reading those two examples that we have two
separate path separators in the same example: virtualClasspath uses
semi-colons (aka win32-style path separators) and extraResourcePaths
uses commas. Maybe we should try for some consistency :)



VirtualWebappLoader already trims the spaces, so I fixed the docs.

extraResourcePaths does not trim, so it needs more work. I agree that
';' is better there.   My plan is to check if the path contains
semicolon ';' and if it does then go with ; as separator. Otherwise fall
back to the current comma ,.


I am trying to follow the docs for setting up new machine, and I'm 
seeing some messed-up line wraps (not wrapping at the width of my 
browser window (in fact, it won't fit on my 1920x1200 monitor), in:


http://tomcat.apache.org/tomcat-7.0-doc/config/context.html

This is in firefox 10.0.2, just installed yesterday on Windows 7 pro 
x64.  So the issue still exists.


Dave





Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

David,

On 3/9/12 1:38 PM, David kerber wrote:
 I am trying to follow the docs for setting up new machine, and I'm 
 seeing some messed-up line wraps (not wrapping at the width of my 
 browser window (in fact, it won't fit on my 1920x1200 monitor),
 in:
 
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html
 
 This is in firefox 10.0.2, just installed yesterday on Windows 7
 pro x64.  So the issue still exists.

The only thing that Konstantin fixed was the non-well-formed XHTML
document. You still have to scroll horizontally to see some of those
examples.

I'm looking for a CSS-only way to do line-wrapping while also
indicating that the lines have been wrapped.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9aUuUACgkQ9CaO5/Lv0PDvHQCfU4twqcEnldiV9q3ExgRjIqOg
YXIAoKI/6R7VM/ngClpsrSYw9NmZCNYU
=jSCp
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Konstantin Kolinko]

2012/3/9 Christopher Schultz ch...@christopherschultz.net:
 On 3/9/12 1:38 PM, David kerber wrote:
 I am trying to follow the docs for setting up new machine, and I'm
 seeing some messed-up line wraps (not wrapping at the width of my
 browser window (in fact, it won't fit on my 1920x1200 monitor),
 in:

 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html

 This is in firefox 10.0.2, just installed yesterday on Windows 7
 pro x64.  So the issue still exists.

 The only thing that Konstantin fixed was the non-well-formed XHTML
 document. You still have to scroll horizontally to see some of those
 examples.

 I'm looking for a CSS-only way to do line-wrapping while also
 indicating that the lines have been wrapped.

1. I also wrapped data in examples where component allows spaces in
its configuration
and lessened indent where it does not jet allow them.

2. The published documentation is updated only with a new Tomcat release.
You have to look at the one published by nightly build to see the
changes. See links on the Buildbot page.

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Konstantin Kolinko]

 The worst offender (in my opinion) is
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.

 By the way, for the page in question, my HTML-checker lists 147 errors (not
 warnings), the few first of which being :

 line 59 column 5 - Error: end tag for element P which is not open
 line 78 column 11 - Error: end tag for element P which is not open
 line 111 column 10 - Error: end tag for element P which is not open
 line 137 column 5 - Error: end tag for element P which is not open
 line 154 column 5 - Error: end tag for element P which is not open

Fixed.


 If VirtualWebappLoader is updated to trim each value in
 virtualClasspath, then that example could be wrapped into several
 lines.

 That seems like a very reasonable thing to do, as long as it's just
 trimming-off leading and trailing whitespace.

 I noticed while I was reading those two examples that we have two
 separate path separators in the same example: virtualClasspath uses
 semi-colons (aka win32-style path separators) and extraResourcePaths
 uses commas. Maybe we should try for some consistency :)


VirtualWebappLoader already trims the spaces, so I fixed the docs.

extraResourcePaths does not trim, so it needs more work. I agree that
';' is better there.   My plan is to check if the path contains
semicolon ';' and if it does then go with ; as separator. Otherwise
fall back to the current comma ,.

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Documentation Question

[Jim Showalter]

Hmm.  Am I to understand this is fixed now?  I tried it and it still seems
to have problems.  However, the other versions ( 7.0) seem to be working
much better (I thought they too had problems when I tried in the past).
Also, I appreciate everyone jumping in quickly to fix this.

Jim

-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] 
Sent: Wednesday, February 22, 2012 10:44 AM
To: Tomcat Users List
Subject: Re: Documentation Question

 The worst offender (in my opinion) is 
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.

 By the way, for the page in question, my HTML-checker lists 147 
 errors (not warnings), the few first of which being :

 line 59 column 5 - Error: end tag for element P which is not open 
 line 78 column 11 - Error: end tag for element P which is not open 
 line 111 column 10 - Error: end tag for element P which is not open 
 line 137 column 5 - Error: end tag for element P which is not open 
 line 154 column 5 - Error: end tag for element P which is not open

Fixed.


 If VirtualWebappLoader is updated to trim each value in 
 virtualClasspath, then that example could be wrapped into several 
 lines.

 That seems like a very reasonable thing to do, as long as it's just 
 trimming-off leading and trailing whitespace.

 I noticed while I was reading those two examples that we have two 
 separate path separators in the same example: virtualClasspath uses 
 semi-colons (aka win32-style path separators) and extraResourcePaths 
 uses commas. Maybe we should try for some consistency :)


VirtualWebappLoader already trims the spaces, so I fixed the docs.

extraResourcePaths does not trim, so it needs more work. I agree that
';' is better there.   My plan is to check if the path contains
semicolon ';' and if it does then go with ; as separator. Otherwise fall
back to the current comma ,.

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Pid]

On 20/02/2012 17:10, Jim Showalter wrote:
 Is there a version of the Tomcat documentation that consistently handles
 word-wrap?   Some of the segments are very difficult to read while others do
 word wrap properly?

Answer 1: Yes, we maintain several versions of the documentation, with
various flaws distributed across each version.  They are served randomly
though, just to keep you on your toes.

Answer 2: I'm not sure I understand what you're referring to.  Could you
give an example, please?


Delete as appropriate.



p

-- 

[key:62590808]



signature.asc
Description: OpenPGP digital signature

Re: Documentation Question

[André Warnier]

Pid wrote:

On 20/02/2012 17:10, Jim Showalter wrote:

Is there a version of the Tomcat documentation that consistently handles
word-wrap?   Some of the segments are very difficult to read while others do
word wrap properly?


Answer 1: Yes, we maintain several versions of the documentation, with
various flaws distributed across each version.  They are served randomly
though, just to keep you on your toes.


+1
I'd also have to look for a specific example, but I also noted that some documentation 
pages (may be in pre-7.0 version), do not wrap up in a normal browser window and exceed 
line length, which makes for having to scroll the display left-right to read the whole thing.



Answer 2: I'm not sure I understand what you're referring to.  Could you
give an example, please?


Will look for some.



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

André,

On 2/21/12 11:51 AM, André Warnier wrote:
 Pid wrote:
 On 20/02/2012 17:10, Jim Showalter wrote:
 Is there a version of the Tomcat documentation that
 consistently handles word-wrap?   Some of the segments are very
 difficult to read while others do word wrap properly?
 
 Answer 1: Yes, we maintain several versions of the documentation,
 with various flaws distributed across each version.  They are
 served randomly though, just to keep you on your toes.
 
 +1 I'd also have to look for a specific example, but I also noted
 that some documentation pages (may be in pre-7.0 version), do not
 wrap up in a normal browser window and exceed line length, which
 makes for having to scroll the display left-right to read the whole
 thing.

Usually this happens because one single code example (or similar) on
the page forces the layout to stretch horizontally to an unreasonable
width. In response, the renderer allows the whole page to flow out to
those boundaries and the page looks ugly.

I even find it irritating when a single code sample runs off the page
and I have to scroll -- even if it doesn't interfere with the rest of
the page.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9D0zkACgkQ9CaO5/Lv0PCFmwCguRb1U0zdCfwRx33MlLgJOrbl
cVYAn3aOPVoIjPDSznhDjfFcF/ilgxcH
=wVcc
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Pid]

On 21/02/2012 13:59, Jim Showalter wrote:
 Hi.  Thanks for the timely response.  I wasn't certain if I should post this
 to the group or not.  I can repost for the archive if you want.

Yes.  Always to the list.

 Here are some examples.
 
 The worst offender (in my opinion) is
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.  The tables
 don't word wrap at all and I can't begin to get the section on my screen
 without the need for horizontal scrolling.   Other sections in the
 configuration documentation word wrap to different degrees.  I like to
 increase the font size slightly and read the documentation by just scrolling
 down.  If I have to go back and forth too much it is very distracting.

Ugh.  That is definitely wrong.
I will take a look later on as to the cause.


p

 Thanks,
 Jim
 
 
 
 -Original Message-
 From: Pid [mailto:p...@pidster.com] 
 Sent: Tuesday, February 21, 2012 8:30 AM
 To: Tomcat Users List
 Subject: Re: Documentation Question
 
 On 20/02/2012 17:10, Jim Showalter wrote:
 Is there a version of the Tomcat documentation that consistently handles
 word-wrap?   Some of the segments are very difficult to read while others
 do
 word wrap properly?
 
 Answer 1: Yes, we maintain several versions of the documentation, with
 various flaws distributed across each version.  They are served randomly
 though, just to keep you on your toes.
 
 Answer 2: I'm not sure I understand what you're referring to.  Could you
 give an example, please?
 
 
 Delete as appropriate.
 
 
 
 p
 


-- 

[key:62590808]



signature.asc
Description: OpenPGP digital signature

Re: Documentation Question

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Pid,

On 2/21/12 12:31 PM, Pid wrote:
 On 21/02/2012 13:59, Jim Showalter wrote:
 The worst offender (in my opinion) is 
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.  The
 tables don't word wrap at all and I can't begin to get the
 section on my screen without the need for horizontal scrolling.
 Other sections in the configuration documentation word wrap to
 different degrees.  I like to increase the font size slightly and
 read the documentation by just scrolling down.  If I have to go
 back and forth too much it is very distracting.
 
 Ugh.  That is definitely wrong. I will take a look later on as to
 the cause.

The problem is the two pre elements at the very bottom of the page:
they have very long lines in them and pre is not supposed to wrap
long lines. This hoses the whole page.

Looks like adding word-wrap:pre-wrap to the style on one way or
another will fix it. Wow, those source - table transformations
are atrocious.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9D3wEACgkQ9CaO5/Lv0PCxuQCglbHjlEpwVb8ZT378kbQ559Do
qtYAoKIplNC/S17GHuOshwAbWIliefjt
=mHms
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Konstantin Kolinko]

2012/2/21 Christopher Schultz ch...@christopherschultz.net:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Pid,

 On 2/21/12 12:31 PM, Pid wrote:
 On 21/02/2012 13:59, Jim Showalter wrote:
 The worst offender (in my opinion) is
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.  The
 tables don't word wrap at all and I can't begin to get the
 section on my screen without the need for horizontal scrolling.
 Other sections in the configuration documentation word wrap to
 different degrees.  I like to increase the font size slightly and
 read the documentation by just scrolling down.  If I have to go
 back and forth too much it is very distracting.

 Ugh.  That is definitely wrong. I will take a look later on as to
 the cause.

 The problem is the two pre elements at the very bottom of the page:
 they have very long lines in them and pre is not supposed to wrap
 long lines. This hoses the whole page.

 Looks like adding word-wrap:pre-wrap to the style on one way or
 another will fix it. Wow, those source - table transformations
 are atrocious.


If VirtualWebappLoader is updated to trim each value in
virtualClasspath, then that example could be wrapped into several
lines.



Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Konstantin,

On 2/21/12 1:39 PM, Konstantin Kolinko wrote:
 2012/2/21 Christopher Schultz ch...@christopherschultz.net:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 Pid,
 
 On 2/21/12 12:31 PM, Pid wrote:
 On 21/02/2012 13:59, Jim Showalter wrote:
 The worst offender (in my opinion) is 
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.
 The tables don't word wrap at all and I can't begin to get
 the section on my screen without the need for horizontal
 scrolling. Other sections in the configuration documentation
 word wrap to different degrees.  I like to increase the font
 size slightly and read the documentation by just scrolling
 down.  If I have to go back and forth too much it is very
 distracting.
 
 Ugh.  That is definitely wrong. I will take a look later on as
 to the cause.
 
 The problem is the two pre elements at the very bottom of the
 page: they have very long lines in them and pre is not supposed
 to wrap long lines. This hoses the whole page.
 
 Looks like adding word-wrap:pre-wrap to the style on one way
 or another will fix it. Wow, those source - table
 transformations are atrocious.
 
 
 If VirtualWebappLoader is updated to trim each value in 
 virtualClasspath, then that example could be wrapped into several 
 lines.

That seems like a very reasonable thing to do, as long as it's just
trimming-off leading and trailing whitespace.

I noticed while I was reading those two examples that we have two
separate path separators in the same example: virtualClasspath uses
semi-colons (aka win32-style path separators) and extraResourcePaths
uses commas. Maybe we should try for some consistency :)

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9D91UACgkQ9CaO5/Lv0PANugCfYz00cDFy+6m5n0eEb0aQZmZ0
0VkAn0U+ieLUD1140H24qrB67TXMKEO9
=DdTR
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[André Warnier]

Pid wrote:

On 21/02/2012 13:59, Jim Showalter wrote:

Hi.  Thanks for the timely response.  I wasn't certain if I should post this
to the group or not.  I can repost for the archive if you want.


Yes.  Always to the list.


Here are some examples.

The worst offender (in my opinion) is
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.  The tables
don't word wrap at all and I can't begin to get the section on my screen
without the need for horizontal scrolling.   Other sections in the
configuration documentation word wrap to different degrees.  I like to
increase the font size slightly and read the documentation by just scrolling
down.  If I have to go back and forth too much it is very distracting.


Ugh.  That is definitely wrong.
I will take a look later on as to the cause.



By the way, for the page in question, my HTML-checker lists 147 errors (not warnings), the 
few first of which being :


line 59 column 5 - Error: end tag for element P which is not open
line 78 column 11 - Error: end tag for element P which is not open
line 111 column 10 - Error: end tag for element P which is not open
line 137 column 5 - Error: end tag for element P which is not open
line 154 column 5 - Error: end tag for element P which is not open
line 180 column 238 - Error: value of attribute VALIGN cannot be CENTER; must be one 
of TOP, MIDDLE, BOTTOM, BASELINE
line 180 column 338 - Error: value of attribute VALIGN cannot be CENTER; must be one 
of TOP, MIDDLE, BOTTOM, BASELINE
line 189 column 51 - Error: value of attribute VALIGN cannot be CENTER; must be one of 
TOP, MIDDLE, BOTTOM, BASELINE
line 189 column 148 - Error: value of attribute VALIGN cannot be CENTER; must be one 
of TOP, MIDDLE, BOTTOM, BASELINE
line 203 column 51 - Error: value of attribute VALIGN cannot be CENTER; must be one of 
TOP, MIDDLE, BOTTOM, BASELINE
line 203 column 133 - Error: value of attribute VALIGN cannot be CENTER; must be one 
of TOP, MIDDLE, BOTTOM, BASELINE
line 207 column 51 - Error: value of attribute VALIGN cannot be CENTER; must be one of 
TOP, MIDDLE, BOTTOM, BASELINE


So I think whoever looks at this has his work cut out..
;-)

(Note that the above kind of thing may be why this is not wrapping etc..  Browsers may 
just give up trying to follow incorrect stylesheet directives and not do anything at all then)



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Konstantin Kolinko]

2012/2/22 André Warnier a...@ice-sa.com:
 Pid wrote:

 On 21/02/2012 13:59, Jim Showalter wrote:

 Hi.  Thanks for the timely response.  I wasn't certain if I should post
 this
 to the group or not.  I can repost for the archive if you want.


 Yes.  Always to the list.

 Here are some examples.

 The worst offender (in my opinion) is
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.  The tables
 don't word wrap at all and I can't begin to get the section on my screen
 without the need for horizontal scrolling.   Other sections in the
 configuration documentation word wrap to different degrees.  I like to
 increase the font size slightly and read the documentation by just
 scrolling
 down.  If I have to go back and forth too much it is very distracting.


 Ugh.  That is definitely wrong.
 I will take a look later on as to the cause.


 By the way, for the page in question, my HTML-checker lists 147 errors (not
 warnings), the few first of which being :

 line 59 column 5 - Error: end tag for element P which is not open
 line 78 column 11 - Error: end tag for element P which is not open
 line 111 column 10 - Error: end tag for element P which is not open
 line 137 column 5 - Error: end tag for element P which is not open
 line 154 column 5 - Error: end tag for element P which is not open

That is usually caused by nesting ul or ol inside a p.  A list
should not be nested in a paragraph, or the validator will complain.

I corrected such nesting in many places. Anyway if a browser wants to
end p before ul, it will end it (/p tag in a paragraph can be
omitted in HTML), and /p will be ignored.

 line 180 column 238 - Error: value of attribute VALIGN cannot be CENTER;
 must be one of TOP, MIDDLE, BOTTOM, BASELINE
 line 180 column 338 - Error: value of attribute VALIGN cannot be CENTER;
 must be one of TOP, MIDDLE, BOTTOM, BASELINE
 line 189 column 51 - Error: value of attribute VALIGN cannot be CENTER;
 must be one of TOP, MIDDLE, BOTTOM, BASELINE
 line 189 column 148 - Error: value of attribute VALIGN cannot be CENTER;
 must be one of TOP, MIDDLE, BOTTOM, BASELINE
 line 203 column 51 - Error: value of attribute VALIGN cannot be CENTER;
 must be one of TOP, MIDDLE, BOTTOM, BASELINE
 line 203 column 133 - Error: value of attribute VALIGN cannot be CENTER;
 must be one of TOP, MIDDLE, BOTTOM, BASELINE
 line 207 column 51 - Error: value of attribute VALIGN cannot be CENTER;
 must be one of TOP, MIDDLE, BOTTOM, BASELINE

ALIGN=CENTER but VALIGN=MIDDLE


 So I think whoever looks at this has his work cut out..
 ;-)

 (Note that the above kind of thing may be why this is not wrapping etc..
  Browsers may just give up trying to follow incorrect stylesheet directives
 and not do anything at all then)

No, it is not.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Konstantin,

On 2/21/12 3:43 PM, Konstantin Kolinko wrote:
 2012/2/22 André Warnier a...@ice-sa.com:
 Pid wrote:
 
 On 21/02/2012 13:59, Jim Showalter wrote:
 
 Hi.  Thanks for the timely response.  I wasn't certain if I
 should post this to the group or not.  I can repost for the
 archive if you want.
 
 
 Yes.  Always to the list.
 
 Here are some examples.
 
 The worst offender (in my opinion) is 
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.
 The tables don't word wrap at all and I can't begin to get
 the section on my screen without the need for horizontal
 scrolling.   Other sections in the configuration
 documentation word wrap to different degrees.  I like to 
 increase the font size slightly and read the documentation by
 just scrolling down.  If I have to go back and forth too much
 it is very distracting.
 
 
 Ugh.  That is definitely wrong. I will take a look later on as
 to the cause.
 
 
 By the way, for the page in question, my HTML-checker lists 147
 errors (not warnings), the few first of which being :
 
 line 59 column 5 - Error: end tag for element P which is not
 open line 78 column 11 - Error: end tag for element P which is
 not open line 111 column 10 - Error: end tag for element P
 which is not open line 137 column 5 - Error: end tag for element
 P which is not open line 154 column 5 - Error: end tag for
 element P which is not open
 
 That is usually caused by nesting ul or ol inside a p.  A
 list should not be nested in a paragraph, or the validator will
 complain.

Many (all?) XSLT processors will emit p / (for example) if there is
no content in a p/p pair. I know that definitely doesn't work in
many (all?) web browsers, even in XHTML mode. In our XSLTs, we have
xsl:text /xsl:text nodes in places like these where otherwise the
results are ... unacceptable (like in a script/script pair where
there is no body at all but we must have an end-tag).

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9EDh8ACgkQ9CaO5/Lv0PAj8gCgh4r4usMNjpelLWYq4J160yb6
rOAAoI7feIOSwDiqC5YnHkhFc/p9EC6f
=kit2
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Documentation Question

[Konstantin Kolinko]

2012/2/22 Christopher Schultz ch...@christopherschultz.net:
 On 2/21/12 3:43 PM, Konstantin Kolinko wrote:
 2012/2/22 André Warnier a...@ice-sa.com:
 Pid wrote:

 On 21/02/2012 13:59, Jim Showalter wrote:

 Hi.  Thanks for the timely response.  I wasn't certain if I
 should post this to the group or not.  I can repost for the
 archive if you want.


 Yes.  Always to the list.

 Here are some examples.

 The worst offender (in my opinion) is
 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.
 The tables don't word wrap at all and I can't begin to get
 the section on my screen without the need for horizontal
 scrolling.   Other sections in the configuration
 documentation word wrap to different degrees.  I like to
 increase the font size slightly and read the documentation by
 just scrolling down.  If I have to go back and forth too much
 it is very distracting.


 Ugh.  That is definitely wrong. I will take a look later on as
 to the cause.


 By the way, for the page in question, my HTML-checker lists 147
 errors (not warnings), the few first of which being :

 line 59 column 5 - Error: end tag for element P which is not
 open line 78 column 11 - Error: end tag for element P which is
 not open line 111 column 10 - Error: end tag for element P
 which is not open line 137 column 5 - Error: end tag for element
 P which is not open line 154 column 5 - Error: end tag for
 element P which is not open

 That is usually caused by nesting ul or ol inside a p.  A
 list should not be nested in a paragraph, or the validator will
 complain.

 Many (all?) XSLT processors will emit p / (for example) if there is
 no content in a p/p pair. I know that definitely doesn't work in
 many (all?) web browsers, even in XHTML mode. In our XSLTs, we have
 xsl:text /xsl:text nodes in places like these where otherwise the
 results are ... unacceptable (like in a script/script pair where
 there is no body at all but we must have an end-tag).

XSLT does not know how tags can be nested and it does not know that
end tag for p is optional.
It happily prints pSee items in my list: ulliitem/li/ul/p.
It is exactly what is written in the source XML.

A strict HTML validator will say that p ends when ul starts.

A correct HTML will be
pSee items in my list:/pulliitem/li/ul

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Documentation Question

[Konstantin Preißer]

Hello Christopher,

 -Original Message-
 From: Christopher Schultz [mailto:ch...@christopherschultz.net]
 Sent: Tuesday, February 21, 2012 10:35 PM
 To: Tomcat Users List
 Subject: Re: Documentation Question
 
 
 Many (all?) XSLT processors will emit p / (for example) if there is
 no content in a p/p pair. I know that definitely doesn't work in
 many (all?) web browsers, even in XHTML mode.

It does work, but only if you deliver the content in XHTML mode, that is, using 
a Content-Type of application/xhtml+xml (because then the browsers use their 
strict XML parser). Otherwise, when it is delivered as text/html, Browsers 
will always use their HTML parser, even if you use a Doctype that declares the 
document as XHTML.
On a local Windows and Linux filesystem, if you save the file as .html, it will 
be treated by browsers as HTML, whereas if you save it as .xhtml, it will be 
treated as XHTML.

For example, if you use the following XHTML document:

!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html xmlns=http://www.w3.org/1999/xhtml;head
meta http-equiv=Content-Type content=text/html; charset=utf-8/
titleTestpage/title
style type=text/css
p { background-color: #F66; height: 50px; }
/style
/headbody
Text p/ Text2
/body/html

If you save this file as .xhtml on your filesystem and open it, the Browser 
will render the page correctly (the red p is between Text1 and Text2). At 
least it works with IE 9 (IE = IE8 don't support XHTML), Firefox, Chrome and 
Opera. ;-)


Regards,
Konstantin Preißer


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Documentation Question

[Jim Showalter]

Is there a version of the Tomcat documentation that consistently handles
word-wrap?   Some of the segments are very difficult to read while others do
word wrap properly?
 
Thanks,
Jim
 

mod_jk --enable-flock documentation question

[fredk2]

Hi,

Reading the mod_jk (1.2.25) compilation documentation for --enable-flock it
says:

In case the operating system supports flock system call use this flag to
enable this faster locks that are implemented as system call instead
emulated by GNU C library.
However those locks does not work on NFS mounted volumes, so you can use
--enable-flock during compile time to force the flocks() calls.

+ this text seems to say to use --enable-flock to tell mod_jk to use the
flock system call - if supported.
Then it says that NFS does not support the flock system call.  Thus it seems
to me that correct sentence whould be:
However those locks do not work on NFS mounted volumes, hence do not set 
--enable-flock during compile time.

./configure says:
Linux   - checking for flock... yes
Solaris - checking for flock... no

So i guess this is a non-issue for Solaris.

+ Is it correct that --enable-flock only affects the handling of JkShmFile?
thus you would mitigate the potential issue(s) if you move this file to a
local disk /tmp while the apache and logfiles can remain on the NFS mount.

Many thanks - Fred
-- 
View this message in context: 
http://www.nabble.com/mod_jk---enable-flock-documentation-question-tf4426869.html#a12628444
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]