temporary fix for tomcat/oracle ?
Like many people here, I have the same problem of PreparedStatement.getMetaData exception when using the Oracle jdbc with Tomcat. I notice that the same jsp page *sometimes* causes that exception, sometimes not, depending on from where I move to that page. So I guess depending on the internal state of thr RowSet, it will decide whetheer it needs the meta data or not ( who knows if this is true, besides JSC team :) ).
In my case, the function that causes the exception is RowSetDataProvider.findFirst(). After adding a call to RowSetDataProvider.cursorFirst() before the call of findFirst, I do not get that exception any more.
I am not sure if this can apply to other functions that fire the getMetaData exception. So far it happens to me only with findFirst and it seems cursorFirst fixes the problem.
Hope it can help somebody.
Vu
