request for enhancement to RemoteServiceRelativePath annotation (GWT 1.5)

[Thad]

From what I'm seeing, the @RemoteServiceRelativePath annotation is
applied at the interface level. I would like to see such an
annotation for the individual methods in a service, similar to the
individual @Resource annotation in an ImageBundle. My image bundles
group icons used for a similar purpose. Why can services do the same?

My application is quite large. Already I have dozens of RPC calls,
and might have over a hundred by the time I'm done (I'm writing front
end to a large server system). To keep things straight, I've grouped
my *Service and *ServiceAsync class in a com.mycompany.myapp.services
package and my *ServiceImpl classes com.mycompany.myapp.server
package. Each of these service triplets bundle methods of a similar
nature: FolderServices, FileServices, IndexDBServices, etc. In order
to use @RemoteServiceRelativePath I'd have to break each method out
into its own file (right?). I'm loath to do this. I'd end up with
hundreds of files. Moreover some of my *ServiceImpl classes have
private methods that are shared by the multiple public methods.
Duplicating these or moving them into a separate class would be more
painful than continuing with the old, pre-1.5 RPC call approach.

[Isaac Truett]

Why do you think you need a different URL for each method?

[Thad]

Hahahahaha! Oh wow! I must have missed something in my reading of
the documentation, but you are so very right. I was in the mindset
that each method call would need a unique URL. So I've tested this on
a small scale in a hosted mode. Then I converted one set of services
to this approach, built the WAR with ant, and deployed it in Tomcat 6
and Apache 2.2. It works faultlessly.

Thank you so much for enlightening me. This is going to make things
much simpler.

On Aug 4, 9:06 pm, "Isaac Truett" <itru...@gmail.com> wrote:
> Why do you think you need a different URL for each method?
>