> > For example we could not get rid of JSF . We are using GWT-JSF-Spring- > Seam-Hibernate and the only reason JSF is still in that equation is > that I could not find a way to integrate GWT with a pageflow framework > like Spring Webflow or jbpm . I loved what GWT offered but it needs > more openess . > The reason GWT doesn't integrate well with webflow or JBPM is because they have a radically different philosophy of doing things.
**Conventional frameworks like webflow, jbpm, struts, jsp, <put-your-technology-here> all have a server side page lifecycle. To go from one page to another, the browser goes to the server, which generates new html content and the browser renders the page again. This is the traditional style of web pages. You can AJAX'ify them by using js libraries like jquery/yui/<insert-your-js-library>, but the basic page flow lifecycle does not change. **GWT has a different architecture. There is only 1 html page in GWT. Once that page has downloaded, it stays in the browser for the length of that session. Transition from one view to another is done on client side using javascript. You can still use server side technologies like jbpm and struts, but their job will be restricted to serving the first html page; thereafter, GWT will take over. Because you are only going to serve 1 html page, using any webframework with GWT is almost always an overkill. So, the reason you can't integrate GWT with Spring Webflow is because they really are two radically different things. By introducing JSF in the picture, you will bridge the gap to some extent, but it is only going to complicate things for you. You have to decide how you want your page transitions to work. If its server side, then just use JSF and forget GWT. If its client side, just use GWT and forget JSF. If its something in between, make sure there are very good reasons for doing so, and then go ahead with a combination of JSF and GWT. The only reason for an in-between approach is a legacy application, everything else can be overcomed. --Sri On 25 April 2010 13:06, Shahzeb Khan <[email protected]> wrote: > Thanks Stephen you did answer my question and by Friday we had decided > to go with GWT . > > however deciding a front end framework based on the dynamics of it's > offering is very rational . > > Both technologies achieve same thing even though by having completely > different architectures and if google is to survive and prosper at > this end ( and we hope\wish that it does since we are going ahead with > it) then it must provide support for other jee frameworks . > > For example we could not get rid of JSF . We are using GWT-JSF-Spring- > Seam-Hibernate and the only reason JSF is still in that equation is > that I could not find a way to integrate GWT with a pageflow framework > like Spring Webflow or jbpm . I loved what GWT offered but it needs > more openess . > > I would appreciate if you do criticize me here if I am doing any thing > wrong . > > On Apr 25, 1:34 am, Stefan Bachert <[email protected]> wrote: > > Hi, > > > > It depends what you understand under theming support. > > > > You can select one of three standard themes within the module.xml. > > And you can create your own if you like. > > > > When you want to exchange the css (at runtime), you already have the > > sample downloaded in GWT 2.0.3. > > It is called "Showcase". > > > > To make a decision between JSF/RF and GWT depend on theming support > > sounds somewhat irrational. > > It is like to choose between car or boat because of the color of the > > vehicle. > > > > By the way, JSF/RF is not officially supported by Google, and RF is an > > implementation of JSF. > > > > Stefan Bacherthttp://gwtworld.de > > > > On 23 Apr., 03:17, Shahzeb Khan <[email protected]> wrote: > > > > > > > > > > > > > Does GWT provide support for themes like whe JSF or rich faces ? > > > > > We are evaluating GWT for using it as the presentation layer over > > > JSF . Other option we have is Richfaces . > > > > > So far we love GWT but support for themes will be the deal breaker or > > > maker . I have noticed some third party gwt support sites provide it > > > but we would not be using any thing else not officically coming from > > > google . > > > > > Thanks in advance . > > > > > -- > > > 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]<google-web-toolkit%[email protected]> > . > > > For more options, visit this group athttp:// > groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > > 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]<google-web-toolkit%[email protected]> > . > > For more options, visit this group athttp:// > groups.google.com/group/google-web-toolkit?hl=en. > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
