axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chathura Ekanayake" <>
Subject Re: [Axis2] Web service with no implementation
Date Tue, 08 May 2007 06:44:53 GMT
Hi Daniel,

I think combination of both Axis2 and Synapse (
would be the ideal solution for your problem.
You can do WSDL first development and expose your service in HTTP transport
using Axis2.

Then you can use Synapse in between your client and the service, therefore
client can just forward messages to Synapse.
Synapse can be configured to route those messages to the service
implementation, even with additional functionalities like
transformations, filtering, etc.

As you have mentioned, client can send messages to Synapse using a JMS
queue, where Synapse routes them to the service
implementation exposed in HTTP.

I would recommend you to join the Synapse user list ( and send your problem with more detailed use


On 5/8/07, Daniel Feist <> wrote:
> Hi,
> I am attempting to implement a web-services using a web service stack such
> as axis in order to export functionality through a web service defined by
> wsdl but with a twist...I want to integrate this into a message based esb
> type architecture.
> What i want to do is the following:
> 1) WSDL first development
> 2) Http transport
> 3) Phase/handlers as normal
> 4) BUT receiver does not invoke a service but rather forwards message
> (SOAP payload, as defined in WSDL) to a message broker ( e.g. JMS queue)
> where it will be routed to the service implementation.
> I don't want to attempt to do this with axis1, and at having quickly
> looking at other web service stacks it doesn't look particularly easy.  I
> was wondering if with the new more open, message based architecture of axis2
> this could be implemented, even if it means using axis2 programatically
> instead of via config file and where I should start looking...?
> thanks,
> Dan

View raw message