Hi Dhanji,
thanks for your quick response! I added the servlet-api.jar and
therefore got rid of the exception.
But now I have another problem: warp-persist behaves like
UnitOfWork.TRANSACTION.
I have several DAOs which each have several @Transactional methods and
I'm doing roughly the following:
BackupJob job = backupJobDao.load(1000);
List<DataObjectRevision> dataObjectRevisions =
dataObjectRevisionDao.forBackupJobAndFetchDataObjects(job);
logger.info("Got "+dataObjectRevisions.size()+" DataObjectRevisions");
Client targetNode = clientDao.getClientByName("ngbs-dev-vault1");
logger.info("Got client "+targetNode);
And I'm getting the following log output, which indicated that
Hibernate opens a new transaction (and session?) for each
@Transactional method.
10:00:38,656 DEBUG JDBCTransaction: begin
10:00:38,657 DEBUG JDBCTransaction: current autocommit status: false
10:00:38,766 DEBUG JDBCTransaction: commit
10:00:38,778 DEBUG JDBCTransaction: committed JDBC Connection
10:00:38,783 DEBUG JDBCTransaction: begin
10:00:38,783 DEBUG JDBCTransaction: current autocommit status: false
10:00:39,604 DEBUG JDBCTransaction: commit
10:00:39,660 DEBUG JDBCTransaction: committed JDBC Connection
10:00:39,662 INFO NgbsServerDaemonImpl$2: Got 154 DataObjectRevisions
10:00:39,665 DEBUG JDBCTransaction: begin
10:00:39,666 DEBUG JDBCTransaction: current autocommit status: false
10:00:39,674 DEBUG JDBCTransaction: commit
10:00:39,676 DEBUG JDBCTransaction: committed JDBC Connection
10:00:39,676 INFO NgbsServerDaemonImpl$2: Got client PhysicalNode
(id=114, name=ngbs-dev-vault1, address=172.22.195.45, metaNode=null)
10:00:39,677 INFO JobControllerFactoryImpl: Trying to save job
10:00:39,678 DEBUG JDBCTransaction: begin
10:00:39,678 DEBUG JDBCTransaction: current autocommit status: false
10:00:39,688 DEBUG JDBCTransaction: commit
As I'm new to Guice and warp-persist maybe I'm missing anything...?
It would be great if you could give me some hint about what I'm doing
wrong here.
Thanks,
Michael