误用JAVA的异常类导致数据库中的事务不回滚

@Override@Transactional("transactionManager")
publicintcreateTest(NoteBookInfonoteBookInfo) throwsException  {
intret=noteBookInfoDaoImpl.create(noteBookInfo);
if(ret==1){
thrownewException("rollback");
    }
return0;
}

@Override@Transactional("transactionManager")
publicintcreateTest(NoteBookInfonoteBookInfo) throwsRuntimeException  {
intret=noteBookInfoDaoImpl.create(noteBookInfo);
if(ret==1){
thrownewRuntimeException("rollback");
    }
return0;
}

/*** Defines zero (0) or more exception {@linkplain Class types}, which must be* subclasses of {@link Throwable}, indicating which exception types must cause* a transaction rollback.* <p>By default, a transaction will be rolled back on {@link RuntimeException}* and {@link Error} but not on checked exceptions (business exceptions). See* {@link org.springframework.transaction.interceptor.DefaultTransactionAttribute#rollbackOn(Throwable)}* for a detailed explanation.* <p>This is the preferred way to construct a rollback rule (in contrast to* {@link #rollbackForClassName}), matching the exception type and its subclasses* in a type-safe manner. See the {@linkplain Transactional class-level javadocs}* for further details on rollback rule semantics.* @see #rollbackForClassName* @see org.springframework.transaction.interceptor.RollbackRuleAttribute#RollbackRuleAttribute(Class)* @see org.springframework.transaction.interceptor.DefaultTransactionAttribute#rollbackOn(Throwable)*/Class<?extendsThrowable>[] rollbackFor() default {};