Thanks Keith, I will give Synapse and WS02 ESB a look. Your point about
lightweight is key. We are considering high message volumes and don't want
artifical latency and heft in processing messages.
On Tue, Oct 21, 2008 at 7:32 PM, keith chapman [EMAIL PROTECTED]wrote:
Hi Barry,
I'd rather
Thanks Deepal, this aligns with our thinking here so good to here your
views. If you know of any examples out there, I would be interested to see.
On Tue, Oct 21, 2008 at 4:41 PM, Deepal jayasinghe [EMAIL PROTECTED]wrote:
Barry Alexander wrote:
Other than you're on your own advice, can you
Hi,
Is there a recommended or commonly used approach to versioning a service
(SOAP, doc/literal) that is to be deployed on Axis2? I'm trying to
provide some means of not breaking consumers of an existing service if I
have to deploy a new version that isn't backwards compatible. We're
using
Howell, David wrote:
Hi,
Is there a recommended or commonly used approach to versioning a
service (SOAP, doc/literal) that is to be deployed on Axis2? I’m
trying to provide some means of not breaking consumers of an existing
service if I have to deploy a new version that isn’t backwards
Other than you're on your own advice, can you provide some guidelines or
best practices regarding versioning?
I thought this was an excellent question and currently of hot discussion
with my co-workers.
Some further questions:
Should message version be embedded as part of SOAP headers
that manage
the deprecation and removal of support for past versions could be used
to handle that.
-Original Message-
From: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 4:42 PM
To: axis-user@ws.apache.org
Subject: Re: Versioning a service deployed on Axis2
Hi Barry,
I'd rather do it in this way. Deploy the two versions of the service as two
separate services in Axis2. But would front Axis2 with a mediation engine,
(you could use Apache Synapse or the WSO2
ESBhttp://wso2.org/projects/esb/java[1] which is built on Apache
Synapse for this purpose).
