Re: possible JDBC 4 EOD bug??

[Lance J. Andersen]

It is definitely a bug Dan if it has not been resolved. If you feel the section in the spec could be clearer, please let me know as i have a small window to clarify this area. -lance Daniel John Debrunner wrote: Vemund Ostgaard wrote: Daniel John Debrunner wrote: If my select returns a column called 'NAME' then it does not map to the JavaBean property called 'name'. Instead the name of the column needs to map to the name of the private field, 'myName'. Then the field is set correctly but the setter is never used. Is this a bug, it seems like it? If I understand you correctly, I believe it is a known bug that I stumbled on myself a while ago. I thought it had been fixed in one of the latest Mustang builds but I haven't verified it myself. Which build have you been using? Thanks, the description was a bit rushed because I had ony a little time before I needed to leave and I wanted to get the question out there. Do you have the bug number for the issue? I'm using b98. Thanks, Dan.