>> Is this okay? Does anyone think we really need to be able to compile >> on older JDKs? Is there any good workaround for this that I havn't >> thought of? > >The ParameterMetaData interface doesn't reference any other object types, >JDK 1.4 or otherwise, so couldn't a definition of the interface be supplied >with Hibernate as an optional item, that developers can install if they need >it? (If that would work.) That seems cleaner to me than having to comment >out lines.
Yeah thats a better approach I guess. But actually I ended up chucking out the PreparedStatement wapper alltogether. I went back to the old design of getPreparedStatement/closePreparedStatement. Anyway the new caching algorithm is a big improvement but I don't want to expend too much more effort in that direction. It would be silly when C3P0 already does all that.... >BTW, I'm still working with JDK 1.3.1 myself (since that's what my clients >are at). We don't take kindly to them newfangled JDKs... ;) Yeah, we are IBM-centric at work so I'm using JDK1.3 most of the time (just not usually for Hibernate). ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
