GWT RPC Supported Service Bus Project

Hi All,
I'm sending this post to ask your opinions about a new open source
project proposal. As you know GWT uses its own propriety protocol for
RPC as recommended way. Therefore remote services need to be written
as servlets and mapped to a URL under web application context.

However many enterprise implements their services as a separate
layer and they uses different techniques such as EJB (RMI/IIOP), Web
Services (SOAP/HTTP). (I do also support idea of separation of
concerns. Keeping business logic layer as separate from UI layer is a
wise idea.)

My project proposal is writing a service bus to simply access to
existent services in the enterprise. Indeed the project is mostly
ready and we're discussing internally whether to publish it as an open
source project or not. Here are the features that we're already
included in the project:

• A single dispatcher servlet to access all backend services.
Therefore all requests will be sent to a single URL under the base web
application URL.
• Adapters for EJB, Web Services, POJO and Spring. Ability to develop
custom adapters (such as mainframe, legacy apps like SAP, Siebel)
• Implicit service registry to query service meta data and locate
service instances
• Declarative service definitions without additional coding. Removing
all server side servlet implementation necessity and expose existing
services to GWT by using a simple xml configuration file.
• Keeping the GWT client side as the same. Accessing services through
client asynchronous service interfaces as we usually do it in GWT.
• Transformation between java classes with transformation maps. For
example transforming an incoming GWT Rpc parameter to a java method
complex parameter type or transforming a complex method return type to
a GWT Serializable complex type
• Implicit JEE security integration: Defining authentication &
authorization & transport layer security policies for service
operations.
• Ability to introduce Interceptors around remote method calls, so
that handling all common concerns like auditing, logging, security
inside interceptors

So I have two questions for those who would like to spend some
time for answering:

1. Do you see a necessity to having a similar capability? Would you
like to have described capabilities as an open source project?
2. What else would you put in that project as feature?

Many thanks for your time and effort in advance.

Serhat Dirik

--
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.