spring - When deploying old GWT app to Tomcat, RPC URL returns 404 -


i'm moving old gwt app 1 server another. both in eclipse , on old tomcat working ok, on new server gwt app gets loaded (so server working , serving files), fails on rpc call returning 404.

my admin , have looked @ possible differences in context paths, tomcat , java versions, , tried recreate config on new server close possible seems we're missing i'm looking fresh ideas.

as mentioned on this link under common pitfalls, indicates web.xml misconfigured, ruled out same web.xml works ok on old server. @remoteservicerelativepath "app.rpc" , in web.xml mapped to:

  <servlet-mapping>     <servlet-name>dispatcher</servlet-name>     <url-pattern>*.rpc</url-pattern>   </servlet-mapping> 

...and in dispatcher servlet mapped correct controller. can give server.xml or other part of config if needed, i'm looking other things incorrect.

solved it, going nuclear , copying exact same tomcat , java version same paths , settings on old server. know not network problem, , request received tomcat never got gwt or application code; either tomcat (5.5 in original configuration, 6.0 in the) or spring (2.0.2) culprit. old application won't updated , due replaced , hope dies quick , painless death.


Comments

Popular posts from this blog

Android layout hidden on keyboard show -

google app engine - 403 Forbidden POST - Flask WTForms -

c - Why would PK11_GenerateRandom() return an error -8023? -