Otiose Cognitions
| September 2002 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | |||||
| Aug Oct | ||||||
Where's JDO?
Riddle me this: The JDO specification (JSR 12) has been final since April 30th, 2002 and a reference implementation is available but the only page with information provided by Sun is this ugly one with a hodpog of links which doesn't even live on the standard Java site. Why isn't JDO getting the attention that all the new XML/Web Services APIs are getting? There seems to be industry acceptance of JDO as evidenced by a number of commercial implementations of the spec. The grassroots support appears to be there as well as evidenced by JDO Central. Why isn't Sun promoting their attempt at a standard, transparent persistence API? It's not like this isn't an important problem. Has someone convinced them that JDO is so bad that it should be swept under the carpet and forgotten?
9:56:01 PM
Riddle me this: The JDO specification (JSR 12) has been final since April 30th, 2002 and a reference implementation is available but the only page with information provided by Sun is this ugly one with a hodpog of links which doesn't even live on the standard Java site. Why isn't JDO getting the attention that all the new XML/Web Services APIs are getting? There seems to be industry acceptance of JDO as evidenced by a number of commercial implementations of the spec. The grassroots support appears to be there as well as evidenced by JDO Central. Why isn't Sun promoting their attempt at a standard, transparent persistence API? It's not like this isn't an important problem. Has someone convinced them that JDO is so bad that it should be swept under the carpet and forgotten?
9:56:01 PM