Your suggestion to attach widgets to divs in page agrees with out experience. We use a static HTML page as a framework and hang the various active bits on it. No need for jsp since all dynamic content is handled by the GWT parts.
We also prefer to spread the application over a family of pages so it behaves more like a normal web site.
The secret to working this way is a good URL design - as in any good web app. To keep everything stateless and generally RESTful your in-page code must inspect the URL to get its context.
It is a paradox, but open sourcing software is all upside for many corporations - if they realise it. An internal project can benefit by sharing and has little to lose by it.
Planned, collaborative development is another case. Development of this open source project of mine: http://cimtool.org/ is funded by its users. The income is limited to development fees which is OK for a project that would never fly in any other model.
I would go as far to that the majority of software in this world would not be a viable product under a fee-for-closed-source-license model.
We have used it for a fairly big internal application for one of our clients. Given we wanted ajax rather than a typical rich client, the main advantage of GWT was that we could program in the same language end-to-end.
We managed to avoid a lot of boilerplate code by using the same data class definitions (POJO's) in the server and client. So an object might be created by hibernate from a database record, copied to the client, displayed and edited, copied back to the server, manipulated there and finally updated in the database via hibernate.
The main omission in GWT is a good framework for binding data to UI elements. Because there is no introspection available in the GWT client environment, it is hard to do this in a generic way. We solved the basic problem by generating class and property descriptors during the usual hibernate code generation step. We then created a UI-POJO binding framework that picks up and uses these descriptors. Again avoiding a lot of boilerplate.
Slashdot Mirror
Your suggestion to attach widgets to divs in page agrees with out experience. We use a static HTML page as a framework and hang the various active bits on it. No need for jsp since all dynamic content is handled by the GWT parts.
We also prefer to spread the application over a family of pages so it behaves more like a normal web site.
The secret to working this way is a good URL design - as in any good web app. To keep everything stateless and generally RESTful your in-page code must inspect the URL to get its context.
It is a paradox, but open sourcing software is all upside for many corporations - if they realise it. An internal project can benefit by sharing and has little to lose by it.
Planned, collaborative development is another case. Development of this open source project of mine: http://cimtool.org/ is funded by its users. The income is limited to development fees which is OK for a project that would never fly in any other model.
I would go as far to that the majority of software in this world would not be a viable product under a fee-for-closed-source-license model.
We would have no problem doing that.
We have used it for a fairly big internal application for one of our clients. Given we wanted ajax rather than a typical rich client, the main advantage of GWT was that we could program in the same language end-to-end.
We managed to avoid a lot of boilerplate code by using the same data class definitions (POJO's) in the server and client. So an object might be created by hibernate from a database record, copied to the client, displayed and edited, copied back to the server, manipulated there and finally updated in the database via hibernate.
The main omission in GWT is a good framework for binding data to UI elements. Because there is no introspection available in the GWT client environment, it is hard to do this in a generic way. We solved the basic problem by generating class and property descriptors during the usual hibernate code generation step. We then created a UI-POJO binding framework that picks up and uses these descriptors. Again avoiding a lot of boilerplate.
Our code for all this is here: http://code.google.com/p/gwt-hibernate/
I'd say GWT worked out pretty well.