GWT SL and annotations

[Roger]

I had posted something in issues (because in my sleepiness I forgot
about the forum).

So yes, if I have

@RemoteServiceRelativePath("rpc/foo")
public interface FooService extends RemoteService {

}

and then also do the GWTHandler stuff in the spring xml.. I see the
warning that the service was already mapped (since it scanned the
annotations above).

So.. that being said (and this goes to the GWT-SL docs too).

If I remove the @RemoteServiceRelativePath stuff above.. everything
compile/deploys.. but it seems my GWT client code "never does the
RPC" (in firebug I see no network requests etc)

So is it a *requirement* of the GWT client code to have the annotation
above? (since in your document/examples, you enver put that
annotation above)

I can't seem to ever make things work without it m'self.

[Roger]

Also.. side note:

I have:
@RemoteServiceRelativePath("rpc/foo")

but in the spring xml I have:
propety name="mappings">
<map>
<entry key="/foo" value-ref="fooSerivce"/>

in the web.xml I have my dispatcher serlvet match on
gwtAppName/rpc/*

so somehow one of the two things 'aint right' hah

[George Georgovassilis]

Hi Roger,

Why don't you just remove the <mappings> ?