Has anyone noticed in your struts application that when you call an oracle
stored procedure and register an output parameter of type OracleTypes.CURSOR
and that function call fails for any reason, any values you may have set in the
oracle session will be lost?
In our application we typically call a stored procedure at app login which sets
the following session variables:
USER_ID
SESSION_ID
LANGUAGE_CODE
TERRITORY_CODE
Then whenever our application calls stored procedures we've written, it simply
uses these variables in where-conditions to limit the data based on the user's
identifiy such as:
WHERE RECORD_USER_ID = FND_PROFILE.VALUE('USER_ID') ...
Anyways, when a SQLException is thrown and caught by the ExceptionHandler,
we've checked the database session variables immediately after the exception
and they're no longer set. I've found that this only happens when an exception
occurs with any call which utilizes the oracle.jdbc.OracleTypes.XXXX classes.
If our calls simply use the java.sql.Types.XXXX classes, this isn't an issue.
Any ideas?
_______________________________________________________
Chris Cranford
Programmer/Developer
SETECH Inc. & Companies
6302 Fairview Rd, Suite 201, Charlotte, NC 28210
Phone: (704) 362-9423, Fax: (704) 362-9409, Mobile: (704) 650-1042
Email: [EMAIL PROTECTED]
