Search:

Got it to work with the AsyncItemProcessor and AsyncItemWriter...which btw I think are great wrappers!!!

I'm seeing the same behaviour, tried using the throttledTaskExecutor that comes with spring batch admin and a SimpleAsyncTaskExecutor with 10 threads. In both cases after the first chunk it seems to...

Clearing up the AppData/Local/Temp directory in Windows seems to fix the problem.

I have a similar issue, not only does the ROO shell not respond but the last action it did was to delete the Roo ITDs on the current domain object.

And now the ROO annotations are not recognized...

I have a step with JdbcPagingItemReader (MS sql server) with skippable exceptions.



<step id="transfer_bond_cashflow" >
<tasklet>
<batch:listeners>
<batch:listener...

Thank you, Alex. I've voted for this and looking forward to its release.

Yes, this is on STS 2.5.0.M3

Hi Stefan

I'm using Roo 1.1.0.M3 on Windows 7 64 bit. The footer.jspx errors are still there.

I use STS 2.5.0.M3 with Roo 1.1.0.M3 on Windows 7, 64-bit java jdk 1.6.0_3



@RooIntegrationTest(entity = Bond.class, findAll=false, persist=false)


when running maven test outside the roo...

I got the same error too, when running "perform tests" in the Roo shell within STS.

Tried to use the workaround by creating the mvn.bat but still getting the same message.


Cannot run program...

Sorry to hijack OP's thread, but I created it using "entity".

I face the same issue, using DATANUCLEUS as provider and MSSQL Server as database. If anyone has a workaround please post it.

Thanks
Shri

Move the code into the java class and then debug. When you are done push it back into the aspect. There is a reference in the documentation material about the AJDT refactoring.

Yes, you need to specify the path of the file, it follows the Spring EL for specifying various paths.

After changing spring-core, spring-infrastructure and spring-test to 2.1.0.RC1, I get the following error


-------------------------------------------------------------------------------
Test...

Added the query to the JIRA issue..

For MS-SQL server, the correct query for

SELECT
SORT_KEY
FROM
( SELECT
E.JOB_EXECUTION_ID AS SORT_KEY,
ROW_NUMBER() OVER...

The tests run fine when run using "perform tests" on the Roo shell. I guess its a non-issue.

Nope, just the default settings for the embedded maven.

Would like some information on this annotation as well.

The error is


java.lang.AssertionError: Too expensive to perform a find all test for 'Stock', as there are 1001 entries; set the...

When I did a next page on the UI for job executions, it fails because of BAD SQL syntax. The DB is SQL server.

The inner query needs an alias for this to work properly.

...

It was incorrect to place the step scope on the reader, writer. Works after that was removed.

This is the reader configuration used by a job


<bean id="assetItemReader" class="org.springframework.batch.item.database.JdbcCursorItemReader" scope="step">
<property name="sql"...

Thanks a lot, Dave. It works after I added the "database.driverClassName" required by the context in the jar file to batch-*.properties. It did not work since the property in the batch-*.property was...

Changing the applicationContext.xml to


<context:property-placeholder location="classpath*:META-INF/spring/*.properties" ignore-unresolvable="true"/>

did not fix the first issue.

The...

I also tried all of the following that didn't work

a) removing the property-placeholder definition from the applicationContext.xml
b) changing the location of the properties to classpath,...