this sounds like a good avenue of exploration. Good luck to you, and thanks for the exploration.
Another approach to the same componentizing is to use html with a sitemesh decorator. These are post page filters that add material, like headers and footers, ... . ----- Original Message ----- From: "Vince" <[email protected]> To: "Google Web Toolkit" <[email protected]> Sent: Sunday, July 19, 2009 4:36:27 PM GMT -05:00 US/Canada Eastern Subject: Standard JSP + GWT Usage Hello, My intro is a bit long but it would explain my case. Pls bear with me... Many thanks... I've started experimenting on a JSP + GWT coupling as part of a project I'm doing. This together with Struts 2.0 is a part of a project initiative that would expand the use of rich UI within a product. The idea comes in different flavors... 1. First and foremost is to use an already existing "header" page component with GWT components as the underlying content. 2. Have that GWT body communicate and reuse existing JSPs which are already standard within the project. 3. And of course, have JSPs communicate with the GWT body. Status of my work: I have successfully "coupled" the header with a GWT body. This also more or less answered the question on how I would facilitate the communication between my GWT section with the rest of the JSPs (vice- versa). I've implemented these simple experiment right on top of Struts 2.0. The makeup of the pages. To incorporate the already existing header JSP. I've renamed the GWT generated <project>.html to <project>.jsp and moved the GWT <script> tag component within the <head> tag of the "header" as the last element. e.g. <project>.jsp 1. <include header> 2. <the rest of the elements here...> Problem: When I try to proceed to another JSP right after a button is clicked from the header, say next.jsp with the following makeup... next.jsp 1. <include header> 2. <the rest of the elements here...> ... I end up seeing the following... 1. The header 2. The intended contents of next.jsp 3. The GWT content previously viewed prior to redirecting to next.jsp. Questions: 1) The first question is, why? 2) I was wondering if I would need to do an elaborate DOM element handling here to fix this. Or have I been doing anything wrong? 3) Is this coupling even "feasible" to implement? Any knowledge enriching feedback would be greatly appreciated. Thanks so much, Vince --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
