You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by "Yee, Richard K CTR DMDC" <Ri...@osd.pentagon.mil> on 2007/01/08 21:56:42 UTC
iBATIS DTD served every 2 seconds....
Clinton,
In your posting on July 25, 2006 you wrote: "The DTDs should be resolved
from the JAR file if you're using a modern version. ".
My question is what exactly is a "modern" version of iBATIS. We are using
iBATIS 2.0.9. In our DTDs we have
<!DOCTYPE daoConfig
PUBLIC "-//ibatis.apache.org//DTD DAO Configuration 2.0//EN"
"http://ibatis.apache.org/dtd/dao-2.dtd
<http://ibatis.apache.org/dtd/dao-2.dtd> ">
<!DOCTYPE sqlMap
PUBLIC "-//ibatis.apache.org//DTD SQL Map 2.0//EN"
"http://ibatis.apache.org/dtd/sql-map-2.dtd
<http://ibatis.apache.org/dtd/sql-map-2.dtd> ">
and
<!DOCTYPE sqlMapConfig
PUBLIC "-//ibatis.apache.org//DTD SQL Map Config 2.0//EN"
"http://ibatis.apache.org/dtd/sql-map-config-2.dtd
<http://ibatis.apache.org/dtd/sql-map-config-2.dtd> ">
However, it seems that the XML parser is still trying to go out over the
Internet to get the dtd files. The attempt fails because our firewall does
not allow outbound requests from the appserver.
This is the error I see:
2007-01-06 18:20:48,486 FATAL org.mycompany.app..listener.ContextListener -
com.ibatis.dao.client.DaoException: Error while configuring DaoManager.
Cause: java.lang.RuntimeException: XML Parser Error. Cause:
java.net.ConnectException: Connection timed out Caused by:
java.lang.RuntimeException: XML Parser Error. Cause:
java.net.ConnectException: Connection timed out.
Sorry to be dense, but what can I use in the DOCTYPE to force the parser to
use the DTD's in the jar file?
We are using the Oracle OC4J 10.1.2 Appserver.
Thanks,
Richard
Re: iBATIS DTD served every 2 seconds....
Posted by Jeff Butler <je...@gmail.com>.
I believe this was fixed in iBATIS 2.1.5. 2.0.9 is ancient history.
Jeff Butler
On 1/8/07, Yee, Richard K CTR DMDC <Ri...@osd.pentagon.mil> wrote:
>
> Clinton,
> In your posting on July 25, 2006 you wrote: "The DTDs should be resolved
> from the JAR file if you're using a modern version. ".
>
> My question is what exactly is a "modern" version of iBATIS. We are using
> iBATIS 2.0.9. In our DTDs we have
>
> <!DOCTYPE daoConfig
> PUBLIC "-//ibatis.apache.org//DTD DAO Configuration 2.0//EN"
> "http://ibatis.apache.org/dtd/dao-2.dtd">
>
> <!DOCTYPE sqlMap
> PUBLIC "-//ibatis.apache.org//DTD SQL Map 2.0//EN"
> "http://ibatis.apache.org/dtd/sql-map-2.dtd">
>
> and
>
> <!DOCTYPE sqlMapConfig
> PUBLIC "-//ibatis.apache.org//DTD SQL Map Config 2.0//EN"
> "http://ibatis.apache.org/dtd/sql-map-config-2.dtd">
>
> However, it seems that the XML parser is still trying to go out over the
> Internet to get the dtd files. The attempt fails because our firewall does
> not allow outbound requests from the appserver.
>
> This is the error I see:
> 2007-01-06 18:20:48,486 FATAL org.mycompany.app..listener.ContextListener
> - com.ibatis.dao.client.DaoException: Error while configuring DaoManager.
> Cause: java.lang.RuntimeException: XML Parser Error. Cause:
> java.net.ConnectException: Connection timed out Caused by:
> java.lang.RuntimeException: XML Parser Error. Cause:
> java.net.ConnectException: Connection timed out.
>
> Sorry to be dense, but what can I use in the DOCTYPE to force the parser
> to use the DTD's in the jar file?
> We are using the Oracle OC4J 10.1.2 Appserver.
>
> Thanks,
>
> Richard
>
>
>
>
>
Re: iBATIS DTD served every 2 seconds....
Posted by Clinton Begin <cl...@gmail.com>.
Hi Richard,
The version you're using is 2 years old, so I'd recommend upgrading to 2.2or
2.3 (I recommend the latter, as it will be made GA soon).
The entity resolvers were updated to handle the apache.org URLs in 2.1.5.
So it's time to upgrade my friend! :-)
Your alternative is to change the doctype declaration to use a file:// URL.
Cheers,
Clinton
On 1/8/07, Yee, Richard K CTR DMDC <Ri...@osd.pentagon.mil> wrote:
>
> Clinton,
> In your posting on July 25, 2006 you wrote: "The DTDs should be resolved
> from the JAR file if you're using a modern version. ".
>
> My question is what exactly is a "modern" version of iBATIS. We are using
> iBATIS 2.0.9. In our DTDs we have
>
> <!DOCTYPE daoConfig
> PUBLIC "-//ibatis.apache.org//DTD DAO Configuration 2.0//EN"
> "http://ibatis.apache.org/dtd/dao-2.dtd">
>
> <!DOCTYPE sqlMap
> PUBLIC "-//ibatis.apache.org//DTD SQL Map 2.0//EN"
> "http://ibatis.apache.org/dtd/sql-map-2.dtd">
>
> and
>
> <!DOCTYPE sqlMapConfig
> PUBLIC "-//ibatis.apache.org//DTD SQL Map Config 2.0//EN"
> "http://ibatis.apache.org/dtd/sql-map-config-2.dtd">
>
> However, it seems that the XML parser is still trying to go out over the
> Internet to get the dtd files. The attempt fails because our firewall does
> not allow outbound requests from the appserver.
>
> This is the error I see:
> 2007-01-06 18:20:48,486 FATAL org.mycompany.app..listener.ContextListener
> - com.ibatis.dao.client.DaoException: Error while configuring DaoManager.
> Cause: java.lang.RuntimeException: XML Parser Error. Cause:
> java.net.ConnectException: Connection timed out Caused by:
> java.lang.RuntimeException: XML Parser Error. Cause:
> java.net.ConnectException: Connection timed out.
>
> Sorry to be dense, but what can I use in the DOCTYPE to force the parser
> to use the DTD's in the jar file?
> We are using the Oracle OC4J 10.1.2 Appserver.
>
> Thanks,
>
> Richard
>
>
>
>
>