Deepal
Actually, I was more thinking about:
Client->Synapse->Synapse->Axis2
Rather than
Client->Axis2->Axis2
Although we could do that, we'd just be replicating something we
already do very well in Synapse.
The custom deployer idea is pretty cool. Can you explain a little how
it works? I haven't really looked at that.
One other thing that would be cool in Synapse is to automatically
enable any *locally* deployed services (in the local Axis2 instance)
as endpoints. We could make sure they get called using the local
transport too. That way, any useful stuff like the CORBA deployer
could be exposed very simply via Synapse.
Paul
On 7/25/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
Hi Paul ,
In Axis2 we can solve this problem by writing a custom Deloyer, say we
have the following use case
- Company A has a web service called "foo" and its wsdl is foo.wsdl
- Company B needs to expose the same service
- What it do is when ever it get a request it will forward that
to Company A and send the response back .
So when we want to do so , we can write a small configuration file
specifying the wsdl location and deploy , then our custom deployer
will pick that and create a proxy service for that. We can come up the
structure of the configuration file and the file extension.
Thanks
Deepal
> One thing that I think would be nice would be to be able to make it
> easier to link one Synapse instance to another. What does that mean?
>
> Well, I know we can share the config with the repository. But I'm
> thinking suppose I just want to talk between two systems. Suppose I
> have one Synapse server exposing 5 proxy services, I'd like them
> automatically available as endpoints in my other Synapse instance. In
> fact I'd also like the same with Axis2. If I have an Axis2 server, it
> would be equally cool to expose all those services as endpoints in
> Synapse too.
>
> For the S->S case, imagine I have two companies. Company A exposes a
> set of internal services using Synapse. I'm in Company B and I want
> those. I should be able to point my Synapse at theirs and have it all
> mesh nicely.
>
> I guess we could do this in a standard way or our own way. Ideally we
> would be so good at consuming WS-P that once we have the WSDLs we can
> then work easily. So it might just be a need to get a list of WSDLs
> via HTTP and then add those as endpoints automatically.
>
> There used to be spec for that (WS Inspection) but it seems dead
> looking at the fact the IBM link is 404 Not Found!
>
> It would also be nice to have some kind of ping service between nodes
> to know they are alive, maybe for load-balance and failover purposes
> too.
>
> Thoughts?
>
> Paul
>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
