Frank, > There may be a requirement to make the SDO project itself 1.4 > compliant. If so we need to fix a few places in the code that are > currently using generics, etc., and then do this in the SDO pom files > as well. You haven't been changing any of the SDO code to make it more > 1.5 dependent, have you?
No, but I want to REALLY REALLY bad... :-) Java 5 is SOOO much nicer. Getting typed collections from the data layers would make life SOOO much better. I'd love to see a Java 5 "extension" to the spec that is basically the exact same API's, just with all the collections typed. That said, I've been completely ignoring the SDO project right now. I'm still trying to get my head around all the sca stuff. As long as the SDO stuff doesn't break, I've been ignoring it. (although I kind of want to look at the tools to make it generate code that is warning free and at least comes close to the style guidelines. The only warnings I have left in sca/model are in the generated code.) That said, the SDO project could probably change over. There are a few things in the sdo-api package that would need some changing, but those are minor. There are only a few Java 5-isms in the sdo-impl package, none in the sdo-plugin (which I should probably do the same thing as 132), and none in sdo-tools. Basically, if you really want to change SDO to JDK 1.4, I could get a patch to you tomorrow. SCA is a completely different story. The sca-api jar cannot be built with "source=1.4". Thus, it's nearly pointless to even think about it. The spec jar itself wouldn't be loadable into a 1.4 JDK. Enjoy! -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED]
