You are 100% correct. Thanks!
Thanks for that. To have the first slash or not have the first slash
has always been a point of confusion for me. Thank you for clearing
that up!
On May 23, 2:49 pm, Ian Petersen wrote:
> You missed the slash character at the start of observationServiceURL.
> The w
You missed the slash character at the start of observationServiceURL.
The work you do in a later post to take a substring of
GWT.getModuleBaseURL() is successful because it leaves the slash
between "http://localhost:8080"; and "celticlock/" behind because you
look for the index of "celticlock" and
Figured out a work around.
String baseUrl = GWT.getModuleBaseURL();
int indexOfC = baseUrl.indexOf("celticlock");
baseUrl = baseUrl.substring(0,indexOfC);
String observationServiceURL = baseUrl + "servlets/celticlock/
greet";
If I s
It looks like the problem is, the moduleBaseUrl for greetingservice is
"http://localhost:8080/celticlock/"; and it's tacking on the serviceUrl
to that possibly.
On May 23, 9:26 am, Sean wrote:
> I thought that would work, but even with:
>
> String observationServiceURL = "servlets/celticlocks
I thought that would work, but even with:
String observationServiceURL = "servlets/celticlocks/greet";
((ServiceDefTarget) greetingService).setServiceEntryPoint
(observationServiceURL);
I still get the message:
HTTP ERROR: 404
NOT_FOUND
RequestURI=/celticlock/servlets/celtic
You're getting the first celticlock in becuase you're appending
GWT.getModuleBaseURL() to the front of observationServiceURL. Since you know
that your servlets are hosted at /servlets, change:
String observationServiceURL = GWT.getModuleBaseURL() +
"servlets/celticlock/greet";
to
String observat
Hi,
I'm trying to deploy an RPC, but I can't figure out how to do it in
1.6. The problem is, the new RPC seems to always have the request
being
[projectname]/[RPC entry Point]
My problem with this is, on my shared Tomcat account, the way I can
tell the server to have Tomcat execute this service
I didn't have to do that. The service path is set as "/myService" in
both Module.gwt.xml and as the argument to
@RemoteServiceRelativePath. I tried "/myModule/myService", but got
404s stating that the server couldn't find "/myModule/myModule/
myService". Some aspects of GWT seem to be tightly-c
Hi Christopher
I had a tough time getting this to work at first too (using 1.5). One
of the changes I
made that I have not seen mentioned in this thread is that I had to
change the
service entry point to something different than what Bruce had in his
initial post
I had to use a full URL to my ser
Sorry, maybe _I_ should be more explicit. In reference to updating
the documentation, I meant including the need to create a web.xml file
and package the server-side code into the webapp pathing. Parsing the
module.gwt.xml file for elements and inserting transformed
and elements into an exter
Having an automated build and deploy process is just a good idea. It saves
you from the tedium and risk of manually moving files around. I would just
as soon choose not to automate my builds as I would choose not to keep my
project in a versioned repository.
I image that the topic of build process
Will do. As an aside, does the Documentation need to be more explicit
about this or am I the exception here? If so, I can submit a change,
if documentation updates are something non-Google contributors are
allowed. Any moderators listening?
Thank you again for your assistance.
On Oct 14, 1:3
You'll want to set yourself up with a proper build process. I suggest Ant.
It's simple, powerful, and there are a number of examples you can borrow
from this forum. Have your Ant script build a .war file and copy it to your
tomcat/webapps directory. Tomcat's default configuration is to automaticall
On Tue, Oct 14, 2008 at 12:34 PM, Christopher Venning
<[EMAIL PROTECTED]> wrote:
> Relevant module code
> ---
> from TestService.java (extends RemoteService):
> @RemoteServiceRelativePath("/testService")
I don't know what difference it makes, but my
@RemoteServiceRelativePath doesn't have a leadi
Thank you very much.
For posterity: I compiled the my.module.server package (with
dependencies) and exported to %TOMCAT_HOME%/webapps/ServerTest/WEB-INF/
lib, where I also copied gwt-servlet.jar (a dependency) from
GWT_HOME. I also created the WEB-INF/web.xml file with the servlet
mapping.
Now,
On Oct 14, 12:53 pm, "Isaac Truett" <[EMAIL PROTECTED]> wrote:
> Did you deploy your compiled servlet? I don't see it listed in the stuff you
> copied to tomcat/webapps/ServerTest.
What do you mean "compiled servlet"?
--~--~-~--~~~---~--~~
You received this mess
You're use GWT RPC, which means you have a RemoteServiceServlet somewhere
that implements the server side of that RPC service. You need to compile
that servlet to a Java .class file and deploy it to your web server. You
also need a web.xml file to map request URLs to your servlet.
On Tue, Oct 14,
Err, sorry. Didn't answer you. No, the changes detailed are the only
changes made to a fresh extract of a freshly-downloaded (MD5-checked)
package of Tomcat (Windows binaries). If there is something else that
needs to be deployed, I have not done that.
On Oct 14, 12:55 pm, Christopher Venning
Did you deploy your compiled servlet? I don't see it listed in the stuff you
copied to tomcat/webapps/ServerTest.
On Tue, Oct 14, 2008 at 12:34 PM, Christopher Venning <
[EMAIL PROTECTED]> wrote:
>
> I cannot seem to get the -noserver mode working with RPCs. I got it
> to work in 1.4 but have ch
I cannot seem to get the -noserver mode working with RPCs. I got it
to work in 1.4 but have changed environments in the last year. There
don't appear to be any Group postings about getting it going since 1.5
was released. Bruce Johnson's original posting (http://
groups.google.com/group/Google-
20 matches
Mail list logo
