db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Monroe" <Greg.Mon...@DukeCE.com>
Subject RE: Should database.dtd alway be the current version?
Date Thu, 14 Dec 2006 21:01:27 GMT
Do'h... should have looked at the code first... 
I misremembered the way the changes were made to keep
from accessing the web during generation.

To quote Emily Litella of the Saturday Night Live news
cast.... "Oh, that's quite different... Never mind".

> -----Original Message-----
> From: Thomas Fischer [mailto:tfischer@apache.org] 
> Sent: Thursday, December 14, 2006 2:28 PM
> To: Apache Torque Developers List
> Subject: RE: Should database.dtd alway be the current version?
> 
> 
> 
> On Thu, 14 Dec 2006, Greg Monroe wrote:
> 
> > Hmm, at first I was going to say not changing makes
> > sense.  But then I remembered that the resolver will
> > try to keep from using the network version in favor
> > of the database.dtd in the generator jar.  This file
> > is always the current version.
> >
> > So, there's a possible issue if you are using the
> > the generic database.dtd in your schema doctype. This
> > can point to different DTDs.  Generator will use the
> > current and other tools that use the web will use the
> > old one.
> >
> 
> No, this is not the current generator behaviour (at least as far as I 
> know). Up to 3.2, the generator looked for the current version (e.g. 
> http://db.apache.org/torque/database_3_2.dtd and resolved 
> this against the 
> local version. Other "unknown" urls (e.g. 
> http://db.apache.org/torque/database.dtd)) were not resolved, so for 
> these, the network version was always used.
> 
> In 3.3 this changen insofar as the generator now recognizes 
> the 3.2 and 
> the 3.3 version if the dtd and can resolve them locally, but 
> it still will 
> not resolve older dtds.
> 
> So unless one explicitly points to the database.dtd in the 
> generator jar,
> the dtd used will not change over time; the only question is 
> if it can 
> still be resolved locally or not.
> 
> >
> >> -----Original Message-----
> >> From: Thomas Fischer [mailto:tfischer@apache.org]
> >> Sent: Thursday, December 14, 2006 9:46 AM
> >> To: Apache Torque Developers List
> >> Subject: Re: Should database.dtd alway be the current version?
> >>
> >> In my eyes, the content of a dtd with an absolute URL should
> >> not change in
> >> time. So from our point of view it may be improper that the
> >> old dtd has no
> >> version number in the name, but it has happened and it has been
> >> around for so long that changing it makes no sense. The 
> only thing we
> >> could do is to remove it, and thus require that all torque
> >> dtds have a
> >> version in their name. But personally I'd just leave it as it is.
> >>
> >>        Thomas
> >>
> >> On Thu, 14 Dec 2006, Greg Monroe wrote:
> >>
> >>> I noticed that the database.dtd on the db.apache.org
> >>> site looks like it is V3.0.0.  Shouldn't this alway
> >>> be the current version?
> >>>
> >>> URL for reference:
> >>>
> >>> http://db.apache.org/torque/dtd/
> >>> Greg Monroe <Monroe@DukeCE.com> (919)680-5050
> >>> C&IS Solutions Team Lead
> >>> Duke Corporate Education, Inc.
> >>> 333 Liggett St.
> >>> Durham, NC 27701
> >>>
> >>>
> >>>
> >>>
> >>> Duke CE Privacy Statement
> >>> Please be advised that this e-mail and any files
> >> transmitted with it are confidential communication or may
> >> otherwise be privileged or confidential and are intended
> >> solely for the individual or entity to whom they are
> >> addressed.  If you are not the intended recipient you may not
> >> rely on the contents of this email or any attachments, and we
> >> ask that you  please not read, copy or retransmit this
> >> communication, but reply to the sender and destroy the email,
> >> its contents, and all copies thereof immediately.  Any
> >> unauthorized dissemination, distribution or copying of this
> >> communication is strictly prohibited.
> >>>
> >>>
> >>>
> >>
> >> 
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> >> For additional commands, e-mail: torque-dev-help@db.apache.org
> >>
> >>
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-dev-help@db.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message