, like creating a
> shared interface which is only implemented on the server, and a static
> field with a pointer to that interface, and then storing your
> implementation into that static variable on the server side. The
> implementation then wraps up any non-GWT supported funcationa
I have created a single page using a GWT component and a class that
acts as a 'bridge' between my business code and the front end
component.
I isolated all the GWT code into a separate package structure for
ease- and included it in my application with no troubles,when it
doesnt reference any othe
I am having a similar issue integrating a GWT page into my existing
J2EE app.
I have isolated all of my GWT code into the 'normal' structure, but
have one Class that 'bridges' my GWT code and my existing backend
business. I was hoping this would make it easier to integrate
dependency-wise.
my co
