Hi Alex,
I wrestled with this one as well - I'd like to see a DTD for server.xml as also The
problem is that, as various connectors/interceptors/valves/whoknowswhat are added to
tomcat during a development cycle, the parameters can change tremendously.
e.g. there was a marked change in the 'shape' of the contexts between the tomcat
3.2.b4 and the final 3.2 production.
Ideally, this could be managed by having different versions of a DTD for each
release/revision of tomcat. The restriction is that some of the current
freedom for 'interceptor' implementors would be lost - you couldn't just change the
parameters to an interceptor on a whim - you'd now need to submit revisions to the DTD
for server.xml thereby adding one extra step to the development cycle.
What do others think - should we consider locking down a DTD for each release of
tomcat that matches the 'current' defintion for all of the components?
I think it's possible and desirable, it just adds a level of complexity to the rollout
of new functionality
Comments?
-Thom
Alex Fernández wrote:
> I cannot understand why there can be no DTD. Yes, the contents may be variable and
> extensible, but that's what XML is -- eXtensible.
>
> At least for closed versions, it should be possible to define the grammar used
> therein; otherwise what is the advantage of using XML? Since my experience with it
> is very limited, I'm probably missing something important here.
>
> Cheers,
>
> Alex.
>
> "Craig R. McClanahan" wrote:
>
> > William Au wrote:
> >
> > > Is the dtd for Tomcat 3.2.1's server.xml available somewhere?
> > >
> >
> > There is no DTD available for this file, and there cannot be -- the sets of
> > elements and attributes (by Tomcat) supported in this file are variable and
> > extensible, and cannot be encoded in a DTD.
> >
> > It won't help you for 3.2.1, but Tomcat 4 has (currently incomplete but getting
> > there) extensive documentation on the configuration directives it supports.
> >
> > >
> > > Bill
> > >
> >
> > Craig McClanahan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
