in your decision.
Jay Jaeger
-Original Message-
From: Ruwan Linton [mailto:ruwan.lin...@gmail.com]
Sent: Sunday, November 21, 2010 10:38 PM
To: u...@synapse.apache.org
Cc: dev@synapse.apache.org
Subject: Re: Synapse configuration namespace
OK
We need to do the 2.0.0 release ASAP
-Original Message-
From: Ruwan Linton [mailto:ruwan.lin...@gmail.com]
Sent: Sunday, November 21, 2010 10:38 PM
To: u...@synapse.apache.org
Cc: dev@synapse.apache.org
Subject: Re: Synapse configuration namespace
OK
We need to do the 2.0.0 release ASAP, it has been dragging way too much
I'm +1 for a namespace change if we have changed the semantics of the
synapse configuration language at a broader level. But since we haven't done
any major change to the configuration language im 0 on this. So my opinion
solely depend on what users will think and how they will get affected.
...@gmail.com]
Sent: Sunday, November 21, 2010 3:25 PM
To: dev@synapse.apache.org
Cc: u...@synapse.apache.org
Subject: Re: Synapse configuration namespace
I'm +1 for a namespace change if we have changed the semantics of the synapse
configuration language at a broader level. But since we haven't done
On Sun, Nov 21, 2010 at 9:22 PM, Hubert, Eric eric.hub...@foxmobile.comwrote:
Well, I think I have to agree with Sanjiva’s statement about the meaning
of namespaces for an end user. I also do not know many people really caring
about namespaces as long as those namespaces are not causing any
OK
We need to do the 2.0.0 release ASAP, it has been dragging way too much, and
I don't want to delay it because of a namespace change and do not want to
call another vote for this. Let me take your votes from this thread and try
to summarize the decision on this.
If I have interpreted this
On Mon, Nov 22, 2010 at 10:07 AM, Ruwan Linton ruwan.lin...@gmail.com wrote:
OK
We need to do the 2.0.0 release ASAP, it has been dragging way too much, and
I don't want to delay it because of a namespace change and do not want to
call another vote for this. Let me take your votes from
-Original Message-
From: Ruwan Linton [mailto:ruwan.lin...@gmail.com]
Sent: Monday, November 08, 2010 4:10 AM
To: dev@synapse.apache.org
Cc: u...@synapse.apache.org
Subject: Re: Synapse configuration namespace
Since we were planing for a 2.0 release, I thought it is OK to do
features.
Regards,
Eric
-Original Message-
From: Ruwan Linton [mailto:ruwan.lin...@gmail.com]
Sent: Monday, November 08, 2010 4:10 AM
To: dev@synapse.apache.org
Cc: u...@synapse.apache.org
Subject: Re: Synapse configuration namespace
Since we were planing for a 2.0 release
,
Eric
-Original Message-
From: Ruwan Linton [mailto:ruwan.lin...@gmail.com]
Sent: Monday, November 08, 2010 4:10 AM
To: dev@synapse.apache.org
Cc: u...@synapse.apache.org
Subject: Re: Synapse configuration namespace
Since we were planing for a 2.0 release, I thought
On Sat, Nov 20, 2010 at 8:58 PM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Also, in general using namespaces to version XML schemas is generally
considered bad practice.
I don't think we are doing a versioning of the synapse configuration schema
with the namespace, anyway most of
Then
I found more incompatible changes :-(
https://issues.apache.org/jira/browse/SYNAPSE-693?focusedCommentId=12934217page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12934217
I do not understand why you are opposing to changing the namespace with 2.0
release, while we
...@synapse.apache.org
Subject: Re: Synapse configuration namespace
Since we were planing for a 2.0 release, I thought it is OK to do backwards
incompatible changes and document them properly. Well we have some changes
in the API as well, which will affect the existing mediators and so forth.
Do you
?
(Maybe this is too late now for the release ... in which case there's no
point doing it later.)
Sanjiva.
On Mon, Apr 26, 2010 at 10:22 PM, Ruwan Linton ruwan.lin...@gmail.com
wrote:
Folks,
We have been using the http://ws.apache.org/ns/synapse as the synapse
configuration namespace
namespace, since synapse was graduated on to the WS project
and we didn't want to introduce a configuration incompatibility because of
becoming a new TLP, and with the new 2.0 release planned to be out, I am
planning to change the synapse configuration namespace to a more meaning
full namespace
this is too late now for the release ... in which case there's
no
point doing it later.)
Sanjiva.
On Mon, Apr 26, 2010 at 10:22 PM, Ruwan Linton ruwan.lin...@gmail.com
wrote:
Folks,
We have been using the http://ws.apache.org/ns/synapse as the synapse
configuration namespace, since
configuration namespace, since synapse was graduated on to the WS project
and we didn't want to introduce a configuration incompatibility because of
becoming a new TLP, and with the new 2.0 release planned to be out, I am
planning to change the synapse configuration namespace to a more meaning
full
ruwan.lin...@gmail.comwrote:
Folks,
We have been using the http://ws.apache.org/ns/synapse as the synapse
configuration namespace, since synapse was graduated on to the WS project
and we didn't want to introduce a configuration incompatibility because of
becoming a new TLP, and with the new 2.0
wrote:
On Mon, Apr 26, 2010 at 10:22 PM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Folks,
We have been using the http://ws.apache.org/ns/synapse as the synapse
configuration namespace, since synapse was graduated on to the WS project
and we didn't want to introduce a configuration
://ws.apache.org/ns/synapse as the synapse
configuration namespace, since synapse was graduated on to the WS project
and we didn't want to introduce a configuration incompatibility because of
becoming a new TLP, and with the new 2.0 release planned to be out, I am
planning to change the synapse
://ws.apache.org/ns/synapse as the synapse
configuration namespace, since synapse was graduated on to the WS project
and we didn't want to introduce a configuration incompatibility because of
becoming a new TLP, and with the new 2.0 release planned to be out, I am
planning to change the synapse
Folks,
We have been using the http://ws.apache.org/ns/synapse as the synapse
configuration namespace, since synapse was graduated on to the WS project
and we didn't want to introduce a configuration incompatibility because of
becoming a new TLP, and with the new 2.0 release planned to be out, I
22 matches
Mail list logo
