I've always used the same URL mapping formula as that - I have never got to bottom of how to get it to work using wild cards etc
I believe the reason is to something do with with the combination of a) GWT.getModuleBaseURL() returning the module path with '.' (dots) instead of '/' (slashes) and b) the way Tomcat etc treat dots in a URL pattern. I recall something about Tomcat treats everything that comes after the first dot in the url as an extension rather than treating the dots as directories (hence the *.do etc in struts). I also believe this comes directly from the servlet 2.4 specification definition of how to treat wild cards in url pattern matches, and last time I looked that up I recall I did not find it particularly intuitive. I think if one wrote one's own static helper that called GWT.getModuleBaseURL() and replaced all the dots with slashes and used that instead in your RPC call set ups, then I think it might behave as one might expect, but I've never got round to trying this yet - I just cut and paste the full module path, dots 'n all, into web.xml :-( There might be a way to manipulate the servlet spec wild card rules to get round this, but I've never yet seen a post explaining how for GWT.getModuleBaseURL() based URLs. On Mar 22, 10:28 am, [email protected] wrote: > > The requested resource (/gwtejb/de.stsch.gwtejb.GwtEjb/GwtEjbSrc) is > > not available. > > Hmmmmm, it works when I change my web.xml to > > <url-pattern>/de.stsch.gwtejb.GwtEjb/GwtEjbSrc</url-pattern> > > Why do I have to include the full package name? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
