Gettin confused

[calos]

hello all,

Its really good tat this group is more active now, m also linkin this
all in one application. but i am gettin confused or one can say, not
able to get complete picture as a whole. my que is:

GWT is basically implementin AJAX, and its paradigm is one page do
everything, while in Spring i can use MVC architecture.Can i implement
MVC in GWT, by makin 4 or 5 modules (application) in GWT and wil link
it thru appname.gwt.xml file.

if i can how?? m havin vage idea, but if someone can put more light on
it, then i wil get the needed help.

Thanks in Advance..

[Rodrigo López Guzmán]

Hi Calos and all,

Spring does have full MVC support and it implements this for web applications. Traditional web applications.

But that is just a part of Spring and you can use it or not. My personal choice is not using it with GWT. The most valueable thing we can have with Spring is its ability to expose POJOs (plain old Java objects) as services, accessible through and from different architectures; one example? as a web service that complies with all the rules that GWT demands.

Doing this, we can have POJOs implementing our services. Any kind of service. We can use existing services. And we don't have to extend any GWT-specific class. That's real flexibility.

The only thing we have to do is to write a Spring service exporter that expose our services as GWT "remote services". Once we have this exporter, we don't have to ever worry again for implementing propiertary rules, such as GWT's requisites for remote services.

In the sample app. I included an exporter that I made myself, using ideas of some bloggers. I would like to change this with the implementation that is included in GWT-widgets.

I don't believe that using Spring's MVC could give real value to our project. It would be a very long discussion, but in short: I think Spring's MVC is content-oriented and what we need for AJAX, and specifically for GWT, is an RPC-oriented approach.

Finally, my suggestion is: forget about Spring's MVC; just use its IoC.


Regards,

Rodrigo.

[calos]

My ideas are also same, as ajax has combined many view, one can say,
as earlier the header or top part of site like heading and logo was
replicated in each page, but thanks to ajax one can overcome this
replication.

I didnt want to jump into d conclusion, so thanks for replyin mate, i
also made an sample application, but its very low level, n it was done
thru POJO only..