Some deprecated warnings are to be expected. Lets get the warnings down to
compatiblity apis and perhaps we could turn it off (let the nightly build
leave it on so we can deprecated use though).
--jason
On Tue, 11 Sep 2001, David Jencks wrote:
> <snip>
> > connector/src/main/org/jboss/resource/adapter/jdbc/local/ResultSetInPool.java
> >
>connector/src/main/org/jboss/resource/adapter/jdbc/local/PreparedStatementInPool.java
> >
> >
> >
> > These two generate deprecation warnings, because they use deprecated
> > methods of JDBC spec (namely [get|set]UnicodeStream and
> > getBigDecimal). Resolving this would require all drivers to support
> > JDBC 2.1 (am I wrong ?). I'm not quite sure wether this is
> > reasonable. Can someone give me a hint about this ? I'll investigate
> > more before correcting (if ever) and submitting patch...
> >
> I don't think we can change this, client code can call these methods: we
> can't require all client code to not use deprecated methods.
>
> david jencks
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
