You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Clinton Begin (JIRA)" <ib...@incubator.apache.org> on 2005/02/12 22:09:12 UTC

[jira] Closed: (IBATIS-71) DTD in sqlMapConfig doesn't get resolved when not connected to internet

     [ http://issues.apache.org/jira/browse/IBATIS-71?page=history ]
     
Clinton Begin closed IBATIS-71:
-------------------------------

      Assign To: Clinton Begin
     Resolution: Cannot Reproduce
    Fix Version: 2.0.9b


Hmmm..I shouldn't second guess myself.  Indeed I did implement the classpath entity resolver and I've confirmed that it resolves from the JAR and not the internet.

This may be an issue with your chosen XML parser, as it may not support entity resolvers properly (or at all).  My test was conducted with the standard parser included with JDK 1.4.

> DTD in sqlMapConfig doesn't get resolved when not connected to internet
> -----------------------------------------------------------------------
>
>          Key: IBATIS-71
>          URL: http://issues.apache.org/jira/browse/IBATIS-71
>      Project: iBatis for Java
>         Type: Bug
>   Components: SQL Maps
>     Versions: 2.0.9
>  Environment: Windows2000, Tomcat 5.0.28
>     Reporter: Joris Vleminckx
>     Assignee: Clinton Begin
>     Priority: Minor
>      Fix For: 2.0.9b

>
> <Clinton Begin >
> http://www.mail-archive.com/ibatis-user-java@incubator.apache.org/msg00892.html:
> Eek!  I think when I changed the parser over in 2.0.9, I forgot to
> implement the JarEntityResolver.  iBATIS has always used a JAR file
> until this last change.
> </Clinton Begin>
> <Bug description>
> > I have used version 1.2.9 of Ibatis in combination with Struts for the last
> > year and am now porting my application to version 2.0 of Ibatis. I have
> > rewritten succesfully my code, but when I launch a Struts action that
> > invocates Ibatis, I receive the following error:
> > 
> > Caused by: java.lang.RuntimeException: Could not initialize DaoConfig.
> > Cause: com.ibatis.dao.client.DaoException: Error while configuring
> > DaoManager. Cause: java.lang.RuntimeException: Error occurred. Cause:
> > com.ibatis.common.xml.NodeletException: Error parsing XML. Cause:
> > java.lang.RuntimeException: Error parsing XPath '/sqlMapConfig/sqlMap'.
> > Cause: com.ibatis.common.xml.NodeletException: Error parsing XML. Cause:
> > java.net.ConnectException: Connection refused: connect
> > Caused by: java.net.ConnectException: Connection refused: connect
> > Caused by: java.lang.RuntimeException: Error parsing XPath
> > '/sqlMapConfig/sqlMap'. Cause: com.ibatis.common.xml.NodeletException: Error
> > parsing XML. Cause: java.net.ConnectException: Connection refused: connect
> > Caused by: java.net.ConnectException: Connection refused: connect
> > Caused by: java.lang.RuntimeException: Error occurred. Cause:
> > com.ibatis.common.xml.NodeletException: Error parsing XML. Cause:
> > java.lang.RuntimeException: Error parsing XPath '/sqlMapConfig/sqlMap'.
> > Cause: com.ibatis.common.xml.NodeletException: Error parsing XML. Cause:
> > java.net.ConnectException: Connection refused: connect
> > Caused by: java.net.ConnectException: Connection refused: connect
> > Caused by: java.lang.RuntimeException: Error parsing XPath
> > '/sqlMapConfig/sqlMap'. Cause: com.ibatis.common.xml.NodeletException: Error
> > parsing XML. Cause: java.net.ConnectException: Connection refused: connect
> > Caused by: java.net.ConnectException: Connection refused: connect
> > at it.urmet.nfd.daoInterfaces.DaoConfig.<clinit>(DaoConfig.java:24)
> > 
> > It looks like the XML parser tries to look up the doctype dtd
> > <!DOCTYPE sqlMapConfig PUBLIC "-//iBATIS.com//DTD SQL Map Config 1.0//EN"
> > "http://www.ibatis.com/dtd/sql-map-config-2.dtd";>
> > of sqlMapConfig, and since I am not directly connected to internet, this
> > fails and makes my app. crash. Any ideas how to overcome this issue? Thanks
> > a lot!
> </Bug description>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira