[
https://issues.apache.org/jira/browse/SYNAPSE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reassigned SYNAPSE-851:
-
Assignee: Rajika Kumarasiri (was: Hiranya Jayathilaka)
> VFS proxy genera
[
https://issues.apache.org/jira/browse/SYNAPSE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reassigned SYNAPSE-818:
-
Assignee: Rajika Kumarasiri
> Update synapse properties mediator guide with
[
https://issues.apache.org/jira/browse/SYNAPSE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reassigned SYNAPSE-854:
-
Assignee: Rajika Kumarasiri (was: Isuru Udana Loku Narangoda)
> Mail pro
I just built Synapse with tests successfully. What command line options do
you use ? Perhaps there is a corrupted jar in you local maven repo ?
Rajika
On Sat, Sep 20, 2014 at 5:10 PM, Hiranya Jayathilaka
wrote:
> When building the Synapse nhttp transport modules I see a bunch of error
> message
I created, https://issues.apache.org/jira/browse/SYNAPSE-994 for this.
Rajika
On Mon, Sep 15, 2014 at 2:02 PM, Hiranya Jayathilaka
wrote:
> Sounds good. Create an issue and see if anybody's willing to send in some
> documentation patches?
>
> On Sat, Sep 13, 2014 at 10:21 PM,
Rajika Kumarasiri created SYNAPSE-994:
-
Summary: Improve documentation with popular deployments of Apache
Synapse
Key: SYNAPSE-994
URL: https://issues.apache.org/jira/browse/SYNAPSE-994
Project
ounds good. Create an issue and see if anybody's willing to send in some
> documentation patches?
>
> On Sat, Sep 13, 2014 at 10:21 PM, Rajika Kumarasiri <
> rajika.kumaras...@gmail.com> wrote:
>
>> 5. Synapse as a REST gateway.
>> 6. Synapse as a WS-Securit
5. Synapse as a REST gateway.
6. Synapse as a WS-Security processor.
On Sat, Sep 13, 2014 at 12:36 PM, Rajika Kumarasiri <
rajika.kumaras...@gmail.com> wrote:
> What do you think if we improve the documentation with couple of popular
> deployment scenarios with Synapse as part of
x27;t require a lot of
> fixing. We do need to setup svnpubsub for distributing binaries and the
> website though. Looks like this requires a bit of work.
>
> Thanks,
> Hiranya
>
> On Wed, Sep 10, 2014 at 6:55 AM, Rajika Kumarasiri <
> rajika.kumaras...@gmail.com> wrot
mons-VFS?
>
> Thanks,
> Hiranya
>
>
> On Mon, Sep 8, 2014 at 8:14 PM, Rajika Kumarasiri <
> rajika.kumaras...@gmail.com> wrote:
>
>> +1. We need to create jira issue per each issue for Axis2 and Rampart
>> once those issue got fixed we can move back to t
+1. We need to create jira issue per each issue for Axis2 and Rampart once
those issue got fixed we can move back to the mainline.
Rajika
On Mon, Sep 8, 2014 at 11:09 PM, Hiranya Jayathilaka
wrote:
> Hi Folks,
>
> It looks like the Axis2 release process is going to take longer than we'd
> like.
[
https://issues.apache.org/jira/browse/SYNAPSE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745003#comment-13745003
]
Rajika Kumarasiri commented on SYNAPSE-502:
---
This is an important featur
[
https://issues.apache.org/jira/browse/SYNAPSE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743836#comment-13743836
]
Rajika Kumarasiri commented on SYNAPSE-502:
---
We can have a configurable
Thanks Hiranya.
Rajika
On Sun, Aug 18, 2013 at 1:23 AM, Hiranya Jayathilaka
wrote:
>
> On Aug 17, 2013, at 7:53 PM, Rajika Kumarasiri <
> rajika.kumaras...@gmail.com> wrote:
>
> One thing I am not clear in the vfs documentation is that the fact "vfs
> transpor
/transports.xml
On Sat, Aug 17, 2013 at 3:15 PM, Rajika Kumarasiri <
rajika.kumaras...@gmail.com> wrote:
> Sure Hiranya. BTW, what's the version of this release ?
>
> Rajika
>
>
> On Sat, Aug 17, 2013 at 2:41 PM, Hiranya Jayathilaka > wrote:
>
>> Hi Rajika,
>>
2013 at 3:15 PM, Rajika Kumarasiri <
rajika.kumaras...@gmail.com> wrote:
> Sure Hiranya. BTW, what's the version of this release ?
>
> Rajika
>
>
> On Sat, Aug 17, 2013 at 2:41 PM, Hiranya Jayathilaka > wrote:
>
>> Hi Rajika,
>>
>> I
Sure Hiranya. BTW, what's the version of this release ?
Rajika
On Sat, Aug 17, 2013 at 2:41 PM, Hiranya Jayathilaka
wrote:
> Hi Rajika,
>
> I'm in the process of revamping the Synapse transports catalog in the
> documentation. Could you please review and update [1] when you get a
> chance? I no
ault behavior is to pass the "Server" header
>> sent by the backend server.
>>
>> Thanks,
>> Hiranya
>>
>>
>> I guess we should probably look at what a reverse proxy like nginx does
>> by default and do whatever they do .. as that's the role
This is fixed now.
Rajika
On Sat, Aug 10, 2013 at 5:11 PM, Hiranya Jayathilaka
wrote:
>
> On Aug 10, 2013, at 12:40 PM, Rajika Kumarasiri <
> rajika.kumaras...@gmail.com> wrote:
>
> No that's not possible. Rabbit MQ doesn't implement any JMS API. I think
>
ayathilaka
> wrote:
>
> Hi Rajika,
>
> Yes, I came across these during the 4.2.4 migration. I think we only use a
> few deprecated constants as of now. All the deprecated function/method
> calls have already been updated. Soon I'll get rid of the deprecated
> constants
I meant it's better not to include that header by default since it can be
considered a security issue. But as you have suggested we also need a way
to configure the header.
Rajika
On Sun, Aug 11, 2013 at 1:52 AM, Hiranya Jayathilaka
wrote:
> Hi Rajika,
>
> On Aug 10, 2013, at 10
+1. Should be use-if-available.
Rajika
On Sun, Aug 11, 2013 at 12:30 AM, Hiranya Jayathilaka
wrote:
> I noticed that both PT and NHTTP transports pass the "Server" header sent
> from the backend server to the client. This is the default programmed
> behavior, and it can be overridden if needed
I think this information also should go into the documentation Hiranya.
Rajika
On Sun, Aug 11, 2013 at 12:21 AM, Hiranya Jayathilaka
wrote:
> Hi Folks,
>
> During the process of migrating to Http Core 4.3, I also took some time to
> unify the logging frameworks used by PT and NHTTP transports.
No that's not possible. Rabbit MQ doesn't implement any JMS API. I think we
will have to exclude rabbitmq client from compile all target and have its
own.
Rajika
On Sat, Aug 10, 2013 at 2:11 AM, Hiranya Jayathilaka
wrote:
>
> On Aug 9, 2013, at 8:57 PM, Rajika Kumarasiri
>
This is because stockquote target depends on compile target. Let me check
how to fix this.
Rajika
On Fri, Aug 9, 2013 at 10:53 PM, Hiranya Jayathilaka
wrote:
> Hi Rajika,
>
> I'm unable to run the sample axis2 client in the latest builds (I'm just
> running ant stockquote):
>
> init:
> [mk
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 go forward.
Rajika
On Fri, Aug 9, 2013 at 3:15 PM, Hiranya Jaya
[
https://issues.apache.org/jira/browse/SYNAPSE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reassigned SYNAPSE-854:
-
Assignee: Rajika Kumarasiri
> Mail proxcy sample bro
+1. I fixed it.
One thing I noticed with the vfs transport is that it requires
some re-factoring. May be we can re-write it completely at some point in
future, possibly replacing the busy loop polling, proper streaming and
large file transfer support etc.. etc..
Rajika
On Fri, Aug 9, 2013 at 2:
[
https://issues.apache.org/jira/browse/SYNAPSE-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734435#comment-13734435
]
Rajika Kumarasiri commented on SYNAPSE-956:
---
I think SYNAPSE-502 trie
[
https://issues.apache.org/jira/browse/SYNAPSE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-502.
---
Resolution: Fixed
Fixed in r1512144.
Users now can specify the parameter
Hiranya,
I noticed there are some deprecated APIs, constants of HC are in use in
nhttp and pass-thru transports. May be you can refactor them too as part
of moving to HC 4.3.
Example, org.apache.http.nio.params.NIOReactorParams
Rajika
This is now fixed.
Rajika
On Thu, Aug 8, 2013 at 4:14 PM, Rajika Kumarasiri <
rajika.kumaras...@gmail.com> wrote:
> Sure, Hiranya, I will do that.
>
> Rajika
>
>
> On Thu, Aug 8, 2013 at 3:58 PM, Hiranya Jayathilaka
> wrote:
>
>> Hi Rajika,
>>
>&g
[
https://issues.apache.org/jira/browse/SYNAPSE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733926#comment-13733926
]
Rajika Kumarasiri commented on SYNAPSE-917:
---
I committed your patch. Pl
[
https://issues.apache.org/jira/browse/SYNAPSE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-917.
---
Resolution: Fixed
> Allow synapse XPath to access system propert
Sure, Hiranya, I will do that.
Rajika
On Thu, Aug 8, 2013 at 3:58 PM, Hiranya Jayathilaka wrote:
> Hi Rajika,
>
> Could you please add this to the pass through transport as well? That's
> what we use by default now.
>
> Thanks,
> Hiranya
>
> On Aug 8, 2013,
Rajika Kumarasiri created SYNAPSE-964:
-
Summary: Add documentation for all Synapse XPath functions.
Key: SYNAPSE-964
URL: https://issues.apache.org/jira/browse/SYNAPSE-964
Project: Synapse
[
https://issues.apache.org/jira/browse/SYNAPSE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-806.
---
Resolution: Fixed
Fixed in r1511994.
Rajika
> Incorporate
[
https://issues.apache.org/jira/browse/SYNAPSE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733899#comment-13733899
]
Rajika Kumarasiri commented on SYNAPSE-806:
---
Please see below for detai
[
https://issues.apache.org/jira/browse/SYNAPSE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733762#comment-13733762
]
Rajika Kumarasiri commented on SYNAPSE-917:
---
How is this coming a
[
https://issues.apache.org/jira/browse/SYNAPSE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733749#comment-13733749
]
Rajika Kumarasiri commented on SYNAPSE-806:
---
Hiranya,
Have we migrate
[
https://issues.apache.org/jira/browse/SYNAPSE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reassigned SYNAPSE-806:
-
Assignee: Rajika Kumarasiri
> Incorporate the improvements in HTTPCORE-
[
https://issues.apache.org/jira/browse/SYNAPSE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reassigned SYNAPSE-806:
-
Assignee: Hiranya Jayathilaka (was: Rajika Kumarasiri)
> Incorporate
Please try;
1. Set the tranport.vfs.FileURI parameter only with user name. Example -
vfs:ftp://user-name@host/home/user/path/to/file.xml
2. Copy the private key into ~/.ssh.
3. Plant the public key into ~/.ssh/authorized_keys in remote server.
Hope this helps.
Rajika
On Wed, Aug 7, 2013 at
I just noticed Andreas has got rid of the javamail dependency completely.
May be you can revert the changes to pom.
Thank you.
Rajika
On Thu, Aug 1, 2013 at 5:57 PM, Hiranya Jayathilaka wrote:
>
> On Aug 1, 2013, at 2:52 PM, Rajika Kumarasiri
> wrote:
>
> +1. I wonder how th
snapshot has a ContentType class which can
> be used to replace these usages of javamail. But until Axis2 switches to
> this new API, we will have to keep using javamail. Correct solution at this
> point is to properly declare the javamail dependency in Synapse poms.
>
> Thanks,
our build setup. From the looks of it maven is unable to
> locate a dependency (probably javamail). Are you building offline?
>
> Thanks,
> Hiranya
>
> On Aug 1, 2013, at 10:02 AM, Rajika Kumarasiri <
> rajika.kumaras...@gmail.com> wrote:
>
> [ERROR] Failed to execut
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project synapse-vfs-transport: Compilation failure:
Compilation failure:
[ERROR]
/home/rajika/project/apache/synapse/trunk/modules/transports/core/vfs/src/main/java/org/apache/synapse/tr
+1.
Rajika
On Tue, Jul 30, 2013 at 8:19 PM, Hiranya Jayathilaka
wrote:
> Hi Folks,
>
> Currently Synapse distribution consists of 3 different versions of the
> bcprov (BouncyCastle) jar.
>
> 1. org.bouncycastle:bcprov-jdk15on:jar:1.49:compile (Added recently to
> support OCSP/CRL - See SYNAPSE-
I added sample #269 for this purpose.
Rajika
On Sun, Jul 28, 2013 at 8:29 PM, Rajika Kumarasiri <
rajika.kumaras...@gmail.com> wrote:
> Sure, I will add that too.
>
> Rajika
>
>
> On Sun, Jul 28, 2013 at 8:09 PM, Hiranya Jayathilaka > wrote:
>
>> BTW, wh
http://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html
http://logging.apache.org/log4j/2.x/manual/async.html#Performance
May be we can migrate to log4j 2 at some point in future.
Rajika
Can you attach a single patch which includes everything ? documentation +
individual patches etc.. etc.. that way it's easy to review and apply.
Rajika
On Mon, Jul 29, 2013 at 10:03 PM, Jeewantha Dharmaparakrama <
jeewamp@gmail.com> wrote:
>
>
>
> On Tue, Jul 30,
Can you attach your patch as a diff against the source tree ?
Rajika
On Mon, Jul 29, 2013 at 9:59 PM, Jeewantha Dharmaparakrama <
jeewamp@gmail.com> wrote:
> Hi Folks,
>
> I recently developed a Certificate Validation feature with OCSP[1] and
> CRL[2] for Synapse which was shipped with the
roker and trying out a proxy service
> would really help.
>
> Thanks,
> Hiranya
>
> On Jul 28, 2013, at 4:35 PM, Hiranya Jayathilaka
> wrote:
>
> > Hi Rajika,
> >
> > On Jul 28, 2013, at 2:49 PM, Rajika Kumarasiri <
> rajika.kumaras...@gmail.com&
I just committed a native AMQP transport implementation for Apache Synapse.
This is based on the AMQP Java client library from RabbitMQ. Due to the
license we'll not distribute the client libraries together with Synapse.
Users who wish to use this feature has to copy the required client
libraries i
It's important to send a fault to client and let the client know what went
wrong. How ever I think wrapping everything inside an Exception will cause
client to end up with all kind of additional errors(that's no interest to
the client) that server might end up within that try/catch block (for
examp
May be we should enable the SSl debug logs and see what's going on ?
Rajika
On Mon, Jul 22, 2013 at 8:23 PM, Hiranya Jayathilaka
wrote:
> Hi Folks,
>
> Currently Synapse is based on HTTP Core 4.1.4. I just tried using 4.2
> instead (just changed the version of the maven dependency). Almost
> ev
[
https://issues.apache.org/jira/browse/SYNAPSE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715245#comment-13715245
]
Rajika Kumarasiri commented on SYNAPSE-917:
---
Sure, what ever way easy for
[
https://issues.apache.org/jira/browse/SYNAPSE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715240#comment-13715240
]
Rajika Kumarasiri commented on SYNAPSE-917:
---
Can you also provide
[
https://issues.apache.org/jira/browse/SYNAPSE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reassigned SYNAPSE-917:
-
Assignee: Rajika Kumarasiri
> Allow synapse XPath to access sys
value.
Rajika
On Tue, Jul 16, 2013 at 3:04 PM, Hiranya Jayathilaka
wrote:
> Hi Rajika,
>
> On Jul 16, 2013, at 11:32 AM, Rajika Kumarasiri <
> rajika.kumaras...@gmail.com> wrote:
>
> This optional regex property let users to extract fine grain information
> form the xpath
This optional regex property let users to extract fine grain information
form the xpath match. In case of missing regex property, system should be
fallback to use the default, which is the xpath result. So
I believe current implementation is correct and we should leave it as it
is.
#2 incorrectly
What are the changes to be specific ?
Rajika
On Mon, Jul 15, 2013 at 11:16 PM, Kasun Indrasiri wrote:
> Apparently, some of the modification done at axis2 level will be required
> to next Synapse release.
> Should we request for an axis2 release? wdyt?
>
> --
> Kasun Indrasiri
> Associate Techn
[
https://issues.apache.org/jira/browse/SYNAPSE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707801#comment-13707801
]
Rajika Kumarasiri commented on SYNAPSE-935:
---
We normally check the cons
[
https://issues.apache.org/jira/browse/SYNAPSE-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707763#comment-13707763
]
Rajika Kumarasiri commented on SYNAPSE-935:
---
BaseTransport has a metho
We also can move to hc 4.2.5. http client 4.2.5 in this release. HC project
is about to release version 4.3 but I am not sure about the time line
though.
Rajika
On Thu, Jul 11, 2013 at 6:26 PM, Hiranya Jayathilaka
wrote:
> Hi Folks,
>
> I just committed the patches for SYNAPSE-913 with some mod
] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR
What does the log says ?
Rajika
On Fri, Jul 12, 2013 at 1:50 PM, Thilini Gamage wrote:
> Hi all,
>
> I tried to build Synapse trunk with tests, but the build is failed. The
> following test case is failing. Any help will be appreciated.
>
> Results :
>
> Failed tests:
> testSubscriptionMessageB
+1. I will help fixing any outstanding issues.
I also wrote a native AMQP transport for Apache synapse and see below for
code. It uses the excellent Rabbit MQ java library for AMQP. May be we can
include that too in the release. We need to make sure that the license of
RabbitMQ java library is com
[
https://issues.apache.org/jira/browse/SYNAPSE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705329#comment-13705329
]
Rajika Kumarasiri commented on SYNAPSE-917:
---
Yeah, feel free to implement
If you are using sample #256, it polls the request message from the
configured email server as the documentation says. If you want to send a
different payload other than the given one, you can try to see the WSDL of
the back end service to get the required payload.
Rajika
On Thu, Jun 27, 2013 at
Rajika Kumarasiri created SYNAPSE-917:
-
Summary: Allow synapse XPath to access system properties
Key: SYNAPSE-917
URL: https://issues.apache.org/jira/browse/SYNAPSE-917
Project: Synapse
Yeah. You can use the filter mediator to decide based on the content(To
address) and XSLT mediator to transform the request to another format.
Check,
http://synapse.apache.org/userguide/samples/sample1.html
http://synapse.apache.org/userguide/samples/sample8.html
Hope this helps.
Rajika
On Fri
Yes. This will be a very interesting feature for Apache Synapse and will
increase the power of Synapse when comes to integration with MSMQ.
As you may aware MSMQ is written in C++ and it has API for C/C++ and COM.
If a Java program wants to connect to MSMQ then there should be a JNI layer
which wi
https://issues.apache.org/jira/browse/SYNAPSE-748
Rajika
On Mon, Mar 12, 2012 at 5:25 PM, Gayan Dhanushka wrote:
>
> Hi,
>
> I am a final year student at University of Moratuwa. I've been able
> download and build the synapse code base. I am looking at the code these
> days and I am willing to p
+1.
Sorry for the late reply.
Rajika
+1.
Rajika
On Fri, Feb 10, 2012 at 6:35 PM, Udayanga Wickramasinghe
wrote:
> Hi All,
>
> During the past couple of months Sadeep has been a key contributor to
> Synapse project. He has been actively involved with the Synapse community
> and has contributed to many of the synapse modules includin
[
https://issues.apache.org/jira/browse/SYNAPSE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri updated SYNAPSE-806:
--
Attachment: SYNAPSE-806.patch
Here is a patch with the required fix for nhttp
[
https://issues.apache.org/jira/browse/SYNAPSE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172179#comment-13172179
]
Rajika Kumarasiri commented on SYNAPSE-806:
---
In addition to upgrade to
[
https://issues.apache.org/jira/browse/SYNAPSE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-819.
---
Resolution: Fixed
Fixed in trunk.
Rajika
> Possi
Issue Type: Bug
Reporter: Rajika Kumarasiri
When running Synapse with a resolving endpoint defined as a local entry
definition and under high concurrency level following fault message can be
seen.
Couldn't find the endpoint with the key :
It seems there is a possible synchroniz
/SYNAPSE-806
Project: Synapse
Issue Type: Improvement
Reporter: Rajika Kumarasiri
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure
Please create an issue in the issue tracker and attach the patch.
Rajika
On Tue, Jul 26, 2011 at 6:00 PM, Piyum Fernando wrote:
> changes added. Please find the attachment.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@syna
[
https://issues.apache.org/jira/browse/SYNAPSE-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-771.
---
Resolution: Fixed
This is now fixed in trunk. I have updated the vfs doc as well
Project: Synapse
Issue Type: Improvement
Reporter: Rajika Kumarasiri
Assignee: Rajika Kumarasiri
It seems when processing a large chunk of files using vfs transport some time a
random failure occurs which seems to be cause by fileObject.move
+1 and welcome.
Rajika
On Sun, May 15, 2011 at 10:24 AM, Supun Kamburugamuva wrote:
> Hi All,
>
> During the past few months Udayanga has being a key contributor to synapse.
> He mainly contributed to two new features. They are Synapse Templates and
> Custom XPath extensions. Apart from this wor
+1. Welcome.
Rajika
On Sun, May 15, 2011 at 10:18 AM, Supun Kamburugamuva wrote:
> Hi All,
>
> Kasun has being contributing for synapse for a quite a long time now. He
> has sent code patches, documentation improvements and has being active in
> the mailing lists. I believe he will continue to
: New Feature
Components: Documentation, Transports
Reporter: Rajika Kumarasiri
Priority: Minor
MSMQ is the messaging broker used by Microsoft[0]. A transport should be
developed which allows Apache Synapse to pick and deliver messages from/to MSMQ
running on
On Fri, Feb 11, 2011 at 10:37 AM, Charith Wickramarachchi <
charith.dhanus...@gmail.com> wrote:
> Hi All ,
>
> I'm going to Re-factor the MessageStore implementation in Synapse tunk
> which was released as an experimental feature.
>
> *Reason behind the refactoring. *
>
> Current MessageStore imp
I guess this can be achieved using a combination of header + property
mediators. But user will have to write more configurations.
Rajika
On Mon, Jan 31, 2011 at 12:46 AM, Supun Kamburugamuva wrote:
> It is often a requirement to have dynamic endpoint URLs. For example
> when people develop synap
https://issues.apache.org/jira/browse/SYNAPSE-626
Rajika
On Sun, Jan 30, 2011 at 1:04 PM, Hiranya Jayathilaka
wrote:
> Hi Rajika,
>
> Do you have a source diff of the patch you applied to the Commons-VFS trunk
> to get it working with Synapse?
>
> Thanks
> --
> Hiranya Jayathilaka
> Senior Softw
+1.
Rajika
On Tue, Jan 25, 2011 at 10:12 PM, Supun Kamburugamuva wrote:
> Hi Folks,
>
> Heshan has being contributing to the Apache Synapse project for quite
> a some time now. He has being sending code patches, documentations and
> participated in discussions and I believe he will continue to d
Ruwan,
I hope I am not late for comments.
1. I just downloaded the synapse-2.0.0-src.tar.gz and the README.txt says
Sepetember 2010 build. I am not sure if it should be change to December
2010.
2. I noticed what Eric has noticed and each folder in the source
distribution(synapse-2.0.0-src.tar.gz)
+1.
Rajika
On Wed, Nov 24, 2010 at 2:17 PM, Ruwan Linton wrote:
> Folks,
>
> Charith has been contributing to the Apache Synapse for quite a while now,
> and has been contributed a full Dead Letter Channel and message stores
> implementation for synapse, including the documents and relevant
> c
[
https://issues.apache.org/jira/browse/SYNAPSE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-707.
---
Resolution: Won't Fix
I'll revert back the fixes. This actually c
[
https://issues.apache.org/jira/browse/SYNAPSE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri reopened SYNAPSE-707:
---
> DBLookup/DBReport mediator should replace a </
[
https://issues.apache.org/jira/browse/SYNAPSE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajika Kumarasiri resolved SYNAPSE-707.
---
Resolution: Fixed
Fix Version/s: 2.0
Fixed in trunk and 2.0 branch.
Rajika
e: Bug
Reporter: Rajika Kumarasiri
If we use a sql statement like "delete from Table where some_value < 1000" this
causes a parsing error. To avoid this we need to encode the SQL string
"delete from Table where some_value < 1000 " and DBLookup/DBReport mediators
sho
On Mon, Nov 15, 2010 at 3:23 PM, Andreas Veithen
wrote:
> The distribution contains commons-io 1.4, while the current transports
> trunk requires 2.0.
>
It seems although the commons-io version is updated into 2.0 still, version
1.4 is pack into distribution.
Rajika
>
> Andreas
>
> On Mon, Nov
On Sat, Sep 25, 2010 at 3:43 PM, Rajika Kumarasiri wrote:
>
>
> On Sat, Sep 25, 2010 at 2:18 PM, Andreas Veithen <
> andreas.veit...@gmail.com> wrote:
>
>> On Fri, Sep 24, 2010 at 06:41, Rajika Kumarasiri wrote:
>> >
>> >
>> > On Thu,
On Sat, Sep 25, 2010 at 2:18 PM, Andreas Veithen
wrote:
> On Fri, Sep 24, 2010 at 06:41, Rajika Kumarasiri wrote:
> >
> >
> > On Thu, Sep 23, 2010 at 11:51 PM, Andreas Veithen
> > wrote:
> >>
> >> Since commons-vfs is an Apache project that uses t
1 - 100 of 216 matches
Mail list logo
