RE: web.xml layout

2001-05-20 Thread Richard Draucker

Hmm... correct me where I may be wrong, please.  

If the xml doc doesn't conform to the DTD, it is
not 'valid' xml.  But, so long as it is 'well formed' the
parser will accept it just the same.  

The parser may look to the DTD for a parsing structure, but
the callback utilization of SAX (assuming Tomcat uses SAX to
parse web.xml) will negate any need to have a 'valid' --
as opposed to 'well formed' -- xml document. 

And that is the crux of my question.  Does it really
matter whether web.xml is 'valid' or simply 'well formed'? 



On Sat, 19 May 2001, you wrote:
 It matters, and doesn't have to do with SAX vs. DOM, it's because
 of the DTD - check out this bit of the DTD:
 !ELEMENT web-app (icon?, display-name?, description?, distribut-able?,
 context-param*, filter*, filter-mapping*, listener*, servlet*,
 servlet-mapping*,
 session-config?, mime-mapping*, welcome-file-list?, error-page*,
 taglib*, resource-env-ref*, resource-ref*, security-constraint*,
 login-config?,
 security-role*, env-entry*, ejb-ref*, ejb-local-ref*)
 
 This says that the servlet-mapping tags must follow all of the servlet.
 Basically the
 tags must be in the order above.
 
 - Robert Petersen
 http://www.orangefood.com
 
 
 -Original Message-
 From: Richard Draucker [mailto:[EMAIL PROTECTED]]
 Sent: Saturday, May 19, 2001 9:24 AM
 To: [EMAIL PROTECTED]
 Subject: web.xml layout
 
 
 Does anyone know if it makes any difference whether I group
 servlet contexts with servlet mappings or keep all contexts
 together and below them keep all mappings together.
 
 Assuming the xml file is being processed by SAX, the
 callback handling would make this irrelevant I would think.
 
 Thoughts?
 
 Thanks,
 Richard
-- 
Richard Draucker,  [EMAIL PROTECTED]
Protected-Data.Com  www.protected-data.com
Remote data support for web developers.











RE: web.xml layout

2001-05-20 Thread Richard Draucker

Great! Thanks for the link, and cudos to Mike Slinn et.al. 
for the good work.


On Sat, 19 May 2001, you wrote:
 FWIW, I think Mike Slinn has put up a web.xml validator (and other
 useful tools/documentation) at
 
 http://tomcat.mslinn.com/
 
 
 On Sat, 19 May 2001, Robert Petersen wrote:
 
  It matters, and doesn't have to do with SAX vs. DOM, it's because
  of the DTD - check out this bit of the DTD:
  !ELEMENT web-app (icon?, display-name?, description?, distribut-able?,
  context-param*, filter*, filter-mapping*, listener*, servlet*,
  servlet-mapping*,
  session-config?, mime-mapping*, welcome-file-list?, error-page*,
  taglib*, resource-env-ref*, resource-ref*, security-constraint*,
  login-config?,
  security-role*, env-entry*, ejb-ref*, ejb-local-ref*)
 
  This says that the servlet-mapping tags must follow all of the servlet.
  Basically the
  tags must be in the order above.
 
  - Robert Petersen
  http://www.orangefood.com
 
 
  -Original Message-
  From: Richard Draucker [mailto:[EMAIL PROTECTED]]
  Sent: Saturday, May 19, 2001 9:24 AM
  To: [EMAIL PROTECTED]
  Subject: web.xml layout
 
 
  Does anyone know if it makes any difference whether I group
  servlet contexts with servlet mappings or keep all contexts
  together and below them keep all mappings together.
 
  Assuming the xml file is being processed by SAX, the
  callback handling would make this irrelevant I would think.
 
  Thoughts?
 
  Thanks,
  Richard
 
 
 
 
 
 
 
 
 
 Milt Epstein
 Research Programmer
 Software/Systems Development Group
 Computing and Communications Services Office (CCSO)
 University of Illinois at Urbana-Champaign (UIUC)
 [EMAIL PROTECTED]
-- 
Richard Draucker,  [EMAIL PROTECTED]
Protected-Data.Com  www.protected-data.com
Remote data support for web developers.











RE: web.xml layout

2001-05-19 Thread CPC Livelink Admin


I believe that the web.xml is parsed using the DTD, so rearranging the
elements will make it complain that the format of the file is incorrect.
Even if you find a container which lets you rearrange, the spec says you
should follow the DTD. So to be portable . . . .

Regards,
Paul


-Original Message-
From: Richard Draucker [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 19, 2001 12:24 PM
To: [EMAIL PROTECTED]
Subject: web.xml layout


Does anyone know if it makes any difference whether I group
servlet contexts with servlet mappings or keep all contexts
together and below them keep all mappings together.

Assuming the xml file is being processed by SAX, the
callback handling would make this irrelevant I would think.

Thoughts?

Thanks,
Richard











RE: web.xml layout

2001-05-19 Thread Robert Petersen

It matters, and doesn't have to do with SAX vs. DOM, it's because
of the DTD - check out this bit of the DTD:
!ELEMENT web-app (icon?, display-name?, description?, distribut-able?,
context-param*, filter*, filter-mapping*, listener*, servlet*,
servlet-mapping*,
session-config?, mime-mapping*, welcome-file-list?, error-page*,
taglib*, resource-env-ref*, resource-ref*, security-constraint*,
login-config?,
security-role*, env-entry*, ejb-ref*, ejb-local-ref*)

This says that the servlet-mapping tags must follow all of the servlet.
Basically the
tags must be in the order above.

- Robert Petersen
http://www.orangefood.com


-Original Message-
From: Richard Draucker [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 19, 2001 9:24 AM
To: [EMAIL PROTECTED]
Subject: web.xml layout


Does anyone know if it makes any difference whether I group
servlet contexts with servlet mappings or keep all contexts
together and below them keep all mappings together.

Assuming the xml file is being processed by SAX, the
callback handling would make this irrelevant I would think.

Thoughts?

Thanks,
Richard











RE: web.xml layout

2001-05-19 Thread Milt Epstein


FWIW, I think Mike Slinn has put up a web.xml validator (and other
useful tools/documentation) at

http://tomcat.mslinn.com/


On Sat, 19 May 2001, Robert Petersen wrote:

 It matters, and doesn't have to do with SAX vs. DOM, it's because
 of the DTD - check out this bit of the DTD:
 !ELEMENT web-app (icon?, display-name?, description?, distribut-able?,
 context-param*, filter*, filter-mapping*, listener*, servlet*,
 servlet-mapping*,
 session-config?, mime-mapping*, welcome-file-list?, error-page*,
 taglib*, resource-env-ref*, resource-ref*, security-constraint*,
 login-config?,
 security-role*, env-entry*, ejb-ref*, ejb-local-ref*)

 This says that the servlet-mapping tags must follow all of the servlet.
 Basically the
 tags must be in the order above.

 - Robert Petersen
 http://www.orangefood.com


 -Original Message-
 From: Richard Draucker [mailto:[EMAIL PROTECTED]]
 Sent: Saturday, May 19, 2001 9:24 AM
 To: [EMAIL PROTECTED]
 Subject: web.xml layout


 Does anyone know if it makes any difference whether I group
 servlet contexts with servlet mappings or keep all contexts
 together and below them keep all mappings together.

 Assuming the xml file is being processed by SAX, the
 callback handling would make this irrelevant I would think.

 Thoughts?

 Thanks,
 Richard









Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]