That issue should be fixed in Spring 3.0.1 (https://jira.springframework.org/browse/SPR-5652)
Type: Posts; User: rkettelerij; Keyword(s):
That issue should be fixed in Spring 3.0.1 (https://jira.springframework.org/browse/SPR-5652)
One option I see is: You can make your JAX-WS SEI (service endpoint interface) Spring aware by having it extend SpringBeanAutowiringSupport.
Then you can inject an intermediate service into your...
Dear community,
Some of you may be familiar with Apache Camel, which is an open source integration framework based on enterprise integration patterns. In that case you may be interested to learn...
This question isn't related to Spring Batch. Quartz support is a core part of Spring so this topic should be moved to the Core Container forum.
Concerning your question; running Quartz inside a...
Do you schedule your second job inside a transaction? Quartz requires that all interaction with the scheduler happens within a transaction (as described in both Spring and Quartz javadocs). Using the...
*kick*
Lucas, just wanting to let you know that the issue described above isn't related to Spring Batch. The problem was that items on the queue were - in case of failure - not part of rollback....
wordywordy probably wonders if Spring Batch will support Java 1.4. Looking at the roadmap in Jira for release 2.0, i'll assume it's Java 5 only (like Spring Intergration).
Issue 2850 is fixed in Spring 2.5.5. The problem is your using MethodInvokingJobDetailFactoryBean together with a persistent jobstore. This is not supported, from the JavaDoc...
Thanks for your quick response.
We're using JtaTransactionManager (actually Oc4jJtaTransactionManager) and CMT combined with a XA datasource. Therefore I don't understand why you suggest turning...
I have a job that reads items from a file, performs some business logic and then writes the resulting items (one by one) to a queue (with JMS). Items are then picked up by a message driven bean for...
Congratulations on this release! Spring Batch is becoming more mature every day. Since I started using Spring Batch two months ago both the codebase and the documentation underwent significant...
Currently I have a job consisting of a single step that processes a single input file which is provided through the job's parameters (and in turn through a StepExecutionResourceProxy which is passed...
The framework should handle this when you implement a restartable job. The reference docs describe how to make a job and a step restartable.
Like I said, there's a property:
<bean id="myJobRepository" class="org.springframework.batch.core.repository.support.JobRepositoryFactoryBean">
<property name="tablePrefix" value="MY_PREFIX_"...
The "BATCH_" part is customizable, you can choose your own prefix. Take a look at the JdbcJobExecutionDao, JdbcJobInstanceDao and JdbcStepExecutionDao classes. There you'll find a property named...
Ok, good to know that I can use the ExecutionContext for this purpose.
I realize that.
What I first had in mind when looking at Spring Batch was that one step would read in a file (and...
There are a few things that caught my attention when using Spring Batch.
Inter-step communication
First of all, there doesn't seem to be any easy way to communicate information (objects, etc)...
During input reading i'd like the FlatFileItemReader to skip bad records (i.e. records that cannot be mapped using the FieldSetMapper), but i'm not sure how to implement that. I've noticed there are...