[
https://issues.apache.org/jira/browse/SYNAPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865612#action_12865612
]
Supun Kamburugamuva commented on SYNAPSE-593:
-
This outSequence foo is defined
Agreed! we should make sure that we generate a unique name consistently. Let
me do that bit of code :-) if you know the problem, and if it is not NP
complete, we can solve it ;-)
If we have spend the time that we spend on writing mails to this thread to
write that bit of code now it is solved.
Th
[
https://issues.apache.org/jira/browse/SYNAPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865610#action_12865610
]
Ruwan Linton commented on SYNAPSE-593:
--
No, when you have a proxy and the out sequenc
+1
On Thu, May 6, 2010 at 11:24 PM, Andreas Veithen
wrote:
> That's a longstanding issue, but until now I have never been able to
> figure out whether it's a problem in the test kit or a bug in the
> transport. Interestingly, after adding the Axis2 transports to the
> Hudson build last week, I no
The reason we wanted a name in the first place was to make sure that
endpoints work correctly in a clustered environment. In a
clustered environment same endpoint in different instances require the same
name to work properly because they exchange the state information using the
name as the key.
So
[
https://issues.apache.org/jira/browse/SYNAPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865576#action_12865576
]
Supun Kamburugamuva commented on SYNAPSE-593:
-
Let me explain my thinking in b
