Rob

Andres

var testClass = new dojo.rpc.JsonService("/dojo_test_server/remoting/TestService");
testClass.mapMethod("key",8).addCallbacks(mapContentCallBack,contentErrBack);

This is enough to call a method on a server side bean and pass the result to the mapContentCallBack function.
It would be great to have something like this in spring 2.1
If you are interested, I would be happy to tidy up this implementation and add things like

• limited overloading support (based on the number of parameters)
• a ProxyFactoryBean

response.setContentType(this.getContentType());

1. Change the default content type to "application/json" (see RFC 4627).
2. Create the JSON object in a separate method (so it can be overridden in a subclass).
3. Add excludes and ignoreDefaultExcludes properties for use in the JSONObject.fromObject call.

Some notes on JsonView v2:

1. Please add an overloaded version of the createJSON method that has request and response parameters (e.g. for access to session data).
2. You should probably replace response.getWriter().write(json.toString()) with json.write(response.getWriter()).

Watch at the attached file JsonView.java.

Change:

protected void writeJSON(Map model, HttpServletRequest request, HttpServletResponse response) throws Exception {
JSON json = createJSON(model, request, response);
json.write(response.getWriter());
}

protected void renderMergedOutputModel(Map model, HttpServletRequest request, HttpServletResponse response) throws Exception {
response.setContentType(getContentType());
writeJSON(model, request, response);
}

http://sourceforge.net/project/showfiles.php?group_id=171425

M.H. Avegaart: I included your latest suggestion too.

http://spring-json.sourceforge.net/

Which implementation, or yet a third solution will be included in Spring 3?

I'm searching scalable, supportable solution for my projects to build a bridge between Browser and Spring's Services - I just want to be able to call remote method using Javacript and searching for an appropriate ServiceExporter.

In this issue we can see two solutions:

1) SmdServiceExporter
Client javascript library: DOJO
Service description: SMD format
Data transfer protocol: JSON-RPC
Server-side library: json-lib

2) JSONRPCServiceExporter.
Client javascript library: prototypejs
Service description: generated javascript code using prototypejs library
Data transfer protocol: JSON-serialized org.springframework.remoting.support.RemoteInvocation class
Server-side library: jsonrpc

Advantages of SmdServiceExporter:

• don't stick to exact javascript library on the client
• known formats are used (SMD and JSON-RPC)
• small size of source code

Disadvantages of SmdServiceExporter:

• no samples
• no unit tests
• no support for clients written in plain java

Advantages of JSONRPCServiceExporter:

• unit tests
• support for clients written in plain java+spring

Disadvantages of JSONRPCServiceExporter:

• too much javascript code (because of using poor prototypejs)
• stick to prototypejs while getting service description
• using "java-like" data transfer protocol style tied to RemoteInvocation class

Conclusion: I think SmdServiceExporter is better than JSONRPCServiceExporter for a long perspective because:

• dojo library is much better in use than prototypejs (avoid looking at UI and so on)
• SmdServiceExporter uses more standards than JSONRPCServiceExporter

But I found some difficulties compiling SmdServiceExporter with latest versions of dojo and json-lib and I think that it doesn't support complex types. So if Rogier would share us updated version it would be appreciated.

BR
Kirill

http://code.google.com/p/spring-jsonrpc/

It's based on the specification being written at:

http://groups.google.com/group/json-rpc

note: The code for this project is not the same code attached to this issue - it's completely different. I just figured I'd let everyone know that it exists