[
https://issues.apache.org/activemq/browse/CAMEL-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63202#action_63202
]
James E commented on CAMEL-185:
-------------------------------
Recently noticed a similar mechanism seems to exist for the 'soafaces' project,
dubbed the UniversalClient API; "An API to use from any GWT client to make SOA
service calls with no RPC." Not sure if it only works for Mule endpoints or
not based on the following.
http://code.google.com/p/soafaces/wiki/UniversalClient
"No need to write GWT RPC code anymore. Use the UniversalClient API to talk
with POJO services that are packaged in your application server and/or talk
with Mule accessible services/endpoints all across your enterprise and
internet. Your GWT application will have convenient access to messaging
services (SOAP, JMS, ESB ...etc) that can return JavaBeans or JSON objects back
to the GWT client. All marshaling is handled by the framework."
> Support GWT RPC encoding for invoking Beans
> -------------------------------------------
>
> Key: CAMEL-185
> URL: https://issues.apache.org/activemq/browse/CAMEL-185
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: Hiram Chirino
> Priority: Minor
> Fix For: Future
>
>
> It would be cool if GWT RPC calls could be handled and routed VIA camel. For
> more info on GWT RPC see:
> http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.RemoteProcedureCalls.html
> They have nice RPC class that allows frameworks to easily encode and decode
> it method invocations.. see:
> http://code.google.com/webtoolkit/documentation/com.google.gwt.user.server.rpc.RPC.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
