Nabble - iBATIS - User - Java

Using Map as a parameter object

2009-12-19T22:06:32Z

Hi! I've been kicking around iBatis3 for a bit, and I'm running into an inconsistency I'd like to resolve.

For most of my DB Handling items I use CaseInsensitiveHashMaps. It's less precise, but since our backend DB is case insensitive, it makes sense to follow through w/ the Java.

If I pass in a CaseInsensitiveHashMap, iBatis doesn't see it as such. From looking at the source, it appears DynamicContext, when it finds any type of Map, merely does a putAll into its HashMap. (which is case-sensitive) Thus, my parameter object is really never consulted; instead, the values were taken, which means any decorators on that Map are silently discarded.

However, if I create a simple class, say MapHolder, with a getMap() method, which returns my CaseInsensitiveHashMap, I have no problems. My guess is because it resolves map to getMap() via bean methods, and returns my original Map object. So the get() method properly finds all mixed case keys.

I'm not sure how widespread this type of usage is... But it seems like an oversight to me.

As I see it, there are four ways I can fix this...
1) Use my MapHolder everywhere. However, this seems rather unnecessary... I would think a get() call on the map is more efficient than a bean resolution and then a get()... Probably not significantly so. But it makes my code look inelegant and I have to use map.param everywhere to reference things, which would make it harder to transparently supply a bean later.
2) Replace the empty ContextMap (bindings) with the actual passed in Map. This provides other issues, for instance, casting without knowing the original Generics.... Plus, I don't think iBatis should modify my original map, which it would do almost immediately. (By injecting _parameter)
3) Extend the ContextMap definition such that a map can be provided as a delegate... Much the same way Defaults work in the java.util.Properties object. Any call to ContextMap.get would first consult itself. If it finds a value, return it. If it doesn't, then consult the "child" map (if non-null), and return any value found. I'd also have to wrap containsKey and some other items.
4) Provide some way to provide a Map decorator to DynamicContext... Or redefine the Context with one that uses a CaseInsensitiveHashMap natively...

So... Certainly some options. Opinions on which way to go?

Thanks.
Joe

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: IBATUS - Fetching a List of List of Strings from the XML Mapping - Help Needed

2009-12-18T08:14:42Z

First off welcome to ibatis!

Second please don't use this email list for help topics like this. You should use the user-java@... for normal question like this. This allows others in the community to help. I have included it in the reply to move this to the correct email list.

Your issue is that you are not setting your result class properly. Ibatis will return a list of your resultClass because you are calling queryForList(). You need to set the resultClass to the actual class that your query returns. It appears from the name of the select that you are looking for claims. If you have a Claim object I would suggest using it as the result class. If not a simple java.util.HashMap would work. I would suggest going the first route and creating a POJO to hold each result and then harness the true mapping power of ibatis.

Nathan

On Fri, Dec 18, 2009 at 12:25 AM, shiva kumar <shiva_kutts@...> wrote:

Hi All,

This is Sivakumar. I am working with a Struts based UI Application. I have a requirement to externalize all the SQL Queries from the DAO Classes to the XML Files using IBATIS Framework. I would need your assistance in solving an issue that i am facing while modifying the Queries. I am facing an issue in a particular method within A DAO Class where the select query returns a List of List of Records in the Normal DAO Query. However i am not able to fetch this when i am using the IBATIS resultClass="list". Please find below the Method below and let me know your suggestions, so that I could fetch a list of List from the IBATIS XML File Mapping. It would be really helpful to me.

    Method before using IBATIS:

    public List findClaims(ClaimSearchCriteriaVO searchCriteriaVO, UserProfileVO userProfileVO) throws DAOException {

      List displayColumns = searchCriteriaVO.getDisplayColumns();

   try{

      sql = prepareSQL(searchCriteriaVO.getDisplayColumns());
      sql.append(" FROM wrkenv01..WKTV_GP00_CLAIMS WHERE ");
      sql.append("USUS_ID = ? AND ");
      sql.append("GP00_SESSION_ID = ? AND ");
      sql.append("WEB_PAGE_IND = ? ");

      if (searchCriteriaVO.getClaimSortColumn() != null && !   searchCriteriaVO.getClaimSortColumn().equalsIgnoreCase(Constants.ASTRIX)) {
        sql.append("ORDER BY " + searchCriteriaVO.getClaimSortColumn());

        if (searchCriteriaVO.getClaimSortOrder() != null && searchCriteriaVO.getClaimSortOrder().equalsIgnoreCase("D")) {
          sql.append(" DESC ");
        } else {
          sql.append(" ASC ");
        }
      }
      pstmt = con.prepareStatement(sql.toString());
      sessionId = String.valueOf(userProfileVO.getSessionId()).trim();
      pstmt.setString(1, userProfileVO.getUserId());
      pstmt.setString(2, sessionId);
      pstmt.setString(3, "S"); // WEB_PAGE_IND 'S' for search
      rs = pstmt.executeQuery();
      searchResultList = new ArrayList();
      while (rs.next()) {
        rowList = new ArrayList();
        rowList.add(DaoUtil.trim(rs.getString("DISPLAY_COLOR_IND")));
        rowList.add(DaoUtil.trim(rs.getString("CLCL_ID")));
        rowList.add(DaoUtil.trim(rs.getString("PRPR_ID")));
        if (displayColumns != null) {
          for (int displayColumnsIter = 0; displayColumnsIter < displayColumns.length; displayColumnsIter++) {
            rowList.add(DaoUtil.trim(rs.getString(displayColumns[displayColumnsIter])));
          }
        }
        searchResultList.add(rowList);
      }
    } catch (SQLException ex) {
      m_logger.error("SQLException in findClaims() :" + ex.getMessage());
      throw new DAOException(ex.getMessage());
    } finally {
      AppDBUtil.closeQueryObjects(rs, pstmt, con);
    }
    return searchResultList;
}

Method after using IBATIS: DAO.java file

public List findClaims(ClaimSearchCriteriaVO searchCriteriaVO, UserProfileVO userProfileVO) throws DAOException {

    String[] displayColumns = null;
    String claimSortColumn = null;
    String claimSortOrder = null;
    List searchResultList = null;

    try {

      displayColumns = searchCriteriaVO.getDisplayColumns();
      claimSortColumn = searchCriteriaVO.getClaimSortColumn();
      claimSortOrder = DaoUtil.trim(searchCriteriaVO.getClaimSortOrder());

      Map findClaimsMap = new HashMap();
      findClaimsMap.put("userID", userProfileVO.getUserId());
      String sessionId = String.valueOf(userProfileVO.getSessionId()).trim();
      findClaimsMap.put("sessionID", sessionId);
      findClaimsMap.put("webPageInd", "S");

      if (displayColumns != null) {

        findClaimsMap.put("displayColumns", displayColumns);
      }
      if (claimSortColumn != null && !claimSortColumn.equalsIgnoreCase(Constants.ASTRIX)) {

        System.out.println("claimSortcolumn"+claimSortColumn);
        findClaimsMap.put("claimSortColumn", claimSortColumn);

        if (claimSortOrder != null) {

          findClaimsMap.put("claimSortOrder", claimSortOrder);
        }
      }
      SqlMapClient sqlMapQueryBuilder = AppUtil.getSQLMapQueryBuilder(m_logger, sqlMapConfigFile);
      searchResultList = sqlMapQueryBuilder.queryForList("Claim.findClaims", findClaimsMap);

      for (int i = 0; i < searchResultList.size(); i++){

        List rowsList = (List) searchResultList.get(i);
        System.out.println("rowsList "+rowsList.size()); // This should contain all the Column Values fetched from the Table. But this prints 0

      }

    } catch (SQLException ex) {

      m_logger.error("SQLException in findClaims() :" + ex.getMessage());
      throw new DAOException(ex.getMessage());
    }
    return searchResultList;
}

using IBATIS: Query.xml file

<select id="findClaims" resultClass="list" >
                 SELECT DISPLAY_COLOR_IND, CLCL_ID, PRPR_ID
                  <isPropertyAvailable property="displayColumns">
                              <iterate prepend ="," property="displayColumns" conjunction=",">
                                    #displayColumns[]#
                                    </iterate>
                        </isPropertyAvailable> as claimsList
                        FROM wrkenv01..WKTV_GP00_CLAIMS WHERE
            USUS_ID = #userID# AND
            GP00_SESSION_ID = #sessionID# AND
         WEB_PAGE_IND = #webPageInd#
         <isPropertyAvailable property="claimSortColumn" >
                                  ORDER BY $claimSortColumn$
                                  <isPropertyAvailable property="claimSortOrder" >
                                              <isEqual property="claimSortOrder" compareValue="D">
                                                            DESC
                                                </isEqual>
                                                <isNotEqual property="claimSortOrder" compareValue="D">
                                                            ASC
                                                </isNotEqual>
                                    </isPropertyAvailable>
                        </isPropertyAvailable>
</select>

Could you please provide your expertise on this?

Thanks,

Shiva

The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.

Re: Stored Procedures iBatis version 3 beta

2009-12-18T07:58:05Z

You might want to check out the new documentation. The new parameter format is: #{param}, not #param#

On Fri, Dec 18, 2009 at 6:44 AM, JJ Stuart <jjstuart@...> wrote:

I'm a newbie to iBatis and am currently trying to call a parameterised stored
procedure using v3.5 beta of iBatis.

The following mapping works with a hardcoded value

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper
PUBLIC "-//ibatis.apache.org//DTD Mapper 3.0//EN"
"http://ibatis.apache.org/dtd/ibatis-3-mapper.dtd">
<mapper namespace="test.TestMapper">

<select id="selectAll" resultType="LoadStageTest"
parameterType="java.lang.Integer">
{call test_proc3 (102)}
</select>
</mapper>

However if I then try to pass a value in using below (inline param)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper
PUBLIC "-//ibatis.apache.org//DTD Mapper 3.0//EN"
"http://ibatis.apache.org/dtd/ibatis-3-mapper.dtd">
<mapper namespace="test.TestMapper">

<select id="selectAll" resultType="LoadStageTest"
parameterType="java.lang.Integer">
{call test_proc3 (#value#)}
</select>
</mapper>

i get the following error

### Error querying database. Cause:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error
in your SQL syntax; check the manual that corresponds to your MySQL server
version for the right syntax to use near '' at line 1

Any help appreciated,

Many thanks

Jonathan

--
View this message in context: http://old.nabble.com/Stored-Procedures-iBatis-version-3-beta-tp26843638p26843638.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Stored Procedures iBatis version 3 beta

2009-12-18T05:44:56Z

I'm a newbie to iBatis and am currently trying to call a parameterised stored procedure using v3.5 beta of iBatis.

The following mapping works with a hardcoded value

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper
PUBLIC "-//ibatis.apache.org//DTD Mapper 3.0//EN"
"http://ibatis.apache.org/dtd/ibatis-3-mapper.dtd">
<mapper namespace="test.TestMapper">

<select id="selectAll" resultType="LoadStageTest" parameterType="java.lang.Integer">
{call test_proc3 (102)}
</select>
</mapper>

However if I then try to pass a value in using below (inline param)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper
PUBLIC "-//ibatis.apache.org//DTD Mapper 3.0//EN"
"http://ibatis.apache.org/dtd/ibatis-3-mapper.dtd">
<mapper namespace="test.TestMapper">

<select id="selectAll" resultType="LoadStageTest" parameterType="java.lang.Integer">
{call test_proc3 (#value#)}
</select>
</mapper>

i get the following error

### Error querying database. Cause: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1

Any help appreciated,

Many thanks

Jonathan

Re: working with "raw" maps instead of entities?

2009-12-17T04:36:59Z

Larry Meadors schrieb:
> Not really a preferred way - it's going to be up to you to decide if
> you want code or configuration.

I see. :)

> I think a row handler might be the best option in this case. So you
> would have ibatis mapping all of your results to a Map, then in your
> RowHandler, you'd take that row, and create the entity object, pluck
> out the fixed values, then copy the rest to your entity's attributes
> map.

But as far as I investigated things by now, I will still have to, say,
come up with some sort of mapping configuration telling which column
(id/name) to be stored in which key/property in java.util.Map? I can't,
like, in an sqlMap definition, "iterate" across all the columns found to
make sure each column gets stored in a Map entry with the same key, like ...

// pseudocode
<resultMap id="mapResult" class="java.util.HashMap">
<for "column" in "result.columns">
<property name="$column" columnName="$column"/>
</for>
</resultMap>

... ? This would make this project drastically easier. ;)

> You could probably create a RowHandler<Entity> sort of solution to do
> that in a more general manner which would eliminate some redundant
> code.

Yes, that's what comes to mind here. But I'm not half-way there yet I
guess. :)

> Sounds like it'd be a fun project. :)

Indeed. :/ The structure in this system, so far, has successfully kept
me from applying virtually any kind of available O/R mapping in a
meaningful way. OTOH however, the iBatis way is pretty straightforward
and easy-to-explain I guess so not having hibernate in here is not all
that bad after all. ;)

K.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: working with "raw" maps instead of entities?

2009-12-17T04:31:42Z

Not really a preferred way - it's going to be up to you to decide if
you want code or configuration.

I think a row handler might be the best option in this case. So you
would have ibatis mapping all of your results to a Map, then in your
RowHandler, you'd take that row, and create the entity object, pluck
out the fixed values, then copy the rest to your entity's attributes
map.

You could probably create a RowHandler<Entity> sort of solution to do
that in a more general manner which would eliminate some redundant
code.

Sounds like it'd be a fun project. :)

Larry

On Thu, Dec 17, 2009 at 5:20 AM, Kristian Rink <lists@...> wrote:

> Larry Meadors schrieb:
>>
>> Interesting idea - so you end up with something like this?
>>
>> myEntity.id
>> myEntity.name
>> myEntity.attributes.someField
>> myEntity.attributes.someOtherField
>
> Yes, that's basically what it is supposed to be. Reason for this: We're, in
> the backend, using a legacy (proprietary :( ) document management system
> which has a somewhat "dynamic" RDBMS database / table structure which is
> subject to extension pretty often, so, asides a couple of "fixed" values
> (id, name, ...), the "dynamic" approach of having everything else in a Map
> or a Properties object so far has proven to be the most straightforward
> solution.
>
>
>> You could do that, but since you're doing "select *" you'd have to do
>> it with a result map or row handler.
>
> Hmmm... is there a "preferred way among these both and/or quick howtos? I
> already stumbled across the RowHandler but, so far, am unsure how to
> correctly apply this one... I'm using iBatis in a Spring 2.x environment,
> btw. :)
>
> TIA and all the best,
> Kristian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: working with "raw" maps instead of entities?

2009-12-17T04:20:08Z

Larry Meadors schrieb:
> Interesting idea - so you end up with something like this?
>
> myEntity.id
> myEntity.name
> myEntity.attributes.someField
> myEntity.attributes.someOtherField

Yes, that's basically what it is supposed to be. Reason for this: We're,
in the backend, using a legacy (proprietary :( ) document management
system which has a somewhat "dynamic" RDBMS database / table structure
which is subject to extension pretty often, so, asides a couple of
"fixed" values (id, name, ...), the "dynamic" approach of having
everything else in a Map or a Properties object so far has proven to be
the most straightforward solution.

> You could do that, but since you're doing "select *" you'd have to do
> it with a result map or row handler.

Hmmm... is there a "preferred way among these both and/or quick howtos?
I already stumbled across the RowHandler but, so far, am unsure how to
correctly apply this one... I'm using iBatis in a Spring 2.x
environment, btw. :)

TIA and all the best,
Kristian

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: working with "raw" maps instead of entities?

2009-12-17T04:08:46Z

Interesting idea - so you end up with something like this?

myEntity.id
myEntity.name
myEntity.attributes.someField
myEntity.attributes.someOtherField

You could do that, but since you're doing "select *" you'd have to do
it with a result map or row handler.

Larry

On Thu, Dec 17, 2009 at 1:32 AM, Kristian Rink <lists@...> wrote:

> Folks;
>
> not sure whether this is a stupid question; I've been playing with this idea
> before already: As far as I see, after dealing with a bunch of other
> approaches (EclipseLink/JPA, hibernate, ...), I saw that in the end parts of
> our backend code ended up being a "weak re-implementation" of the iBatis
> idea, which makes me reconsider iBatis once again. For now, looking at the
> feature set, there is one thing I would want to do with iBatis, but I am not
> sure how to do so / whether it can be done at all:
>
> In my situation, I select * from a bunch of tables joined via an identifier,
> to, by then, take the identifier and a few other "fixed" columns which will
> appear all the time and put them into designated values of an entity, and
> the "rest" of the selection simply goes to a Map<string,string> inside the
> entity. While this works pretty well, say, inside a Spring JdbcTemplate
> mapper, I am unsure how / if to do something like this in an iBatis
> configuration file as well. So to ask:
>
> - Is it possible?
> - How to do it, if so?
>
> Thanks a bunch in advance and kindest regards,
> Kristian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

working with "raw" maps instead of entities?

2009-12-17T00:32:44Z

Folks;

not sure whether this is a stupid question; I've been playing with this
idea before already: As far as I see, after dealing with a bunch of
other approaches (EclipseLink/JPA, hibernate, ...), I saw that in the
end parts of our backend code ended up being a "weak re-implementation"
of the iBatis idea, which makes me reconsider iBatis once again. For
now, looking at the feature set, there is one thing I would want to do
with iBatis, but I am not sure how to do so / whether it can be done at all:

In my situation, I select * from a bunch of tables joined via an
identifier, to, by then, take the identifier and a few other "fixed"
columns which will appear all the time and put them into designated
values of an entity, and the "rest" of the selection simply goes to a
Map<string,string> inside the entity. While this works pretty well, say,
inside a Spring JdbcTemplate mapper, I am unsure how / if to do
something like this in an iBatis configuration file as well. So to ask:

- Is it possible?
- How to do it, if so?

Thanks a bunch in advance and kindest regards,
Kristian

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

RE: feature request for iBatis3

2009-12-16T17:28:59Z

Already there
https://issues.apache.org/jira/browse/IBATIS-717

Thanks a lot for looking in to it!

-----Original Message-----
From: Clinton Begin [mailto:clinton.begin@...]
Sent: Wednesday, December 16, 2009 8:25 PM
To: user-java@...
Subject: Re: feature request for iBatis3

Can you create a jira ticket for this? It might actually already
work, if we allow it in the DTD.

Clinton

On 2009-12-16, OBender <osya_bender@...> wrote:

> Hi All,
>
>
>
> I guess this is a corner case but it is pretty important one for projects
> with legacy data models.
>
> Let say there is a table in DB that contains:
>
>
>
> Column Type
>
> id int
>
> s1 string
>
> s2 string
>
> s3 string
>
>
>
>
>
> Also let say it is modeled (historically) by two immutable objects:
>
>
>
> public class ObjX
>
> {
>
> private final int id;
>
> private final String s1;
>
> private final ObjY objY;
>
>
>
> public ObjX( int id, String s1, ObjY objY )
>
> {
>
> ...
>
> }
>
> }
>
>
>
> public class ObjY
>
> {
>
> private final String s2;
>
> private final String s3;
>
>
>
> public ObjY( String s2, String s3 )
>
> {
>
> ...
>
> }
>
> }
>
>
>
> In this case there seems to be no way to build a result map for ObjX in
> iBatis without changing ObjX code but what if we cannot change it?
>
>
>
> It would be nice if we could use resultMap in <constructor>/<arg> element.
>
> This way one could write something like:
>
>
>
> <resultMap type="ObjX" id="ObjXResult">
>
> <constructor>
>
> <idArg column="id" javaType="_int" />
>
> <arg column="s1" javaType="String" />
>
> <arg javaType="ObjY" resultMap="ObjYResult"/>
>
> </constructor>
>
> </resultMap>
>
>
>
> <resultMap type="ObjY" id="ObjYResult">
>
> <constructor>
>
> <arg column="s2" javaType="String" />
>
> <arg column="s3" javaType="String" />
>
> </constructor>
>
> </resultMap>
>
>
>
> Comparable result could be achieved with TypeHandler but it will require
> column names to be hardcoded in the TypeHandler implementation also will
> require adding one TypeHandler per each such a case.
>
>
>
> Thanks
>
>

--
Sent from my mobile device

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.716 / Virus Database: 270.14.101/2555 - Release Date: 12/14/09
14:40:00

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: feature request for iBatis3

2009-12-16T17:24:42Z

Can you create a jira ticket for this? It might actually already
work, if we allow it in the DTD.

Clinton

On 2009-12-16, OBender <osya_bender@...> wrote:

feature request for iBatis3

2009-12-16T14:17:35Z

Hi All,

I guess this is a corner case but it is pretty important one for projects with legacy data models.

Let say there is a table in DB that contains:

Column Type

id int

s1 string

s2 string

s3 string

Also let say it is modeled (historically) by two immutable objects:

public class ObjX

{

private final int id;

private final String s1;

private final ObjY objY;

public ObjX( int id, String s1, ObjY objY )

{

...

}

public class ObjY

{

private final String s2;

private final String s3;

public ObjY( String s2, String s3 )

{

...

}

In this case there seems to be no way to build a result map for ObjX in iBatis without changing ObjX code but what if we cannot change it?

It would be nice if we could use resultMap in <constructor>/<arg> element.

This way one could write something like:

</constructor>

</resultMap>

</constructor>

</resultMap>

Comparable result could be achieved with TypeHandler but it will require column names to be hardcoded in the TypeHandler implementation also will require adding one TypeHandler per each such a case.

Thanks

RE: Lazy loading differences between ibatis 2 and 3

2009-12-16T11:11:42Z

Having a proxy that always extends Employee (never Director) would delay the lazy load. But doing this would cause this method to always return false:
public boolean askARase() {
if (this.getBoss() instanceof Director) {
return true;
} else {
return false;
}
}

The proxy can only extend a single class, so when the boss proxy is created it must be of the right class. To be of the right class, the select must be executed before boss property is accessed in any way (including instanceof test). To be sure boss property is of the right type, it must be loaded as soon as any method on Employee is called.

I supposed an optimization that can be added to iBATIS is to check if the property is loaded by a select. If so, check it the select's resultMap contains a discriminator tag. If so load it before any method is called. If not, create a proxy and load the real object only when one of it's method is called.

If you program such a patch, I'm sure it will be appreciated.

Christian

-----Original Message-----
From: Carlos Pita [mailto:carlosjosepita@...]
Sent: Wednesday, December 16, 2009 2:00 PM
To: user-java@...
Subject: Re: Lazy loading differences between ibatis 2 and 3

But as the proxy is a subclass of Employee, this.getBoss() will get intercepted by the proxy method handler which will load the boss immediately before hasMoney() is invoked on it. So I see no need to load it at the point of askARase() invocation.

Regards
--
Carlos

On Wed, Dec 16, 2009 at 4:45 PM, Poitras Christian <Christian.Poitras@...> wrote:

> Hi Bardamu,
>
> I think it was not clear enough due to the lack of Proxy explanation.
> If I have an employee and I call getBoss() on it, it has to load the boss property. But what if I call a method like this in employee?
> public boolean askARase() {
> if (this.getBoss().hasMoney()) {
> return true;
> } else {
> return false;
> }
> }
>
> Then, I hope the boss property is loaded before hasMoney() is called on it.
> The boss property itself is a proxy that can be defined as <E extends Employee>, but what is E? Since iBATIS does not know for sure, I has to call the select to get the right type for boss as soon as any method on Employee is called.
>
> Christian
>
>
> -----Original Message-----
> From: Carlos Pita [mailto:carlosjosepita@...]
> Sent: Wednesday, December 16, 2009 12:16 PM
> To: user-java@...
> Subject: Re: Lazy loading differences between ibatis 2 and 3
>
> Hi Christian,
>
> I understand your point but I don't get its relation to my question at all. Continuing your example, I would ask why employee.getName() will prematurely load the boss. A priori, I would expect the proxy to be smarter and only trigger the loading of boss if getBoss() was effectively called.
>
> Regards
> --
> Bardamu
>
> On Wed, Dec 16, 2009 at 3:09 PM, Poitras Christian <Christian.Poitras@...> wrote:
>> Hi,
>>
>> The major problem that was present in iBATIS 2 was that lazy loaded class where not always of the right type.
>> For exemple, if I have multiple subclasses of a class.
>> Person
>> Employee inherits Person
>> Director inherits Employee
>>
>> If I have an object Employee with a method getBoss() that returns an Employee (lazy loaded), I expect that sometimes it will be a director.
>> In iBATIS 2, testing (employee.getBoss() instanceof Director) will always be false. This problem is due to the fact that iBATIS does not know the real class of the boss property and creates a Proxy of Employee.
>> In iBATIS 3, testing (employee.getBoss() instanceof Director) will be true if the employee's boss is a Director. To know the real type, the statement must be executed.
>>
>> Christian
>>
>>
>> -----Original Message-----
>> From: Carlos Pita [mailto:carlosjosepita@...]
>> Sent: Wednesday, December 16, 2009 11:45 AM
>> To: user-java@...
>> Subject: Lazy loading differences between ibatis 2 and 3
>>
>> Hi all,
>>
>> I've the following sqlmap for ibatis 2. Suppose ibatis has its
>> lazy-loading feature enabled and I obtain a user U by means of
>> findUserById. Then I call U.getEmail() and findMemberById is not
>> executed. That's fine, one wouldn't expect the associated member to
>> be loaded until there is a real need for it. Of course, if then I
>> call
>> U.getMember().getDescription() findMemberById does execute its select, in due time. That said, for ibatis 3 the same example executes findMemberById as soon as U.getEmail() is invoked, loading the member before time. That's not surprising if one inspects the code of ResultObjectProxy (relevant parts copied below). Is this intended to work the way it does or is it a bug?
>>
>> <sqlMap namespace="User">
>>
>> <resultMap id="userMap" class="User">
>> <result property="email" column="email"/>
>> <result property="member" column="member_id"
>> select="findMemberById"/>
>> </resultMap>
>>
>> <resultMap id="memberMap" class="Member">
>> <result property="description" column="description"/>
>> </resultMap>
>>
>> <select id="findUserById" resultMap="userMap">
>> select * from qpoint_user where id = #id#
>> </select>
>>
>> <select id="findMemberById" resultMap="memberMap">
>> select * from cpp_member where member_id = #id#
>> </select>
>>
>> </sqlMap>
>>
>>
>> public class ResultObjectProxy {
>>
>> public Object invoke(Object o, Method method, Object[] args) throws
>> Throwable {
>> try {
>> if (!Object.class.equals(method.getDeclaringClass()) &&
>> PropertyNamer.isGetter(method.getName())) {
>> lazyLoader.loadAll(); <-- this loads all asociations for
>> every getter invoked on this proxy
>> }
>> return method.invoke(target, args);
>> } catch (Throwable t) {
>> throw ExceptionUtil.unwrapThrowable(t);
>> }
>> }
>> }
>>
>> Regards
>> --
>> Bardamu
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@...
>> For additional commands, e-mail: user-java-help@...
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@...
>> For additional commands, e-mail: user-java-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: Lazy loading differences between ibatis 2 and 3

2009-12-16T11:04:52Z

Carlos,

We implemented it this way to handle issues with circular
dependencies. Essentially, yes, all dependencies will be loaded if
you access any of them.

If your getName() getter method accessed the "boss" field internally,
it would fail.

Clinton

On Wed, Dec 16, 2009 at 10:16 AM, Carlos Pita <carlosjosepita@...> wrote:

> Hi Christian,
>
> I understand your point but I don't get its relation to my question at
> all. Continuing your example, I would ask why employee.getName() will
> prematurely load the boss. A priori, I would expect the proxy to be
> smarter and only trigger the loading of boss if getBoss() was
> effectively called.
>
> Regards
> --
> Bardamu
>
> On Wed, Dec 16, 2009 at 3:09 PM, Poitras Christian
> <Christian.Poitras@...> wrote:
>> Hi,
>>
>> The major problem that was present in iBATIS 2 was that lazy loaded class where not always of the right type.
>> For exemple, if I have multiple subclasses of a class.
>> Person
>> Employee inherits Person
>> Director inherits Employee
>>
>> If I have an object Employee with a method getBoss() that returns an Employee (lazy loaded), I expect that sometimes it will be a director.
>> In iBATIS 2, testing (employee.getBoss() instanceof Director) will always be false. This problem is due to the fact that iBATIS does not know the real class of the boss property and creates a Proxy of Employee.
>> In iBATIS 3, testing (employee.getBoss() instanceof Director) will be true if the employee's boss is a Director. To know the real type, the statement must be executed.
>>
>> Christian
>>
>>
>> -----Original Message-----
>> From: Carlos Pita [mailto:carlosjosepita@...]
>> Sent: Wednesday, December 16, 2009 11:45 AM
>> To: user-java@...
>> Subject: Lazy loading differences between ibatis 2 and 3
>>
>> Hi all,
>>
>> I've the following sqlmap for ibatis 2. Suppose ibatis has its lazy-loading feature enabled and I obtain a user U by means of findUserById. Then I call U.getEmail() and findMemberById is not executed. That's fine, one wouldn't expect the associated member to be loaded until there is a real need for it. Of course, if then I call
>> U.getMember().getDescription() findMemberById does execute its select, in due time. That said, for ibatis 3 the same example executes findMemberById as soon as U.getEmail() is invoked, loading the member before time. That's not surprising if one inspects the code of ResultObjectProxy (relevant parts copied below). Is this intended to work the way it does or is it a bug?
>>
>> <sqlMap namespace="User">
>>
>> <resultMap id="userMap" class="User">
>> <result property="email" column="email"/>
>> <result property="member" column="member_id" select="findMemberById"/>
>> </resultMap>
>>
>> <resultMap id="memberMap" class="Member">
>> <result property="description" column="description"/>
>> </resultMap>
>>
>> <select id="findUserById" resultMap="userMap">
>> select * from qpoint_user where id = #id#
>> </select>
>>
>> <select id="findMemberById" resultMap="memberMap">
>> select * from cpp_member where member_id = #id#
>> </select>
>>
>> </sqlMap>
>>
>>
>> public class ResultObjectProxy {
>>
>> public Object invoke(Object o, Method method, Object[] args) throws Throwable {
>> try {
>> if (!Object.class.equals(method.getDeclaringClass()) &&
>> PropertyNamer.isGetter(method.getName())) {
>> lazyLoader.loadAll(); <-- this loads all asociations for every getter invoked on this proxy
>> }
>> return method.invoke(target, args);
>> } catch (Throwable t) {
>> throw ExceptionUtil.unwrapThrowable(t);
>> }
>> }
>> }
>>
>> Regards
>> --
>> Bardamu
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@...
>> For additional commands, e-mail: user-java-help@...
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@...
>> For additional commands, e-mail: user-java-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: Lazy loading differences between ibatis 2 and 3

2009-12-16T11:00:10Z

But as the proxy is a subclass of Employee, this.getBoss() will get
intercepted by the proxy method handler which will load the boss
immediately before hasMoney() is invoked on it. So I see no need to
load it at the point of askARase() invocation.

Regards
--
Carlos

On Wed, Dec 16, 2009 at 4:45 PM, Poitras Christian
<Christian.Poitras@...> wrote:

> Hi Bardamu,
>
> I think it was not clear enough due to the lack of Proxy explanation.
> If I have an employee and I call getBoss() on it, it has to load the boss property. But what if I call a method like this in employee?
> public boolean askARase() {
> if (this.getBoss().hasMoney()) {
> return true;
> } else {
> return false;
> }
> }
>
> Then, I hope the boss property is loaded before hasMoney() is called on it.
> The boss property itself is a proxy that can be defined as <E extends Employee>, but what is E? Since iBATIS does not know for sure, I has to call the select to get the right type for boss as soon as any method on Employee is called.
>
> Christian
>
>
> -----Original Message-----
> From: Carlos Pita [mailto:carlosjosepita@...]
> Sent: Wednesday, December 16, 2009 12:16 PM
> To: user-java@...
> Subject: Re: Lazy loading differences between ibatis 2 and 3
>
> Hi Christian,
>
> I understand your point but I don't get its relation to my question at all. Continuing your example, I would ask why employee.getName() will prematurely load the boss. A priori, I would expect the proxy to be smarter and only trigger the loading of boss if getBoss() was effectively called.
>
> Regards
> --
> Bardamu
>
> On Wed, Dec 16, 2009 at 3:09 PM, Poitras Christian <Christian.Poitras@...> wrote:
>> Hi,
>>
>> The major problem that was present in iBATIS 2 was that lazy loaded class where not always of the right type.
>> For exemple, if I have multiple subclasses of a class.
>> Person
>> Employee inherits Person
>> Director inherits Employee
>>
>> If I have an object Employee with a method getBoss() that returns an Employee (lazy loaded), I expect that sometimes it will be a director.
>> In iBATIS 2, testing (employee.getBoss() instanceof Director) will always be false. This problem is due to the fact that iBATIS does not know the real class of the boss property and creates a Proxy of Employee.
>> In iBATIS 3, testing (employee.getBoss() instanceof Director) will be true if the employee's boss is a Director. To know the real type, the statement must be executed.
>>
>> Christian
>>
>>
>> -----Original Message-----
>> From: Carlos Pita [mailto:carlosjosepita@...]
>> Sent: Wednesday, December 16, 2009 11:45 AM
>> To: user-java@...
>> Subject: Lazy loading differences between ibatis 2 and 3
>>
>> Hi all,
>>
>> I've the following sqlmap for ibatis 2. Suppose ibatis has its
>> lazy-loading feature enabled and I obtain a user U by means of
>> findUserById. Then I call U.getEmail() and findMemberById is not
>> executed. That's fine, one wouldn't expect the associated member to be
>> loaded until there is a real need for it. Of course, if then I call
>> U.getMember().getDescription() findMemberById does execute its select, in due time. That said, for ibatis 3 the same example executes findMemberById as soon as U.getEmail() is invoked, loading the member before time. That's not surprising if one inspects the code of ResultObjectProxy (relevant parts copied below). Is this intended to work the way it does or is it a bug?
>>
>> <sqlMap namespace="User">
>>
>> <resultMap id="userMap" class="User">
>> <result property="email" column="email"/>
>> <result property="member" column="member_id"
>> select="findMemberById"/>
>> </resultMap>
>>
>> <resultMap id="memberMap" class="Member">
>> <result property="description" column="description"/>
>> </resultMap>
>>
>> <select id="findUserById" resultMap="userMap">
>> select * from qpoint_user where id = #id#
>> </select>
>>
>> <select id="findMemberById" resultMap="memberMap">
>> select * from cpp_member where member_id = #id#
>> </select>
>>
>> </sqlMap>
>>
>>
>> public class ResultObjectProxy {
>>
>> public Object invoke(Object o, Method method, Object[] args) throws
>> Throwable {
>> try {
>> if (!Object.class.equals(method.getDeclaringClass()) &&
>> PropertyNamer.isGetter(method.getName())) {
>> lazyLoader.loadAll(); <-- this loads all asociations for
>> every getter invoked on this proxy
>> }
>> return method.invoke(target, args);
>> } catch (Throwable t) {
>> throw ExceptionUtil.unwrapThrowable(t);
>> }
>> }
>> }
>>
>> Regards
>> --
>> Bardamu
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@...
>> For additional commands, e-mail: user-java-help@...
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@...
>> For additional commands, e-mail: user-java-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

RE: Lazy loading differences between ibatis 2 and 3

2009-12-16T10:45:05Z

Hi Bardamu,

I think it was not clear enough due to the lack of Proxy explanation.
If I have an employee and I call getBoss() on it, it has to load the boss property. But what if I call a method like this in employee?
public boolean askARase() {
if (this.getBoss().hasMoney()) {
return true;
} else {
return false;
}
}

Then, I hope the boss property is loaded before hasMoney() is called on it.
The boss property itself is a proxy that can be defined as <E extends Employee>, but what is E? Since iBATIS does not know for sure, I has to call the select to get the right type for boss as soon as any method on Employee is called.

Christian

-----Original Message-----
From: Carlos Pita [mailto:carlosjosepita@...]
Sent: Wednesday, December 16, 2009 12:16 PM
To: user-java@...
Subject: Re: Lazy loading differences between ibatis 2 and 3

Hi Christian,

I understand your point but I don't get its relation to my question at all. Continuing your example, I would ask why employee.getName() will prematurely load the boss. A priori, I would expect the proxy to be smarter and only trigger the loading of boss if getBoss() was effectively called.

Regards
--
Bardamu

On Wed, Dec 16, 2009 at 3:09 PM, Poitras Christian <Christian.Poitras@...> wrote:

> Hi,
>
> The major problem that was present in iBATIS 2 was that lazy loaded class where not always of the right type.
> For exemple, if I have multiple subclasses of a class.
> Person
> Employee inherits Person
> Director inherits Employee
>
> If I have an object Employee with a method getBoss() that returns an Employee (lazy loaded), I expect that sometimes it will be a director.
> In iBATIS 2, testing (employee.getBoss() instanceof Director) will always be false. This problem is due to the fact that iBATIS does not know the real class of the boss property and creates a Proxy of Employee.
> In iBATIS 3, testing (employee.getBoss() instanceof Director) will be true if the employee's boss is a Director. To know the real type, the statement must be executed.
>
> Christian
>
>
> -----Original Message-----
> From: Carlos Pita [mailto:carlosjosepita@...]
> Sent: Wednesday, December 16, 2009 11:45 AM
> To: user-java@...
> Subject: Lazy loading differences between ibatis 2 and 3
>
> Hi all,
>
> I've the following sqlmap for ibatis 2. Suppose ibatis has its
> lazy-loading feature enabled and I obtain a user U by means of
> findUserById. Then I call U.getEmail() and findMemberById is not
> executed. That's fine, one wouldn't expect the associated member to be
> loaded until there is a real need for it. Of course, if then I call
> U.getMember().getDescription() findMemberById does execute its select, in due time. That said, for ibatis 3 the same example executes findMemberById as soon as U.getEmail() is invoked, loading the member before time. That's not surprising if one inspects the code of ResultObjectProxy (relevant parts copied below). Is this intended to work the way it does or is it a bug?
>
> <sqlMap namespace="User">
>
> <resultMap id="userMap" class="User">
> <result property="email" column="email"/>
> <result property="member" column="member_id"
> select="findMemberById"/>
> </resultMap>
>
> <resultMap id="memberMap" class="Member">
> <result property="description" column="description"/>
> </resultMap>
>
> <select id="findUserById" resultMap="userMap">
> select * from qpoint_user where id = #id#
> </select>
>
> <select id="findMemberById" resultMap="memberMap">
> select * from cpp_member where member_id = #id#
> </select>
>
> </sqlMap>
>
>
> public class ResultObjectProxy {
>
> public Object invoke(Object o, Method method, Object[] args) throws
> Throwable {
> try {
> if (!Object.class.equals(method.getDeclaringClass()) &&
> PropertyNamer.isGetter(method.getName())) {
> lazyLoader.loadAll(); <-- this loads all asociations for
> every getter invoked on this proxy
> }
> return method.invoke(target, args);
> } catch (Throwable t) {
> throw ExceptionUtil.unwrapThrowable(t);
> }
> }
> }
>
> Regards
> --
> Bardamu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

Re: Lazy loading differences between ibatis 2 and 3

2009-12-16T09:16:15Z

Hi Christian,

I understand your point but I don't get its relation to my question at
all. Continuing your example, I would ask why employee.getName() will
prematurely load the boss. A priori, I would expect the proxy to be
smarter and only trigger the loading of boss if getBoss() was
effectively called.

Regards
--
Bardamu

On Wed, Dec 16, 2009 at 3:09 PM, Poitras Christian
<Christian.Poitras@...> wrote:

> Hi,
>
> The major problem that was present in iBATIS 2 was that lazy loaded class where not always of the right type.
> For exemple, if I have multiple subclasses of a class.
> Person
> Employee inherits Person
> Director inherits Employee
>
> If I have an object Employee with a method getBoss() that returns an Employee (lazy loaded), I expect that sometimes it will be a director.
> In iBATIS 2, testing (employee.getBoss() instanceof Director) will always be false. This problem is due to the fact that iBATIS does not know the real class of the boss property and creates a Proxy of Employee.
> In iBATIS 3, testing (employee.getBoss() instanceof Director) will be true if the employee's boss is a Director. To know the real type, the statement must be executed.
>
> Christian
>
>
> -----Original Message-----
> From: Carlos Pita [mailto:carlosjosepita@...]
> Sent: Wednesday, December 16, 2009 11:45 AM
> To: user-java@...
> Subject: Lazy loading differences between ibatis 2 and 3
>
> Hi all,
>
> I've the following sqlmap for ibatis 2. Suppose ibatis has its lazy-loading feature enabled and I obtain a user U by means of findUserById. Then I call U.getEmail() and findMemberById is not executed. That's fine, one wouldn't expect the associated member to be loaded until there is a real need for it. Of course, if then I call
> U.getMember().getDescription() findMemberById does execute its select, in due time. That said, for ibatis 3 the same example executes findMemberById as soon as U.getEmail() is invoked, loading the member before time. That's not surprising if one inspects the code of ResultObjectProxy (relevant parts copied below). Is this intended to work the way it does or is it a bug?
>
> <sqlMap namespace="User">
>
> <resultMap id="userMap" class="User">
> <result property="email" column="email"/>
> <result property="member" column="member_id" select="findMemberById"/>
> </resultMap>
>
> <resultMap id="memberMap" class="Member">
> <result property="description" column="description"/>
> </resultMap>
>
> <select id="findUserById" resultMap="userMap">
> select * from qpoint_user where id = #id#
> </select>
>
> <select id="findMemberById" resultMap="memberMap">
> select * from cpp_member where member_id = #id#
> </select>
>
> </sqlMap>
>
>
> public class ResultObjectProxy {
>
> public Object invoke(Object o, Method method, Object[] args) throws Throwable {
> try {
> if (!Object.class.equals(method.getDeclaringClass()) &&
> PropertyNamer.isGetter(method.getName())) {
> lazyLoader.loadAll(); <-- this loads all asociations for every getter invoked on this proxy
> }
> return method.invoke(target, args);
> } catch (Throwable t) {
> throw ExceptionUtil.unwrapThrowable(t);
> }
> }
> }
>
> Regards
> --
> Bardamu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

RE: Lazy loading differences between ibatis 2 and 3

2009-12-16T09:09:32Z

Hi,

The major problem that was present in iBATIS 2 was that lazy loaded class where not always of the right type.
For exemple, if I have multiple subclasses of a class.
Person
Employee inherits Person
Director inherits Employee

If I have an object Employee with a method getBoss() that returns an Employee (lazy loaded), I expect that sometimes it will be a director.
In iBATIS 2, testing (employee.getBoss() instanceof Director) will always be false. This problem is due to the fact that iBATIS does not know the real class of the boss property and creates a Proxy of Employee.
In iBATIS 3, testing (employee.getBoss() instanceof Director) will be true if the employee's boss is a Director. To know the real type, the statement must be executed.

Christian

-----Original Message-----
From: Carlos Pita [mailto:carlosjosepita@...]
Sent: Wednesday, December 16, 2009 11:45 AM
To: user-java@...
Subject: Lazy loading differences between ibatis 2 and 3

Hi all,

I've the following sqlmap for ibatis 2. Suppose ibatis has its lazy-loading feature enabled and I obtain a user U by means of findUserById. Then I call U.getEmail() and findMemberById is not executed. That's fine, one wouldn't expect the associated member to be loaded until there is a real need for it. Of course, if then I call
U.getMember().getDescription() findMemberById does execute its select, in due time. That said, for ibatis 3 the same example executes findMemberById as soon as U.getEmail() is invoked, loading the member before time. That's not surprising if one inspects the code of ResultObjectProxy (relevant parts copied below). Is this intended to work the way it does or is it a bug?

<sqlMap namespace="User">

<resultMap id="userMap" class="User">
<result property="email" column="email"/>
<result property="member" column="member_id" select="findMemberById"/>
</resultMap>

<resultMap id="memberMap" class="Member">
<result property="description" column="description"/>
</resultMap>

<select id="findUserById" resultMap="userMap">
select * from qpoint_user where id = #id#
</select>

<select id="findMemberById" resultMap="memberMap">
select * from cpp_member where member_id = #id#
</select>

</sqlMap>

public class ResultObjectProxy {

public Object invoke(Object o, Method method, Object[] args) throws Throwable {
try {
if (!Object.class.equals(method.getDeclaringClass()) &&
PropertyNamer.isGetter(method.getName())) {
lazyLoader.loadAll(); <-- this loads all asociations for every getter invoked on this proxy
}
return method.invoke(target, args);
} catch (Throwable t) {
throw ExceptionUtil.unwrapThrowable(t);
}
}
}

Regards
--
Bardamu

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Lazy loading differences between ibatis 2 and 3

2009-12-16T08:45:03Z

Hi all,

I've the following sqlmap for ibatis 2. Suppose ibatis has its
lazy-loading feature enabled and I obtain a user U by means of
findUserById. Then I call U.getEmail() and findMemberById is not
executed. That's fine, one wouldn't expect the associated member to be
loaded until there is a real need for it. Of course, if then I call
U.getMember().getDescription() findMemberById does execute its select,
in due time. That said, for ibatis 3 the same example executes
findMemberById as soon as U.getEmail() is invoked, loading the member
before time. That's not surprising if one inspects the code of
ResultObjectProxy (relevant parts copied below). Is this intended to
work the way it does or is it a bug?

<sqlMap namespace="User">

<resultMap id="userMap" class="User">
<result property="email" column="email"/>
<result property="member" column="member_id" select="findMemberById"/>
</resultMap>

<resultMap id="memberMap" class="Member">
<result property="description" column="description"/>
</resultMap>

<select id="findUserById" resultMap="userMap">
select * from qpoint_user where id = #id#
</select>

<select id="findMemberById" resultMap="memberMap">
select * from cpp_member where member_id = #id#
</select>

</sqlMap>

public class ResultObjectProxy {

public Object invoke(Object o, Method method, Object[] args) throws
Throwable {
try {
if (!Object.class.equals(method.getDeclaringClass()) &&
PropertyNamer.isGetter(method.getName())) {
lazyLoader.loadAll(); <-- this loads all asociations for
every getter invoked on this proxy
}
return method.invoke(target, args);
} catch (Throwable t) {
throw ExceptionUtil.unwrapThrowable(t);
}
}
}

Regards
--
Bardamu

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: When can we get next version which is "iBATIS for Java 2.3.5" ?

2009-12-15T09:20:27Z

Making 2.0 Java 6 compilable is pretty simple I think. As for the release, it's a volunteer effort, so it's just a matter of finding time.

On Tue, Dec 15, 2009 at 10:15 AM, J.C. <jchamlin@...> wrote:

Ah, I had a jdk\bin in the path that was Java 5, but JAVA_HOME was set to a
Java 6 JDK. So I guess the build requires not just that a Java 5 version be
in the path first, but rather that JAVA_HOME is set to the JDK you want it
to use to build.

Okay, so I just did a mvn package and it built and tested successfully. :) I
got an artifact, ibatis-sqlmap-SNAPSHOT-r890827.jar as the result in the
target directory.

So, two questions then:
1) Can we get an official release of iBatis 2.3.5?
2) Can you add support for Java 6, since 5 is officially past its
end-of-life as of a few months ago? Here we've got some wrappers that are
Java 6 (and JDBC 4.0 compliant), but will also run against Java 5 (and JDBC
3.5 too, it's not that difficult to use reflection for the few delegate
methods that need it).

-J.C.

Clinton Begin wrote:
>
> It does compile under Java 5. That's the release it's built for. Was
> your
> JAVA_HOME env var set correctly?
>
> Clinton
>
> On Tue, Dec 15, 2009 at 9:03 AM, J.C. <jchamlin@...> wrote:
>
>>
>> First, I apologize in advance for resurrecting an old thread, but its
>> content
>> still seems very relevant.
>>
>> I went looking for an updated version of iBatis 2.3.4 that addresses this
>> issue:
>>
>> https://issues.apache.org/jira/browse/IBATIS-517
>>
>> It looks like in the "release notes" for iBatis 2.3.5 it is listed as
>> fixed:
>>
>>
>> http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10601&styleName=Html&version=12313829
>>
>> However, these release notes are just generated by JIRA, and iBatis 2.3.5
>> does not appear to be released yet.
>>
>> It has been six months since this original message, and over a year since
>> the 2.3.4 release (Sept 2008). Is there any chance of getting iBatis
>> 2.3.5
>> officially released soon?
>>
>> I also tried downloading the source and building it. It won't compile
>> with
>> Java 6, or Java 5 (it looks like it provides implementations of
>> java.sql.ResultSet and java.sql.DataSource that aren't Java 5 or Java 6
>> compliant).
>>
>> [INFO] Compilation failure
>>
>>
>> R:\ibatis\ibatis-2.3.5\ibatis-2-core\src\com\ibatis\sqlmap\engine\type\CallableStatementResultSet.java:[29,7]
>> com.ibatis.sqlmap.engine.type.Callab
>> leStatementResultSet is not abstract and does not override abstract
>> method
>> updateNClob(java.lang.String,java.io.Reader) in java.sql.ResultSet
>>
>>
>> R:\ibatis\ibatis-2.3.5\ibatis-2-core\src\com\ibatis\common\jdbc\SimpleDataSource.java:[52,7]
>> com.ibatis.common.jdbc.SimpleDataSource is not abstra
>> ct and does not override abstract method isWrapperFor(java.lang.Class<?>)
>> in
>> java.sql.Wrapper
>>
>> I could try building with Java 1.4; however, Java 1.4 was end-of-life
>> October 2008. FYI, Java 5 was also end-of-life October 2009.
>>
>> http://java.sun.com/products/archive/eol.policy.html
>>
>> Someone really should update the code to compile under Java 6 (maybe with
>> a
>> source=1.6 and target=1.5). If I did the work for this and submitted a
>> patch, would someone apply it to the trunk (and then maybe do a release)?
>>
>> Thanks!
>>
>> -J.C.
>>
>> 2009/6/5 原田太輔 <keenbeauty@...>:
>> > Dear Committers
>> >
>> > We are using "iBATIS for java" latest release version. That's jar is
>> > ibatis-2.3.4.726.jar.
>> > And Now We are facing trouble in our project for ibatis-540
>> > (https://issues.apache.org/jira/browse/IBATIS-540).
>> >
>> > Do you have any idea about when we can get next version which is
>> > "iBATIS for Java 2.3.5" ?
>> > https://issues.apache.org/jira/browse/IBATIS/fixforversion/12313829
>> >
>> >
>> > Best regards.
>> >
>> > Dai
>> >
>>
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/When-can-we-get-next-version-which-is-%22iBATIS-for-Java-2.3.5%22---tp23889479p26796226.html
>> Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@...
>> For additional commands, e-mail: user-java-help@...
>>
>>
>
>

--
View this message in context: http://old.nabble.com/When-can-we-get-next-version-which-is-%22iBATIS-for-Java-2.3.5%22---tp23889479p26798300.html

Sent from the iBATIS - User - Java mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: When can we get next version which is "iBATIS for Java 2.3.5" ?

2009-12-15T09:15:03Z

Ah, I had a jdk\bin in the path that was Java 5, but JAVA_HOME was set to a Java 6 JDK. So I guess the build requires not just that a Java 5 version be in the path first, but rather that JAVA_HOME is set to the JDK you want it to use to build.

Okay, so I just did a mvn package and it built and tested successfully. :) I got an artifact, ibatis-sqlmap-SNAPSHOT-r890827.jar as the result in the target directory.

So, two questions then:
1) Can we get an official release of iBatis 2.3.5?
2) Can you add support for Java 6, since 5 is officially past its end-of-life as of a few months ago? Here we've got some wrappers that are Java 6 (and JDBC 4.0 compliant), but will also run against Java 5 (and JDBC 3.5 too, it's not that difficult to use reflection for the few delegate methods that need it).

-J.C.

Clinton Begin wrote:

It does compile under Java 5. That's the release it's built for. Was your
JAVA_HOME env var set correctly?

Clinton

On Tue, Dec 15, 2009 at 9:03 AM, J.C. <jchamlin@gmail.com> wrote:

>
> First, I apologize in advance for resurrecting an old thread, but its
> content
> still seems very relevant.
>
> I went looking for an updated version of iBatis 2.3.4 that addresses this
> issue:
>
> https://issues.apache.org/jira/browse/IBATIS-517
>
> It looks like in the "release notes" for iBatis 2.3.5 it is listed as
> fixed:
>
>
> http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10601&styleName=Html&version=12313829
>
> However, these release notes are just generated by JIRA, and iBatis 2.3.5
> does not appear to be released yet.
>
> It has been six months since this original message, and over a year since
> the 2.3.4 release (Sept 2008). Is there any chance of getting iBatis 2.3.5
> officially released soon?
>
> I also tried downloading the source and building it. It won't compile with
> Java 6, or Java 5 (it looks like it provides implementations of
> java.sql.ResultSet and java.sql.DataSource that aren't Java 5 or Java 6
> compliant).
>
> [INFO] Compilation failure
>
>
> R:\ibatis\ibatis-2.3.5\ibatis-2-core\src\com\ibatis\sqlmap\engine\type\CallableStatementResultSet.java:[29,7]
> com.ibatis.sqlmap.engine.type.Callab
> leStatementResultSet is not abstract and does not override abstract method
> updateNClob(java.lang.String,java.io.Reader) in java.sql.ResultSet
>
>
> R:\ibatis\ibatis-2.3.5\ibatis-2-core\src\com\ibatis\common\jdbc\SimpleDataSource.java:[52,7]
> com.ibatis.common.jdbc.SimpleDataSource is not abstra
> ct and does not override abstract method isWrapperFor(java.lang.Class<?>)
> in
> java.sql.Wrapper
>
> I could try building with Java 1.4; however, Java 1.4 was end-of-life
> October 2008. FYI, Java 5 was also end-of-life October 2009.
>
> http://java.sun.com/products/archive/eol.policy.html
>
> Someone really should update the code to compile under Java 6 (maybe with a
> source=1.6 and target=1.5). If I did the work for this and submitted a
> patch, would someone apply it to the trunk (and then maybe do a release)?
>
> Thanks!
>
> -J.C.
>
> 2009/6/5 原田太輔 <keenbeauty@gmail.com>:
> > Dear Committers
> >
> > We are using "iBATIS for java" latest release version. That's jar is
> > ibatis-2.3.4.726.jar.
> > And Now We are facing trouble in our project for ibatis-540
> > (https://issues.apache.org/jira/browse/IBATIS-540).
> >
> > Do you have any idea about when we can get next version which is
> > "iBATIS for Java 2.3.5" ?
> > https://issues.apache.org/jira/browse/IBATIS/fixforversion/12313829
> >
> >
> > Best regards.
> >
> > Dai
> >
>
>
>
> --
> View this message in context:
> http://old.nabble.com/When-can-we-get-next-version-which-is-%22iBATIS-for-Java-2.3.5%22---tp23889479p26796226.html
> Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
> For additional commands, e-mail: user-java-help@ibatis.apache.org
>
>

Re: When can we get next version which is "iBATIS for Java 2.3.5" ?

2009-12-15T09:03:22Z

It does compile under Java 5. That's the release it's built for. Was your JAVA_HOME env var set correctly?

Clinton

On Tue, Dec 15, 2009 at 9:03 AM, J.C. <jchamlin@...> wrote:

First, I apologize in advance for resurrecting an old thread, but its content
still seems very relevant.

I went looking for an updated version of iBatis 2.3.4 that addresses this
issue:

https://issues.apache.org/jira/browse/IBATIS-517

It looks like in the "release notes" for iBatis 2.3.5 it is listed as fixed:

http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10601&styleName=Html&version=12313829

However, these release notes are just generated by JIRA, and iBatis 2.3.5
does not appear to be released yet.

It has been six months since this original message, and over a year since
the 2.3.4 release (Sept 2008). Is there any chance of getting iBatis 2.3.5
officially released soon?

I also tried downloading the source and building it. It won't compile with
Java 6, or Java 5 (it looks like it provides implementations of
java.sql.ResultSet and java.sql.DataSource that aren't Java 5 or Java 6
compliant).

[INFO] Compilation failure

R:\ibatis\ibatis-2.3.5\ibatis-2-core\src\com\ibatis\sqlmap\engine\type\CallableStatementResultSet.java:[29,7]
com.ibatis.sqlmap.engine.type.Callab
leStatementResultSet is not abstract and does not override abstract method
updateNClob(java.lang.String,java.io.Reader) in java.sql.ResultSet

R:\ibatis\ibatis-2.3.5\ibatis-2-core\src\com\ibatis\common\jdbc\SimpleDataSource.java:[52,7]
com.ibatis.common.jdbc.SimpleDataSource is not abstra
ct and does not override abstract method isWrapperFor(java.lang.Class<?>) in
java.sql.Wrapper

I could try building with Java 1.4; however, Java 1.4 was end-of-life
October 2008. FYI, Java 5 was also end-of-life October 2009.

http://java.sun.com/products/archive/eol.policy.html

Someone really should update the code to compile under Java 6 (maybe with a
source=1.6 and target=1.5). If I did the work for this and submitted a
patch, would someone apply it to the trunk (and then maybe do a release)?

Thanks!

-J.C.

2009/6/5 原田太輔 <keenbeauty@...>:
> Dear Committers
>
> We are using "iBATIS for java" latest release version. That's jar is
> ibatis-2.3.4.726.jar.
> And Now We are facing trouble in our project for ibatis-540
> (https://issues.apache.org/jira/browse/IBATIS-540).
>
> Do you have any idea about when we can get next version which is
> "iBATIS for Java 2.3.5" ?
> https://issues.apache.org/jira/browse/IBATIS/fixforversion/12313829
>
>
> Best regards.
>
> Dai
>

--
View this message in context: http://old.nabble.com/When-can-we-get-next-version-which-is-%22iBATIS-for-Java-2.3.5%22---tp23889479p26796226.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: When can we get next version which is "iBATIS for Java 2.3.5" ?

2009-12-15T08:03:49Z

First, I apologize in advance for resurrecting an old thread, but its content still seems very relevant.

I went looking for an updated version of iBatis 2.3.4 that addresses this issue:

https://issues.apache.org/jira/browse/IBATIS-517

It looks like in the "release notes" for iBatis 2.3.5 it is listed as fixed:

http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10601&styleName=Html&version=12313829

However, these release notes are just generated by JIRA, and iBatis 2.3.5 does not appear to be released yet.

It has been six months since this original message, and over a year since the 2.3.4 release (Sept 2008). Is there any chance of getting iBatis 2.3.5 officially released soon?

I also tried downloading the source and building it. It won't compile with Java 6, or Java 5 (it looks like it provides implementations of java.sql.ResultSet and java.sql.DataSource that aren't Java 5 or Java 6 compliant).

[INFO] Compilation failure

R:\ibatis\ibatis-2.3.5\ibatis-2-core\src\com\ibatis\sqlmap\engine\type\CallableStatementResultSet.java:[29,7] com.ibatis.sqlmap.engine.type.Callab
leStatementResultSet is not abstract and does not override abstract method updateNClob(java.lang.String,java.io.Reader) in java.sql.ResultSet

R:\ibatis\ibatis-2.3.5\ibatis-2-core\src\com\ibatis\common\jdbc\SimpleDataSource.java:[52,7] com.ibatis.common.jdbc.SimpleDataSource is not abstra
ct and does not override abstract method isWrapperFor(java.lang.Class<?>) in java.sql.Wrapper

I could try building with Java 1.4; however, Java 1.4 was end-of-life October 2008. FYI, Java 5 was also end-of-life October 2009.

http://java.sun.com/products/archive/eol.policy.html

Someone really should update the code to compile under Java 6 (maybe with a source=1.6 and target=1.5). If I did the work for this and submitted a patch, would someone apply it to the trunk (and then maybe do a release)?

Thanks!

-J.C.

2009/6/5 原田太輔 <keenbeauty@gmail.com>:
> Dear Committers
>
> We are using "iBATIS for java" latest release version. That's jar is
> ibatis-2.3.4.726.jar.
> And Now We are facing trouble in our project for ibatis-540
> (https://issues.apache.org/jira/browse/IBATIS-540).
>
> Do you have any idea about when we can get next version which is
> "iBATIS for Java 2.3.5" ?
> https://issues.apache.org/jira/browse/IBATIS/fixforversion/12313829
>
>
> Best regards.
>
> Dai
>

Re: logging sql statements

2009-12-14T18:02:51Z

Perhaps no documentation on that subject, but Page 2 reads:

-----------------------------------------------

Help make this documentation better…

If you find this documentation lacking in any way, or missing documentation for a feature, then the best thing to do is learn about it and then write the documentation yourself!

We accept public documentation contributions through our wiki at:

http://opensource.atlassian.com/confluence/oss/display/IBATIS/Contribute+Documentation

You’re the best author of this documentation, people like you have to read it!
-----------------------------------------------

Of course, these comments are welcome on this list too, but definitely post it to the wiki as well.

Cheers, :-)
Clinton

On Mon, Dec 14, 2009 at 6:29 PM, Stephen Friedrich <stephen.friedrich@...> wrote:
>
> I haven't found any documentation either, but had to refer to the source code to find usages of Loggers.
> This log category can be valuable, too:
> <category name="com.ibatis" additivity="false">
> <priority value="debug"/>
> </category>
>
> -----Ursprüngliche Nachricht-----
> Von: Rick.Wellman [mailto:Rick.Wellman@...]
> Gesendet: Dienstag, 15. Dezember 2009 00:56
> An: user-java@...
> Betreff: RE: logging sql statements
>
> iBatis relies on logging of the underlying JDBC statements which is documented (somewhere).
> We use the following settings in our log4j.xml file, adjust to your liking:
> 
> <category name="java.sql">
> <priority value="info" />
> </category>
>
> <category name="java.sql.ResultSet">
> <priority value="info" />
> </category>
>
> -----Original Message-----
> From: Trenton D. Adams [mailto:trenta@...]
> Sent: Monday, December 14, 2009 5:51 PM
> To: user-java
> Subject: logging sql statements
>
> Hi Guys,
>
> I've searched the net like crazy, and there doesn't seem to be anything reasonable describing how to have iBatis print out the parsed SQL that is being run, during an error.
>
> Is this possible?
>
> Currently I tried the following, to no avail...
>
> LogFactory.selectLog4JLogging();
>
> log4j.logger.com.ibatis=DEBUG
>
> Trenton D. Adams
> Systems Analyst/Web Software Engineer
> Navy Penguins at your service!
> Athabasca University
> (780) 675-6195
> :wq!
>
> __
> This communication is intended for the use of the recipient to whom it
> is addressed, and may contain confidential, personal, and or privileged
> information. Please contact us immediately if you are not the intended
> recipient of this communication, and do not copy, distribute, or take
> action relying on it. Any communications received in error, or
> subsequent reply, should be deleted or destroyed.
> ---
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>

Re: Null Pointer Exception on Malformed

2009-12-14T17:59:13Z

Yep, bug. NPEs are always bugs -- we don't consider them "acceptable". Can you submit this as a Jira ticket?

Thanks much!

Clinton

On Mon, Dec 14, 2009 at 12:06 PM, Soks86 <michael.chrostowski@...> wrote:

Hi,

I was using <foreach> in an <insert> (within a <mapper>) statement and I got
the following NPE:

Caused by: java.lang.NullPointerException
at java.util.regex.Pattern.<init>(Pattern.java:1132)
at java.util.regex.Pattern.compile(Pattern.java:823)
at java.lang.String.replaceFirst(String.java:2146)
at
org.apache.ibatis.builder.xml.dynamic.ForEachSqlNode$FilteredDynamicContext$1.handleToken(ForEachSqlNode.java:116)
at
org.apache.ibatis.parsing.GenericTokenParser.parse(GenericTokenParser.java:29)
at
org.apache.ibatis.builder.xml.dynamic.ForEachSqlNode$FilteredDynamicContext.appendSql(ForEachSqlNode.java:121)
at
org.apache.ibatis.builder.xml.dynamic.TextSqlNode.apply(TextSqlNode.java:18)
at
org.apache.ibatis.builder.xml.dynamic.MixedSqlNode.apply(MixedSqlNode.java:14)
at
org.apache.ibatis.builder.xml.dynamic.ForEachSqlNode.apply(ForEachSqlNode.java:51)
at
org.apache.ibatis.builder.xml.dynamic.MixedSqlNode.apply(MixedSqlNode.java:14)
at
org.apache.ibatis.builder.xml.dynamic.DynamicSqlSource.getBoundSql(DynamicSqlSource.java:22)
at
org.apache.ibatis.mapping.MappedStatement.getBoundSql(MappedStatement.java:198)
at
org.apache.ibatis.executor.statement.BaseStatementHandler.<init>(BaseStatementHandler.java:45)
at
org.apache.ibatis.executor.statement.PreparedStatementHandler.<init>(PreparedStatementHandler.java:16)
at
org.apache.ibatis.executor.statement.RoutingStatementHandler.<init>(RoutingStatementHandler.java:27)
at
org.apache.ibatis.session.Configuration.newStatementHandler(Configuration.java:192)
at
org.apache.ibatis.executor.SimpleExecutor.doUpdate(SimpleExecutor.java:27)
at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:65)
at
org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:39)
at
org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:93)
... 26 more

This occurred when I didn't specify the item field in my <foreach> tag. Once
I specify item="something" then the NPE goes away. Changing the statement
within the <foreach> did not seem to effect this. Bug?
--
View this message in context: http://old.nabble.com/Null-Pointer-Exception-on-Malformed-%3Cforeach%3E-tp26779961p26779961.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

AW: logging sql statements

2009-12-14T17:29:14Z

I haven't found any documentation either, but had to refer to the source code to find usages of Loggers.
This log category can be valuable, too:
<category name="com.ibatis" additivity="false">
<priority value="debug"/>
</category>

-----Ursprüngliche Nachricht-----
Von: Rick.Wellman [mailto:Rick.Wellman@...]
Gesendet: Dienstag, 15. Dezember 2009 00:56
An: user-java@...
Betreff: RE: logging sql statements

iBatis relies on logging of the underlying JDBC statements which is documented (somewhere).
We use the following settings in our log4j.xml file, adjust to your liking:

<category name="java.sql">
<priority value="info" />
</category>

<category name="java.sql.ResultSet">
<priority value="info" />
</category>

-----Original Message-----
From: Trenton D. Adams [mailto:trenta@...]
Sent: Monday, December 14, 2009 5:51 PM
To: user-java
Subject: logging sql statements

Hi Guys,

I've searched the net like crazy, and there doesn't seem to be anything reasonable describing how to have iBatis print out the parsed SQL that is being run, during an error.

Is this possible?

Currently I tried the following, to no avail...

LogFactory.selectLog4JLogging();

log4j.logger.com.ibatis=DEBUG

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

RE: logging sql statements

2009-12-14T15:55:42Z

iBatis relies on logging of the underlying JDBC statements which is documented (somewhere).
We use the following settings in our log4j.xml file, adjust to your liking:

<category name="java.sql">
<priority value="info" />
</category>

<category name="java.sql.ResultSet">
<priority value="info" />
</category>

-----Original Message-----
From: Trenton D. Adams [mailto:trenta@...]
Sent: Monday, December 14, 2009 5:51 PM
To: user-java
Subject: logging sql statements

Hi Guys,

I've searched the net like crazy, and there doesn't seem to be anything reasonable describing how to have iBatis print out the parsed SQL that is being run, during an error.

Is this possible?

Currently I tried the following, to no avail...

LogFactory.selectLog4JLogging();

log4j.logger.com.ibatis=DEBUG

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

logging sql statements

2009-12-14T15:50:56Z

Hi Guys,

I've searched the net like crazy, and there doesn't seem to be anything reasonable describing how to have iBatis print out the parsed SQL that is being run, during an error.

Is this possible?

Currently I tried the following, to no avail...

LogFactory.selectLog4JLogging();

log4j.logger.com.ibatis=DEBUG

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Null Pointer Exception on Malformed

2009-12-14T11:06:42Z

Hi,

I was using <foreach> in an <insert> (within a <mapper>) statement and I got the following NPE:

Caused by: java.lang.NullPointerException
at java.util.regex.Pattern.<init>(Pattern.java:1132)
at java.util.regex.Pattern.compile(Pattern.java:823)
at java.lang.String.replaceFirst(String.java:2146)
at org.apache.ibatis.builder.xml.dynamic.ForEachSqlNode$FilteredDynamicContext$1.handleToken(ForEachSqlNode.java:116)
at org.apache.ibatis.parsing.GenericTokenParser.parse(GenericTokenParser.java:29)
at org.apache.ibatis.builder.xml.dynamic.ForEachSqlNode$FilteredDynamicContext.appendSql(ForEachSqlNode.java:121)
at org.apache.ibatis.builder.xml.dynamic.TextSqlNode.apply(TextSqlNode.java:18)
at org.apache.ibatis.builder.xml.dynamic.MixedSqlNode.apply(MixedSqlNode.java:14)
at org.apache.ibatis.builder.xml.dynamic.ForEachSqlNode.apply(ForEachSqlNode.java:51)
at org.apache.ibatis.builder.xml.dynamic.MixedSqlNode.apply(MixedSqlNode.java:14)
at org.apache.ibatis.builder.xml.dynamic.DynamicSqlSource.getBoundSql(DynamicSqlSource.java:22)
at org.apache.ibatis.mapping.MappedStatement.getBoundSql(MappedStatement.java:198)
at org.apache.ibatis.executor.statement.BaseStatementHandler.<init>(BaseStatementHandler.java:45)
at org.apache.ibatis.executor.statement.PreparedStatementHandler.<init>(PreparedStatementHandler.java:16)
at org.apache.ibatis.executor.statement.RoutingStatementHandler.<init>(RoutingStatementHandler.java:27)
at org.apache.ibatis.session.Configuration.newStatementHandler(Configuration.java:192)
at org.apache.ibatis.executor.SimpleExecutor.doUpdate(SimpleExecutor.java:27)
at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:65)
at org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:39)
at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:93)
... 26 more

This occurred when I didn't specify the item field in my <foreach> tag. Once I specify item="something" then the NPE goes away. Changing the statement within the <foreach> did not seem to effect this. Bug?

RE: iterate not working

2009-12-14T06:25:58Z

The remove first prepend is intended to remove the first prepend of a sub-condition.
For exemple:
<iterate prepend="," removeFirstPrepend="true" property="name">
<isNotNull prepend="removeMe" property="name[]">
substr(upper(#name[].firstName#),1,1)||upper(#name[].lastName#)
</isNotNull>
</iterate>

What you want is:
<iterate separator="," property="name">
substr(upper(#name[].firstName#),1,1)||upper(#name[].lastName#)
</iterate>

Christian

-----Original Message-----
From: Trenton D. Adams [mailto:trenta@...]
Sent: Friday, December 11, 2009 6:32 PM
To: user-java
Subject: iterate not working

Hi Guys,

I am using 2.3.0.

I'm wondering why this does not work...
IN (
<iterate prepend="," removeFirstPrepend="true" property="name">
substr(upper(#name[].firstName#),1,1)||upper(#name[].lastName#)
</iterate>
)

But this does...
IN (''
<iterate prepend="," property="name">
substr(upper(#name[].firstName#),1,1)||upper(#name[].lastName#)
</iterate>
)

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: Beta 6 Oracle Invalid column type: getCLOB not implemented

2009-12-13T21:36:14Z

On 12/13/2009 3:26 PM, Jeff Butler wrote:
> I believe I have found and fixed the error in iBATIS. Please try
> building from SVN and let me know if the issue is resolved.

I built from head in SVN and it is working again for our application.
Thanks, I'll update the issue.

>
> Jeff Butler
>
>
> On Fri, Dec 11, 2009 at 11:10 PM, Guy Rouillier<guyr-ml1@...> wrote:
>> I've posted an update to Jira issue IBATIS-712. I can get this to fail
>> repeatedly with a simple command line program, on either Windows or Linux,
>> with either JDK 5 or JDK 6 and any Oracle driver appropriate for the JDK
>> version. We are using Oracle 10g 10.0.2.0.3.
>>
>> Please let me know what else I can do to assist in debugging this. This is
>> an obvious showstopper for us to deploy our app with iBATIS.
>>
>> Thanks.
>>
>> On 12/10/2009 1:06 PM, Guy Rouillier wrote:
>>>
>>> On 12/10/2009 12:19 PM, Jeff Butler wrote:
>>>>
>>>> JDBC 3 has always been a requirement. There was a change in this area
>>>> in ibatis but I don't recall the particulars right now. I'll need to
>>>> do a bit of research to recall.
>>>>
>>>> Hmmm works on windows but not on linux? I'd double check to make sure
>>>> that there is not an older driver sneaking into the mix on linux.
>>>
>>> I created a simple JSP in the same Tomcat context as our application, to
>>> make sure it would load the same JDBC driver as our app. Here is what I
>>> executed:
>>>
>>> <%
>>> ... get a connection
>>> DatabaseMetaData dmd = conn.getMetaData();
>>> aDriverVersion = dmd.getDriverVersion();
>>> %>
>>>
>>> <p> Driver version:<%= aDriverVersion %>
>>>
>>>
>>> On both Windows and Linux, the result is
>>>
>>> Driver version: 11.2.0.1.0
>>>
>>> Please let me know if I can help in any way to isolate this issue. Thanks.
>>>
>>>>
>>>> On 12/10/09, Guy Rouillier<guyr-ml1@...> wrote:
>>>>>
>>>>> On 12/10/2009 11:33 AM, Jeff Butler wrote:
>>>>>>
>>>>>> This method (getCLOB) is a JDBC 3 method. You must now use a driver
>>>>>> that is JDBC 3 compliant.
>>>>>
>>>>> I'm using the ojdbc6.jar driver from 11g (although our databases are
>>>>> 10g, the 11g drivers are required for JDK 6.) The Oracle JDBC FAQ says
>>>>> this about JDBC version support:
>>>>>
>>>>> Oracle 11.1.0 and 11.2.0 support:
>>>>>
>>>>> Full support for JDBC 3.0 in the JDK 1.5 drivers.
>>>>> Full support for JDBC 4.0 in the JDK 1.6 drivers with the
>>>>> exception of SQLXML which is not supported.
>>>>>
>>>>> I wouldn't think the JDBC 3 requirement was introduced between Beta 5
>>>>> and Beta 6, right? The code works fine with the Beta 5 code.
>>>>>
>>>>> The best hint I could find with some quick Googling is that getCLOB
>>>>> should not be used to retrieve a VARCHAR column. All the character
>>>>> columns in the table I supplied in the Jira issue are VARCHAR; the table
>>>>> has no CLOB columns.
>>>>>
>>>>> I'm also at a loss to figure out why everything works fine on Windows
>>>>> but fails on Linux. Same Oracle driver, same JDK version, same Tomcat
>>>>> version. Obviously, the VM is native code.
>>>>>
>>>>> Something has changed between Beta 5 and Beta 6 to cause this.
>>>>>
>>>>> Thanks.
>>>>>
>>>>>>
>>>>>> On 12/10/09, Guy Rouillier<guyr-ml1@...> wrote:
>>>>>>>
>>>>>>> I'm getting a catastrophic failure with Beta 6 that does not happen
>>>>>>> with
>>>>>>> Beta 5. I opened Jira issue IBATIS-712 for this:
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/IBATIS-712: Oracle Invalid
>>>>>>> column
>>>>>>> type: getCLOB not implemented for class
>>>>>>> oracle.jdbc.driver.T4CVarcharAccessor
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> --
>>>>>>> Guy Rouillier
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: user-java-unsubscribe@...
>>>>>>> For additional commands, e-mail: user-java-help@...
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Guy Rouillier
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: user-java-unsubscribe@...
>>>>> For additional commands, e-mail: user-java-help@...
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> Guy Rouillier
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@...
>> For additional commands, e-mail: user-java-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

--
Guy Rouillier

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: Beta 6 Oracle Invalid column type: getCLOB not implemented

2009-12-13T21:12:01Z

Yep, I think you got it Jeff. That is so odd, how both Derby and HSQLDB don't care if you use CLOB or String... regardless, it was a typo.

Thanks!

Clinton

On Sun, Dec 13, 2009 at 1:26 PM, Jeff Butler <jeffgbutler@...> wrote:

I believe I have found and fixed the error in iBATIS. Please try
building from SVN and let me know if the issue is resolved.

Jeff Butler

On Fri, Dec 11, 2009 at 11:10 PM, Guy Rouillier <guyr-ml1@...> wrote:
> I've posted an update to Jira issue IBATIS-712. I can get this to fail
> repeatedly with a simple command line program, on either Windows or Linux,
> with either JDK 5 or JDK 6 and any Oracle driver appropriate for the JDK
> version. We are using Oracle 10g 10.0.2.0.3.
>
> Please let me know what else I can do to assist in debugging this. This is
> an obvious showstopper for us to deploy our app with iBATIS.
>
> Thanks.
>
> On 12/10/2009 1:06 PM, Guy Rouillier wrote:
>>
>> On 12/10/2009 12:19 PM, Jeff Butler wrote:
>>>
>>> JDBC 3 has always been a requirement. There was a change in this area
>>> in ibatis but I don't recall the particulars right now. I'll need to
>>> do a bit of research to recall.
>>>
>>> Hmmm works on windows but not on linux? I'd double check to make sure
>>> that there is not an older driver sneaking into the mix on linux.
>>
>> I created a simple JSP in the same Tomcat context as our application, to
>> make sure it would load the same JDBC driver as our app. Here is what I
>> executed:
>>
>> <%
>> ... get a connection
>> DatabaseMetaData dmd = conn.getMetaData();
>> aDriverVersion = dmd.getDriverVersion();
>> %>
>>
>> <p> Driver version: <%= aDriverVersion %>
>>
>>
>> On both Windows and Linux, the result is
>>
>> Driver version: 11.2.0.1.0
>>
>> Please let me know if I can help in any way to isolate this issue. Thanks.
>>
>>>
>>> On 12/10/09, Guy Rouillier<guyr-ml1@...> wrote:
>>>>
>>>> On 12/10/2009 11:33 AM, Jeff Butler wrote:
>>>>>
>>>>> This method (getCLOB) is a JDBC 3 method. You must now use a driver
>>>>> that is JDBC 3 compliant.
>>>>
>>>> I'm using the ojdbc6.jar driver from 11g (although our databases are
>>>> 10g, the 11g drivers are required for JDK 6.) The Oracle JDBC FAQ says
>>>> this about JDBC version support:
>>>>
>>>> Oracle 11.1.0 and 11.2.0 support:
>>>>
>>>> Full support for JDBC 3.0 in the JDK 1.5 drivers.
>>>> Full support for JDBC 4.0 in the JDK 1.6 drivers with the
>>>> exception of SQLXML which is not supported.
>>>>
>>>> I wouldn't think the JDBC 3 requirement was introduced between Beta 5
>>>> and Beta 6, right? The code works fine with the Beta 5 code.
>>>>
>>>> The best hint I could find with some quick Googling is that getCLOB
>>>> should not be used to retrieve a VARCHAR column. All the character
>>>> columns in the table I supplied in the Jira issue are VARCHAR; the table
>>>> has no CLOB columns.
>>>>
>>>> I'm also at a loss to figure out why everything works fine on Windows
>>>> but fails on Linux. Same Oracle driver, same JDK version, same Tomcat
>>>> version. Obviously, the VM is native code.
>>>>
>>>> Something has changed between Beta 5 and Beta 6 to cause this.
>>>>
>>>> Thanks.
>>>>
>>>>>
>>>>> On 12/10/09, Guy Rouillier<guyr-ml1@...> wrote:
>>>>>>
>>>>>> I'm getting a catastrophic failure with Beta 6 that does not happen
>>>>>> with
>>>>>> Beta 5. I opened Jira issue IBATIS-712 for this:
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/IBATIS-712: Oracle Invalid
>>>>>> column
>>>>>> type: getCLOB not implemented for class
>>>>>> oracle.jdbc.driver.T4CVarcharAccessor
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> --
>>>>>> Guy Rouillier
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: user-java-unsubscribe@...
>>>>>> For additional commands, e-mail: user-java-help@...
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Guy Rouillier
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-java-unsubscribe@...
>>>> For additional commands, e-mail: user-java-help@...
>>>>
>>>>
>>>
>>
>>
>
>
> --
> Guy Rouillier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: Beta 6 Oracle Invalid column type: getCLOB not implemented

2009-12-13T12:26:09Z

I believe I have found and fixed the error in iBATIS. Please try
building from SVN and let me know if the issue is resolved.

Jeff Butler

On Fri, Dec 11, 2009 at 11:10 PM, Guy Rouillier <guyr-ml1@...> wrote:

> I've posted an update to Jira issue IBATIS-712. I can get this to fail
> repeatedly with a simple command line program, on either Windows or Linux,
> with either JDK 5 or JDK 6 and any Oracle driver appropriate for the JDK
> version. We are using Oracle 10g 10.0.2.0.3.
>
> Please let me know what else I can do to assist in debugging this. This is
> an obvious showstopper for us to deploy our app with iBATIS.
>
> Thanks.
>
> On 12/10/2009 1:06 PM, Guy Rouillier wrote:
>>
>> On 12/10/2009 12:19 PM, Jeff Butler wrote:
>>>
>>> JDBC 3 has always been a requirement. There was a change in this area
>>> in ibatis but I don't recall the particulars right now. I'll need to
>>> do a bit of research to recall.
>>>
>>> Hmmm works on windows but not on linux? I'd double check to make sure
>>> that there is not an older driver sneaking into the mix on linux.
>>
>> I created a simple JSP in the same Tomcat context as our application, to
>> make sure it would load the same JDBC driver as our app. Here is what I
>> executed:
>>
>> <%
>> ... get a connection
>> DatabaseMetaData dmd = conn.getMetaData();
>> aDriverVersion = dmd.getDriverVersion();
>> %>
>>
>> <p> Driver version: <%= aDriverVersion %>
>>
>>
>> On both Windows and Linux, the result is
>>
>> Driver version: 11.2.0.1.0
>>
>> Please let me know if I can help in any way to isolate this issue. Thanks.
>>
>>>
>>> On 12/10/09, Guy Rouillier<guyr-ml1@...> wrote:
>>>>
>>>> On 12/10/2009 11:33 AM, Jeff Butler wrote:
>>>>>
>>>>> This method (getCLOB) is a JDBC 3 method. You must now use a driver
>>>>> that is JDBC 3 compliant.
>>>>
>>>> I'm using the ojdbc6.jar driver from 11g (although our databases are
>>>> 10g, the 11g drivers are required for JDK 6.) The Oracle JDBC FAQ says
>>>> this about JDBC version support:
>>>>
>>>> Oracle 11.1.0 and 11.2.0 support:
>>>>
>>>> Full support for JDBC 3.0 in the JDK 1.5 drivers.
>>>> Full support for JDBC 4.0 in the JDK 1.6 drivers with the
>>>> exception of SQLXML which is not supported.
>>>>
>>>> I wouldn't think the JDBC 3 requirement was introduced between Beta 5
>>>> and Beta 6, right? The code works fine with the Beta 5 code.
>>>>
>>>> The best hint I could find with some quick Googling is that getCLOB
>>>> should not be used to retrieve a VARCHAR column. All the character
>>>> columns in the table I supplied in the Jira issue are VARCHAR; the table
>>>> has no CLOB columns.
>>>>
>>>> I'm also at a loss to figure out why everything works fine on Windows
>>>> but fails on Linux. Same Oracle driver, same JDK version, same Tomcat
>>>> version. Obviously, the VM is native code.
>>>>
>>>> Something has changed between Beta 5 and Beta 6 to cause this.
>>>>
>>>> Thanks.
>>>>
>>>>>
>>>>> On 12/10/09, Guy Rouillier<guyr-ml1@...> wrote:
>>>>>>
>>>>>> I'm getting a catastrophic failure with Beta 6 that does not happen
>>>>>> with
>>>>>> Beta 5. I opened Jira issue IBATIS-712 for this:
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/IBATIS-712: Oracle Invalid
>>>>>> column
>>>>>> type: getCLOB not implemented for class
>>>>>> oracle.jdbc.driver.T4CVarcharAccessor
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> --
>>>>>> Guy Rouillier
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: user-java-unsubscribe@...
>>>>>> For additional commands, e-mail: user-java-help@...
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Guy Rouillier
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-java-unsubscribe@...
>>>> For additional commands, e-mail: user-java-help@...
>>>>
>>>>
>>>
>>
>>
>
>
> --
> Guy Rouillier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Re: Ibator and Microsoft Access

2009-12-12T10:44:06Z

Yes, the jdbc-odbc bridge is not really intended for real use, and
sucks pretty bad.

Without knowing why you are using access, it's hard to recommend a
course of action - if you can use a different DB, by all means, do.
Access is hands down the crappiest choice you could make. :)

If you are using it because you have to (it's tied to another system
that uses access directly), then you may need to look for a commercial
driver. The jdbc-odbc bridge will not work.

If you are creating a new system, then look at postgresql, mysql, or derby.

Larry

On Sat, Dec 12, 2009 at 9:32 AM, Monky <promiller@...> wrote:

>
> Hello,
> I am having problems using Ibatis/Ibator (ibatis-2.3.4.726 and the latest
> ibator as eclipse plugin installed via
> http://ibatis.apache.org/tools/ibator) with a connection to Microsoft
> Access.
> When I use the Ibator eclipse Plugin to "Generate iBatis Artifacts" many
> things get generated properly but I get the warnings:
> "Generation Warnings Occured
> Cannot obtain primary key information from the database, generated objects
> may be incomplete"
> The second line appears once for every table.
>
> I use the standard driver:
> Driver: sun.jdbc.odbc.JdbcOdbcDriver
> URL: jdbc:odbc:DRIVER={Microsoft Access Driver
> (*.mdb)};DBQ=[ABSOLUTE_PATH_TO_MY_DB_FILE];DriverID=22
>
> I guess the sun JDBC-ODBC-Bridge does not fully support table meta data for
> Mircosoft Access. Am I supposing correct?
> Is there another (free) driver that could be used?
> Is there a way to tell iBator about primary keys manually? (Something like:
> every table has a "PKEY" column that is a integer auto increment primary key
> field)
>
> Any help appretiates.
> Regards,
> Sebastian
> --
> View this message in context: http://old.nabble.com/Ibator-and-Microsoft-Access-tp26758969p26758969.html
> Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-java-unsubscribe@...
> For additional commands, e-mail: user-java-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@...
For additional commands, e-mail: user-java-help@...

Ibator and Microsoft Access

2009-12-12T08:32:17Z

Hello,
I am having problems using Ibatis/Ibator (ibatis-2.3.4.726 and the latest ibator as eclipse plugin installed via http://ibatis.apache.org/tools/ibator) with a connection to Microsoft Access.
When I use the Ibator eclipse Plugin to "Generate iBatis Artifacts" many things get generated properly but I get the warnings:
"Generation Warnings Occured
Cannot obtain primary key information from the database, generated objects may be incomplete"
The second line appears once for every table.

I use the standard driver:
Driver: sun.jdbc.odbc.JdbcOdbcDriver
URL: jdbc:odbc:DRIVER={Microsoft Access Driver (*.mdb)};DBQ=[ABSOLUTE_PATH_TO_MY_DB_FILE];DriverID=22

I guess the sun JDBC-ODBC-Bridge does not fully support table meta data for Mircosoft Access. Am I supposing correct?
Is there another (free) driver that could be used?
Is there a way to tell iBator about primary keys manually? (Something like: every table has a "PKEY" column that is a integer auto increment primary key field)

Any help appretiates.
Regards,
Sebastian