Actually, that sounds different. The trouble I have is when Spring tries to locate the view thusly:
1. HelloController returns "hello/hello". 2. InternalResourceViewResolver attempts to map this to /WEB-INF/views/hello/hello.jsp 3. Jetty's web container attempts to find this resource in the URL pattern "/*". 4. No joy. The limitation seems to be in Jetty alone, so you might still see it with struts; I don't know if you need a similar construct in web.xml but I imagine so, based on what I remember from old struts from years ago. I've seen the Jetty limitation documented elsewhere that it can't handle the "/*". On Thu, Jun 3, 2010 at 8:21 AM, Andrew <[email protected]> wrote: > Hi Bill, > > I can see what you mean now. I have actually jumped over to a Struts > 2 app at the moment, and whenever I change Java code I need to stop > the development server and restart it. Very painful. > > Is this just the way it is, or are we missing something? > > Regards, > Andrew. > > On Jun 3, 10:32 am, Bill Milligan <[email protected]> wrote: > > If you've gotten past point 2, I'd love to see it. Redeploying every > time I > > make a change is driving me batty. > > > > > > > > On Wed, Jun 2, 2010 at 7:38 PM, Andrew <[email protected]> wrote: > > > Thank you very much Bill. The suggestion in point 1 worked a treat. > > > > > To answer your other questions, I am using asm 2.1 and spring 3.0.2. > > > > > My url pattern is: > > > > > <url-pattern>/*</url-pattern> > > > > > When I said that the app was actually running, I meant that even > > > though there were those errors in the console, I was able to browse to > > > the hello world file and it gave me the expected output so it appeared > > > the errors actually hadn't stopped anything from working. > > > > > If you would like me to send you my eclipse project in a zip file > > > please let me know and I'm happy to do so. > > > > > Best regards, > > > Andrew. > > > > > On Jun 3, 12:04 am, Bill <[email protected]> wrote: > > > > Okay, a few things I found out -- > > > > > > 1. The suggestion athttp:// > > > code.google.com/p/googleappengine/issues/detail?id=2527 > > > > works quite well. You'll find the afflicted appengine-agent.jar in > > > > your eclipse plugins folder under > > > > com.google.appengine.eclipse.sdkbundle.<version>/appengine-java-sdk- > > > > <version>/lib/agent. Use jarjar to fix internal refs to its own asm > > > > code, completely compartmentalizing it away from everything else. > > > > Ignore the "ln -s" suggestion, I have no idea what that's about > except > > > > possibly it's someone's idea to avoid renaming a file, and the > > > > "plugin.jar" to "plugin2.jar" is just an example. It's not really > > > > relevant. > > > > 2. It won't matter once you get this working. Jetty will not be > able > > > > to find your hello.jsp. I can't figure out why, but I believe it has > > > > something to do with the URL pattern in web.xml. I tried moving it > > > > around without success. > > > > 3. Both problems are non-issues on production. I deployed the hello > > > > app out there and everything just worked. On one hand it's good, but > > > > on the other, this drastically disimproves my build-test-turnaround > > > > time. > > > > > > On Jun 1, 10:56 pm, Andrew <[email protected]> wrote: > > > > > > > Hi, > > > > > > > I'm trying to get spring 3.0 up and running as per the blog post at > > > > > > > > http://www.ardentlord.com/apps/blog/show/829881-spring-3-0-on-google-. > > > .. > > > > > > > However I'm running into some issues when I try and start it up in > > > > > Development (have not tried in production yet): > > > > > > > The console is showing a stack of these messages: > > > > > > > 02/06/2010 2:50:19 AM > > > > > com.google.appengine.tools.development.agent.impl.Transformer > > > > > transform > > > > > SEVERE: Unable to instrument > > > > > > org.springframework.web.servlet.view.DefaultRequestToViewNameTranslator. > > > > > Security restrictions may not be entirely emulated. > > > > > java.lang.NoSuchMethodError: > org.objectweb.asm.ClassWriter.<init>(I)V > > > > > > > However as far as I can tell the app is actually running. > > > > > > > There was a thread in this group late last year that described a > > > > > similar issue, and the suggested solution seemed to be to rename > the > > > > > plugin.jar file to plugin2.jar: > > > > > > > > http://groups.google.com.au/group/google-appengine-java/browse_thread. > > > .. > > > > > > > However the posters seemed to be using macs. I am on Windows 7 > > > > > (Eclipse Galileo with the Google Plugin) and cannot locate this > file - > > > > > does anyone have any advice on where I may find it? > > > > > > > Best regards, > > > > > Andrew. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Google App Engine for Java" group. > > > To post to this group, send email to > > > [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<google-appengine-java%[email protected]> > <google-appengine-java%2b[email protected]> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-appengine-java?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
