History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEA-17266
Type: New Feature New Feature
Status: Open Open
Assignee: Nikolay Chashnikov
Reporter: Jim Adkins
Votes: 2
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
IDEA: Feedback

Spring integration via integrated Tomcat server (GWT "hosted mode")

Created: 27 Feb 08 20:13   Updated: 11 Mar 08 14:01
Component/s: GWT Support

Build: 7,590
Severity: High


 Description  « Hide
Background:

Currently, when using the Run/Debug tool in conjunction with a GWT Configuration, the plug-in "stomps" the items in the integrated Tomcat cache area (.../gwt/gwt.<n>/run/tomcat/webapps/ROOT/WEB-INF).

Of particular interest, is the "web.xml" file. This file is regenerated with information relating to the "com.google.gwt.dev.shell.GWTShellServlet" servlet mappings.

We are utilizing the Spring framework within our application, so we have a our "web.xml" file configured to use the "org.springframework.web.servlet.DispatcherServlet", which refers to a "spring-servlet.xml" file that defines an "urlMapping" to a "org.gwtwidgets.server.spring.GWTHandler" class that is ultimately bound to our GWT Remote Service.

Since no mechanism exists to define this information, it is incumbent upon the user to locate "static" files generated by the GWTShell call and manually copy these files into an external container (Jetty, Tomcat, WebLogic, etc.) so that IoC items are properly created. This condition also requires the use of a "remote" debugger as well.

Feature Request:

It would be great, if the GWT Studio plugin, would allow the user to specify a particular "deployment descriptor" to be parsed, having it's contents dynamically included into the integrated tomcat's "web.xml" file.

Or, alternately, have a mechanism available to "preserve" the deployment descriptor, so that the user could modify it by hand.

Thanks!



 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.