[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Publishing remote services as WS
- From: Marcelo Mayworm <mayworm@xxxxxxxxx>
- Date: Thu, 17 Jun 2010 00:43:05 +0200
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Dg/qfw3ti5QYDd9xSObG0jmGz3tWUwoYE5k5fSbwnxiocsDm+NE/+owXzPW9kTmxv/ 2DX/V3Xhg/W8A3LBbWxXjgbLQoDb+7CYqwGLX+mJY0RG5jCWgRJIGtHGerYXtG0IOiVv m1eJ3oyAjNjVAYEeEuUMIYIyV9wsC3j5SsGw4=
I will create tomorrow a wiki page with an example and giving a description about the possibilities around that code, can be more useful for the ecf community(and maybe we can get more feedback from others).
But basically what it does is create on the fly a web service from any ECF remote service. There is a container adapter where you can pass a remote service and the code will deploy a web service through the Axis. There is a strong dependency with the Axis behind the scenes, in this moment I'm not considering to have other WS frameworks pluggable as well, but we can discuss about this "strategy".
On Wed, Jun 16, 2010 at 11:19 PM, Wim Jongman <wim.jongman@xxxxxxxxx>
Can you please give a description of the possibilities of this code? It sounds very interesting. Does your code make it possible to transform any remote server on the fly to a web service? What is the relation to Axis and are other ws frameworks pluggable as well?
I have been working in this the bug . I know that it is a busy time around Helios release, but if you guys have comments/suggestion around this implementation, it will be really welcome.
ecf-dev mailing list