--Scott thanks - preparedStatement.unwrap() did the job for using
OraclePreparedStatement but given the JavaDoc warning about the cost of calling
unwrap() we are have to make a policy decision to only use
OraclePreparedStatement where we really need a feature such as named parameters
--
I
Alan,
while migrating from 2.1 to 3.1 we've had a similar issue and it could be
solved by explicitly using old-encoding.
Maybe you could find useful information in this thread:
http://maillist.caucho.com/pipermail/resin-interest/2009-February/003334.html
-- Steffen
-Ursprüngliche
Thanks for taking the time to make the suggestion Steffen
I had seen this thread i my research on the problem - I am trying to
find out if the old encoding is available for use when working with a
digest in the code so I can calculate both digest until all users have
migrated.
Regards
Alan
On Sep 21, 2011, at 10:38 AM, Alan Wright wrote:
Thanks for taking the time to make the suggestion Steffen
I had seen this thread i my research on the problem - I am trying to
find out if the old encoding is available for use when working with a
digest in the code so I can calculate both