In GWT recommended project structure, client code and server code are
placed in one project. I find this structure is not so development-
friendly in practice. (GWT 1.6 has some new update to the project
structure to make it more like standard WAR project, but client and
server code are still in o
Well my gwt project I seperated the client and server side. The main
thing that is possible if it was one project is passing objects
stright to the server.
So my project use json to create objects when the client ask for stuff
from the server.
There might be ways to have the object passing but I
Hello,
Which means that you are using java as a server side language ?
If yes, what library you are using for json ?
Regards,
Miroslav
flyingb...@gmail.com wrote:
> Well my gwt project I seperated the client and server side. The main
> thing that is possible if it was one project is passing o
On 1 avr, 21:27, Ken wrote:
> In GWT recommended project structure, client code and server code are
> placed in one project. I find this structure is not so development-
> friendly in practice. (GWT 1.6 has some new update to the project
> structure to make it more like standard WAR project, bu
> Why not just give the MyProjectWeb project to the GWTShell in the
> classpath? Provided you used the "client" and "server" subpackages of
> the same "root" package in all three projects (or made a gwt module in
> the same package as the server code in the MyProjectGwt project and
> inherited it
>> Agreed (though sticking to the recommended client and server, and
>> possibly shared, subpackages, it's still fairly easy to *not*
>> reference client code form server code and vice versa).
>
> Human beings will make mistake if they are able to. I don't want to
> keep telling my developers all
>If you're referencing server-only code from the client, then you have
>a fundamental problem in what you're trying to do. Same if you're
>referencing a Widget from the server. Your developers should already
>know that. If they don't, they need to be educated anyway. It's not
>"rules and tricks" b
Nothing says that you do. But you will want to then have at least a
3rd project that contains the common types shared between client &
server. And you'll probably want to leave the RPC code in the
client-side project to separate your front-end code from your back-end
business logic.
On Mon, Apr