On Wed, Sep 15, 2010 at 11:33 PM, lalit <lalit.bhatt@gmail.com> wrote:
Deepak - I have used the following structure
SpringApplicationContext, SpringGwtRemoteServiceServlet ,
PersonServiceImpl go into the server side code.
The interfaces PersonService and PersonServiceAsync become part of
GWT client side code.
Regarding wsdl files consumption see the section on JAX-WS here
http://www.lalitbhatt.com/tiki-index.php?page=JAX-WS especiall JAX-WS
client side section. This approach uses JAX-WS approach.
For data binding you can use JAXB. The details can be seen here
http://www.lalitbhatt.com/tiki-index.php?page=JAXB. JAX-WS anyway uses
it internally.
Also just a disclaimer, the approach I took is as per Spring4GWT
project so it's there idea.
Jason- I looked into your approach and conceptually they look similar
in terms of that you are redirecting the request to Spring MVC
infrastructure. IMHO the aprroach I took as per Sping4GWT is better as
one does not have to carry the SpringMVC baggage.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
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 google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment