I dont believe jk mapping is the issue because i get the same results if i use port 8080 or port 80. I do have apache2 in front of Tomcat6 but everything seems to be working correctly. Like i said the webapp works when i turn on the invoker code in the tomcat web.xml so i am guessing it has something to do with tomcat6/gwt.
Here is my context info: <Context displayName="test.domain1.org" docBase="/var/lib/tomcat6/domain1/" path="/" antiResourceLocking="false" privileged="true" /> Thank you again for your help. On Feb 18, 9:48 am, olivier nouguier <[email protected]> wrote: > On Thu, Feb 18, 2010 at 3:10 PM, Eric <[email protected]> wrote: > > Thanks for your reply. Where would you "hard code" the GWT-RPC url? > > > When *not* using the annotation you can specify by code the remote end > > point. > > > I have verified that there isnt a leading "/" in the > > GreetingService.java file. See below: > > > package com.sample.myproject.client; > > > i > > Okai for the GWT code. > I'm still believe it's a "path issue". > 2 tracks : > What is the contextPath of your webapp ? > If it is "simple" then you should remove the "simple" token from your > servlet mapping. > > How does apache forward the request to tomcat? > If it is a jk mapping issues you're app will work with tomcat only (8080). > > HIH > > -- > A coward is incapable of exhibiting love; it is the prerogative of the > brave. > -- > Mohandas Gandhi -- 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.
