Hello Allen

Following up on Kersten's post, a few words about the SL [1]. The main
aim was to create a seamless, non-invasive integration of the RPC
protocol and services. From our POV, a service is a business object
that should not import or otherwise depend on RPC or other APIs, since
a service passes only domain objects (or domain view objects) between
the client and the server. Hence the SL uses the notion of exporters
and handlers, which provide in runtime an RPC facade to existing
spring managed beans and glue them to the web interface. In the
dowload section [2] you'll find a short demo.

[1] http://gwt-widget.sourceforge.net/
[2] 
http://sourceforge.net/project/showfiles.php?group_id=169692&package_id=204985&release_id=623028

On Nov 7, 7:29 pm, Allen Firstenberg <[EMAIL PROTECTED]> wrote:
> I've gone through the documentation, and while I see a lot of "here is
> how you can do it with spring", most seem to be referencing hacks and
> work-arounds that were necessary in 1.3.  In 1.4, there was supposed
> to be changes in the GWT framework to make spring integration easier,
> and demonstration code somewhere to illustrate this - but I don't seem
> to be able to find either.  Am I just misunderstanding Issue 389?
>
> Thanks for any pointers.
>
> Allen
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to