This should be pretty simple...
1. SqlMap --> SqlMapClient
2. XmlSqlMapBuilder.buildSqlMap --> SqlMapClientBuilder.buildSqlMapClient
Then make sure you use the 2.x versions of the DTDs.
Jeff Butler
On 11/18/05, Scott Purcell <[EMAIL PROTECTED]> wrote:
I am using the 2.1.5 Ibatis and I am fol
I am using the 2.1.5 Ibatis and I am following a 1.0 example (see below).
Currently I am trying to compile the below code, but the SqlMap and the
XmlSqlMapBuilder do not exist in the 2.1.5 libs. When looking through the
download I see them in the lib folder under 1-x-Compatibility. But I real
Here's the 2.1.6 code
http://svn.apache.org/repos/asf/ibatis/tags/java_release_2.1.6-589/java/mapper/mapper2/src/com/ibatis/sqlmap/engine/builder/xml/SqlMapClasspathEntityResolver.java
ClintonOn 11/18/05, Clinton Begin <[EMAIL PROTECTED]> wrote:
Sorry, my bad. This code isn't in 2.1.6. It w
Sorry, my bad. This code isn't in 2.1.6. It will be in the next release.
Cheers,
Clinton
On 11/18/05, Clinton Begin <[EMAIL PROTECTED]> wrote:
2.1.6 improved this yet again. So you should upgrade if you can.
Here's the code:
http://svn.apache.org/repos/asf/ibatis/trunk/java/mapper/mappe
2.1.6 improved this yet again. So you should upgrade if you can.
Here's the code:
http://svn.apache.org/repos/asf/ibatis/trunk/java/mapper/mapper2/src/com/ibatis/sqlmap/engine/builder/xml/SqlMapClasspathEntityResolver.java
It should be case insensitive and should fully support both ibatis.c
Unfortunately, I am using 2.1.5.
Jeff Butler a écrit :
The entity resolver ignores the public id - the system id is what's
important. There was a bug in this area that was fixed in version
2.1.5 - make sure you are using that version. If you are not using
2.1.5, then you'll need to use the
Oh
the reason i am using ibatis is because in my
application i want to make provision to add SQL
statements to get data in XML files in future, so by
default we provide some information, but if our
clients require additional data, they need to define
SQL statements in sqlMap, i have logic which wil
The DTD requires that sqlMap have at least one sub element.
This is kind of funny - if it is not legel to define any SQL, why are you using iBATIS? :)
Jeff Butler
On 11/18/05, Ashish Kulkarni <[EMAIL PROTECTED]> wrote:
HelloWhy do i get following errorCaused by:org.xml.sax.SAXParseException: E
The entity resolver ignores the public id - the system id is what's important. There was a bug in this area that was fixed in version 2.1.5 - make sure you are using that version. If you are not using 2.1.5, then you'll need to use the old system ids.
Jeff Butler
On 11/18/05, Niels Beekman <[
Hello
Why do i get following error
Caused by:
org.xml.sax.SAXParseException: Element "sqlMap"
requires additional elements.
at java/lang/Throwable.(Throwable.java:195)
at java/lang/Exception.(Exception.java:41)
at
org/x
One of the developers should comment on this, personally I think the identifier
will be recognized in future versions, amongst other reasons, it saves bandwith
and is a small effort.
Niels
-Original Message-
From: Vincent NICOLAS [mailto:[EMAIL PROTECTED]
Sent: vrijdag 18 november 2005
Thanks you for the quick answer. Does this mean that I will have to
change it again with a future revision of iBatis ? Or will the
//iBatis.com be recognize too in future releases ?
Niels Beekman a écrit :
iBATIS uses a SAX EntityResolver to resolve DTD's from the iBATIS jars.
The public ide
Wow - synchronicity. This is the same as IBATIS-225 (just filed). I agree that this should be fixed/enhanced. There are some issues, but we should be able to overcome them.
Jeff Butler
On 11/18/05, Paul Benedict <[EMAIL PROTECTED]
> wrote:
Clinton,One of the most disappointing aspects of IBA
what happens if the ping fails. does the connection getting removed from
the pool?
the reason why i don't have pinging enabled is because i want to control
the case when a connection is closed for one cluster on my own (so i can
switch to another cluster). even if i could solve the problem by pi
Hi Jeff,
Thanks for the clarification. I have filed a jira request (IBATIS-225)
Anyone who may find this useful, please vote for it.
Huy
Jeff Butler wrote:
I believe this is because reusing result maps is a feature of the
"groupBy" function, and iBATIS assumes the property will be a
Collect
what happens if the ping fails. does the connection getting removed from
the pool?
the reason why i don't have pinging enabled is because i want to control
the case when a connection is closed for one cluster on my own (so i can
switch to another cluster). even if i could solve the problem by pi
iBATIS uses a SAX EntityResolver to resolve DTD's from the iBATIS jars.
The public identifier //ibatis.apache.org does not resolve to the jars
yet. If you use the following:
http://ibatis.apache.org/dtd/sql-map-config-2.dtd";>
it should work.
Niels
-Original Message-
From: Vincent NICOL
Hi everyone,
I'm trying to change my DOCTYPE from
2.0//EN" "http://www.ibatis.com/dtd/sql-map-config-2.dtd";>
to the new one :
2.0//EN" "http://ibatis.apache.org/dtd/sql-map-config-2.dtd";>
However, doing so leads to an error when I launch Tomcat (4.1.31, from
Eclipse 3.1) : a connect error
18 matches
Mail list logo
