Hi, I don't have an answer on the portal part of your question, but a few thoughts on the other parts:
> Are there limitations to using GWT, for example can you use, > hibernate, spring, and spring security? GWT runs on the client (except for the parts from gwt-servlet.jar, which run on the server if you choose to use GWTRPC). So on the server, you can use whatever you want - this is not restricted by GWT. You just have to make sure, that GWT can handle the objects you transfer to the client - remember that everything used on the client has to be compiled to JavaScript, so it needs the source code for the entire object graph that is used. If you want to minimize these dependencies, you're probably best advised to use DTOs and keep the objects for the client simple. > Is there a danger in locking ourselves into GWT for web based > application development that we cannot move away from it? This depends on how much you rely on the Java to JavaScript magic (which won't be provided by a lot of other frameworks, I'm afraid). So if the complex parts of your application are either executed on the server side, or if they're written in JavaScript, you won't have much lock-in. But if it's written in Java, and it has to be executed on the client-side, you probably will. HTH Chris On Mar 9, 12:44 pm, Portal Developer <[email protected]> wrote: > Hi, > I would like to get people's opinions around the adoption of GWT as a > web application development platform. > > Most of our development is carried out using java / php and we are > looking to standardise on a new framework for developing web based > applications. We have a mixture of portal based development and php > applications. > We would like to maintain our portal based development in java but how > well does GWT integrate with portals? > > Is there a danger in locking ourselves into GWT for web based > application development that we cannot move away from it? > > Are there limitations to using GWT, for example can you use, > hibernate, spring, and spring security? > > If we decide later that GWT isn't the way to go can we reuse what was > developed in java for GWT, for example is is it possible to develop > generic enough classes for GWT that can be used outside of GWT as > well. > > I would be grateful for thoughts and opinions, good and bad. Both > sides of the story would be helpful. > > Thanks, -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
