Mar 19th, 2010, 06:56 AM
Problem with Roo Security set-up in STS 2.3.1
It seems that if you avoid "run as server" until after you add security, things works fine. Not really sure why
There is small bug with the applicationContext-security.xml view. STS 2.3.1 complains that <http auto-config="true" use-expressions="true"> is not valid due to Static factory method 'createSingleAttributeList' with 1 arguments not found in factory bean class 'org.springframework.security.access.SecurityConfi g' .
If you just do <http> the error goes away, but then project url goes 404.
But this seems to be more of an STS 2.3.1 issue...so I will check JIRA for that and post if not there. Cheers!
I am attempting to work through the wedding example found at http://blog.springsource.com/2009/05/27/roo-part-2/
I already figured out the change need for entity set up (--class instead of --name)
I can run the selenium tests. I can run as server in STS 2.3.1 (Build: 201003091003 on Windows XP) and successfully CRUD wedding RSVPs from http://localhost:8080/wedding
However, I am stymied by the security portion. The instructions say to issue "security setup" on the Roo console.
I do this within STS 2.3.1. I see the correct output and tomcat redeploys correctly.
However when I attempt to reload the wedding page, I am now greeted with an internal error message and the console spews a whole lot of error messages... the root cause of which appears to be:
org.springframework.web.servlet.tags.form.InputTag - Neither BindingResult nor plain target object for bean name 'rsvp' available as request attribute
I have attached the error dump as a text file in zip in case this is of help.
Any words of wisdom are greatly appreciated. Thank you
Last edited by emaggini; Mar 19th, 2010 at 07:58 AM.
Reason: updated info
Mar 23rd, 2010, 12:57 PM
Solution found here:
Update to spring security 3.0.2.RELEASE and restart the server.
Mar 23rd, 2010, 02:32 PM
Mar 23rd, 2010, 11:13 PM
The upcoming Roo 1.1 M1 release will ship with a Spring Security 3.0.2 setup.