This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

So in the xml source code it seems to be an issue with a "<" simbol from the above FOR loop. I mean it's a less than, not a tag one. Is there any way to modify this file?? i don't fin it anywhere in my project...this file seems to be dinamic generated??

Comment

I remember something like this happening to me. Check both your log file and your console. If you don't find any errors there, look carefully at the source of your page. I think it will be a page that reports an error, and it's the error report that actually breaks the page and causes the invalid xml.

Comment

I remember something like this happening to me. Check both your log file and your console. If you don't find any errors there, look carefully at the source of your page. I think it will be a page that reports an error, and it's the error report that actually breaks the page and causes the invalid xml.

You're absolutely right Mike, this happens every time there's a page error (e.g. a malformed JSP document or a missing translation of an i18n message code). I don't know what I was thinking pointing the poor guy to default.jspx, even though that's where the incorrectly blamed JavaScript is actually located.

"org.springframework.beans.factory.NoSuchBeanDefin itionException: No bean named 'springSecurityFilterChain' is defined"

and also "The requested resource (/pizza) is not available." on the browser.

And i have two errors:
1 - "classpath error: unable to find org.aspectj.lang.JoinPoint (check that aspectjrt.jar is in your classpath)"
2 - "Unexpected exception parsing XML document from file [C:/Documents and Settings/Administrador/Documents/workspace-sts-2.3.0.RELEASE/pizza/src/main/webapp/WEB-INF/spring/webmvc-config.xml]; nested exception is org.springframework.beans.factory.NoSuchBeanDefini tionException: No bean named 'org.springframework.web.servlet.handler.SimpleUrl HandlerMapping#pizza#src/main/webapp/WEB-INF/spring/webmvc-config.xml#20' is defined"

In the wedding example is the same, but in tomcat console i get:
"java.lang.IllegalArgumentException: Invalid 'log4jConfigLocation' parameter: class path resource [META-INF/spring/log4j.properties] cannot be resolved to URL because it does not exist"

I'm following step by step th documentation examples, i don't know what's happening...i tried reinstalling STS but i get the same thing...

Comment

It looks like you have made some changes in your application configs (web.xml, app contexts, etc). Make sure that you have run 'security setup' which installs the applicationContext-security.xml config and registers the springSecurityFilterChain in web.xml. Maybe you run the tutorial again from scratch.

Also Roo ships a sample script called 'vote.roo' which installs security by default. You could take a look there to see how those configs are different to yours at the moment.

Comment

it's me again, i've been trying to fix the "Error de lectura XML...", and i found that Internet Explorer doesn't show that thing, it shows me the Roo's "Internal Error" view...don't know anything else to do...

Comment

The xml error is a symptom of the way the internal error is handled. So forget about the xml error for now - you need to diagnose the internal error. As Andrews pointed out, this can be caused by a missing i18n translation, or by bad xml in a jspx file. (I notice your language is "es" - maybe there is a missing message code in messages_es.properties?)

I'm genuinely surprised that there is nothing reported in your log file or your Tomcat console.

Beyond that, unless Roo is generating a bad messages_es.properties file (it works for me), it's not a Roo issue. You'll just to debug it like you would debug any other web application.

Comment

I just got that same error again this morning. If you look into your application server's log file you'll find a more detailed description of what initially went wrong!

For me it was a UTF-8 bug as the default.jspx is stored in UTF-8 encoding but all the other jspx files are most likely ISO-8859-1. So if you put a "special char" inside the latter ones you recieve the error message you named above. (I think it was something like "Invalid byte 1 of 1-byte UTF-8 sequence" in the log file)

The solution for me is to change the jspx files to UTF-8 which I did by adding the following as the second line to every file: