Quote:
can I use the same datasource for existing JDBC code and the new code which we are trying to build using hibernate.
In my opinion there should be no problem.
In order to gain the datasource in hibernate you must let register it with JNDI.
You may to have adjust the pool-size of your datasource configuration,
if there in future are coming connection requests over hibernate too.
Further thing to consider is to avoid lock-situations between the objects you access
with hibernate as well as with JDBC directly.
On the other hand if you choose for optimistic locking (and versioning) in hibernate,
then you must also check for version attribute manuall when you modify them with JDBC directly.
Best would be that the objects you access with Hibernate are not correlated to the objects you access with JDBC directly.
Quote:
We will not be able to create a new datasource specifically for hibernate.
Why not?
In most application servers there is possible to configure more than one datasource.
I think that should also be possible in websphere application server, is'nt it?