I added the PDF dates because there was a fair amount of confusion about which version of the PDF was actually current. I think it's a good idea because the documentation changes so frequently, but is so rarely published. But I'm not dogmatic about it. My main thing is that I'd like it to be cl
Nah, #1 I've uploaded the DTDs now#2 Let's fix it. That's what Betas are for. :-) Only the build
number will change, and only the manifest files use that particular
version number, so no biggie. I've updated the build script so that it uses the same build number for
the filename as the manifest
Heh, calling employeeDao.delete(...) seems explicit to me. ;-)It also lets me make them extend a common base dao that does all the work for me:===public class CrudDaoImpl extends SqlMapClientTemplate
implements CrudDao { protected String namespace; Logger log = Logger.getLogger(CrudDaoImpl.c
+1 for beta (woo hoo!)
Issues I've noticed so far:
1. The new DTDs did not get copied to the web site
2. The version number in version.properties did not get updated, so the JARs are still tagged as version 2.1.7
3. The update dates for the PDFs did not get updated on the web page
I can deal
That will teach you for not naming your methods explicitly. Delete? Delete what? ;-)Good point though Larry. If you design your DAOs to be very small and follow some convention like select, insert, update, deleteyou might have this problem. As a more general solution, I'd suggest just choos
+1 with a warning to upgraders that almost got me.If you have a class defined like this:public class MyDaoImpl extends SqlMapDaoTemplate implements MyDao...and a method like this:public void delete (String key)
It won't compile until you rename your delete because it thinks you are trying to overri
+1 for 2.2.0 beta ;-)
Regards,
Sven
Clinton Begin wrote:
PMC Members,
You've no doubt seen the 2.2.0 beta release email. Unless you find any
significant problems with the build, please now vote for iBATIS for Java
2.2.0 to be promoted to General Availabilty status.
This vote will close Frida
On 8/16/06, Clinton Begin <[EMAIL PROTECTED]> wrote:
This vote will close Friday, August 18th.
Hmmm, a quality vote never really "closes". If we find an issue with
the build next week, or next month, or next year, we can change our
votes and downgrade the quality.
The convention is to wait 72
PMC Members, You've no doubt seen the 2.2.0 beta release email. Unless you find any significant problems with the build, please now vote for iBATIS for Java 2.2.0 to be promoted to General Availabilty status.
This vote will close Friday, August 18th.Best regards,Clinton
