realize additional logic for RF proxies, with @Category or another
way? Currently I super sourced some RF core classes and replaced the
generator. I'am able to use @Category as described in AutoBeans. But
this means a lot of merging work on new releases. Did I miss something
with RF too implement additional logic in RF? It wouldn't be that much
work to enable @Category for proxies in a proper manner.
Another thing are all the private methods in RF / AutoBean generators
and in Service Layer logic on server side. These private methods
forces us to copy/paste a lot of code whenever we want to extend some
logic. What's the reason for this private restriction? Why not
protected?
--
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-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
ReplyDeletekanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees
kanchipuram silk sarees