I'm sure it's in the works, but I'm not working at Google… ;-)
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-
hi Thomas,
Any plans on getting similar checks that performed by
RequestFactoryInterfaceValidator to the Eclipse plugin so it will show
it immediately there is an error and possibly offered a suggestion
right there thru Ctrl-1?
Thanks,
Joseph
--
You received this message because you are subscr
...and proxies and contexts are needed at runtime by the
RequestFactoryServlet, so they should really be in "shared".
The domain objects and services should be in "server" though, of course
(IMO, even if using interfaces, though YMMV). I use the @ProxyForName and
@ServiceName annotations (rathe
Breaking the app into server, client and shared is a right thing to do, but
placing proxies, requests and services there does not seem right.
Proxies and requests belong to the client, services to the server.
Shared packages should contain code used by both the client and the server
(common c
Thank You.
I am trying to breaking my app into: client, server, and shared modules.
in the shared module, I would like to put
RequestContext, and Entity/Value Proxy interfaces,
as well as server side Interfaces corresponding to RequestContext,
for example, this shared module:
EmployeeProxy -
On Sunday, March 6, 2011 9:51:11 PM UTC-8, zixzigma wrote:
>
> It is often recommended that, it is a good practice, for components,
> such as client/server communicate through interface.
>
> when working with RequestFactory,
> we need to define RequestContext, which makes use of Entity/Value Pro
On Monday, March 7, 2011 6:51:11 AM UTC+1, zixzigma wrote:
>
> It is often recommended that, it is a good practice, for components,
> such as client/server communicate through interface.
>
> when working with RequestFactory,
> we need to define RequestContext, which makes use of Entity/Value Pro
It is often recommended that, it is a good practice, for components,
such as client/server communicate through interface.
when working with RequestFactory,
we need to define RequestContext, which makes use of Entity/Value Proxies.
these are all interfaces.
however, Server side code, cannot impl
