Here's the solution that we chose to use.
Inside the ejbCreate() method, we added code to
* get a Connection from DriverManager
* from the Connection, get a PreparedStatement with the SQL to grab
the next sequence number from the db
("SELECT customer_seq.nextval FROM dual")
* execute the prepared statement query
* grab the sequence number out of the result set.
* close the Connection
My understanding is that most EJB containers will pool database connections.
So even thought the bean thinks it's opening and closing database
connections, those connections are actually pooled. So, in effect, we use
the connection just to get a PreparedStatement that gives us the ability to
perform our own custom queries from inside the Entity bean using its
database pool.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
