Hi Paul,

which release of castor are you refering to?

Some weeks ago Werner committed a patch that should have enabled Castor
to always read DTD's and XSD's of Castor from its own JAR file. Please
search release notes yourself if you like to know in which release it is
included.

At the moment I don't know if you can savely omit the DTD definition. I
have to leave this question open for someone else.

Ralf


Paul Bertrand schrieb:
> Hello
>  
> We are currently using the great Castor API in our project and
> unfortunately it happens that, sometimes our application is running on
> firewalled servers blocking most of the traffic.
> The problem we encountered is that by defining the dtd location in the
> begining of each mapping file as this
>  
> <!DOCTYPE mapping PUBLIC "-//EXOLAB/Castor Object Mapping DTD Version
> 1.0//EN" "http://www.castor.org/mapping.dtd";>
>  
> it happens that we can not reach the website creating. Then it creates
> naturally an exception telling us that the validating process can t be done.
>  
> We can not declare the DTD as SYSTEM instead of PUBLIC because we have
> too many mapping files located at different places ( plus mapping in
> .jar files).
> I tried to remove the DTD definition and it works. It appeared that the
> validation of the file does occur even without the dtd declaration
> (internal validating????). I added some misspelled attributes and
> elements in the mapping and the same exception has been thrown.
>  
> The purpose of this message is that I would like to be absolutely sure
> before changing 50 mappings that removing the DTD definition is safe.
>  
> Thanks

-- 

Syscon Ingenieurbüro für
Meß- und Datentechnik GmbH
Ralf Joachim
Raiffeisenstraße 11
D-72127 Kusterdingen
Germany

Tel.   +49 7071 3690 52
Mobil: +49 173 9630135
Fax    +49 7071 3690 98

Email: [EMAIL PROTECTED]
Web:   www.syscon-world.de

-------------------------------------------------
If you wish to unsubscribe from this list, please 
send an empty message to the following address:

[EMAIL PROTECTED]
-------------------------------------------------

Reply via email to