synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mukund Balasubramanian" <muk...@infravio.com>
Subject Re: A few basic doubts..
Date Fri, 14 Oct 2005 19:25:47 GMT
Interestingly, I agree about the services being logically remote but stil believe that you
can, without losing architectural cleanliness and functionality, plug synapse into axis 2.
Why would we preclude that? 

it us commonly termed the "agent" or "co-deploy" model of a broker/mediator.




-----Original Message-----
From: Sanjiva Weerawarana <sanjiva@opensource.lk>
To: synapse-dev@ws.apache.org <synapse-dev@ws.apache.org>
Sent: Fri Oct 14 14:17:20 2005
Subject: Re: A few basic doubts..

The view we discussed in Cupertino was that Synapse, even though it
embeds Axis2, will not operate as a service runtime but only as a
mediation runtime. In other words, the actual services which are to be
mediated are logically remote.

Sanjva.

On Fri, 2005-10-14 at 14:00 +0530, Vikas wrote:
> Thanks Saminda..
> 
> Any thoughts abt the second pt..
> >> How will an existing service express the need for mediation i.e. say i 
> >> own service1 and service2 and want service1 to be mediated using 
> >> Synapse..Where do i say that?
> Or is it implicit that services needing mediation go into the repository in 
> our package structure[maybe axis2-repo].. cant it be external 
> services?[axis2 on another machine].
> 
> Thanks for the responses..
> 
> 
> ----- Original Message ----- 
> From: "Saminda Abeyruwan" <saminda@opensource.lk>
> To: <synapse-dev@ws.apache.org>
> Sent: Friday, October 14, 2005 1:15 PM
> Subject: Re: A few basic doubts..
> 
> 
> > Hi Vikas,
> >
> > At the end we are looking for package structure as follows,
> >
> > ...
> > [synapse-1.0]
> > synapse.xml
> > [mediators] All synapse mediators {SampleMedator.sar ..}
> > [qos] security.mar / sandesha.mar ....
> > [axis2-repo]
> > axis2.xml
> > [modules] synapse-1.0.mar / addressing.mar
> > [lib] *.jar
> > ...
> >
> > [] represent folders.
> >
> > So. synapse-xx.mar will contain the Rule engine. Since we don't need 
> > default dispatchers, our Dispatcher "SynapseDispatcher" will be configured 
> > via axis2.xml. Return/send paths will be available with using 
> > AxisEngine.receive(MC) and AxisEngine.send(MC) at appropriate locations. 
> > We have to come up with our own Deployers too.
> >
> > Saminda
> >
> >
> > Vikas wrote:
> >
> >> Hi!
> >> I was just curious..How is going to be
> >> Will Synapse be a pluggin into AXIS2 or will it be a superset comprising 
> >> AXIS2+other things??
> >> How will an existing service express the need for mediation i.e. say i 
> >> own service1 and service2 and want service1 to be mediated using 
> >> Synapse..Where do i say that?
> >> Thanks..
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: synapse-dev-help@ws.apache.org
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org



Mime
View raw message