Re: svn commit: r1909778 - in /synapse/site/dev: developer-guide.html release-process.html

These pages are generated from files in https://github.com/apache/synapse/tree/master/modules/documentation/src/site/xdoc/dev. Shouldn't those files have been updated first? Andreas On Fri, May 12, 2023 at 5:48 PM wrote: > Author: isudana > Date: Fri May 12 16:48:49 2023 > New Revision: 1909778

Re: Error when amending WSDL Endpoint serialization unit tests

I think the problem is your change in WSDLEndpointFactory.createEndpoint, specifically this line: wsdlEndpoint.setWsdlURI(injectEnvironmentVariables(wsdlURI).trim()); A few lines after that, the original wsdlURI is used in the following expression: new URL(wsdlURI) That results in an error. An

Re: Synapse source is migrated to Github

It looks like this was never set up properly. https://github.com/apache/synapse/commit/07c91f87e739bd647b11294ebfa94d684774648f should fix that. Andreas On Mon, Aug 19, 2019 at 5:38 AM Vanjikumaran Sivajothy < vanjikuma...@gmail.com> wrote: > We were listening into comm...@synapse.apache.org for

[jira] [Commented] (SYNAPSE-1102) Performance save - Replace instances of Math.Random with Random.nextDouble

[ https://issues.apache.org/jira/browse/SYNAPSE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837798#comment-16837798 ] Andreas Veithen commented on SYNAPSE-1102: -- Your patch replaces {{Math.ra

Re: [VOTE] Release Apache Synapse 3.0.0 Take 2

.0.0 and 3.0.1 a few times between > take 1 and take 2. > > > Thanks, > Ravi > > On 4 January 2017 at 10:08, Andreas Veithen > wrote: >> >> There is at least one file that still contains a SNAPSHOT version: >> >> >> modules/packaging/package-arche

Re: [VOTE] Release Apache Synapse 3.0.0 Take 2

There is at least one file that still contains a SNAPSHOT version: modules/packaging/package-archetype/src/main/resources/archetype-resources/pom.xml Andreas On Tue, Jan 3, 2017 at 10:27 PM, Ravi Undupitiya wrote: > > We have now had the voting open for more than 72 hours. There are 9 +1 (>3

[jira] [Commented] (SYNAPSE-1092) Create Dockerfile and base image for synapse

[ https://issues.apache.org/jira/browse/SYNAPSE-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796229#comment-15796229 ] Andreas Veithen commented on SYNAPSE-1092: -- Why not OpenJDK? >

Re: [VOTE] Release Apache Synapse 3.0.0

I will be partially offline for a couple of days and have a closer look on Monday or Tuesday. Andreas On Fri, Dec 30, 2016 at 3:51 PM, Ravi Undupitiya wrote: > This is a call for votes to release Apache Synapse 3.0.0 > > Please review the distribution artifacts: > https://dist.apache.org/repos/d

Re: svn commit: r1776536 - /synapse/branches/3.0/pom.xml

Use project.version instead of synapse.version, or if you don't want to change various POMs, use: ${project.version} Andreas On Fri, Dec 30, 2016 at 10:04 AM, wrote: > Author: ravi > Date: Fri Dec 30 10:04:31 2016 > New Revision: 1776536 > > URL: http://svn.apache.org/viewvc?rev=1776536&view=r

Re: svn commit: r1776523 - in /synapse/branches/3.0: modules/core/src/test/resources/synapse-libraries/assembly/filter.properties pom.xml

The fact that you need to update the version number in filter.properties would mean that you can't use maven-release-plugin to manage the release end-to-end. However, I can't find any usages of the product.name and product.version properties, so it's probably safe to remove that file entirely. And

Re: svn commit: r1776510 - /synapse/branches/3.0/

se-process.html > > On 30 December 2016 at 12:06, Andreas Veithen > wrote: >> >> Why? >> >> Andreas >> >> On Fri, Dec 30, 2016 at 12:59 AM, wrote: >> > Author: ravi >> > Date: Fri Dec 30 00:59:14 2016 >> > New Revision: 177651

Re: svn commit: r1776510 - /synapse/branches/3.0/

Why? Andreas On Fri, Dec 30, 2016 at 12:59 AM, wrote: > Author: ravi > Date: Fri Dec 30 00:59:14 2016 > New Revision: 1776510 > > URL: http://svn.apache.org/viewvc?rev=1776510&view=rev > Log: > Creating 3.0 branch from current trunk > > Added: > synapse/branches/3.0/ (props changed) >

Re: svn commit: r1749134 - in /synapse/dist: ./ HEADER.html README.html

in > SYNAPSE-993, I believe we don't really need to maintain a dist folder inside > synapse svn location. I will delete dist if that's the case. > > On 19 June 2016 at 21:33, Andreas Veithen wrote: >> >> On Sun, Jun 19, 2016 at 8:19 AM, wrote: >> > Author: rav

Re: svn commit: r1749134 - in /synapse/dist: ./ HEADER.html README.html

On Sun, Jun 19, 2016 at 8:19 AM, wrote: > Author: ravi > Date: Sun Jun 19 07:19:08 2016 > New Revision: 1749134 > > URL: http://svn.apache.org/viewvc?rev=1749134&view=rev > Log: > Adding dist folder for SvnPubSub > > Added: > synapse/dist/ > synapse/dist/HEADER.html > synapse/dist/REA

[jira] [Commented] (SYNAPSE-993) Use Svnpubsub for Site and Dists

[ https://issues.apache.org/jira/browse/SYNAPSE-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15338587#comment-15338587 ] Andreas Veithen commented on SYNAPSE-993: - Yes, release candidates are uplo

[jira] [Commented] (SYNAPSE-1041) xml string set in the Script mediator is not honored as OM in Fault mediator

[ https://issues.apache.org/jira/browse/SYNAPSE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319165#comment-15319165 ] Andreas Veithen commented on SYNAPSE-1041: -- {noformat} +/** +

[jira] [Resolved] (SYNAPSE-485) Replace the use of sun.misc.Service with something available on other JDKs

[ https://issues.apache.org/jira/browse/SYNAPSE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-485. - Resolution: Fixed Assignee: Andreas Veithen (was: Paul Fremantle) Fix

Re: svn commit: r1746027 - in /synapse/trunk/java: ./ modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/util/ modules/transports/core/nhttp/src/test/java/org/apache/syn

... unless of course the release fails because we don't succeed to get the required 3 votes (which is currently the case). Andreas On Sun, May 29, 2016 at 9:33 PM, Andreas Veithen wrote: > We are going to release with 1.7.3. > > Andreas > > On Sun, May 29, 2016 at 7:54 PM,

Re: Synapse 2.2.0 release and future

On May 30, 2016 8:37 PM, "Hiranya Jayathilaka" wrote: > > > > On May 30, 2016, at 9:13 AM, Auke Schrijnen wrote: > > > > Hiranya, Andreas, others, > > > > It looks like the mail from Brett worked as a wakeup call, the seems to be more > > activity in the last week than the last year. > > > > I've

[jira] [Commented] (SYNAPSE-1023) DISABLE_CHUNKING property is not honored in the response path of PT

[ https://issues.apache.org/jira/browse/SYNAPSE-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306847#comment-15306847 ] Andreas Veithen commented on SYNAPSE-1023: -- {noformat} +private

Re: svn commit: r1746027 - in /synapse/trunk/java: ./ modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/util/ modules/transports/core/nhttp/src/test/java/org/apache/syn

We are going to release with 1.7.3. Andreas On Sun, May 29, 2016 at 7:54 PM, Hiranya Jayathilaka wrote: > Hi Andreas, > > How is this going to impact the release process, if we are to release with > Axis2 1.7.2? > > Thanks, > Hiranya > >> On May 29, 2016, at 8:54 AM, veit...@apache.org wrote: >

Re: svn commit: r1746052 - in /synapse/trunk/java/modules/transports/core/nhttp: ./ src/main/java/org/apache/synapse/transport/nhttp/ src/main/java/org/apache/synapse/transport/passthru/ src/main/java

It's the other way round: spaces, not tabs. Andreas On Sun, May 29, 2016 at 8:28 PM, wrote: > Author: dushan > Date: Sun May 29 19:28:02 2016 > New Revision: 1746052 > > URL: http://svn.apache.org/viewvc?rev=1746052&view=rev > Log: > correcting code styles for the fix SYNAPSE-1025 > > Modified:

Re: svn commit: r1746042 - in /synapse/trunk/java/modules/transports/core/nhttp: ./ src/main/java/org/apache/synapse/transport/nhttp/ src/main/java/org/apache/synapse/transport/passthru/ src/main/java

Please note that we use spaces, not tabs for indentation. Andreas On Sun, May 29, 2016 at 7:27 PM, wrote: > Author: dushan > Date: Sun May 29 18:27:45 2016 > New Revision: 1746042 > > URL: http://svn.apache.org/viewvc?rev=1746042&view=rev > Log: > merging https://issues.apache.org/jira/browse/S

[jira] [Resolved] (SYNAPSE-1027) Deferred building regression due to pass through handling

[ https://issues.apache.org/jira/browse/SYNAPSE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-1027. -- Resolution: Fixed Fix Version/s: 3.0 > Deferred building regression due

[jira] [Commented] (SYNAPSE-1027) Deferred building regression due to pass through handling

[ https://issues.apache.org/jira/browse/SYNAPSE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305882#comment-15305882 ] Andreas Veithen commented on SYNAPSE-1027: -- There is some interference

[jira] [Assigned] (SYNAPSE-1027) Deferred building regression due to pass through handling

[ https://issues.apache.org/jira/browse/SYNAPSE-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned SYNAPSE-1027: Assignee: Andreas Veithen (was: Hiranya Jayathilaka) > Deferred build

[jira] [Commented] (SYNAPSE-1012) Add Xpath Base64 decode function

[ https://issues.apache.org/jira/browse/SYNAPSE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304719#comment-15304719 ] Andreas Veithen commented on SYNAPSE-1012: -- byte[] decodedValue = new Ba

[jira] [Commented] (SYNAPSE-1012) Add Xpath Base64 decode function

[ https://issues.apache.org/jira/browse/SYNAPSE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304707#comment-15304707 ] Andreas Veithen commented on SYNAPSE-1012: -- Try to write a unit test that

[jira] [Reopened] (SYNAPSE-1012) Add Xpath Base64 decode function

[ https://issues.apache.org/jira/browse/SYNAPSE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reopened SYNAPSE-1012: -- That line of code doesn't make sense: decodedValue = new Base64().decode(value.get

[jira] [Commented] (SYNAPSE-1018) Migrating from Log4j 1.x to Apache Log4j 2

[ https://issues.apache.org/jira/browse/SYNAPSE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304607#comment-15304607 ] Andreas Veithen commented on SYNAPSE-1018: -- Synapse uses Commons Log

Re: Synapse 2.2.0 release and future

On Thu, May 19, 2016 at 7:47 AM, Auke Schrijnen wrote: > Hi all! > > We are sad to see the development of Synapse slowly stop. We use Synapse in > our integration platform since 2012 which has proved it’s use and still > perfectly does the job. Over the years we had to apply some patches, > esp

Re: Willing to help with PMC

elopment and to invest time into a release. > And for that, I have as much time as required. And I might have time > going forward for more, although that will require some work on my part to > get more familiar with the Synapse project itself. > > Does that help? > > Tha

Re: Willing to help with PMC

How much effort would you be willing to put into this? To stay alive this project needs to make progress towards a release. I think that the code itself is in a releasable state, and with the release of Axis2 and Rampart 1.7.0 there are no more snapshot dependencies. On the other hand, the release

Re: svn commit: r1731416 - /synapse/trunk/java/modules/core/src/test/java/org/apache/synapse/eventing/builders/MessageBuilderTest.java

On Sat, Feb 20, 2016 at 3:52 PM, Isuru Udana wrote: > Hi Andreas, > > It looks like following two tests are failing as > testSubscriptionMessageBuilderScenarioFive is getting executed before them. > > testSubscriptionMessageBuilderScenarioFour(org.apache.synapse.eventing.builders.MessageBuilderTes

Re: Build problems

On Fri, Feb 19, 2016 at 4:41 PM, Roger and Beth Whitcomb wrote: > Hi all, > I've just now pulled the latest source (apparently 2.2.0-SNAPSHOT > version) and tried to build according to the instructions here: > http://synapse.apache.org/dev/developer-guide.html > But I'm getting several bui

Re: Build problems

Hi Roger, I saw your message on bo...@apache.org. You should probably post that here as well because not everybody watches that list. Andreas On Fri, Feb 19, 2016 at 4:41 PM, Roger and Beth Whitcomb wrote: > Hi all, > I've just now pulled the latest source (apparently 2.2.0-SNAPSHOT > versi

Re: Time to Call it a Day?

I think that the primary reason for slowness is here: http://svn.apache.org/viewvc/axis/axis2/java/core/trunk/modules/integration/pom.xml?revision=1686544&view=markup#l492 Andreas On Thu, Jul 2, 2015 at 3:29 AM, Deepal jayasinghe wrote: > Another big item would be to reduce time it takes for Ax

Re: Time to Call it a Day?

There is another area where help would be welcome. I did some work recently to make the build succeed on Java 7, and I know that it works on Mac OS X (because I use that OS) and Linux (because the build works on Jenkins). On the other hand, Deepal reported that he had/has problems building on Windo

[jira] [Resolved] (SYNAPSE-283) Create Debian packages for Synapse

[ https://issues.apache.org/jira/browse/SYNAPSE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-283. - Resolution: Won't Fix > Create Debian packages for

[jira] [Commented] (SYNAPSE-990) Endpoint Address Timeout per method/function level

[ https://issues.apache.org/jira/browse/SYNAPSE-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072237#comment-14072237 ] Andreas Veithen commented on SYNAPSE-990: - What about using local-name($

Re: svn commit: r1610262 - /synapse/trunk/java/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/connections/TargetConnections.java

That doesn't look thread safe: * Calling containsKey is not the same as a null check. * "double checked locking" is an anti-pattern because it is unsafe. * In addition to that, you added an unsynchronized call to the get method. Andreas On Sun, Jul 13, 2014 at 7:15 PM, wrote: > Author: uswick >

[jira] [Commented] (SYNAPSE-849) Cannot reply or makefault when client sends malformed XML - org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException

[ https://issues.apache.org/jira/browse/SYNAPSE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041417#comment-14041417 ] Andreas Veithen commented on SYNAPSE-849: - What is the type of incoming mes

Re: Build failed in Jenkins: Synapse - Trunk #4789

Done. Andreas On Sun, Jan 26, 2014 at 12:22 PM, Sagara Gunathunga wrote: > Please upgrade Neethi version into 3.0.4-SNAPSHOT or just remove > Neethi from dependency entries so that it can resolve correct Neethi > version from Axis2 to fix this build failure. > > Thanks ! > > On Sun, Jan 26, 201

[jira] [Commented] (SYNAPSE-434) Concurrency level provided by the mail and VFS transports listeners is insufficient

[ https://issues.apache.org/jira/browse/SYNAPSE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849012#comment-13849012 ] Andreas Veithen commented on SYNAPSE-434: - Yes, I think that this is reso

[jira] [Resolved] (SYNAPSE-986) Upgrade Synapse to use XMLSchema2

[ https://issues.apache.org/jira/browse/SYNAPSE-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-986. - Resolution: Fixed Fix Version/s: (was: 2.1) 3.0

[jira] [Commented] (SYNAPSE-986) Upgrade Synapse to use XMLSchema2

[ https://issues.apache.org/jira/browse/SYNAPSE-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842290#comment-13842290 ] Andreas Veithen commented on SYNAPSE-986: - Why not just drop the depend

Re: svn commit: r1211407 [1/7] - in /synapse/trunk/java/modules/integration: ./ src/ src/test/ src/test/java/ src/test/java/org/ src/test/java/org/apache/ src/test/java/org/apache/synapse/ src/test/ja

I understand the reason now. See r1547184. Andreas On Sun, Nov 24, 2013 at 8:41 PM, Hiranya Jayathilaka wrote: > Hi Andreas, > > On Nov 24, 2013, at 3:30 AM, Andreas Veithen > wrote: > > On Wed, Dec 7, 2011 at 1:17 PM, wrote: > > + > +

Re: HTTP Core Performance and Reactor Buffer Size

ing them to 8k: > > http.socket.rcv-buffer-size > http.socket.snd-buffer-size > > WDYT? > +1 Andreas > Thanks, > Hiranya > > On Nov 24, 2013, at 11:10 AM, Oleg Kalnichevski wrote: > > On Sun, 2013-11-24 at 17:29 +0100, Andreas Veithen wrote: > > Oleg, &g

Re: HTTP Core Performance and Reactor Buffer Size

On Sun, Nov 24, 2013 at 5:40 PM, Andreas Veithen wrote: > What I still don't understand completely is why this causes such a > slowdown. The effect of the issue in httpcore-nio is that the peer > sees the TCP window size gradually drop from 43690 to 8192. Would that > trigger

Re: HTTP Core Performance and Reactor Buffer Size

On Sun, Nov 24, 2013 at 2:21 PM, Oleg Kalnichevski wrote: > On Sun, 2013-11-24 at 14:15 +0100, Andreas Veithen wrote: >> Instead of taking 40 seconds, the scenario now takes 20 seconds, with the >> request processing completing in less than a second. So there is still a >>

Re: HTTP Core Performance and Reactor Buffer Size

in Synapse. Andreas On Sun, Nov 24, 2013 at 1:32 PM, Oleg Kalnichevski wrote: > On Sun, 2013-11-24 at 13:02 +0100, Andreas Veithen wrote: >> All, >> >> While debugging this scenario (on Ubuntu with the default receive >> buffer size of 8192 and a payload of 1M), I noticed

Re: HTTP Core Performance and Reactor Buffer Size

r 24, 2013, Oleg Kalnichevski wrote: > On Sun, 2013-11-24 at 13:02 +0100, Andreas Veithen wrote: > > All, > > > > While debugging this scenario (on Ubuntu with the default receive > > buffer size of 8192 and a payload of 1M), I noticed something else. > > Very

Re: HTTP Core Performance and Reactor Buffer Size

All, While debugging this scenario (on Ubuntu with the default receive buffer size of 8192 and a payload of 1M), I noticed something else. Very early in the test execution, there are TCP retransmissions from the client to Synapse. This is of course weird and should not happen. While trying to unde

Re: svn commit: r1211407 [1/7] - in /synapse/trunk/java/modules/integration: ./ src/ src/test/ src/test/java/ src/test/java/org/ src/test/java/org/apache/ src/test/java/org/apache/synapse/ src/test/ja

On Wed, Dec 7, 2011 at 1:17 PM, wrote: > + > +org.apache.maven.plugins > +maven-surefire-plugin > +2.9 > + > + > + > +suite > +

Re: svn commit: r1533847 - in /synapse/trunk/java/modules/integration/src/test: java/org/apache/synapse/samples/framework/ java/org/apache/synapse/samples/framework/config/ java/org/apache/synapse/sam

; I'm on Mac OS X (Mountain Lion) too, and hasn't encountered this issue so > far. Can you reproduce it consistently, or is it intermittent? It's more > likely that this is problem happens on a specific JVM version. Wouldn't be > the first time that a particular JVM versio

[jira] [Resolved] (SYNAPSE-985) Synapse still referring to incorrect (old) Maven dependencies

[ https://issues.apache.org/jira/browse/SYNAPSE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-985. - Resolution: Fixed Fix Version/s: (was: 2.1) 3.0

Re: Test Failure in Synapse Trunk Build

Just for the records: the issue is caused by some broken code, but occurs only on Java 1.7. For more information, see: http://markmail.org/message/5pqsmf55zds77wqn Andreas On Fri, Jul 12, 2013 at 8:25 PM, Hiranya Jayathilaka wrote: > Perhaps some issue specific to your build environment? It bui

Re: svn commit: r1533847 - in /synapse/trunk/java/modules/integration/src/test: java/org/apache/synapse/samples/framework/ java/org/apache/synapse/samples/framework/config/ java/org/apache/synapse/sam

It looks like that test case causes problems on some platforms. On Mac OS X it hangs after printing the following log messages: 2013-10-27 11:03:32,801 [-] [main] INFO Sample10002 Testing DirectMediation; Payload size: 500B 2013-10-27 11:03:32,834 [-] [main] INFO Sample10002 >>>

[jira] [Commented] (SYNAPSE-955) XPath1.0 Implementation On Top Of XMLStream

[ https://issues.apache.org/jira/browse/SYNAPSE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797304#comment-13797304 ] Andreas Veithen commented on SYNAPSE-955: - I applied xmlstreamingxpathv_6.p

Re: Synapse: tcp-listener: handling of multiple syslog messages in one TCP message?

On Fri, Aug 9, 2013 at 9:26 PM, Rajika Kumarasiri wrote: > Yeah, actually I have started working on a new syslog consumer > implementation. As part of this I am also planning to write brand new TCP > and UDP transports(for high volume syslog message deployments). I will > report any progress as I

Re: Streaming processing in Synapse with AXIOM

On Tue, Aug 13, 2013 at 12:06 PM, Auke Schrijnen wrote: > Hi all, > > We have a couple of custom mediators for Synapse to do various > transformations, > logging, validation, filtering and caching. Working with the AXIOM model is > pretty straight forward, one can easily navigate through the mode

Re: Build failed in Jenkins: Synapse - Trunk #4684

FYI: This is caused by a problem with the Axis2 build; the artifacts for the JMS transport have not been built and are out-of-date. Working on it. Andreas On Sun, Aug 4, 2013 at 7:40 PM, Apache Jenkins Server wrote: > See > > Chang

Re: compilation errors

On Fri, Aug 2, 2013 at 12:56 AM, Hiranya Jayathilaka wrote: > > On Aug 1, 2013, at 3:12 PM, Rajika Kumarasiri > wrote: > > I just noticed Andreas has got rid of the javamail dependency completely. > May be you can revert the changes to pom. > > > There are more touch points, coming through the Ax

Re: svn commit: r730466 [2/3] - in /synapse/trunk/java: ./ modules/core/src/main/java/org/apache/synapse/config/ modules/core/src/main/java/org/apache/synapse/config/xml/ modules/core/src/main/java/or

Using static fields to store error information here doesn't look right. BTW, this causes a build failure with Java 1.7 (on Linux) because the corresponding test cases are executed in a different order than with Java 1.6. Andreas On Wed, Dec 31, 2008 at 9:26 PM, wrote: > +public class Subscripti

Re: XPath1.0 implementation on top of XML Stream

Where's the source code? I don't see any commits in your SVN repo [1] since May 21. Also, what is the algorithm that you finally selected? Andreas [1] https://subversion.assembla.com/svn/streaming-xpath/ On Sun, Jul 28, 2013 at 11:18 AM, Isuru Ranawaka wrote: > Hi all, > > Following Axis suppo

Re: svn commit: r1504950 - /synapse/trunk/java/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/nhttp/HttpCoreNIOSender.java

I don't think that this is the correct fix for SYNAPSE-866. My interpretation is that the original intent of the code you removed was to avoid logging an exception when the client closes the connection (which is not a very exceptional situation). The problem is that this code is triggered also in o

[jira] [Commented] (SYNAPSE-881) When SynapseRecevieCallback handler receives SOAP fault from backend then synapse Message helper always try to cast SOAP Fault detail entries to OMElement without ty

[ https://issues.apache.org/jira/browse/SYNAPSE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657270#comment-13657270 ] Andreas Veithen commented on SYNAPSE-881: - @Dushan: can we get a test case

Re: Clarifications on Supporting SWIFT Protocol for Apache Synapse

On Tue, May 7, 2013 at 6:38 PM, Chaamini Mangaleswaran wrote: > Hi Hiranya, > > I read SWIFT Specifications and I found out the following : > > An organization has to connect to SWIFTNet to connect with all the > institutions participating. SWIFTNetLink is a mandatory software product > for the

Re: Build Failure at Apache Synapse - FIX Transport

pendency? > > > On Mon, Apr 29, 2013 at 1:41 PM, Andreas Veithen > wrote: >> >> The fundamental problem is that unlike other projects, the Synapse >> project has no policy to only allow dependencies on artifacts that are >> available from Maven central.

Re: Build Failure at Apache Synapse - FIX Transport

> That being said, IIRC in Maven 3.0.4 the certificate validation policy > was changed and Mavan now validates the hostname. Probably you will be > able to build Synapse if you downgrade to Maven 3.0.3. Correcting my previous statement: the validation policy changed in 3.0.5, and 3.0.4 works. Sti

Re: Build Failure at Apache Synapse - FIX Transport

The fundamental problem is that unlike other projects, the Synapse project has no policy to only allow dependencies on artifacts that are available from Maven central. That means that Synapse has dependencies hosted in third party repositories over which the project has no control. If some of these

Re: GSOC Project Proposal for XPath1.0 implementation On Top Of XML Stream

The current version of the proposal in Google Melange mentions: "Support for XPath Axis" XPath defines 13 different axes. Which of them are you planning to implement? Andreas On Sun, Apr 21, 2013 at 5:08 PM, Isuru Ranawaka wrote: > hi all, > This Proposal is for develop Xpath Engine On top Of X

Re: Project Ideas For GSOC 2013

The idea would be to implement the necessary changes in Axiom, Axis2 and Synapse so that DOOM can be used end-to-end for the messages that flow through Axis2 and Synapse. That has potential benefits for scenarios that use WS-Security (because it avoids LLOM <-> DOOM transformations in Rampart) or m

[jira] [Resolved] (SYNAPSE-904) The wsdl used with samples (repository/conf/sample/resources/proxy/sample_proxy_1.wsdl) is outdated.

[ https://issues.apache.org/jira/browse/SYNAPSE-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-904. - Resolution: Fixed The WSDL has been updated as part of the solution for SYNAPSE-905

[jira] [Resolved] (SYNAPSE-905) Namespace mismatch in samples that use SimpleStockQuoteService

[ https://issues.apache.org/jira/browse/SYNAPSE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-905. - Resolution: Fixed Assignee: Andreas Veithen Implemented solution (2

[jira] [Resolved] (SYNAPSE-910) NHTTP transport does not allow to write empty string as a SOAPAction header.

[ https://issues.apache.org/jira/browse/SYNAPSE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-910. - Resolution: Fixed > NHTTP transport does not allow to write empty string a

[jira] [Resolved] (SYNAPSE-912) Synapse should support "text/xml" as a REST content type.

[ https://issues.apache.org/jira/browse/SYNAPSE-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-912. - Resolution: Fixed > Synapse should support "text/xml" as a REST

[jira] [Commented] (SYNAPSE-745) Implement a Collection of Integration Patterns for Synapse

[ https://issues.apache.org/jira/browse/SYNAPSE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457659#comment-13457659 ] Andreas Veithen commented on SYNAPSE-745: - I tested samples 851, 852 and 853

Re: Improving Synapse CBR performance.

On Wed, Sep 12, 2012 at 5:59 PM, Amila Suriarachchi wrote: > hi all, > > For SOAP message based content based routing, currently we use SOAPBuilder > and SOAPMessageFormater to build the soap envelop and serialize it. But > however in the content based routing the only message part required to rea

Re: Improving Synapse CBR performance.

On Wed, Sep 12, 2012 at 10:36 PM, Hiranya Jayathilaka wrote: > Hi Amila, > > AFAIU this improvement gets rid of the SOAP serialization overhead (at the > cost of more memory). This is certainly an interesting idea but goes against > the philosophy that we have been following up to now - we don't b

[VOTE] Solution for SYNAPSE-905

All, Please have a look at the following issue: https://issues.apache.org/jira/browse/SYNAPSE-905 In the issue description I propose two solutions for the problem. Both of which will/may cause some collateral damages (to the samples), but we need to decide which one to implement. I'm in favor of

[jira] [Updated] (SYNAPSE-905) Namespace mismatch in samples that use SimpleStockQuoteService

[ https://issues.apache.org/jira/browse/SYNAPSE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated SYNAPSE-905: Description: According to the WSDL generated by Axis2, SimpleStockQuoteService uses two

Fwd: svn commit: r1060750 - /synapse/trunk/java/repository/conf/sample/synapse_sample_15.xml

Supun, Where is the documentation for this sample? Andreas -- Forwarded message -- From: Date: Wed, Jan 19, 2011 at 11:33 AM Subject: svn commit: r1060750 - /synapse/trunk/java/repository/conf/sample/synapse_sample_15.xml To: comm...@synapse.apache.org Author: supun Date: Wed

[jira] [Resolved] (SYNAPSE-906) Sample 158 sends POX instead of SOAP

[ https://issues.apache.org/jira/browse/SYNAPSE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-906. - Resolution: Fixed Assignee: Andreas Veithen > Sample 158 sends POX instead

[jira] [Created] (SYNAPSE-906) Sample 158 sends POX instead of SOAP

Andreas Veithen created SYNAPSE-906: --- Summary: Sample 158 sends POX instead of SOAP Key: SYNAPSE-906 URL: https://issues.apache.org/jira/browse/SYNAPSE-906 Project: Synapse Issue Type: Bug

[jira] [Created] (SYNAPSE-905) Sample 158 produces SOAP message that doesn't conform to the WSDL of the target service

Andreas Veithen created SYNAPSE-905: --- Summary: Sample 158 produces SOAP message that doesn't conform to the WSDL of the target service Key: SYNAPSE-905 URL: https://issues.apache.org/jira/browse/SYNAPS

[jira] [Resolved] (SYNAPSE-876) Sample 158: Exposing a SOAP Service Over JSON; jsonclient Error!!!

[ https://issues.apache.org/jira/browse/SYNAPSE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-876. - Resolution: Invalid Fix Version/s: (was: FUTURE) The documentation of sample

[jira] [Updated] (SYNAPSE-876) Sample 158: Exposing a SOAP Service Over JSON; jsonclient Error!!!

[ https://issues.apache.org/jira/browse/SYNAPSE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated SYNAPSE-876: Summary: Sample 158: Exposing a SOAP Service Over JSON; jsonclient Error!!! (was: Sample

[jira] [Updated] (SYNAPSE-876) Sample 440: Exposing a SOAP Service Over JSON; jsonclient Error!!!

[ https://issues.apache.org/jira/browse/SYNAPSE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated SYNAPSE-876: Priority: Minor (was: Critical) Assignee: Andreas Veithen > Sample 440: Expos

[jira] [Commented] (SYNAPSE-883) ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to org.apache.axiom.soap.SOAPFault error occurs when handling SOAPFault in out path of R

[ https://issues.apache.org/jira/browse/SYNAPSE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424347#comment-13424347 ] Andreas Veithen commented on SYNAPSE-883: - The ClassCastException occurs bec

[jira] [Commented] (SYNAPSE-892) JS mediator child dependancies (includes) not properly serializing throwing Class Cast Exception

[ https://issues.apache.org/jira/browse/SYNAPSE-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424309#comment-13424309 ] Andreas Veithen commented on SYNAPSE-892: - Can you please submit a unit

[jira] [Commented] (SYNAPSE-881) When SynapseRecevieCallback handler receives SOAP fault from backend then synapse Message helper always try to cast SOAP Fault detail entries to OMElement without ty

[ https://issues.apache.org/jira/browse/SYNAPSE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424305#comment-13424305 ] Andreas Veithen commented on SYNAPSE-881: - Axiom actually has an API that al

[jira] [Assigned] (SYNAPSE-881) When SynapseRecevieCallback handler receives SOAP fault from backend then synapse Message helper always try to cast SOAP Fault detail entries to OMElement without typ

[ https://issues.apache.org/jira/browse/SYNAPSE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned SYNAPSE-881: --- Assignee: Andreas Veithen > When SynapseRecevieCallback handler receives S

[jira] [Commented] (SYNAPSE-893) Resequencing Message Processor For Synapse

[ https://issues.apache.org/jira/browse/SYNAPSE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415543#comment-13415543 ] Andreas Veithen commented on SYNAPSE-893: - Unit tests? Documenta

[jira] [Resolved] (SYNAPSE-867) SwA responses are processed incorrectly

[ https://issues.apache.org/jira/browse/SYNAPSE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved SYNAPSE-867. - Resolution: Fixed Fix Version/s: FUTURE Fixed for 2.2 (BTW, why is there no 2.2

Re: Jenkins build is still unstable: Synapse - Trunk #4208

http://markmail.org/message/xjegfgznilfidahf http://markmail.org/message/whwkv4pck6ezluih Andreas On Mon, Apr 30, 2012 at 10:57, Hiranya Jayathilaka wrote: > The SwA integration test is failing. Any idea why? > > Thanks, > Hiranya > > > On Mon, Apr 30, 2012 at 1:26 PM, Apache Jenkins Server > w

[jira] [Commented] (SYNAPSE-867) SwA responses are processed incorrectly

[ https://issues.apache.org/jira/browse/SYNAPSE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264550#comment-13264550 ] Andreas Veithen commented on SYNAPSE-867: - One possible (clean) solution

[jira] [Updated] (SYNAPSE-867) SwA responses are processed incorrectly

[ https://issues.apache.org/jira/browse/SYNAPSE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated SYNAPSE-867: Attachment: capture.txt > SwA responses are processed incorrec

[jira] [Created] (SYNAPSE-867) SwA responses are processed incorrectly

Andreas Veithen created SYNAPSE-867: --- Summary: SwA responses are processed incorrectly Key: SYNAPSE-867 URL: https://issues.apache.org/jira/browse/SYNAPSE-867 Project: Synapse Issue Type

Re: Jenkins build became unstable: Synapse - Trunk #4204

FYI: Because of SYNAPSE-866 the logs don't show the reason of the failure, but after debugging, the exception is: java.lang.IllegalStateException: The content of the MIME part has already been consumed at org.apache.axiom.attachments.PartImpl.getContent(PartImpl.java:154) at org.ap

  1   2   3   4   5   6   7   8   9   >