title: Why is default isolation level of every method (of a spring batch job) for a spring integration and batch transaction set to SERIALIZABLE?
body: <p>I have a spring integration + batch application.</p>
  
  <p>The integration is used to read a file with a inboun channel adapter and call a batch job.
  The jobRepository is defined from :
  org.springframework.batch.core.repository.support.JobRepositoryFactoryBean</p>
  
  <p>The transaction manager is org.springframework.orm.jpa.JpaTransactionManager.</p>
  
  <p>When the application starts I don't know why but I read this strange kind of configuration:</p>
  
  <pre><code>[5860] [2012-03-12 17:40:47,267] D [main] [org.springframework.transaction.interceptor.NameMatchTransactionAttributeSource] Adding transactional method [*] with attribute [PROPAGATION_REQUIRED,ISOLATION_DEFAULT]
  [5860] [2012-03-12 17:40:47,267] D [main] [org.springframework.transaction.interceptor.NameMatchTransactionAttributeSource] Adding transactional method [create*] with attribute [PROPAGATION_REQUIRES_NEW,ISOLATION_SERIALIZABLE]
  [5860] [2012-03-12 17:40:47,267] D [main] [org.springframework.transaction.interceptor.NameMatchTransactionAttributeSource] Adding transactional method [getLastJobExecution*] with attribute [PROPAGATION_REQUIRES_NEW,ISOLATION_SERIALIZABLE]
  </code></pre>
  
  <p>It seems that for default every jobmethod is configured with isolation SERIALIZABLE, but I didn't set it nowhere.
  Any idea how to set the default isolation level as ISOLATION_DEFAULT?</p>