You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by Elmer Smith <es...@venterraliving.com> on 2009/03/09 19:18:27 UTC
ibator context menu in eclipse 3.4 missing
Hi,
Is there still a context menu in eclipse 3.4 for the ibator plug-in? I
am migrating from 3.2 to 3.4 eclipse, and when I right click the config
file, I no longer get an ibator menu option?
Thanks,
Elmer
This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if an electronic communication.
Re: OutOfMemoryError
Posted by Sundar Sankar <fa...@gmail.com>.
I have had OOM, when there was too much of data being retrieved by Ibatis.
with 2000+ statements, I see that as one of the possibility. My heap was
holding up for X amount of data, and I had a hack to loop it when more than
X was there. Increasing the heap helped me too.
-Sundar
On Wed, Mar 11, 2009 at 12:41 AM, Kengkaj Sathianpantarit <
kengkaj.s@gmail.com> wrote:
> Try to increase java heap space by using -Xmx option.
>
> Best Regards,
> Kengkaj
> email: kengkaj.s at gmail dot com
>
>
> On Tue, Mar 10, 2009 at 7:30 PM, Ben Shory <be...@sapiens.com> wrote:
>
>> Hi,
>> I have ~2000 statements spread over a few hundreds of sqlmap.xml
>> As soon as I init the SqlMapClient I get:
>>
>> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
>> at java.util.Arrays.copyOfRange(Arrays.java:3209)
>> at java.lang.String.<init>(String.java:216)
>> at
>> com.sun.org.apache.xerces.internal.xni.XMLString.toString(XMLString.java
>> :185)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanElementDec
>> l(XMLDTDScannerImpl.java:908)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDecls(XMLD
>> TDScannerImpl.java:1980)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDTDExterna
>> lSubset(XMLDTDScannerImpl.java:320)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver
>> .dispatch(XMLDocumentScannerImpl.java:1201)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver
>> .next(XMLDocumentScannerImpl.java:1089)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDri
>> ver.next(XMLDocumentScannerImpl.java:1002)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLD
>> ocumentScannerImpl.java:648)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.s
>> canDocument(XMLDocumentFragmentScannerImpl.java:510)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
>> 1Configuration.java:807)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
>> 1Configuration.java:737)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.jav
>> a:107)
>> at
>> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.jav
>> a:225)
>> at
>> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Docume
>> ntBuilderImpl.java:283)
>> at
>> com.ibatis.common.xml.NodeletParser.createDocument(NodeletParser.java:18
>> 9)
>> at
>> com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:59)
>> at
>> com.ibatis.sqlmap.engine.builder.xml.SqlMapParser.parse(SqlMapParser.jav
>> a:44)
>> at
>> com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser$10.process(SqlMa
>> pConfigParser.java:279)
>> at
>> com.ibatis.common.xml.NodeletParser.processNodelet(NodeletParser.java:12
>> 1)
>> at
>> com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:84)
>> at
>> com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:102)
>> at
>> com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:72)
>> at
>> com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:60)
>> at
>> com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser.parse(SqlMapConf
>> igParser.java:71)
>> at
>> com.ibatis.sqlmap.client.SqlMapClientBuilder.buildSqlMapClient(SqlMapCli
>> entBuilder.java:90)
>> at com.sapiens.ri.util.Test.main(Test.java:24)
>>
>> Any thoughts?
>>
>> BTW I don't need all of the statements all of the time, is there some
>> kind of lazy init?
>>
>>
>
Re: OutOfMemoryError
Posted by Kengkaj Sathianpantarit <ke...@gmail.com>.
Try to increase java heap space by using -Xmx option.
Best Regards,
Kengkaj
email: kengkaj.s at gmail dot com
On Tue, Mar 10, 2009 at 7:30 PM, Ben Shory <be...@sapiens.com> wrote:
> Hi,
> I have ~2000 statements spread over a few hundreds of sqlmap.xml
> As soon as I init the SqlMapClient I get:
>
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOfRange(Arrays.java:3209)
> at java.lang.String.<init>(String.java:216)
> at
> com.sun.org.apache.xerces.internal.xni.XMLString.toString(XMLString.java
> :185)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanElementDec
> l(XMLDTDScannerImpl.java:908)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDecls(XMLD
> TDScannerImpl.java:1980)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDTDExterna
> lSubset(XMLDTDScannerImpl.java:320)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver
> .dispatch(XMLDocumentScannerImpl.java:1201)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver
> .next(XMLDocumentScannerImpl.java:1089)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDri
> ver.next(XMLDocumentScannerImpl.java:1002)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLD
> ocumentScannerImpl.java:648)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.s
> canDocument(XMLDocumentFragmentScannerImpl.java:510)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
> 1Configuration.java:807)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
> 1Configuration.java:737)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.jav
> a:107)
> at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.jav
> a:225)
> at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Docume
> ntBuilderImpl.java:283)
> at
> com.ibatis.common.xml.NodeletParser.createDocument(NodeletParser.java:18
> 9)
> at
> com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:59)
> at
> com.ibatis.sqlmap.engine.builder.xml.SqlMapParser.parse(SqlMapParser.jav
> a:44)
> at
> com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser$10.process(SqlMa
> pConfigParser.java:279)
> at
> com.ibatis.common.xml.NodeletParser.processNodelet(NodeletParser.java:12
> 1)
> at
> com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:84)
> at
> com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:102)
> at
> com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:72)
> at
> com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:60)
> at
> com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser.parse(SqlMapConf
> igParser.java:71)
> at
> com.ibatis.sqlmap.client.SqlMapClientBuilder.buildSqlMapClient(SqlMapCli
> entBuilder.java:90)
> at com.sapiens.ri.util.Test.main(Test.java:24)
>
> Any thoughts?
>
> BTW I don't need all of the statements all of the time, is there some
> kind of lazy init?
>
>
OutOfMemoryError
Posted by Ben Shory <be...@sapiens.com>.
Hi,
I have ~2000 statements spread over a few hundreds of sqlmap.xml
As soon as I init the SqlMapClient I get:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOfRange(Arrays.java:3209)
at java.lang.String.<init>(String.java:216)
at
com.sun.org.apache.xerces.internal.xni.XMLString.toString(XMLString.java
:185)
at
com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanElementDec
l(XMLDTDScannerImpl.java:908)
at
com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDecls(XMLD
TDScannerImpl.java:1980)
at
com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.scanDTDExterna
lSubset(XMLDTDScannerImpl.java:320)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver
.dispatch(XMLDocumentScannerImpl.java:1201)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver
.next(XMLDocumentScannerImpl.java:1089)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDri
ver.next(XMLDocumentScannerImpl.java:1002)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLD
ocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.s
canDocument(XMLDocumentFragmentScannerImpl.java:510)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
1Configuration.java:807)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
1Configuration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.jav
a:107)
at
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.jav
a:225)
at
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Docume
ntBuilderImpl.java:283)
at
com.ibatis.common.xml.NodeletParser.createDocument(NodeletParser.java:18
9)
at
com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:59)
at
com.ibatis.sqlmap.engine.builder.xml.SqlMapParser.parse(SqlMapParser.jav
a:44)
at
com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser$10.process(SqlMa
pConfigParser.java:279)
at
com.ibatis.common.xml.NodeletParser.processNodelet(NodeletParser.java:12
1)
at
com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:84)
at
com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:102)
at
com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:72)
at
com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:60)
at
com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser.parse(SqlMapConf
igParser.java:71)
at
com.ibatis.sqlmap.client.SqlMapClientBuilder.buildSqlMapClient(SqlMapCli
entBuilder.java:90)
at com.sapiens.ri.util.Test.main(Test.java:24)
Any thoughts?
BTW I don't need all of the statements all of the time, is there some
kind of lazy init?
RE: ibator context menu in eclipse 3.4 missing
Posted by Elmer Smith <es...@venterraliving.com>.
Thank you Jeff, that did the trick.
And might I add that I love iBATIS and the iBator plug-in, and both of them "kicks ass and takes names". Top notch work on both products.
Cheers,
Elmer
-----Original Message-----
From: Jeff Butler [mailto:jeffgbutler@gmail.com]
Sent: Monday, March 09, 2009 3:01 PM
To: user-java@ibatis.apache.org
Subject: Re: ibator context menu in eclipse 3.4 missing
The DOCTYPE is wrong. It still has some Abator stuff in it. Copy the
correct DOCTYPE from here:
http://ibatis.apache.org/docs/tools/ibator/migratingFromAbator.html
Jeff Butler
On Mon, Mar 9, 2009 at 1:56 PM, Elmer Smith <es...@venterraliving.com> wrote:
> Thanks Jeff. I checked and it seems like the file is in the right format:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE abatorConfiguration
> PUBLIC "-//Apache Software Foundation//DTD Abator for iBATIS Configuration 1.0//EN"
> "http://ibatis.apache.org/dtd/ibator-config_1_0.dtd">
>
> <ibatorConfiguration>
>
> <classPathEntry location="${ibator.database.driver.path}" />
>
> <ibatorContext id="chorus" targetRuntime="Ibatis2Java5">
> <jdbcConnection
> driverClass="net.sourceforge.jtds.jdbc.Driver"
> connectionURL="jdbc:jtds:sqlserver://${ibator.chorus.dburl}"
> userId="${ibator.chorus.dbuser}" password="${ibator.chorus.dbpassword}">
> </jdbcConnection>
>
> <javaModelGenerator
> targetPackage="com.ocs.businesslogic.dataobjects"
> targetProject="chorus\src\java">
> <property name="enableSubPackages" value="true" />
> <property name="trimStrings" value="true" />
> <property name="rootClass" value="com.ocs.businesslogic.dataobjects.DataObjectBase" />
> </javaModelGenerator>
>
> <sqlMapGenerator targetPackage="com.ocs.businesslogic.sqlmap"
> targetProject="chorus\src\resources">
> <property name="enableSubPackages" value="true" />
> </sqlMapGenerator>
>
> <daoGenerator type="SPRING"
> targetPackage="com.ocs.businesslogic.dao"
> targetProject="chorus\src\java">
> <property name="enableSubPackages" value="true" />
> </daoGenerator>
>
> <table tableName="application" catalog="chorus">
> <generatedKey column="application_id"
> sqlStatement="select ident_current('application')" identity="true" />
> </table>
>
> </ibatorContext>
> </ibatorConfiguration>
>
>
> I migrated from 3.2 to 3.4, but after didn't see the abator plug in. I added the site through the Help menu, and it seemed to work (Software Updates shows Ibator Version 1.2).
>
> I'm not too sure what to check next.
>
>
>
> -----Original Message-----
> From: Jeff Butler [mailto:jeffgbutler@gmail.com]
> Sent: Monday, March 09, 2009 2:38 PM
> To: user-java@ibatis.apache.org
> Subject: Re: ibator context menu in eclipse 3.4 missing
>
> Yes there is. Make sure you are using Ibator - not Abator. Also,
> make sure that you've migrated any Abator config files to the new
> Ibator format. Ibator will not process or show a context menu for any
> Abator configuration files.
>
> Jeff Butler
>
>
> On Mon, Mar 9, 2009 at 1:18 PM, Elmer Smith <es...@venterraliving.com> wrote:
>> Hi,
>>
>>
>>
>> Is there still a context menu in eclipse 3.4 for the ibator plug-in? I am
>> migrating from 3.2 to 3.4 eclipse, and when I right click the config file, I
>> no longer get an ibator menu option?
>>
>>
>>
>> Thanks,
>>
>> Elmer
>>
>> This message (including any attachments) is intended only for the use of the
>> individual or entity to whom it is addressed and may contain information
>> that is non-public, proprietary, privileged, confidential, and exempt from
>> disclosure under applicable law or may constitute attorney work product. If
>> you are not the intended recipient, you are hereby notified that any use,
>> dissemination, distribution, or copying of this communication is strictly
>> prohibited. If you have received this communication in error, please notify
>> us immediately by telephone and (i) destroy this message if a facsimile or
>> (ii) delete this message immediately if an electronic communication.
>
> This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if an electronic communication.
>
>
This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if an electronic communication.
Re: ibator context menu in eclipse 3.4 missing
Posted by Jeff Butler <je...@gmail.com>.
The DOCTYPE is wrong. It still has some Abator stuff in it. Copy the
correct DOCTYPE from here:
http://ibatis.apache.org/docs/tools/ibator/migratingFromAbator.html
Jeff Butler
On Mon, Mar 9, 2009 at 1:56 PM, Elmer Smith <es...@venterraliving.com> wrote:
> Thanks Jeff. I checked and it seems like the file is in the right format:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE abatorConfiguration
> PUBLIC "-//Apache Software Foundation//DTD Abator for iBATIS Configuration 1.0//EN"
> "http://ibatis.apache.org/dtd/ibator-config_1_0.dtd">
>
> <ibatorConfiguration>
>
> <classPathEntry location="${ibator.database.driver.path}" />
>
> <ibatorContext id="chorus" targetRuntime="Ibatis2Java5">
> <jdbcConnection
> driverClass="net.sourceforge.jtds.jdbc.Driver"
> connectionURL="jdbc:jtds:sqlserver://${ibator.chorus.dburl}"
> userId="${ibator.chorus.dbuser}" password="${ibator.chorus.dbpassword}">
> </jdbcConnection>
>
> <javaModelGenerator
> targetPackage="com.ocs.businesslogic.dataobjects"
> targetProject="chorus\src\java">
> <property name="enableSubPackages" value="true" />
> <property name="trimStrings" value="true" />
> <property name="rootClass" value="com.ocs.businesslogic.dataobjects.DataObjectBase" />
> </javaModelGenerator>
>
> <sqlMapGenerator targetPackage="com.ocs.businesslogic.sqlmap"
> targetProject="chorus\src\resources">
> <property name="enableSubPackages" value="true" />
> </sqlMapGenerator>
>
> <daoGenerator type="SPRING"
> targetPackage="com.ocs.businesslogic.dao"
> targetProject="chorus\src\java">
> <property name="enableSubPackages" value="true" />
> </daoGenerator>
>
> <table tableName="application" catalog="chorus">
> <generatedKey column="application_id"
> sqlStatement="select ident_current('application')" identity="true" />
> </table>
>
> </ibatorContext>
> </ibatorConfiguration>
>
>
> I migrated from 3.2 to 3.4, but after didn't see the abator plug in. I added the site through the Help menu, and it seemed to work (Software Updates shows Ibator Version 1.2).
>
> I'm not too sure what to check next.
>
>
>
> -----Original Message-----
> From: Jeff Butler [mailto:jeffgbutler@gmail.com]
> Sent: Monday, March 09, 2009 2:38 PM
> To: user-java@ibatis.apache.org
> Subject: Re: ibator context menu in eclipse 3.4 missing
>
> Yes there is. Make sure you are using Ibator - not Abator. Also,
> make sure that you've migrated any Abator config files to the new
> Ibator format. Ibator will not process or show a context menu for any
> Abator configuration files.
>
> Jeff Butler
>
>
> On Mon, Mar 9, 2009 at 1:18 PM, Elmer Smith <es...@venterraliving.com> wrote:
>> Hi,
>>
>>
>>
>> Is there still a context menu in eclipse 3.4 for the ibator plug-in? I am
>> migrating from 3.2 to 3.4 eclipse, and when I right click the config file, I
>> no longer get an ibator menu option?
>>
>>
>>
>> Thanks,
>>
>> Elmer
>>
>> This message (including any attachments) is intended only for the use of the
>> individual or entity to whom it is addressed and may contain information
>> that is non-public, proprietary, privileged, confidential, and exempt from
>> disclosure under applicable law or may constitute attorney work product. If
>> you are not the intended recipient, you are hereby notified that any use,
>> dissemination, distribution, or copying of this communication is strictly
>> prohibited. If you have received this communication in error, please notify
>> us immediately by telephone and (i) destroy this message if a facsimile or
>> (ii) delete this message immediately if an electronic communication.
>
> This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if an electronic communication.
>
>
RE: ibator context menu in eclipse 3.4 missing
Posted by Elmer Smith <es...@venterraliving.com>.
Thanks Jeff. I checked and it seems like the file is in the right format:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE abatorConfiguration
PUBLIC "-//Apache Software Foundation//DTD Abator for iBATIS Configuration 1.0//EN"
"http://ibatis.apache.org/dtd/ibator-config_1_0.dtd">
<ibatorConfiguration>
<classPathEntry location="${ibator.database.driver.path}" />
<ibatorContext id="chorus" targetRuntime="Ibatis2Java5">
<jdbcConnection
driverClass="net.sourceforge.jtds.jdbc.Driver"
connectionURL="jdbc:jtds:sqlserver://${ibator.chorus.dburl}"
userId="${ibator.chorus.dbuser}" password="${ibator.chorus.dbpassword}">
</jdbcConnection>
<javaModelGenerator
targetPackage="com.ocs.businesslogic.dataobjects"
targetProject="chorus\src\java">
<property name="enableSubPackages" value="true" />
<property name="trimStrings" value="true" />
<property name="rootClass" value="com.ocs.businesslogic.dataobjects.DataObjectBase" />
</javaModelGenerator>
<sqlMapGenerator targetPackage="com.ocs.businesslogic.sqlmap"
targetProject="chorus\src\resources">
<property name="enableSubPackages" value="true" />
</sqlMapGenerator>
<daoGenerator type="SPRING"
targetPackage="com.ocs.businesslogic.dao"
targetProject="chorus\src\java">
<property name="enableSubPackages" value="true" />
</daoGenerator>
<table tableName="application" catalog="chorus">
<generatedKey column="application_id"
sqlStatement="select ident_current('application')" identity="true" />
</table>
</ibatorContext>
</ibatorConfiguration>
I migrated from 3.2 to 3.4, but after didn't see the abator plug in. I added the site through the Help menu, and it seemed to work (Software Updates shows Ibator Version 1.2).
I'm not too sure what to check next.
-----Original Message-----
From: Jeff Butler [mailto:jeffgbutler@gmail.com]
Sent: Monday, March 09, 2009 2:38 PM
To: user-java@ibatis.apache.org
Subject: Re: ibator context menu in eclipse 3.4 missing
Yes there is. Make sure you are using Ibator - not Abator. Also,
make sure that you've migrated any Abator config files to the new
Ibator format. Ibator will not process or show a context menu for any
Abator configuration files.
Jeff Butler
On Mon, Mar 9, 2009 at 1:18 PM, Elmer Smith <es...@venterraliving.com> wrote:
> Hi,
>
>
>
> Is there still a context menu in eclipse 3.4 for the ibator plug-in? I am
> migrating from 3.2 to 3.4 eclipse, and when I right click the config file, I
> no longer get an ibator menu option?
>
>
>
> Thanks,
>
> Elmer
>
> This message (including any attachments) is intended only for the use of the
> individual or entity to whom it is addressed and may contain information
> that is non-public, proprietary, privileged, confidential, and exempt from
> disclosure under applicable law or may constitute attorney work product. If
> you are not the intended recipient, you are hereby notified that any use,
> dissemination, distribution, or copying of this communication is strictly
> prohibited. If you have received this communication in error, please notify
> us immediately by telephone and (i) destroy this message if a facsimile or
> (ii) delete this message immediately if an electronic communication.
This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if an electronic communication.
Re: ibator context menu in eclipse 3.4 missing
Posted by Jeff Butler <je...@gmail.com>.
Yes there is. Make sure you are using Ibator - not Abator. Also,
make sure that you've migrated any Abator config files to the new
Ibator format. Ibator will not process or show a context menu for any
Abator configuration files.
Jeff Butler
On Mon, Mar 9, 2009 at 1:18 PM, Elmer Smith <es...@venterraliving.com> wrote:
> Hi,
>
>
>
> Is there still a context menu in eclipse 3.4 for the ibator plug-in? I am
> migrating from 3.2 to 3.4 eclipse, and when I right click the config file, I
> no longer get an ibator menu option?
>
>
>
> Thanks,
>
> Elmer
>
> This message (including any attachments) is intended only for the use of the
> individual or entity to whom it is addressed and may contain information
> that is non-public, proprietary, privileged, confidential, and exempt from
> disclosure under applicable law or may constitute attorney work product. If
> you are not the intended recipient, you are hereby notified that any use,
> dissemination, distribution, or copying of this communication is strictly
> prohibited. If you have received this communication in error, please notify
> us immediately by telephone and (i) destroy this message if a facsimile or
> (ii) delete this message immediately if an electronic communication.