You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by Thomas Fischer <tf...@apache.org> on 2006/01/28 16:55:37 UTC

Torque tries to get database.dtd over the net if no dtd is specified

Is this necessary ?? I would think if no dtd is given, we could use the 
one which comes in the generator jar without accessing the net for it.

See the DTDResolver.resolveEntity() code.

Please make yourself heard if you find a reason for the current behaviour. 
I'm going to change it if I hear nothing.

        Thomas

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


Re: Torque tries to get database.dtd over the net if no dtd is specified

Posted by Thomas Fischer <fi...@seitenbau.net>.
Thomas Vandahl <th...@tewisoft.de> schrieb am 30.01.2006 09:33:17:

> Thomas Fischer wrote:
> > Is this necessary ?? I would think if no dtd is given, we could use the

> > one which comes in the generator jar without accessing the net for it.
> >
> > See the DTDResolver.resolveEntity() code.
> >
> > Please make yourself heard if you find a reason for the current
> > behaviour. I'm going to change it if I hear nothing.
>
> I guess the question is, why the resolver tries to get another DTD at
> all. I thought the structure of the XML was tied to the particular
> generator version. Validating against another DTD doesn't make sense and
> can cause errors. So my suggestion is to validate against the built-in
> DTD *only*, no matter what DTD is referenced in the XML file.
>
> Bye, Thomas.
>

Hm, I can imagine "legal" reasons for using another DTD. Maybe someone
wants to enforce using just a subset of features by having his own dtd. Or
someone might want to add additional elements and attributes to use the
same xml file for Torque and something else.

So "forcing" a validation against a specific dtd is a bad thing in my
opinion. That said, the solution I proposed above is also "bad" insofar as
it does not allow the user not to validate against a dtd. So my new
proposal would be that if the user decides not to use any dtd (for whatever
reason), we allow him not using a dtd (and not force the torque dtd on
him.)

Besides, always using the Torque dtd for validating is very
counterintuitive in my opinion (and probably against the xml specs).

    Thomas


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


Re: Torque tries to get database.dtd over the net if no dtd is specified

Posted by Thomas Vandahl <th...@tewisoft.de>.
Thomas Fischer wrote:
> Is this necessary ?? I would think if no dtd is given, we could use the 
> one which comes in the generator jar without accessing the net for it.
> 
> See the DTDResolver.resolveEntity() code.
> 
> Please make yourself heard if you find a reason for the current 
> behaviour. I'm going to change it if I hear nothing.

I guess the question is, why the resolver tries to get another DTD at 
all. I thought the structure of the XML was tied to the particular 
generator version. Validating against another DTD doesn't make sense and 
can cause errors. So my suggestion is to validate against the built-in 
DTD *only*, no matter what DTD is referenced in the XML file.

Bye, Thomas.


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


RE: Torque tries to get database.dtd over the net if no dtd is specified

Posted by Thomas Fischer <tf...@apache.org>.

On Mon, 30 Jan 2006, Greg Monroe wrote:

> Only issue I can think of is if you're upgrading torque and have a
> schema with the old version dtd in the doctype.  Will the change
> cause the generator choke on old schema defs?
>

Current behaviour is: The generator only has the _CURRENT_ dtd in its jar 
files. Older dtd's are accessed over the net. This is a problem if (and 
only if) someone does not have access to the internet on the computer 
where the generator is build.I did not propose tho change that.

The disussin was about what happens if _NO_ dtd is given in the schema xml 
file. Currently, the 3.2 dtd is used. This is not standard behaviour. 
After discussion with Thomas V on the list, my current proposal is not to 
check against a dtd if no dtd is given.

     Thomas

> ________________________________
>
> From: Thomas Fischer [mailto:tfischer@apache.org]
> Sent: Sat 1/28/2006 10:55 AM
> To: torque-dev@db.apache.org
> Subject: Torque tries to get database.dtd over the net if no dtd is specified
>
>
>
> Is this necessary ?? I would think if no dtd is given, we could use the
> one which comes in the generator jar without accessing the net for it.
>
> See the DTDResolver.resolveEntity() code.
>
> Please make yourself heard if you find a reason for the current behaviour.
> I'm going to change it if I hear nothing.
>
>        Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
>
>
>
> 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


RE: Torque tries to get database.dtd over the net if no dtd is specified

Posted by Greg Monroe <Gr...@DukeCE.com>.
Only issue I can think of is if you're upgrading torque and have a
schema with the old version dtd in the doctype.  Will the change
cause the generator choke on old schema defs?
 

________________________________

From: Thomas Fischer [mailto:tfischer@apache.org]
Sent: Sat 1/28/2006 10:55 AM
To: torque-dev@db.apache.org
Subject: Torque tries to get database.dtd over the net if no dtd is specified



Is this necessary ?? I would think if no dtd is given, we could use the
one which comes in the generator jar without accessing the net for it.

See the DTDResolver.resolveEntity() code.

Please make yourself heard if you find a reason for the current behaviour.
I'm going to change it if I hear nothing.

        Thomas

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




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.