Error on Spring Surf Tutorial Example

[kamal_1]

Thanks for your information yong....

[yqu]

For that urlrewrite.xml issue, all you need to do is

Fix: Preferences -> General -> Network Connections -> Cache and remove the cached DTD, then rebuild the project.

Yong

[sujitpal]

My environment:
- Roo 1.0.2.RELEASE
- Spring Surf Roo Addion 1.0.0.M3

I manually changed the Jetty port in the pom.xml to 8081 since I need Tomcat to serve Alfresco on port 8080.

I think there may be a problem with the URL published here:

Chapter 2, Section 1.3:
Once the Jetty server is started, we are ready to visit our new Surf application at http://localhost:8180/.

The above is definitely incorrect (unless the ROOT context is being used and Jetty is started on port 8180 by default), IMO it should be:
http://localhost:8080/community

However, I don't seem to get this URL to work. For me Jetty returns the following message:
HTTP ERROR: 500
Could not resolve view with name '' in servlet with name 'Spring Surf Dispatcher Servlet'
RequestURI=/community/

However, I do get the console page:
http://localhost:8081/community/console

All I have done so far are run the following roo commands:

project --topLevelPackage com.mycompany.community
surf install

and modified the pom.xml to use jetty.port=8081 instead of default 8080.

Any pointers would be appreciated. Not sure if I am using a wrong URL or there is something I need to do to one of the files to get this to work.

I see that others have gone further down the tutorial than I have, so hopefully you have seen this problem and know of a fix.

Thanks very much,
Sujit

[kamal_1]

Hi,,,
I also found the same issue. My alfresco was running in the port 8080 and I managed to have another tomcat to run on the port 8081 FOR MY SPRING SURF.

Then I thought to deploy this by having a small change in the pom.xml file as:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>tomcat-maven-plugin</artifactId>
<version>1.0-beta-1</version>
<configuration>
<url>http://localhost:8081/manager/html</url>
</configuration>
</plugin>

[sujitpal]

Thanks kamal_1, so it looks like some dependency on Tomcat (perhaps some default configuration that is not present in Jetty?). I will try out your suggestion.