I'm pretty sure by default you can't. If you feel the urge to fiddle you
could do something in ServiceLayerDecorator.getProperty that picks up on
some extra state with the request.
I know the requirement you mean though. Some extra layer of fetch profile.
Not sure it would be worth the extra
Thanks for the reply.
Yea :/, the work involved in fiddling with the service layer decorator and
server-side RF at that level currently outweighs the benefit for my need
which is what I was avoiding. I think if I fiddled at that level I might
just end up making the .with() work with primitives
If you try the multiple Proxies approach could you report back to the
group? Be interesting to hear if it works out nicely. Proxies being allowed
to have their own inheritance tree etc seems powerful but I'm quite sure
for good or evil.
On Wednesday, July 24, 2013 12:20:11 PM UTC+1, GWTter
Will do. My approach would involve distinct proxies since I don't think RF
allows for inheritance on EntityProxys even if they both have @proxyfor
defined because it looks for the methods defined exactly on the proxy (it
definitely won't currently let you do it server-side with your locators).
On Wednesday, July 24, 2013 1:39:19 PM UTC+2, GWTter wrote:
Will do. My approach would involve distinct proxies since I don't think RF
allows for inheritance on EntityProxys even if they both have @proxyfor
defined because it looks for the methods defined exactly on the proxy (it
On Wednesday, July 24, 2013 2:36:34 PM UTC+2, Thomas Broyer wrote:
On Wednesday, July 24, 2013 1:39:19 PM UTC+2, GWTter wrote:
Will do. My approach would involve distinct proxies since I don't think
RF allows for inheritance on EntityProxys even if they both have @proxyfor
defined
Hi Thomas,
This is great, I was hoping this was the case. I knew polymorphism worked
well but I wasn't sure whether you could define EntityProxy super classes
and that RF would still be able to find the super class properties from the
child proxy without having to explicitly define them in the
Hi all,
I have a String username field on a user entity which I'd rather not
populate whenever I request it which is why I have not defined the getter
in the EntityProxy. This works fine, however there are some instances where
I would like to have RequestFactory populate that string field when
