Advanced cross-module usage

I'm not sure what I'm doing is the best approach but something is wrong for sure:

I have a core module  "A" that does nothing but implement all logic and composites, a module of front-end (separated for reasons partially outside the scope of this discussion) "B" that implements in the onModuleLoad producing the interface response and basically all the web application, indeed since there's no specific need B doesn't have any servlet but maps the existing A servlet in web.xml with something like:

<servlet-mapping>

    <servlet-name>A</servlet-name>

    <url-pattern>/B/A</url-pattern>

</servlet-mapping>

and so far (right or wrong, nice or ugly) all works perfectly.

I also have a C module that has his own servlet, a complete implementation with html, servlet and module declaration, now: from C I need to use some composite declared in A but this composite in his implementation uses some A rpc producing as result:

   [WARN] C: An IncompatibleRemoteServiceException was thrown while processing this call.

com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: This application is out of date, please click the refresh button on your browser. ( Blocked attempt to access interface 'A', which is not implemented by 'C-Impl'; this is either misconfiguration or a hack attempt )

So the basic question is: how can I share a complete implementation (composite that already works as interface + RPC logics that right now produces the exception) cross modules?

Anyone with a deep understanding that can point me in the right direction?

Thanks

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.