Search:

Turns out the solution is simple:

- Add MethodValidationPostProcessor to the spring context.
- Annotate type with @Validated

Hope this helps someone as this doesn't appear to be documented.

I would like to use JSR 303 to validate beans in my application context. I have a small @Configuration that adds three beans:

- LocalValidatorFactoryBean
- BeanValidationPostProcessor
-...

I would like to find all ObjectIdentity's a particular Sid has permission for (for instance, what objects of class xyz does sidxyz have read permission for). This seems like a common task however it...

Sorry, one more update. =)

While changing the output directory allowed me to run grails from Eclipse->Debug and debug the application I am not able to consistently hot deploy any code changes. The...

Turns out this was being caused by eclipse generating class files to the same location the grails tomcat server was running from. I changed my projects output directory to something other than...

I am still getting this error however I am now running Grails 1.2.0 and STS nightly from last week. Any ideas?

I upgraded my grails application from the command line from 1.1.1 to 1.1.2. After that succeeded I went back into STS and did a grails->refresh depdencies and then ran a build. The maven builder when...

I am getting the following exception when running my maven managed grails application via STS nightly (from today). Anyone else see this or know what might cause it?

Running script...

I created a defect with the attached project.

https://issuetracker.springsource.com/browse/STS-691

Yes the hard crash was the same as before, STS just disappears. If I restart STS it immediate starts building when it starts up and but crashes before the build completes. Fixing the compile errors...

This worked great, thanks.

I ran into an issue with asserts in groovy because STS compiles groovy files with Groovy 1.7 but grails 1.1.1 uses a Groovy 1.6 runtime. This results in NoSuchMethodException's being thrown about...

I experienced another hard crash today. This time I capture the console.app output (it is attached to this post) which looks like it might have some useful information.

It appears what happened...

I have tried refreshing the dependencies from the grails menu however that does not help.

It looks like the jars from plugins/acegi/lib are added but some lib is still missing. These imports...

I have a maven managed grails project imported into STS 2.2.1 with the acegi plugin installed. STS does not add the acegi plugin dependencies from the plugin's lib directory.

I could add the...

I just enabled dependency resolution and auto build after having it off for a few days and it is no longer crashing. I will keep an eye on the console output should it happen again and email you the...

Thanks for the quick response Christian.

I upgraded from 2.2.0 using the "Check for updates" feature in the "Help" menu. Please note this was occurring using 2.2.0 as well. I updated to 2.2.1 in...

Also it may be important to know this was occurring earlier today before I upgraded to 2.2.1 .

I am experiencing a hard crash while running STS 2.2.1 on MacOS with two maven managed grails project in my workspace. The crash seems to occur when a build is %90+ complete and the entire...

I haven't made any progress on this (been working on other issues).

It seems like the best case would be if when a write fails the retry only retries the write (in a new transaction). I briefly...

Ive found the best method to get parameters to your Reader and Writer is by using the @BeforeStep annotation which gives you access to the StepExecution. Then you can get the job parameters with:...

I have a batch job that reads a single row from the database (ItemReader), performs some time intensive calculations (ItemProcessor) and then inserts a handful of rows into another table...

Any suggestions for a convenient way to set the throttleLimit of a step when using the batch namespace to configure your job?

Solution is to add scope="step" to the <bean id="" ...> tag.

It is important to add the string: scope="step" to your reader bean definition otherwise the expression will not work. See the documentation and the bold highlights in the thread you mentioned.