See https://hudson.apache.org/hudson/job/Synapse%20-%20Trunk/2674/
-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
[
https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912858#action_12912858
]
Hiranya Jayathilaka commented on SYNAPSE-618:
-
Hi Charith,
A few points to
Planning to branch off in the night LKT.
Ruwan
On Mon, Sep 20, 2010 at 11:46 AM, Hiranya Jayathilaka
hiranya...@gmail.comwrote:
On Mon, Sep 20, 2010 at 11:43 AM, Andreas Veithen
andreas.veit...@gmail.com wrote:
The Axis2 1.5.2 Maven artifacts started to appear on Maven central.
The
[
https://issues.apache.org/jira/browse/SYNAPSE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton resolved SYNAPSE-357.
--
Fix Version/s: 2.0
Resolution: Fixed
Fixed for the 2.0 and on the trunk
Provide a
[
https://issues.apache.org/jira/browse/SYNAPSE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912887#action_12912887
]
Ruwan Linton commented on SYNAPSE-357:
--
Folks, we have the ability to specify
Issue when using the DynamicLordBalancingEndpoint to handl REST message.
Key: SYNAPSE-686
URL: https://issues.apache.org/jira/browse/SYNAPSE-686
Project: Synapse
Issue
[
https://issues.apache.org/jira/browse/SYNAPSE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton resolved SYNAPSE-522.
--
Resolution: Fixed
This has been fixed for the 2.0 release with the properties support for
[
https://issues.apache.org/jira/browse/SYNAPSE-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Jayasoma updated SYNAPSE-686:
-
Attachment: patch.txt
Herewith I have attached patch which provides a workaround for
[
https://issues.apache.org/jira/browse/SYNAPSE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912900#action_12912900
]
Sameera Jayasoma commented on SYNAPSE-683:
--
Thanks Supun and Hiranya.
Improvements to HTTP Redirection(3xx) handling in Synapse
-
Key: SYNAPSE-687
URL: https://issues.apache.org/jira/browse/SYNAPSE-687
Project: Synapse
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SYNAPSE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Jayasoma updated SYNAPSE-687:
-
Attachment: patch.txt
Here, we are changing only the host name and the port of the new
I have added the required artifacts into the wso2 m2 repo at (
http://dist.wso2.org/maven2). You'll need to do an online build once to
bring those artifacts into your local maven repo.
Rajika
On Mon, Sep 20, 2010 at 2:20 PM, Rajika Kumarasiri raj...@wso2.com wrote:
Some time back we discussed
[
https://issues.apache.org/jira/browse/SYNAPSE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-626.
---
Resolution: Fixed
Fixed in r999310.
Rajika
Moving into commons-vfs trunk for vfs
[
https://issues.apache.org/jira/browse/SYNAPSE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-507.
---
Fix Version/s: 2.0
Resolution: Fixed
I have fixed the issue - SYNAPSE-626,
[
https://issues.apache.org/jira/browse/SYNAPSE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reassigned SYNAPSE-560:
-
Assignee: Rajika Kumarasiri
JmsCorrelationId set incorrectly for response
Rajika, Please verify the VFS samples and the possible scenarios. If you
have already verified them please ignore this :-)
Thanks,
Ruwan
On Tue, Sep 21, 2010 at 4:42 PM, Rajika Kumarasiri raj...@wso2.com wrote:
I have added the required artifacts into the wso2 m2 repo at (
[
https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charith Dhanushka Wickramarachchi updated SYNAPSE-618:
--
Attachment: messagestore_patch_9.diff
Hi Hiranya,
I
[
https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12913109#action_12913109
]
Charith Dhanushka Wickramarachchi edited comment on SYNAPSE-618 at 9/21/10 1:48
PM:
Hi,
In the current trunk the PriorityExecutor is not a SynapseArtifact. but IMHO
since its a synapse configuration element it need to be a synapse artifact.
But to make it a Synapse Artifact we need to make the commons module depend
on synapse-core which will introduce a cyclic dependency.
So i
Moving Synapse Artifact into the commons is not a good solution as that will
result in core API being moved to commons. We need to think through and come
to a conclusion.
Thanks,
Ruwan
On Tue, Sep 21, 2010 at 11:47 PM, Charith Wickramarachchi
charith.dhanus...@gmail.com wrote:
Hi,
In the
Folks, the branching is getting delayed a bit since I need to do some
changes to the synapse core to fix some API level issues, once that is done
I will branch off for the 2.0 probably within the next few hours.
In the mean time I heard back from the rampart community and we should be
able to use
21 matches
Mail list logo
