> There is no doubt that choosing GWT means ur web app has to be purely > Java-based. > As rightly pointed out in above post, u would require GWT (client- > side) and Spring/Hibernate or other similar technologies (server-side) > to create a maintainable, efficient Java web app. Thus u would be > learning a whole new techs to bring ur web app live.
Not true. GWT does not require a Java backend and a Java backend does not require Spring, Hibernate, or anything of the sort. GWT does not replace PHP on the server or CSS on the client. GWT replaces most or all of your handwritten JS and AJAX. There's plenty of information in the forum history about integrating PHP and GWT. On Fri, Sep 4, 2009 at 1:59 AM, sidni<[email protected]> wrote: > > Hey Spierce, > > If u require AJAX enabled web app, GWT is viable option but it seems u > dont have much hands-on with JAVA/its related technology and learning > the whole JAVA web App stack is quite an effort from scratch. > > There is no doubt that choosing GWT means ur web app has to be purely > Java-based. > As rightly pointed out in above post, u would require GWT (client- > side) and Spring/Hibernate or other similar technologies (server-side) > to create a maintainable, efficient Java web app. Thus u would be > learning a whole new techs to bring ur web app live. > > If u r comfortable with Php world, I would suggest u stick to it and > find ways to introduce Ajax within it, in the end ur goal is not to > learn different technologies or be an architect but to build ur web > app, make it live. > > Hope it doesnt confuse u, > Nitesh > > > On Sep 3, 10:36 pm, mikedshaffer <[email protected]> wrote: >> I'll throw in here.... >> >> GWT is primarily a client side technology, so in your statement >> "better off sticking with PHP, JS, & CSS", GWT would replace only the >> last 2. PHP (obviously) only runs on the server. By choosing GWT you >> will still need to choose a server side technology assuming you want >> to connect to a database. Many people are familiar with PHP, so they >> stick with that, communicating between client and server using JSON, >> which GWT handles terrifically. You can also use Java for your server >> side technology, and then you can very simply use GWT-RPC to handle >> your communication. As for connecting to MySQL, Java will connect to >> MySQL all day long, as will PHP. Just a matter of what syntax/stack >> you are familiar with. The key thing to focus on here with GWT is >> that it is an AJAX client "library" that makes it very easy to build >> powerful AJAX web clients (or substitute your favorite acronym for >> that) using Java syntax. If you use Java for your server tier, then >> you get to use a teenie bit more GWT, but that's it. >> >> Does that make sense? >> >> Later, >> >> Shaffer >> >> On Sep 2, 6:54 pm, David Given <[email protected]> wrote: >> >> >> >> > -----BEGIN PGP SIGNED MESSAGE----- >> > Hash: SHA1 >> >> > spierce7 wrote: >> >> > [...] >> >> > > By the way, I'm going to need to integrate with a web database. The >> > > obvious one for me was MySQL, but that was mainly because PHP >> > > integrates so easily with it. What kind of options do I have with this >> > > while using GWT? I'd rather not have to have GWT integrate with PHP, >> > > and then MySQL, or some other ridiculous thing. What options do I have >> > > here? Thanks in advance! >> >> > I'm using Berkeley DB JE for one of my apps; it's a pure-Java >> > reimplementation of the old classic Berkeley DB non-relational database. >> > It's got some really nice Java reflection glue that combines well with >> > GWT's RPC glue. I can pull an object out of the database on the server >> > and pass it directly to the client in about three lines of code, and GWT >> > and Berkeley DB take care of all the plumbing. And because it's pure >> > Java, there's no extra dependencies on the server --- you just drop the >> > jarfile in WEB-INF/lib and it Just Works(tm). >> >> > A server-side RPC implementation can be as literally trivial as this: >> >> > DataObject getFromDB(int key) >> > { >> > try >> > { >> > return _index.get(key); >> > } >> > catch (DatabaseException e) >> > { >> > return null; >> > } >> >> > } >> >> > - -- >> > ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─────http://www.cowlark.com───── >> > │ >> > │ "People who think they know everything really annoy those of us who >> > │ know we don't." --- Bjarne Stroustrup >> > -----BEGIN PGP SIGNATURE----- >> > Version: GnuPG v1.4.9 (GNU/Linux) >> > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/ >> >> > iD8DBQFKnxPQf9E0noFvlzgRAhmbAJ9VSY0eSfTjCoUUwNyJtf32UyYNcgCghhbe >> > Qe2VV/Tvae3wndsEBQJvyKo= >> > =4rPN >> > -----END PGP SIGNATURE------ Hide quoted text - >> >> - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
