[jira] Resolved: (SYNAPSE-520) Issue when security different security policies are applied to a proxy service and an associated endpoint

[ https://issues.apache.org/jira/browse/SYNAPSE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera resolved SYNAPSE-520. --- Resolution: Fixed Fix Version/s: 1.3 Assignee: Asankha C. Perera

[jira] Updated: (SYNAPSE-357) Provide a switch to send mediator to specify whether to build the envelope before sending or not

[ https://issues.apache.org/jira/browse/SYNAPSE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-357: -- Attachment: synapse-357.patch Provide a switch to

[jira] Commented: (SYNAPSE-524) Patches are not applied to the WAR distribution

[ https://issues.apache.org/jira/browse/SYNAPSE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12688622#action_12688622 ] Andreas Veithen commented on SYNAPSE-524: - Why into the system classpath?

[jira] Commented: (SYNAPSE-524) Patches are not applied to the WAR distribution

[ https://issues.apache.org/jira/browse/SYNAPSE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12688741#action_12688741 ] Asankha C. Perera commented on SYNAPSE-524: --- It could be any classpath, which

[jira] Resolved: (SYNAPSE-454) cant start synapse 1.1

[ https://issues.apache.org/jira/browse/SYNAPSE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera resolved SYNAPSE-454. --- Resolution: Won't Fix Assignee: Asankha C. Perera The default scripts would

[jira] Resolved: (SYNAPSE-456) dbloopup gives com.mysql.jdbc.CommunicationsException after idling a night

[ https://issues.apache.org/jira/browse/SYNAPSE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera resolved SYNAPSE-456. --- Resolution: Fixed Fix Version/s: 1.3 Assignee: Asankha C. Perera

[jira] Assigned: (SYNAPSE-496) Out Action always urn:mediateResponse instead of value returned from server

[ https://issues.apache.org/jira/browse/SYNAPSE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera reassigned SYNAPSE-496: - Assignee: Asankha C. Perera Out Action always urn:mediateResponse instead of

[jira] Commented: (SYNAPSE-496) Out Action always urn:mediateResponse instead of value returned from server

[ https://issues.apache.org/jira/browse/SYNAPSE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12688831#action_12688831 ] Asankha C. Perera commented on SYNAPSE-496: --- Bill, Can you explain this a bit

RE: VFS - Synapse Memory Leak

Hello Andreas, This all works really well. Streaming uses no memory at all. Got a java mediator also streaming payloads and with massive files never uses much more than 40K for Synapse. Using just the OUT_ONLY property set; uses much more memory but it stabilises and does not grow. Thanks.

[jira] Created: (SYNAPSE-525) Option to reserve addressing headers should be available

Option to reserve addressing headers should be available Key: SYNAPSE-525 URL: https://issues.apache.org/jira/browse/SYNAPSE-525 Project: Synapse Issue Type: Bug Components: