Re: possible JDBC 4 EOD bug??

2006-09-18 Thread Vemund Ostgaard
Daniel John Debrunner wrote: My understanding was that this would be fixed by 6460994, which went into b97. Is there a link for that bug? It's not found at: http://bugs.sun.com/bugdatabase/index.jsp I'm not sure why its not visible there. Anyway, it seems that bug is not relevant to

Re: possible JDBC 4 EOD bug??

2006-09-15 Thread Vemund Ostgaard
Daniel John Debrunner wrote: I'm trying to understand the expected behaviour of the assignment of columns from an EOD SQL @Select to a data class using JavaBeans style property accessors. I'm looking at section 19.1.5 User Class of JDBC 4.0. I have a class similar to the example but a little

Re: possible JDBC 4 EOD bug??

2006-09-15 Thread Daniel John Debrunner
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

Re: possible JDBC 4 EOD bug??

2006-09-15 Thread 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:

Re: possible JDBC 4 EOD bug??

2006-09-15 Thread Daniel John Debrunner
Lance J. Andersen wrote: 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. I think if the functionality is working then the spec is fine, I only got confused by the

Re: possible JDBC 4 EOD bug??

2006-09-15 Thread Vemund Ostgaard
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

Re: possible JDBC 4 EOD bug??

2006-09-15 Thread Daniel John Debrunner
Vemund Ostgaard wrote: My understanding was that this would be fixed by 6460994, which went into b97. Is there a link for that bug? It's not found at: http://bugs.sun.com/bugdatabase/index.jsp Google shows nothing obvious for it. Thanks, Dan.

Re: possible JDBC 4 EOD bug??

2006-09-15 Thread Daniel John Debrunner
Daniel John Debrunner wrote: Lance J. Andersen wrote: 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. I think if the functionality is working then the spec is

Re: possible JDBC 4 EOD bug??

2006-09-15 Thread Lance J. Andersen
Daniel John Debrunner wrote: Daniel John Debrunner wrote: Lance J. Andersen wrote: 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.

possible JDBC 4 EOD bug??

2006-09-14 Thread Daniel John Debrunner
I'm trying to understand the expected behaviour of the assignment of columns from an EOD SQL @Select to a data class using JavaBeans style property accessors. I'm looking at section 19.1.5 User Class of JDBC 4.0. I have a class similar to the example but a little different. The difference is the