I'd recommend filing a feature request if you're interested in something
like this; that will get the right eyes on it.
On Tue, Mar 2, 2010 at 10:53 AM, Chris Lercher cl_for_mail...@gmx.netwrote:
On Mar 2, 4:39 pm, Rajeev Dayal rda...@google.com wrote:
While you might be able to make
Hey Chris,
This would not do any magic to handle serialization between the client and
server versions of the types. While you might be able to make something work
out here, it would definitely not be supported behavior (as we've not
thought through this use case).
Rajeev
On Mon, Feb 22, 2010
Glad that worked out for you, and thanks for posting an example. super-src
is definitely a strange concept, so it helps to have a clear example of how
to use it, and why it might be valuable :)
On Wed, Feb 24, 2010 at 11:16 AM, Tim K timk...@gmail.com wrote:
Great answer Rajeev! I worked up a
On Mar 2, 4:39 pm, Rajeev Dayal rda...@google.com wrote:
While you might be able to make something work
out here, it would definitely not be supported behavior (as we've not
thought through this use case).
Thanks, that's what I needed to know - I'd personally only use it, if
it were supported
I think you can achieve this by using GWT's super-source mechanism:
http://code.google.com/webtoolkit/doc/latest/DevGuideOrganizingProjects.html#DevGuideModuleXml
On Fri, Feb 19, 2010 at 2:48 PM, Tim K timk...@gmail.com wrote:
I have a server version of a class in one jar, and a client version
Cool, does this also allow for serialization between client and server
version out of the box, or will this require any special additional
serialization code?
BTW, this would probably solve the issues in this thread about reusing
TopLink objects etc on the client:
I have a server version of a class in one jar, and a client version of
the class in another. The client version is restricted to JRE
emulation, while the server version can use the entire JRE. Can the
google plug-in for eclipse be configured to use the server jar for the
server code and the
