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:[email protected]] Sent: Monday, March 09, 2009 3:01 PM To: [email protected] 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 <[email protected]> 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:[email protected]] > Sent: Monday, March 09, 2009 2:38 PM > To: [email protected] > 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 <[email protected]> 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.
