Re: Improve Apache Syanspe Release Process

[Isuru Udana]

Hi Rosen,

I appreciate your interest in improving the Apache Synapse release process.
We considered simplifying the release process while doing the last release,
but couldn't get going.
I think we can study other Apache projects that have already moved to the
Github actions-based release process first.

Thanks.



On Tue, Nov 7, 2023 at 10:27 PM Rosen Silva  wrote:

> Hi All,
>
> I hope this email finds you well. I wanted to initiate a discussion
> regarding the improvement of our release process for Apache Synapse[1
> <https://synapse.apache.org/dev/release-process.html>]. I believe that by
> working together, we can streamline the release process, make it more
> efficient, and ensure the highest quality for our releases.
>
> The purpose of this email is to gather your thoughts, ideas, and feedback
> on this matter. Below is a summary of the key points we have identified for
> potential improvement:
>
> 1. *Automation with GitHub Actions:* Consider implementing GitHub Actions
> to automate various aspects of the release process, reducing manual effort
> and minimizing errors.
>
> 2. *Continuous Integration (CI):* Strengthen our use of CI tools to
> ensure that code changes are continuously built and tested to catch issues
> early.
>
> 3. *Secure Key Management:* Enhance the management of GPG keys for
> signing releases, including secure and possibly automated key handling.
>
> 4. *Automated Staging Repository Management:* Automate the opening,
> closing, and dropping of staging repositories in our repository manager to
> ensure consistency and reduce manual errors.
>
> 5. *Compliance with Best Practices:* Continuously review and update our
> release process to align with best practices for open-source projects and
> Apache Software Foundation requirements.
>
> I invite you to share your thoughts, ideas, and any additional areas you
> believe we should focus on for the improvement of our release process. Your
> feedback is invaluable, and this discussion will help shape the future of
> our release process.
>
> Please reply to this email with your comments, suggestions, or any
> insights you might have. Let's work together to make the Apache Synapse
> release process more efficient, reliable, and user-friendly.
>
> Thank you for your contributions and commitment to the success of Apache
> Synapse.
>
> [1] https://synapse.apache.org/dev/release-process.html
>
> Best regards,
>
> --
>
> *Rosen Silva*
> Associate Technical Lead - WSO2
>
> Email: ros...@wso2.com
> Mobile: +94770677418
> Web: https://wso2.com/
>


-- 
*Isuru Udana*
Director - Engineering
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: What's the reason for Synapse being OSGi

[Isuru Udana]

Hi Nuwan

On Sat, Oct 14, 2023 at 12:50 PM Nuwan Jayawardene 
wrote:

> Hi Isuru,
> for clarification, is the plan to replace OSGi with an alternative or is
> it just removing dead weight?
>
I don't see we are gaining anything from OSGi here, so no alternative is
required.

>
> Best
>
> On Thu, Oct 12, 2023 at 3:14 PM Isuru Udana  wrote:
>
>> Hi all,
>>
>> I am trying to understand the advantage of making Synapse jars as OSGi
>> bundles.
>> Anyone can recall the original decision behind this?
>> I found the following blog written by Ruwan in 2008, but still, it is
>> unclear what advantage we are gaining from OSGi.
>>
>> http://blog.ruwan.org/2008/07/apache-synapse-artifacts-are-osgi.html
>>
>> Going forward to support future JDK versions, this will become a little
>> problematic. If there is no real reason shall we remove OSGi?
>>
>> Thanks.
>>
>> --
>> *Isuru Udana*
>> Director - Engineering
>> WSO2 Inc.; http://wso2.com
>> Member, Apache Software Foundation; http://www.apache.org
>>
>> *email: isud...@gmail.com * cell: +94 77 3791887
>>
>>
>
> --
> *Nuwan Jayawardene*
> https://www.linkedin.com/m/in/nuwanjaya
>
>

-- 
*Isuru Udana*
Director - Engineering
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

What's the reason for Synapse being OSGi

[Isuru Udana]

Hi all,

I am trying to understand the advantage of making Synapse jars as OSGi
bundles.
Anyone can recall the original decision behind this?
I found the following blog written by Ruwan in 2008, but still, it is
unclear what advantage we are gaining from OSGi.

http://blog.ruwan.org/2008/07/apache-synapse-artifacts-are-osgi.html

Going forward to support future JDK versions, this will become a little
problematic. If there is no real reason shall we remove OSGi?

Thanks.

-- 
*Isuru Udana*
Director - Engineering
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: Support Re-Sequence Message Store in Synapse

[Isuru Udana]

Hi Pamod,

It's a useful feature. Please go ahead.

Thanks.

On Mon, Sep 11, 2023 at 3:40 PM Pamod Sylvester  wrote:

> Hi Devs,
>
> What do you think of introducing support to re-sequence messages ?
>
> similar to [1] and [2]. I would like to work on a PR and send it across
>
> [1]
> https://wso2docs.atlassian.net/wiki/spaces/IntegrationPatterns/pages/36864402/Resequencer
>
> [2] https://camel.apache.org/components/next/eips/resequence-eip.html
>
> Thanks,
> Pamod
> <https://camel.apache.org/components/next/eips/resequence-eip.html>
> Resequence
> <https://camel.apache.org/components/next/eips/resequence-eip.html>
> Camel is an open source integration framework that empowers you to quickly
> and easily integrate various systems consuming or producing data.
> camel.apache.org
>
>

-- 
*Isuru Udana*
Director - Engineering
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: [VOTE] Release Apache Synapse 3.0.2 RC2

[Isuru Udana]

+1 (binding)

On Fri, May 5, 2023 at 12:05 AM shafreen anfar 
wrote:

> This is a call for votes to release Apache Synapse 3.0.2 RC2.
>
>
> Please review the distribution artifacts:
>
> https://dist.apache.org/repos/dist/dev/synapse/3.0.2/RC2/
>
>
> The nexus staging repository is available at:
>
> https://repository.apache.org/content/repositories/orgapachesynapse-1007
>
>
> Git Tag (5ef7d61c43c5527a0fd3dc31966871643bdd4eeb):
>
> https://github.com/apache/synapse/tree/Apache-Synapse-3.0.2
>
>
> Public key:
>
>
> https://keyserver.ubuntu.com/pks/lookup?op=get=0xc18dac2a0ad6b97e1bd3035500c0cbb505824e73
>
>
> Issues Fixed:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SYNAPSE%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%203.0.2%20ORDER%20BY%20updated%20DESC%2C%20
> priority%20DESC%2C%20created%20ASC
> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20SYNAPSE%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%203.0.2%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC>
>
>
> Instructions on how to validate distribution artifacts before voting:
>
> http://www.apache.org/dev/release.html#approving-a-release
>


-- 
*Isuru Udana*
Director - Engineering
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

[jira] [Resolved] (SYNAPSE-1127) Add parameter injection capability to Synapse endpoints

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1127.
--
Fix Version/s: 3.0.2
   Resolution: Fixed

> Add parameter injection capability to Synapse endpoints
> ---
>
> Key: SYNAPSE-1127
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1127
> Project: Synapse
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 3.0.1
>Reporter: Nuwan Jayawardene
>Assignee: Isuru Udana
>Priority: Major
> Fix For: 3.0.2
>
>
> Adds parameter injection capability to Synapse endpoints in support of 
> Containerization of Integration Framework project: 
> https://issues.apache.org/jira/browse/SYNAPSE-1125
>  
> Associated PRs include:
> [https://github.com/apache/synapse/pull/55]
> [https://github.com/apache/synapse/pull/79]
> https://github.com/apache/synapse/pull/81



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1127) Add parameter injection capability to Synapse endpoints

[Isuru Udana (Jira)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718153#comment-17718153
 ] 

Isuru Udana commented on SYNAPSE-1127:
--

PRs merged.

> Add parameter injection capability to Synapse endpoints
> ---
>
> Key: SYNAPSE-1127
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1127
> Project: Synapse
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 3.0.1
>Reporter: Nuwan Jayawardene
>Assignee: Isuru Udana
>Priority: Major
> Fix For: 3.0.2
>
>
> Adds parameter injection capability to Synapse endpoints in support of 
> Containerization of Integration Framework project: 
> https://issues.apache.org/jira/browse/SYNAPSE-1125
>  
> Associated PRs include:
> [https://github.com/apache/synapse/pull/55]
> [https://github.com/apache/synapse/pull/79]
> https://github.com/apache/synapse/pull/81



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1112) Move to OpenJDK

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1112.
--
Resolution: Fixed

> Move to OpenJDK 
> 
>
> Key: SYNAPSE-1112
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1112
> Project: Synapse
>  Issue Type: Task
>Reporter: Ravi Undupitiya
>    Assignee: Isuru Udana
>Priority: Major
> Fix For: FUTURE
>
>
> Given the recent Oracle JDK licensing changes, we should ensure synapse can 
> be built and used on OpenJDK and change our build to OpenJDK.  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1106) OOM with large responses where it involves content-aware mediation in response path

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1106.
--
Fix Version/s: 3.0.2
   Resolution: Fixed

> OOM with large responses where it involves content-aware mediation in 
> response path
> ---
>
> Key: SYNAPSE-1106
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1106
> Project: Synapse
>  Issue Type: Bug
>Reporter: Madhawa Kasun Gunasekara
>    Assignee: Isuru Udana
>Priority: Major
> Fix For: 3.0.2
>
> Attachments: Fix_SYNAPSE-1106.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> MessageContext class store messageContext object in a ThreadLocalVariable 
> where it doesn't clear created ThreadLocal variables properly. Therefore 
> synapse passthrough threads contain created the Theadlocal variable which 
> refers to the created soap envelope during the mediation level. Because of 
> the retained ThreadLocal variables, Passthrough threads consumes a huge 
> amount of memory which leads to OOM.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Closed] (SYNAPSE-1105) Concurrency issue in IOReactor's Target getConnections

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana closed SYNAPSE-1105.

Resolution: Invalid

> Concurrency issue in IOReactor's Target getConnections
> --
>
> Key: SYNAPSE-1105
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1105
> Project: Synapse
>  Issue Type: Bug
>Reporter: Madhawa Kasun Gunasekara
>    Assignee: Isuru Udana
>Priority: Major
> Attachments: Fix_SYNAPSE-1105.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> TargetConnections getConnection method doesn't retrun null when the 
> connection is not available.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1120) Max delivery only works in OUT_ONLY scenario

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1120.
--
Fix Version/s: 3.0.2
   Resolution: Fixed

> Max delivery only works in OUT_ONLY scenario 
> -
>
> Key: SYNAPSE-1120
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1120
> Project: Synapse
>  Issue Type: Bug
>Reporter: Shafreen
>    Assignee: Isuru Udana
>Priority: Major
> Fix For: 3.0.2
>
>
> Max delivery drop doesn't work in Message Store Message Processor scenario 
> when OUT_ONLY property is not set. In other words, for two-way scenario it 
> fails.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1121) Reply sequence is not invoked by the Message Processor

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1121.
--
Fix Version/s: 3.0.2
   Resolution: Fixed

> Reply sequence is not invoked by the Message Processor
> --
>
> Key: SYNAPSE-1121
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1121
> Project: Synapse
>  Issue Type: Bug
>Reporter: Shafreen
>    Assignee: Isuru Udana
>Priority: Major
> Fix For: 3.0.2
>
>
> In Message Store Message Processor scenario upon successful delivery it is 
> required to invoke the reply sequence. But it does not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1123) [Message Processor] Fault sequence is not invoked in OUT_ONLY scenario

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1123.
--
Fix Version/s: 3.0.2
   Resolution: Fixed

> [Message Processor] Fault sequence is not invoked in OUT_ONLY scenario
> --
>
> Key: SYNAPSE-1123
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1123
> Project: Synapse
>  Issue Type: Bug
>Reporter: Shafreen
>    Assignee: Isuru Udana
>Priority: Major
> Fix For: 3.0.2
>
>
> At the moment, when there is a failure in Message Processor (i.e. Connection 
> refused) fault sequence is not invoked in OUT_ONLY scenario.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1122) Adding another interval for retry in Scheduled Message Forwarding Processor

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1122.
--
Fix Version/s: 3.0.2
   Resolution: Fixed

> Adding another interval for retry in Scheduled Message Forwarding Processor
> ---
>
> Key: SYNAPSE-1122
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1122
> Project: Synapse
>  Issue Type: Bug
>Reporter: Shafreen
>    Assignee: Isuru Udana
>Priority: Major
> Fix For: 3.0.2
>
>
> At the moment we only support one interval for both fetching messages from 
> the store and retrying when there is a failure. But, IMO, these are two 
> different concepts and deserve two different configurations. Therefore, I am 
> proposing a new configuration parameter for latter. Something as below,
>   
>  1
>   
>  This will allow the user to control the speed of retry when there is a 
> failure. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Should we target the next Synapse release this April

[Isuru Udana]

On Sat, Apr 1, 2023, 16:16 shafreen anfar  wrote:

> Hi Nuwan and Isuru,
>
> > Hope you are doing well now. Glad to have you back!
> Thanks, I am doing much better now!
>
> Should I schedule a call this Monday at 9 PM IST to discuss next actions?
>
+1

>
> On Tue, Mar 28, 2023 at 9:33 PM Isuru Udana  wrote:
>
>> Hi Shafreen,
>>
>> If you can drive the release, I can help too.
>>
>> Thanks.
>>
>>
>> On Mon, Mar 27, 2023 at 9:45 PM Nuwan Jayawardene 
>> wrote:
>>
>>> Hi Shafreen,
>>> Hope you are doing well now. Glad to have you back!
>>> I’d be happy to support with this.
>>>
>>> On Mon, 27 Mar 2023 at 20:58, shafreen anfar 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Was away due to medical reasons. I can contribute to the release if
>>>> others are interested.
>>>>
>>>> On Thu, Nov 24, 2022 at 12:56 AM Nuwan Jayawardene 
>>>> wrote:
>>>>
>>>>> Hi Shafreen,
>>>>> kind follow-up on this.
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Mar 4, 2022 at 10:57 PM shafreen anfar <
>>>>> anfar.shafr...@gmail.com> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Since we have done bug fixes and a few improvements, I wonder if we
>>>>>> should do a Synapse release this April. As a post release task we should
>>>>>> also look into using github actions to automate the steps in the release
>>>>>> process. In fact, we wanted to do a release last year but unfortunately 
>>>>>> we
>>>>>> couldn't proceed.
>>>>>>
>>>>>> Anyway, I would like to hear from the community as well.
>>>>>>
>>>>>> Thanks,
>>>>>> Shafreen
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Nuwan Jayawardene*
>>>>> Assistant Lecturer, Informatics Institute of Technology (IIT).
>>>>> Research Assistant, University of Moratuwa
>>>>>
>>>>> https://www.linkedin.com/m/in/nuwanjaya
>>>>>
>>>>> --
>>> *Nuwan Jayawardene*
>>> https://www.linkedin.com/m/in/nuwanjaya
>>>
>>>
>>
>> --
>> *Isuru Udana*
>> Director - Engineering
>> WSO2 Inc.; http://wso2.com
>> Member, Apache Software Foundation; http://www.apache.org
>>
>> *email: isud...@gmail.com * cell: +94 77 3791887
>>
>>

Re: Blocker while adding parameter injection to RecipientList endpoint members

[Isuru Udana]

Hi Nuwan,

On Fri, Mar 10, 2023 at 6:37 PM Nuwan Jayawardene  wrote:

> Hi all,
> I'm currently working on the $subject and ran into a blocker while
> tackling serialization with injected environmental variables.
>
> In earlier applications of parameter injection (eg: WSDLEndpoint,
> AddressEndpoint) how I achieved injection is by modifying a particular
> setter method in the respective endpoint to ingest an environment variable
> value while preserving the original variable name. Latter was done to
> make serialization possible.
> An example is included herewith:
>
> [image: Selection_558.png]
>
> While working on RecipientList endpoints I've identified 2 parameters that
> are candidates for injection; httpPort and httpsPort.
> The XML value extraction happens in the factory in the method linked
> herewith:
>
> https://github.com/apache/synapse/blob/610baef00b1824d7d1341491ecc7f7d9b15485d3/modules/core/src/main/java/org/apache/synapse/config/xml/endpoints/RecipientListEndpointFactory.java#L147
>
> The issue I'm facing is that the extracted parameters are populating a
> class named *Member* which is provided by Axios2 which I cannot edit.
> While performing the injection in the factory works for deserialization,
> it doesn't work for serialization, which requires preserving the original
> environmental variable name, ideally in the Member class.
>
> I suppose extending Member and creating a new class for this purpose is a
> solution, however, I'm unsure if that would have cascading issues with
> other components of Synapse.
> Looking forward to hearing your feedback on this as well as alternative
> solutions.
>
I think we should skip this part. It's too complicated and not many people
are using this feature.

>
> Best
>
> --
> *Nuwan Jayawardene*
> https://www.linkedin.com/m/in/nuwanjaya
>
>
>

-- 
*Isuru Udana*
Director - Engineering
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: Selecting parameters for injection in Dynamic Load balancing

[Isuru Udana]

Hi Nuwan,

It looks like there are no environment dependant parameters in it. So
nothing needs to be done there.





On Thu, Feb 16, 2023 at 6:34 PM Nuwan Jayawardene  wrote:

> Hi all,
> I'm currently working on LoadBalance endpoints with regard to the Synapse
> containerization project
> <https://github.com/orgs/apache/projects/212/views/1>.
>
> So far, session-less load balancing seems to be working fine due to the
> work done on AddressEndpoints in PR #55
> <https://github.com/apache/synapse/pull/55>. In it, I'm injecting
> endpoint URIs via environment parameters.
> My current issue involves the dynamic load-balancing component of
> LoadBalance endpoints.
> Upon studying the Sample 57
> <https://synapse.apache.org/userguide/samples/sample57.html>
> configuration I'm unsure whether there are any 'injectable parameters' for
> dynamic load-balancing, especially considering there are no static URIs and
> nodes are discovered dynamically.
>
> I've already created a draft PR
> <https://github.com/apache/synapse/pull/79> with my current work. I'm
> hoping to add any changes and convert it to a finalized state based on the
> feedback received here.
> Hoping to hear your thoughts on this.
>
> Kind regards
> --
> *Nuwan Jayawardene*
> https://www.linkedin.com/m/in/nuwanjaya
>
>
>

-- 
*Isuru Udana*
Director - Engineering
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: Overloading ConfigUtils methods

[Isuru Udana]

Hi Nuwan,

fetchEnvironmentVariables is a utility method to fetch a particular
environment variable, can there be any other parameter types other than
string?

On Sun, Jan 22, 2023 at 12:21 PM Nuwan Jayawardene 
wrote:

> Hi all,
> I'm currently working on modifying the LoadBalance endpoint parameters
> (algorithm, members) to support parameter injection similar to how SOAP
> <https://github.com/n-jay/synapse/blob/61fb9e4da909b00d6da8dfe9fb57a3c0a5892793/modules/core/src/main/java/org/apache/synapse/endpoints/EndpointDefinition.java#L218>
> and WSDL
> <https://github.com/n-jay/synapse/blob/61fb9e4da909b00d6da8dfe9fb57a3c0a5892793/modules/core/src/main/java/org/apache/synapse/endpoints/WSDLEndpoint.java#L121>
> endpoints were amended in my PR
> <https://github.com/apache/synapse/pull/55>.
> You can note that I've used the fetchEnvironmentVariables method in
> ConfigUtils
> <https://github.com/n-jay/synapse/blob/61fb9e4da909b00d6da8dfe9fb57a3c0a5892793/modules/core/src/main/java/org/apache/synapse/config/xml/endpoints/utils/ConfigUtils.java>,
> for this purpose in the case of SOAP and WSDL endpoints.
> However, you'll also note that fetchEnvironmentVariables
> <https://github.com/n-jay/synapse/blob/61fb9e4da909b00d6da8dfe9fb57a3c0a5892793/modules/core/src/main/java/org/apache/synapse/config/xml/endpoints/utils/ConfigUtils.java#L26>
>  currently
> takes in a string argument whereas certain parameters deal with custom
> types such as LoadBalanceAlgorithm in the setAlgorithm
> <https://github.com/apache/synapse/blob/21bd3c960bb0b96cf5e78aa5ad52d782881ed42c/modules/core/src/main/java/org/apache/synapse/endpoints/LoadbalanceEndpoint.java#L267>
> method.
>
> Is it recommended that I *overload* the fetchEnvironmentVariables method
> for each new type I encounter or is it best if the existing 
> fetchEnvironmentVariables
> method *is **modified* to accommodate multiple types of parameters?
>
> Hoping to get some thoughts on this.
> Best
> --
> *Nuwan Jayawardene*
> https://www.linkedin.com/m/in/nuwanjaya
>
>
>

-- 
*Isuru Udana*
Director - Engineering
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: Should we target the next Synapse release this April

[Isuru Udana]

Hi Shafreen,

On Tue, Jun 7, 2022 at 9:13 PM shafreen anfar 
wrote:

> Hi Isuru,
>
> On Tue, Jun 7, 2022 at 8:49 PM Nuwan Jayawardene 
> wrote:
>
>> Unfortunately, still wasn't able to Shafreen.
>> Waiting for some suggestions from @Isuru Udana  about
>> the implementation 
>>
>> And there are some additional pending, although noncritical, PRs as well.
>>
>
> Any thoughts? Should we include those for the next release ?
>
I will review and merge this.
>
>>
>>
>>
>>
>> On Tue, Jun 7, 2022 at 8:17 PM shafreen anfar 
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> On Sat, Mar 12, 2022 at 10:06 AM Nuwan Jayawardene 
>>> wrote:
>>>
>>>> Hi Shafreen,
>>>>
>>>>> Let's try to include your functionality as well.
>>>>>
>>>> Awesome. I've already sent a PR with the first couple of changes.
>>>> Working on the rest of the changes atm.
>>>>
>>>
>>> Did you merge these changes ?
>>>
>>>
>>>>
>>>>  Let's explore the possibility of doing so while working on the release
>>>>> process.
>>>>>
>>>> Looking forward to it!
>>>>
>>>> Kind regards
>>>>
>>>>
>>>>
>>>> On Sat, Mar 12, 2022 at 9:02 AM shafreen anfar <
>>>> anfar.shafr...@gmail.com> wrote:
>>>>
>>>>> Hi Nuwan,
>>>>>
>>>>> On Sat, Mar 5, 2022 at 6:11 PM Nuwan Jayawardene 
>>>>> wrote:
>>>>>
>>>>>> Hi Shafreen,
>>>>>> I'm currently working on some functionality brought forward from the
>>>>>> GSoC 2021 project.
>>>>>> There's still some more work to do on that, however, in addition to
>>>>>> that, I'm interested in working on the Github Actions pipeline to
>>>>>> automate releases, if that's ok.
>>>>>>
>>>>>
>>>>> Let's try to include your functionality as well.
>>>>>
>>>>> Also, it is great to hear that you are interested in automating the
>>>>> release process using GitHub actions. Let's explore the possibility of
>>>>> doing so while working on the release process.
>>>>>
>>>>>
>>>>>> Thanks and regards
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Mar 4, 2022 at 10:57 PM shafreen anfar <
>>>>>> anfar.shafr...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Since we have done bug fixes and a few improvements, I wonder if we
>>>>>>> should do a Synapse release this April. As a post release task we should
>>>>>>> also look into using github actions to automate the steps in the release
>>>>>>> process. In fact, we wanted to do a release last year but unfortunately 
>>>>>>> we
>>>>>>> couldn't proceed.
>>>>>>>
>>>>>>> Anyway, I would like to hear from the community as well.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Shafreen
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Nuwan Jayawardene*
>>>>>> Assistant Lecturer, Informatics Institute of Technology (IIT).
>>>>>> Research Assistant, University of Moratuwa
>>>>>>
>>>>>> https://www.linkedin.com/m/in/nuwanjaya
>>>>>>
>>>>>>
>>>>
>>>> --
>>>> *Nuwan Jayawardene*
>>>> Assistant Lecturer, Informatics Institute of Technology (IIT).
>>>> Research Assistant, University of Moratuwa
>>>>
>>>> https://www.linkedin.com/m/in/nuwanjaya
>>>>
>>>>
>>
>> --
>> *Nuwan Jayawardene*
>> Assistant Lecturer, Informatics Institute of Technology (IIT).
>> Research Assistant, University of Moratuwa
>>
>> https://www.linkedin.com/m/in/nuwanjaya
>>
>>

-- 
*Isuru Udana*
Associate Director / Architect
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: Pull request template for Synapse

[Isuru Udana]

Hi Nuwan,

Yes we don't have a template for pull request description.
I am +1 to create something.
But by looking at the template you have used, I think some fields are not
useful.
Let's discuss and comeup with a new template for us.

Thanks.

On Fri, 3 Jun 2022, 15:05 Nuwan Jayawardene,  wrote:

> Hi all,
>>
>> While working on Synapse I noticed that there was no template for pull
>> requests as seen in other open-source projects. Therefore I went ahead and
>> added a template based on the one present in the WSO2 micro-integrator repo
>> (and other WSO2 products).
>>
> kind follow-up for some feedback on this.
>
> Thanks and regards
>
>
>
>
>
> On Thu, May 19, 2022 at 7:00 PM Nuwan Jayawardene 
> wrote:
>
>> Hi all,
>> While working on Synapse I noticed that there was no template for pull
>> requests as seen in other open-source projects. Therefore I went ahead and
>> added a template based on the one present in the WSO2 micro-integrator repo
>> (and other WSO2 products).
>>
>> The associated PR is linked herewith:
>> https://github.com/apache/synapse/pull/59
>>
>> Kind regards
>> --
>> *Nuwan Jayawardene*
>> Assistant Lecturer, Informatics Institute of Technology (IIT).
>> Research Assistant, University of Moratuwa
>>
>> https://www.linkedin.com/m/in/nuwanjaya
>>
>>
>>
>
> --
> *Nuwan Jayawardene*
> Assistant Lecturer, Informatics Institute of Technology (IIT).
> Research Assistant, University of Moratuwa
>
> https://www.linkedin.com/m/in/nuwanjaya
>
>
>

Re: Unable to find unit test class for WSDL endpoints

[Isuru Udana]

On Wed, Mar 23, 2022 at 9:05 AM Nuwan Jayawardene  wrote:

> Noted Isuru,
> shall I attempt to write a unit test to fill the gap if it's required?
>
+1

>
> Kind regards
>
>
>
>
> On Tue, Mar 22, 2022 at 11:42 PM Isuru Udana  wrote:
>
>> Hi Nuwan,
>>
>> It looks like there is no unit test exists for the WSDLEndpointFactory.
>>
>> Thanks.
>>
>> On Tue, Mar 22, 2022 at 9:44 AM Nuwan Jayawardene 
>> wrote:
>>
>>> Hi all,
>>> I recently created a PR adding new functionality to the
>>> AddressEndpointFactory
>>> <https://github.com/apache/synapse/pull/55/commits/a85a439e10a75d75a925e33414c2e75c5f07e1f5>
>>> class and associated unit test in the AddressEndpointSerializationTest
>>> <https://github.com/apache/synapse/pull/55/commits/6869b869892d0d26022aaddff0acc069a3d5b2bb>
>>> class.
>>>
>>> I'm currently trying to write the unit tests for similar functionality
>>> I've written for the WSDLEndpointFactory. However, I've been having some
>>> trouble finding out the associated unit tests for the methods in
>>> WSDLEndpointFactory.
>>>
>>> I tried debugging via mvn test -Dmaven.surefire.debug to find out if
>>> any unit test will hit my debug point but had no luck.
>>>
>>> Would appreciate some feedback on this.
>>> Kind regards
>>> --
>>> *Nuwan Jayawardene*
>>> Assistant Lecturer, Informatics Institute of Technology (IIT).
>>> Research Assistant, University of Moratuwa
>>>
>>> https://www.linkedin.com/m/in/nuwanjaya
>>>
>>>
>>>
>>
>> --
>> *Isuru Udana*
>> Associate Director / Architect
>> WSO2 Inc.; http://wso2.com
>> Member, Apache Software Foundation; http://www.apache.org
>>
>> *email: isud...@gmail.com * cell: +94 77 3791887
>>
>>
>
> --
> *Nuwan Jayawardene*
> Assistant Lecturer, Informatics Institute of Technology (IIT).
> Research Assistant, University of Moratuwa
>
> https://www.linkedin.com/m/in/nuwanjaya
>
>

-- 
*Isuru Udana*
Associate Director / Architect
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: Unable to find unit test class for WSDL endpoints

[Isuru Udana]

Hi Nuwan,

It looks like there is no unit test exists for the WSDLEndpointFactory.

Thanks.

On Tue, Mar 22, 2022 at 9:44 AM Nuwan Jayawardene  wrote:

> Hi all,
> I recently created a PR adding new functionality to the
> AddressEndpointFactory
> <https://github.com/apache/synapse/pull/55/commits/a85a439e10a75d75a925e33414c2e75c5f07e1f5>
> class and associated unit test in the AddressEndpointSerializationTest
> <https://github.com/apache/synapse/pull/55/commits/6869b869892d0d26022aaddff0acc069a3d5b2bb>
> class.
>
> I'm currently trying to write the unit tests for similar functionality
> I've written for the WSDLEndpointFactory. However, I've been having some
> trouble finding out the associated unit tests for the methods in
> WSDLEndpointFactory.
>
> I tried debugging via mvn test -Dmaven.surefire.debug to find out if any
> unit test will hit my debug point but had no luck.
>
> Would appreciate some feedback on this.
> Kind regards
> --
> *Nuwan Jayawardene*
> Assistant Lecturer, Informatics Institute of Technology (IIT).
> Research Assistant, University of Moratuwa
>
> https://www.linkedin.com/m/in/nuwanjaya
>
>
>

-- 
*Isuru Udana*
Associate Director / Architect
WSO2 Inc.; http://wso2.com
Member, Apache Software Foundation; http://www.apache.org

*email: isud...@gmail.com * cell: +94 77 3791887

Re: Should we target the next Synapse release this April

[Isuru Udana]

+1 for doing the release this April.

On Sat, Mar 5, 2022 at 6:11 PM Nuwan Jayawardene  wrote:

> Hi Shafreen,
> I'm currently working on some functionality brought forward from the GSoC
> 2021 project.
> There's still some more work to do on that, however, in addition to that,
> I'm interested in working on the Github Actions pipeline to
> automate releases, if that's ok.
>
> Thanks and regards
>
>
>
>
> On Fri, Mar 4, 2022 at 10:57 PM shafreen anfar 
> wrote:
>
>> Hi All,
>>
>> Since we have done bug fixes and a few improvements, I wonder if we
>> should do a Synapse release this April. As a post release task we should
>> also look into using github actions to automate the steps in the release
>> process. In fact, we wanted to do a release last year but unfortunately we
>> couldn't proceed.
>>
>> Anyway, I would like to hear from the community as well.
>>
>> Thanks,
>> Shafreen
>>
>
>
> --
> *Nuwan Jayawardene*
> Assistant Lecturer, Informatics Institute of Technology (IIT).
> Research Assistant, University of Moratuwa
>
> https://www.linkedin.com/m/in/nuwanjaya
>
>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Unable to resolve dependencies for synapse-extensions when building

[Isuru Udana]

Hi Nuwan,

Are you building with tests? If not can you please try build with tests?

On Mon, 27 Dec 2021, 10:10 Nuwan Jayawardene,  wrote:

> Hi all,
> I was recently building Synapse on a fresh machine and ran into the
> following error midway through;
>
> [ERROR] Failed to execute goal on project synapse-extensions: Could not
> resolve dependencies for project
> org.apache.synapse:synapse-extensions:bundle:3.0.2-SNAPSHOT: Could not find
> artifact org.apache.synapse:synapse-core:jar:tests:3.0.2-SNAPSHOT in
> apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1]
>
> A screenshot is also attached herewith;
> [image: image.png]
>
> Assuming it was an issue with my Java install or due to version
> incompatibility in the new machine I decided to wipe the .m2 repo of an
> older machine (where the build was successful thus far) and start a fresh
> build.
> This build too was met with the exact same error.
>
> Both machine environments have *Java SE 1.8.0_141* and *Maven 3.6.3 *
>
> Would greatly appreciate some thoughts on this.
> Kind regards
>
> --
> *Nuwan Jayawardene*
> Assistant Lecturer, Informatics Institute of Technology (IIT).
> Research Assistant, University of Moratuwa
>
> https://www.linkedin.com/m/in/nuwanjaya
>
>
>

Re: Importing new libraries into Synapse

[Isuru Udana]

Hi Nuwan,

Please find answers inline below.

On Tue, Sep 21, 2021 at 12:45 AM Nuwan Jayawardene 
wrote:

> [image: image.gif]Hi All,
>
>1. I did some further work on this and tried importing the new version
>of JUnit (version 5) using the following snippet in the pom.xml;[image:
>image.png]
>however, this did not prompt the newly added dependency to be
>downloaded after a mvn clean install.
>Would greatly appreciate some thoughts on how to rectify this.
>
> This version of the library might be already in your local m2 repo (.m2
directory).

>
>1. I also noticed that the repositories included in the pom.xml is
>only the WSO2 public maven repo and Maven central is not included.
>Is it allowed to include Maven central as well so there's access to a
>wider no. of external libraries?
>
> Yes. We can get libraries from Maven central.


> Kind regards
>
>
>
>
>
>
> On Fri, Sep 17, 2021 at 1:49 AM Nuwan Jayawardene 
> wrote:
>
>> Hi All,
>> I've a couple of doubts to clarify on importing external libraries into
>> Synapse.
>>
>>1. Is there a vouching process to see if a particular library is
>>suitable to be used (other than the license).
>>
>> The license is the most important factor. If you are introducing a new
dependency, please initiate a mail and discuss it with the community before
proceeding.

>
>>1. When adding a new dependency after including it in the pom.xml as
>>follows...
>>[image: image.png]
>>is running a mvn clean install or mvn install -Dmaven.test.skip=true 
>> sufficient
>>or do we need to delete the .m2 directory as well and redownload all the
>>dependencies?
>>
>> If you already have the particular version of the library in your local
m2 repo (.m2 directory) it won't download again until you delete it from
the .m2 directory.

>
>>1.
>>I tried the 2 former commands however it doesn't seem to
>>have downloaded the library from maven central.
>>
>> Would appreciate your thoughts on this.
>> Regards
>> --
>> *Nuwan Jayawardene*
>> Assistant Lecturer, Informatics Institute of Technology (IIT).
>> Research Assistant, University of Moratuwa
>>
>> https://www.linkedin.com/m/in/nuwanjaya
>>
>>
>>
>
> --
> *Nuwan Jayawardene*
> Assistant Lecturer, Informatics Institute of Technology (IIT).
> Research Assistant, University of Moratuwa
>
> https://www.linkedin.com/m/in/nuwanjaya
>
>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: [Proposal] Providing tooling support for Synapse

[Isuru Udana]

Hi Nadeeshaan,

This is a great idea.
+1 for preparing a proposal.

Are you mainly looking into code editing experience or do you think we can
implement a graphical editor on top of that?

Thank you.

On Fri, Aug 13, 2021 at 12:31 AM Nadeeshaan Gunasinghe <
nadeeshaangunasin...@gmail.com> wrote:

> Hi all,
>
> I would like to initiate a proposal for providing the tooling support for
> Synapse. As the first step, we can provide a VSCode plugin for synapse
> developers with the following features.
>
> 1. Content Assist
> 2. Syntax highlighting
> 3. Jump to definitions
> 4. Rename and etc.
>
> If we can get the language smartness provider backend implemented with a
> Language Server implementation, it is easy to provide the same tooling
> capabilities for various editors, including cloud-based as well as desktop
> editors.
>
> Appreciate your feedback on this.
>
> Cheers,
>
> *Nadeeshaan Gunasinghe*
> Technical Lead, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <https://mail.google.com/mail/u/1/#>
> <http://www.facebook.com/nadeeshaan.gunasinghe>
> <http://lk.linkedin.com/in/nadeeshaan> <http://twitter.com/Nadeeshaan>
> <http://nadeeshaan.blogspot.com/>
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Verifying CI/CD state of Synapse GitHub repo

[Isuru Udana]

Hi Nuwan,

On Wed, Apr 7, 2021 at 6:28 PM Nuwan Jayawardene  wrote:

> Hi,
> I've recently been working on the Apache Synapse project and need to get
> some questions/doubts cleared regarding the repository.
>
> 1. Is the https://github.com/apache/synapse repo the actual repo used by
> Synapse devs or is it a mirror?
>
This is the actual repo. This was initially created as a mirror for the svn
repository and now we have made it the mainstream.

> 2. I noticed something odd while perusing the README, in that the "synapse
> daily build passing" badge seems to be a static .svg and not connected to a
> build configuration .yml.
>
@Shafreen  can you please check on this?


> [image: image.png]
> Clicking on it also opens a separate window for an image file.
> [image: image.png]
> Is this on purpose or am I mistaken?
>
> Regards
>
> --
>
> *Nuwan Jayawardene*
> Visiting Lecturer, Informatics Institute of Technology (IIT).
> Research Assistant, University of Moratuwa
> Tel - +94 71 181 3299
> https://www.linkedin.com/m/in/nuwanjaya
>
>
>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Improving Message Forwarding Processor Deactivate Implementation

[Isuru Udana]

Hi Shafreen,

On Wed, 2 Dec 2020, 22:00 Shafreen,  wrote:

> Hi All,
>
> At the moment when we deactivate the Message Forwarding Processor (MFP)
> what happens internally is that the scheduler keeps on executing the MFP
> according to the given interval. Inside the MFP we just have an if
> condition to check whether the MFP is deactivated. If so, it will
> immediately skip the execution of MFP.
>
> IMO, this redundant execution of MFP wastes CPU cycles. This could be
> especially problematic, when running in a constrained environment where the
> CPU cycles are limited. We can improve the implementation by deactivating
> the scheduler job itself and reactivating when needed.
>
> WDYT ?
>
+1. That should be the correct solution.

>
> Thanks,
> Shafreen
>

Re: Improving how Target Endpoint is Associated with Message Forwarding Processor

[Isuru Udana]

Thanks Shafreen. I reviewed it and suggested a few minor modifications.

On Sun, Nov 1, 2020 at 11:42 AM Shafreen  wrote:

> Hi All,
>
> Please find the below PR for this improvement.
>
> https://github.com/apache/synapse/pull/50
>
> I will send another PR updating the doc once this is merged.
>
> On Sat, Oct 17, 2020 at 9:27 AM Vanjikumaran Sivajothy <
> vanjikuma...@gmail.com> wrote:
>
>> I agree with your suggestion; it is much better clean design approach.
>>
>>
>> On Fri, Oct 16, 2020 at 8:34 PM Shafreen 
>> wrote:
>>
>>> Hi All,
>>>
>>> Any opinion on this?
>>>
>>> On Sun, Oct 11, 2020 at 11:45 AM Shafreen 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Each Message Forwarding Processor must have a target endpoint. At the
>>>> moment we configure this target endpoint by adding a property in the
>>>> in-sequence of proxy service as follows.
>>>>
>>>> 
>>>>
>>>> IMO, this way of associating target-endpoint with Message Forwarding
>>>> Processor is not only error prone but also less readable. Therefore, I
>>>> think we can improve configuring target endpoint by making it at an
>>>> attribute of the Message Forwarding Processor as follows,
>>>>
>>>> >>> "org.apache.synapse.message.processors.forward.ScheduledMessageForwardingProcessor"
>>>> name="ScheduledProcessor" messageStore="MyStore"
>>>> *targetEndpoint="StockQuoteServiceEp"*> 
>>>> 1 3
>>>> true 
>>>>
>>>> WDYT ?
>>>>
>>> --
>> Sent from Gmail Mobile
>>
>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Something has gone wrong in the github daily build workflow

[Isuru Udana]

+1, let's remove it.

On Sun, Oct 11, 2020 at 12:01 PM Shafreen  wrote:

> On Mon, Sep 21, 2020 at 8:02 PM Shafreen  wrote:
>
>> Hi All,
>>
>> It seems the badge is broken, should we remove it ?
>>
>
> Kind reminder. IMO, It doesn't look good when you go to github and see
> this as the first sight.
>
> https://github.com/apache/synapse
>
>
>>
>>
>> On Wed, Sep 16, 2020 at 8:50 PM Shafreen 
>> wrote:
>>
>>> On Mon, Aug 24, 2020 at 10:40 PM Vanjikumaran Sivajothy <
>>> vanjikuma...@gmail.com> wrote:
>>>
>>>> Ack,
>>>> Was there any documented anomaly?
>>>>
>>>
>>> Sorry for the late reply. It seems the issue is happening when building
>>> with java 8. I could see a few NPEs in the log file, which is caused when
>>> setting up the SSL connection. This only happens in the github environment.
>>> I could not reproduce this locally. However, it seems others don't have the
>>> same problem. I did a bit of googling but no luck.
>>>
>>> For now, I have removed [1] Java 8 from both daily and PR builds. I am
>>> further looking into this. Once I figure it out, I will incorporate java 8
>>> back into the build.
>>>
>>> [1] https://github.com/apache/synapse/pull/49
>>>
>>>
>>>>
>>>> On Mon, Aug 24, 2020 at 9:31 AM Shafreen 
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Please find the fix for the daily build. Basically, for now I have
>>>>> removed the build matrix and just configured the build to run on
>>>>> latest-ubuntu with Java 8. I will send another PR to include a workflow to
>>>>> build on windows.
>>>>>
>>>>> https://github.com/apache/synapse/pull/48
>>>>>
>>>>> On Tue, Aug 11, 2020 at 10:39 PM Shafreen 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> It seems something has gone wrong in the github daily build workflow.
>>>>>> I think this is due to some changes on github side. I am looking into it.
>>>>>>
>>>>>> Thanks,
>>>>>> Shafreen
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Vanji
>>>>
>>>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Next Apache Synapse Release 3.0.2

[Isuru Udana]

+1

On Wed, Oct 7, 2020 at 10:12 PM Vanjikumaran Sivajothy <
vanjikuma...@gmail.com> wrote:

> Hi Dev,
> We do have a considerable amount of patch applied to do the next release.
> Therefore, shall we initiate the next release process?
>
>
> --
> Best Regards,
> Vanji
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Message Forwarding Processor consumes all the messages at once

[Isuru Udana]

e interval that is there for
>>>>>>>>>> Message Processor.
>>>>>>>>>>
>>>>>>>>>> On Fri, May 29, 2020 at 12:04 PM Vanjikumaran Sivajothy <
>>>>>>>>>> vanjikuma...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> What about the configuration of the interval?
>>>>>>>>>>>
>>>>>>>>>>> On Thu, May 28, 2020 at 8:53 AM Shafreen <
>>>>>>>>>>> anfar.shafr...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>
>>>>>>>>>>>> How about a property name as below? we can make it false by
>>>>>>>>>>>> default which would give us the current behaviour.
>>>>>>>>>>>>
>>>>>>>>>>>> true
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, May 25, 2020 at 10:41 AM prabath 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +1 to support both behaviors.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, May 24, 2020 at 12:26 AM Shafreen <
>>>>>>>>>>>>> anfar.shafr...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Vanji,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, May 23, 2020 at 2:51 PM Vanjikumaran Sivajothy <
>>>>>>>>>>>>>> vanjikuma...@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Let’s consider the current behaviors as a default.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Adding additional Optional property may control to make sure
>>>>>>>>>>>>>>> the backward comparability.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Okay. We can add a new parameter, that way we can have both
>>>>>>>>>>>>>> behaviors as you mentioned.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, May 23, 2020 at 12:46 AM Shafreen <
>>>>>>>>>>>>>>> anfar.shafr...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Current behaviour of the Message Forwarding Processor is to
>>>>>>>>>>>>>>>> consume all the messages at once. For instance, say, the 
>>>>>>>>>>>>>>>> Message Forwarding
>>>>>>>>>>>>>>>> Processor is configured to run every 10 seconds and the 
>>>>>>>>>>>>>>>> Message store is
>>>>>>>>>>>>>>>> filled with 5 messages within the 10 second gap. In such a 
>>>>>>>>>>>>>>>> situation,
>>>>>>>>>>>>>>>> Message Forwarding Processor consumes all 5 messages and try 
>>>>>>>>>>>>>>>> to send it to
>>>>>>>>>>>>>>>> back-end as fast as possible. I think this behaviour is not 
>>>>>>>>>>>>>>>> optimal. The
>>>>>>>>>>>>>>>> purpose of Message Forwarding Processor it to send messages to 
>>>>>>>>>>>>>>>> the back-end
>>>>>>>>>>>>>>>> in a controlled rate. So that the back-end server can handle 
>>>>>>>>>>>>>>>> the load. IMO,
>>>>>>>>>>>>>>>> ideal behaviour should be to consume one message at a time and 
>>>>>>>>>>>>>>>> try to send
>>>>>>>>>>>>>>>> it to the back-end as per the configured interval.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> However, if the configured interval is a cron expression,
>>>>>>>>>>>>>>>> in such cases the current behaviour is correct. Because cron 
>>>>>>>>>>>>>>>> expressions
>>>>>>>>>>>>>>>> could have very large intervals.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Therefore, I think it is best to keep the current behaviour
>>>>>>>>>>>>>>>> for cron intervals but change it for normal intervals as 
>>>>>>>>>>>>>>>> aforementioned.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> WDYT ?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Shafreen
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Prabath Ariyarathna.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Best Regards,
>>>>>>>>>>> Vanji
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Best Regards,
>>>>>>> Vanji
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Vanji
>>>>>
>>>>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: [Message Processor] Fault sequence is not invoked in OUT_ONLY scenario

[Isuru Udana]

Hi Shafreen,

I have merged the PR.

Thanks.

On Sat, May 16, 2020 at 9:23 PM Shafreen  wrote:

> Hi All,
>
> Build has passed for this PR. Please do have a look when you all get some
> free time.
>
> On Sat, May 2, 2020 at 7:51 PM Shafreen  wrote:
>
>> Hi All
>>
>> On Thu, Apr 23, 2020 at 8:19 PM shafreen anfar 
>> wrote:
>>
>>> On Sun, Apr 19, 2020 at 3:28 PM Ravi Undupitiya <
>>> ravi.undupit...@gmail.com> wrote:
>>>
>>>> It makes sense to do this. The idea of the fault sequence is for it to
>>>> be used as an exception handling sequence, so OUT_ONLY should not change
>>>> this.
>>>>
>>>
>>> Yeah, will send a PR fixing this.
>>>
>>
>> The below PR has the fix for the discussed issue.
>>
>> https://github.com/apache/synapse/pull/45
>>
>>
>>>
>>>
>>>>
>>>> On Sun, 19 Apr 2020 at 1:08 pm, shafreen anfar <
>>>> anfar.shafr...@gmail.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> At the moment, when there is a failure in Message Processor (i.e.
>>>>> Connection refused) fault sequence is not invoked in OUT_ONLY scenario.
>>>>> IMO, we should invoke fault sequence even in  OUT_ONLY scenario. What do
>>>>> you all think ?
>>>>>
>>>>> Thanks,
>>>>> Shafreen
>>>>>
>>>>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Do we need to make sure build works on Java 1.7 ?

[Isuru Udana]

Hi Shafreen,

We haven't stopped the support for JDK 1.7. So, Yes. build should work in
1.7

Thanks.

On Sat, Apr 11, 2020 at 11:11 AM shafreen anfar 
wrote:

> Hi All,
>
> If so, I can update the build matrix to run on java 1.7 as well.
>
> Thanks,
> Shafreen
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Improving Message Forwarding Processor (MFP) to support HTTP status codes

[Isuru Udana]

Hi Shafreen,

This is a very useful feature. We'll review and merge the PR.

Thanks. Regards

On Sat, Mar 28, 2020 at 10:23 PM shafreen anfar 
wrote:

> Hi All,
>
> At the moment, current MFP implementation does not support retrying based
> on HTTP status codes. It only supports retrying for transport level
> failures but not for application level failures. As you know, in HTTP
> protocol, application level failures are distinguished using different
> status codes. In the case of MFP, it is important to be able to retry for
> 5xx server errors. But there also could be rare occasions in which retrying
> for 4xx and 3xx are useful. Especially when dealing with servers that do
> not follow HTTP protocol exactly as it is.
>
> Therefore, I have improved MFP implementation to support retrying based on
> the returned HTTP status code as well. Say, a user wants to retry for HTTP
> status codes 500 and 504 but not for any other HTTP status code. In that
> case user can configure the MFP as below. Please note the parameter in bold
> font which I have introduced along with this feature.
>
> http://ws.apache.org/ns/synapse;
>
> class="org.apache.synapse.message.processors.forward.ScheduledMessageForwardingProcessor"
>   name="Processor2"
>   messageStore="JMSMS">
>4
> name="message.processor.reply.sequence">replySequence
>1000
>*500, 504*
> 
>
> Please not that the above parameter does not come to effect in case of
> out-only. Implementation of this feature can be found in [1]. Once this is
> merged, I am planning to send another PR for the required documentation
> changes.
>
> [1] https://github.com/apache/synapse/pull/32
>
> Thanks,
> Shafreen
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Adding another interval for retry in Scheduled Message Forwarding Processor (SMFP)

[Isuru Udana]

Hi Shafreen,

+1, as you said fetching messages and retrying are two different concepts
and we need to have two configurable parameters.

Thanks.

On Sun, Mar 29, 2020 at 10:32 AM shafreen anfar 
wrote:

> Hi All,
>
> At the moment we only support one interval for both fetching messages from
> the store and retrying when there is a failure. But, IMO, these are two
> different concepts and deserve two different configurations. Therefore, I
> am proposing a new configuration parameter for latter. Something as below,
>
> 1
>
> This will allow the user to control the speed of retry when there is a
> failure.
>
> What do you think?
>
> Thanks,
> Shafreen
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

[jira] [Commented] (SYNAPSE-1118) Support for CIFS-based integrations via JCIFS

[Isuru Udana (Jira)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066605#comment-17066605
 ] 

Isuru Udana commented on SYNAPSE-1118:
--

Great. If you have any questions, please feel free to raise them on 
dev@synapse.apache.org mailing list.

> Support for CIFS-based integrations via JCIFS
> -
>
> Key: SYNAPSE-1118
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1118
> Project: Synapse
>  Issue Type: New Feature
>  Components: Transports
> Environment: Microsoft Windows, Linux
>Reporter: Luis Mendes
>Assignee: Isuru Udana
>Priority: Minor
>  Labels: features
>
> The idea is to introduce support for basic access to remote 
> directories/shares, typically on LAN, via CIFS. This will enhance the 
> integration capabilities of Apache Synapse specifically in the context of EAI.
> To this end, I suggest the use of the JCifs API 
> ([https://github.com/codelibs/jcifs)] and work with the current solution 
> development and configuration model of Synapse to easily manipulate and 
> configure the usage of JCifs in accessing shared directories in either 
> Windows or Linux based shared directories.
> JCifs has support for several authentication mechanisms, which as I see it, 
> should be made easy to configure and use through Apache Synapse. In order to 
> make this feature more manageable, I will be primarily investing my time in 
> the support for the most basic domain-based user/password authentication 
> (NTLM). Support for Kerberos based authentication will, potentially, be 
> deferred to future versions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1117) Adding CI Badge in the Github ReadMe file

[Isuru Udana (Jira)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057534#comment-17057534
 ] 

Isuru Udana commented on SYNAPSE-1117:
--

Should we put CI build status or the Jenjins build status? I think it should be 
jenkins.

> Adding CI Badge in the Github ReadMe file
> -
>
> Key: SYNAPSE-1117
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1117
> Project: Synapse
>  Issue Type: Wish
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>Priority: Minor
> Attachments: Screen Shot 2020-03-11 at 12.43.56 PM.png
>
>
> Adding this badge will indicate the stability of the build-in read me itself.
> !Screen Shot 2020-03-11 at 12.43.56 PM.png|width=512,height=154!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Closed] (SYNAPSE-1116) Log mediator doesn't work as expected when category set to DEBUG

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana closed SYNAPSE-1116.


> Log mediator doesn't work as expected when category set to DEBUG
> 
>
> Key: SYNAPSE-1116
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1116
> Project: Synapse
>  Issue Type: Improvement
>Affects Versions: 3.0.1
>Reporter: Mohamad Anfar Mohamad Shafreen
>    Assignee: Isuru Udana
>Priority: Major
>
> Consider the below Proxy service in which I have configured the log-mediator 
> to print logs only when the category is set to DEBUG. However, there is no 
> way to start the server with log-mediator debug logs enabled. 
> Only way to print the property values inside the log mediator is by 
> configuring debug mode for the class in the log4j.properties. But this is 
> wrong because aforementioned configuration is there for the implementer of 
> log-mediator but not for the synapse user.
>  
> {code:java}
> http://ws.apache.org/ns/synapse;
>name="test"
>transports="http,https"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  
> 
>  
>  
>   
>
>
> 
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1116) Log mediator doesn't work as expected when category set to DEBUG

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1116.
--
Resolution: Fixed

Closing the issue as PR is merged. Thanks for your contribution.

> Log mediator doesn't work as expected when category set to DEBUG
> 
>
> Key: SYNAPSE-1116
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1116
> Project: Synapse
>  Issue Type: Improvement
>Affects Versions: 3.0.1
>Reporter: Mohamad Anfar Mohamad Shafreen
>    Assignee: Isuru Udana
>Priority: Major
>
> Consider the below Proxy service in which I have configured the log-mediator 
> to print logs only when the category is set to DEBUG. However, there is no 
> way to start the server with log-mediator debug logs enabled. 
> Only way to print the property values inside the log mediator is by 
> configuring debug mode for the class in the log4j.properties. But this is 
> wrong because aforementioned configuration is there for the implementer of 
> log-mediator but not for the synapse user.
>  
> {code:java}
> http://ws.apache.org/ns/synapse;
>name="test"
>transports="http,https"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  
> 
>  
>  
>   
>
>
> 
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Build fails with integration test

[Isuru Udana]

Jenkins build has passed with these changes.

On Wed, Mar 11, 2020 at 6:29 AM Vanjikumaran Sivajothy <
vanjikuma...@gmail.com> wrote:

> Given Pull request for the fix is Merged.
>
> On Tue, Mar 10, 2020 at 5:55 PM Isuru Udana  wrote:
>
>> Hi All,
>>
>> I sent a PR to fix this issue.
>> https://github.com/apache/synapse/pull/26
>>
>> Thanks.
>>
>> On Mon, Mar 9, 2020 at 9:05 PM Isuru Udana  wrote:
>>
>>> Hi Shafreen,
>>>
>>> I am also experiencing the same. I will create a new certificate for
>>> Synapse.
>>>
>>> Thanks.
>>>
>>> On Sun, Mar 8, 2020 at 10:30 PM shafreen anfar 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Test case for, Sample 100: Using WS-Security for outgoing messages is
>>>> failing on master. It seems certificates related to this test expired.
>>>> Following is the error I get. Does anyone else come-across the same issue ?
>>>>
>>>> org.apache.axis2.AxisFault: The signature or decryption was invalid
>>>> (The provided certificate is invalid)
>>>> at
>>>> org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
>>>> at
>>>> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95)
>>>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:335)
>>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:308)
>>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:250)
>>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:156)
>>>> at
>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:178)
>>>> at
>>>> org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:454)
>>>> at
>>>> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:280)
>>>> at
>>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>> Caused by: org.apache.ws.security.WSSecurityException: The signature or
>>>> decryption was invalid (The provided certificate is invalid)
>>>> at
>>>> org.apache.ws.security.validate.SignatureTrustValidator.validateCertificates(SignatureTrustValidator.java:106)
>>>> at
>>>> org.apache.ws.security.validate.SignatureTrustValidator.validate(SignatureTrustValidator.java:68)
>>>> at
>>>> org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:186)
>>>> at
>>>> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:402)
>>>> at
>>>> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:309)
>>>> at
>>>> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:254)
>>>> at org.apache.rampart.RampartEngine.process(RampartEngine.java:161)
>>>> at
>>>> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
>>>> ... 11 more
>>>> Caused by: java.security.cert.CertificateExpiredException: *NotAfter:
>>>> Wed Mar 04 23:17:59 IST 2020*
>>>> at
>>>> sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
>>>> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
>>>> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
>>>> at
>>>> org.apache.ws.security.validate.SignatureTrustValidator.validateCertificates(SignatureTrustValidator.java:103)
>>>>
>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Associate Director/Architect
>>>
>>>
>>>
>>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>>>  *
>>>
>>>
>>>
>>
>> --
>> *Isuru Udana*
>> Associate Director/Architect
>>
>>
>>
>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>>  *
>>
>>
>>
>
> --
> Best Regards,
> Vanji
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Add an improvement to log-mediator

[Isuru Udana]

Hi Shafreen,

I have merged the Pull request. Can you please send a PR to update the
documentation as well?

Thanks.

On Fri, Mar 6, 2020 at 7:06 AM shafreen anfar 
wrote:

> On Thu, Mar 5, 2020 at 7:42 AM Sagara Gunathunga <
> sagara.gunathu...@gmail.com> wrote:
>
>>
>>
>> Although this makes the life easier by eliminating the log4j.properties
>> modifications, still, one has to restart the server to see debug logs. It
>> would have been great to have a simple remote API to make these changes on
>> a running server.
>>
>
> Agreed. Having to restart could be problematic, especially in production
> environment. I will check how we can improve this further as the next step.
> Also, log4j.properties modification actually prints logs related to
> implementation of log-mediator along with synapse user log-mediator output.
> Provided fix eliminates these additional logs.
>
>
>>
>> BTW this is a useful improvement; but, you need to think about a better
>> name than "synapseDebug" to reflect the purpose of this setting. To me,
>> synapseDebug implies that the whole server will be in debug mode and can be
>> connected through an IDE.  What about more descriptive and generic name
>> like this   *-synapse.mediator.log.level.debug* that can be used to
>> change the log of the level of log mediator without limiting to debug
>> only?
>>
>> Thanks!
>>
>> On Thu, Mar 5, 2020 at 2:06 PM shafreen anfar 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am Shafreen and I've been working with Synapse for many years. With
>>> this mail I am sending a fix [1] to solve one of the issues I've been
>>> facing.
>>>
>>> At the moment, even though log-mediator has a category called DEBUG,
>>> there is no way to enable this category. Therefore, no logs are printed
>>> under this category. The only workaround we have for this problem is to
>>> enable debug logs for log-mediator class itself by configuring
>>> log4j.properties file. But I believe, this configuration is for people who
>>> implement log-mediator but not for synapse users.
>>>
>>> IMO, synapse users should be able to enable debug mode of the
>>> log-mediator without touching the log4j.properties file. As a solution, I
>>> have done a fix [1] in which synapse users can start the server as follows,
>>>
>>> sh synapse.sh -synapseDebug
>>>
>>> When the server is started with the above flag, all the logs of
>>> log-mediator under the category DEBUG is printed. For more information,
>>> please have a look at [1] and [2]. Also, please note that the provided fix
>>> is tested in both linux and windows.
>>>
>>> [1] https://github.com/apache/synapse/pull/24
>>> [2] https://issues.apache.org/jira/browse/SYNAPSE-1116
>>>
>>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog  - http://ssagara.blogspot.com
>> Web  - http://people.apache.org/~sagara/
>> LinkedIn - http://www.linkedin.com/in/ssagara
>>
>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Continuous Integration (CI) with Github Actions

[Isuru Udana]

Hi Shafreen,

I have merged the pull request.
I still can't see the workflow get attached to the existing PRs, does it
only work for the new PRs?



On Tue, Mar 10, 2020 at 10:46 PM Vanjikumaran Sivajothy <
vanjikuma...@gmail.com> wrote:

> Shafreen,
> +1 for the Github Workflow.
>
> adding fortnightly build action plan also allow, us to monitor these
> certificate issue.
> Will you be able to look into that too?
>
> On Tue, Mar 10, 2020 at 10:10 AM Isuru Udana  wrote:
>
>> +1
>> Let me first check the current build failure before merging this.
>>
>> On Tue, Mar 10, 2020 at 7:01 PM Madhawa Kasun Gunasekara <
>> madhaw...@gmail.com> wrote:
>>
>>> +1
>>> This is great.
>>>
>>>
>>> On Tue, Mar 10, 2020 at 2:18 PM shafreen anfar 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> At the moment, when there is a new PR, we always have to build locally
>>>> to make sure the new PR doesn't introduce any regression issues. However,
>>>> with Github Actions we can automate this effort with zero cost. I have
>>>> written a Github workflow to automatically build new PRs to check its
>>>> validity. Current Github workflow only runs on latest-ubuntu with Java 8.
>>>> However, we can further improve it as we move forward. Please, find the PR
>>>> for this improvement in link [1]. Once merged it will look like in the
>>>> below image.
>>>>
>>>> [image: image.png]
>>>>
>>>> [1] https://github.com/apache/synapse/pull/25
>>>>
>>>> Thanks
>>>> Shafreen
>>>>
>>>
>>
>> --
>> *Isuru Udana*
>> Associate Director/Architect
>>
>>
>>
>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>>  *
>>
>>
>>
>
> --
> Best Regards,
> Vanji
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: OpenJDK Support (was: Introducing Docker and K8S artifacts)

[Isuru Udana]

On Wed, Nov 27, 2019 at 5:38 AM Isuru Udana  wrote:

> Hi All,
>
> As we discussed, I tried to configure Jenkins to use OpenJDK 8 for our
> Jenkins build. But unfortunately, it has been deprecated by the
> infrastructure team[1].
> Apache POI project has reported a Jira ticket[2] asking to put it back as
> they require it.
> I also commented on the same ticket mentioning our requirements. Let's
> wait for few days to see whether we get a resolution.
>

Infra team has added back the OpenJDK 1.8 242 to the Jenkins yesterday. We
can move forward with that.

>
> [1]
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
> [2] https://issues.apache.org/jira/browse/INFRA-19411
>
>
> ------ Forwarded message -
> From: Isuru Udana 
> Date: Wed, Nov 20, 2019 at 9:22 PM
> Subject: Re: Introducing Docker and K8S artifacts
> To: 
>
>
> +1 for the idea. I think it's a good time to think about the overall
> strategy of the project too.
>
> For testing synapse in OpenJDK, I can configure Jenkins build to use
> OpenJDK.
>
> On Wed, Nov 20, 2019 at 11:07 AM Ravi Undupitiya <
> ravi.undupit...@gmail.com> wrote:
>
>> I think this is a great idea. There was some discussion around using OSGi
>> for containerisation, but in a World of docker and k8s a lot of the uses
>> cases for OSGi will be catered for and I can only think of a very limited
>> set of use cases for needing both.
>>
>> We should probably base off OpenJDK for this and given the recent Oracle
>> licensing changes we should move to OpenJDK.
>>
>> On Wed, 20 Nov 2019 at 16:06, Vanjikumaran Sivajothy <
>> vanjikuma...@gmail.com> wrote:
>>
>>> Hi Dev,
>>>
>>> Recently we moved the Apache synapse codebase to GitHub successfully and
>>> started to merge the existing pull request after careful consideration.
>>>
>>> As the next step for synapse development, I would like to propose to
>>> Introduce Docker and K8s artifacts for apache synapse to enable users to
>>> use the Apache synapse in the container ecosystem.
>>>
>>> I have created few issues in jira tickets[1]; If anyone
>>> interested pleases send a pull request
>>>
>>> [1]https://issues.apache.org/jira/browse/SYNAPSE-
>>> --
>>> Best Regards,
>>> Vanji
>>>
>>
>
> --
> *Isuru Udana*
> Senior Technical Lead
>
>
>
>
> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>  blog: http://mytecheye.blogspot.com/
> <http://mytecheye.blogspot.com/>*
>
>
>
>
>
> --
> *Isuru Udana*
> Senior Technical Lead
>
>
>
>
> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>  blog: http://mytecheye.blogspot.com/
> <http://mytecheye.blogspot.com/>*
>
>
>
>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Build fails with integration test

[Isuru Udana]

Hi All,

I sent a PR to fix this issue.
https://github.com/apache/synapse/pull/26

Thanks.

On Mon, Mar 9, 2020 at 9:05 PM Isuru Udana  wrote:

> Hi Shafreen,
>
> I am also experiencing the same. I will create a new certificate for
> Synapse.
>
> Thanks.
>
> On Sun, Mar 8, 2020 at 10:30 PM shafreen anfar 
> wrote:
>
>> Hi All,
>>
>> Test case for, Sample 100: Using WS-Security for outgoing messages is
>> failing on master. It seems certificates related to this test expired.
>> Following is the error I get. Does anyone else come-across the same issue ?
>>
>> org.apache.axis2.AxisFault: The signature or decryption was invalid (The
>> provided certificate is invalid)
>> at
>> org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
>> at
>> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95)
>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:335)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:308)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:250)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:156)
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:178)
>> at
>> org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:454)
>> at
>> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:280)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: org.apache.ws.security.WSSecurityException: The signature or
>> decryption was invalid (The provided certificate is invalid)
>> at
>> org.apache.ws.security.validate.SignatureTrustValidator.validateCertificates(SignatureTrustValidator.java:106)
>> at
>> org.apache.ws.security.validate.SignatureTrustValidator.validate(SignatureTrustValidator.java:68)
>> at
>> org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:186)
>> at
>> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:402)
>> at
>> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:309)
>> at
>> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:254)
>> at org.apache.rampart.RampartEngine.process(RampartEngine.java:161)
>> at
>> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
>> ... 11 more
>> Caused by: java.security.cert.CertificateExpiredException: *NotAfter:
>> Wed Mar 04 23:17:59 IST 2020*
>> at
>> sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
>> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
>> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
>> at
>> org.apache.ws.security.validate.SignatureTrustValidator.validateCertificates(SignatureTrustValidator.java:103)
>>
>
>
> --
> *Isuru Udana*
> Associate Director/Architect
>
>
>
> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>  *
>
>
>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Continuous Integration (CI) with Github Actions

[Isuru Udana]

+1
Let me first check the current build failure before merging this.

On Tue, Mar 10, 2020 at 7:01 PM Madhawa Kasun Gunasekara <
madhaw...@gmail.com> wrote:

> +1
> This is great.
>
>
> On Tue, Mar 10, 2020 at 2:18 PM shafreen anfar 
> wrote:
>
>> Hi All,
>>
>> At the moment, when there is a new PR, we always have to build locally to
>> make sure the new PR doesn't introduce any regression issues. However, with
>> Github Actions we can automate this effort with zero cost. I have written a
>> Github workflow to automatically build new PRs to check its validity.
>> Current Github workflow only runs on latest-ubuntu with Java 8. However, we
>> can further improve it as we move forward. Please, find the PR for this
>> improvement in link [1]. Once merged it will look like in the below image.
>>
>> [image: image.png]
>>
>> [1] https://github.com/apache/synapse/pull/25
>>
>> Thanks
>> Shafreen
>>
>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Build fails with integration test

[Isuru Udana]

Hi Shafreen,

I am also experiencing the same. I will create a new certificate for
Synapse.

Thanks.

On Sun, Mar 8, 2020 at 10:30 PM shafreen anfar 
wrote:

> Hi All,
>
> Test case for, Sample 100: Using WS-Security for outgoing messages is
> failing on master. It seems certificates related to this test expired.
> Following is the error I get. Does anyone else come-across the same issue ?
>
> org.apache.axis2.AxisFault: The signature or decryption was invalid (The
> provided certificate is invalid)
> at
> org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
> at
> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:95)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:335)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:308)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:250)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:156)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:178)
> at
> org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:454)
> at
> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:280)
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ws.security.WSSecurityException: The signature or
> decryption was invalid (The provided certificate is invalid)
> at
> org.apache.ws.security.validate.SignatureTrustValidator.validateCertificates(SignatureTrustValidator.java:106)
> at
> org.apache.ws.security.validate.SignatureTrustValidator.validate(SignatureTrustValidator.java:68)
> at
> org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:186)
> at
> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:402)
> at
> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:309)
> at
> org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:254)
> at org.apache.rampart.RampartEngine.process(RampartEngine.java:161)
> at
> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
> ... 11 more
> Caused by: java.security.cert.CertificateExpiredException: *NotAfter: Wed
> Mar 04 23:17:59 IST 2020*
> at
> sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
> at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> at
> org.apache.ws.security.validate.SignatureTrustValidator.validateCertificates(SignatureTrustValidator.java:103)
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

Re: Add an improvement to log-mediator

[Isuru Udana]

On Thu, Mar 5, 2020 at 7:42 AM Sagara Gunathunga <
sagara.gunathu...@gmail.com> wrote:

>
>
> Although this makes the life easier by eliminating the log4j.properties
> modifications, still, one has to restart the server to see debug logs. It
> would have been great to have a simple remote API to make these changes on
> a running server.
>
+1, we can do it as an improvement.

>
> BTW this is a useful improvement; but, you need to think about a better
> name than "synapseDebug" to reflect the purpose of this setting. To me,
> synapseDebug implies that the whole server will be in debug mode and can be
> connected through an IDE.  What about more descriptive and generic name
> like this   *-synapse.mediator.log.level.debug* that can be used to
> change the log of the level of log mediator without limiting to debug
> only?
>
Yes, this is a useful improvement. IMO, we can treat this as a starting
point for implementing a debug mode for the server (Logs become part of
it).


btw,
Shafreen and Sagara,
Welcome to the Synapse-dev. Looking forward to more contributions from you
:)

>
> Thanks!
>
> On Thu, Mar 5, 2020 at 2:06 PM shafreen anfar 
> wrote:
>
>> Hi All,
>>
>> I am Shafreen and I've been working with Synapse for many years. With
>> this mail I am sending a fix [1] to solve one of the issues I've been
>> facing.
>>
>> At the moment, even though log-mediator has a category called DEBUG,
>> there is no way to enable this category. Therefore, no logs are printed
>> under this category. The only workaround we have for this problem is to
>> enable debug logs for log-mediator class itself by configuring
>> log4j.properties file. But I believe, this configuration is for people who
>> implement log-mediator but not for synapse users.
>>
>> IMO, synapse users should be able to enable debug mode of the
>> log-mediator without touching the log4j.properties file. As a solution, I
>> have done a fix [1] in which synapse users can start the server as follows,
>>
>> sh synapse.sh -synapseDebug
>>
>> When the server is started with the above flag, all the logs of
>> log-mediator under the category DEBUG is printed. For more information,
>> please have a look at [1] and [2]. Also, please note that the provided fix
>> is tested in both linux and windows.
>>
>> [1] https://github.com/apache/synapse/pull/24
>> [2] https://issues.apache.org/jira/browse/SYNAPSE-1116
>>
>>
>
> --
> Sagara Gunathunga
>
> Blog  - http://ssagara.blogspot.com
> Web  - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
>


-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

[jira] [Commented] (SYNAPSE-1114) HTTP Transport based on Netty.io

[Isuru Udana (Jira)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036337#comment-17036337
 ] 

Isuru Udana commented on SYNAPSE-1114:
--

Thanks, Madhawa.
Please note that Jira ticket cannot be assigned to you at this moment as you 
are yet to become a committer. 

> HTTP Transport based on Netty.io
> 
>
> Key: SYNAPSE-1114
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1114
> Project: Synapse
>  Issue Type: New Feature
>  Components: Transports
>    Reporter: Isuru Udana
>    Assignee: Isuru Udana
>Priority: Major
>
> Netty is an NIO client-server framework that enables development of 
> high-performing network applications. 
> It has a simple API that an application can use to interact with. 
> The use of netty will allow us to extend the HTTP transport capabilities 
> beyond a simple client-server application. Support for HTTP/2 is one such 
> feature.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Created] (SYNAPSE-1114) HTTP Transport based on Netty.io

[Isuru Udana (Jira)]

Isuru Udana created SYNAPSE-1114:


 Summary: HTTP Transport based on Netty.io
 Key: SYNAPSE-1114
 URL: https://issues.apache.org/jira/browse/SYNAPSE-1114
 Project: Synapse
  Issue Type: New Feature
  Components: Transports
Reporter: Isuru Udana
Assignee: Isuru Udana


Netty is an NIO client-server framework that enables development of 
high-performing network applications. 
It has a simple API that an application can use to interact with. 
The use of netty will allow us to extend the HTTP transport capabilities beyond 
a simple client-server application. Support for HTTP/2 is one such feature.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Positioning Synapse as an Integration Framework

[Isuru Udana]

On Thu, Feb 13, 2020 at 8:53 PM Madhawa Kasun Gunasekara <
madhaw...@gmail.com> wrote:

> Hi All,
>
> Shall we start working on this? I believe there are so many things to
> improve. so let's start listing them. after that, we can prioritize items
> and create Jira tickets.
>
> +1. I will first work on integrating a build system (Travis or Jenkins)
for Pull Requests, that will make PR merging easier.

Thanks.


> Thanks,
> Madhawa
>
>
> On Tue, Jan 7, 2020 at 7:10 PM Madhawa Kasun Gunasekara <
> madhaw...@gmail.com> wrote:
>
>> +1,
>> Moving forward for the container friendly integration framework is a
>> great idea. How about considering for version 4.x.x. release. I can help
>> too.
>>
>> Thanks,
>> Madhawa
>>
>>
>> On Thu, Dec 12, 2019 at 2:38 AM Isuru Udana  wrote:
>>
>>> Hi All,
>>>
>>> It has been 12 years since Synapse was founded (2007-12-19). As we all
>>> know in the last few years we did not have a good run. The activity of the
>>> project has significantly gone down and there is not much of a contribution
>>> from the majority of the committers.
>>>
>>> Also, ESB architectural style is no longer the preferred style for doing
>>> the integration. The world has been moved towards container friendly
>>> products, microservices, and cloud-native technologies. However, the
>>> integration problem solved by the ESB architecture still exists and handled
>>> by different entities.
>>>
>>> Even though Synapse is an ESB, it has most of the qualities (ex: faster
>>> startup time, low resource consumption, etc.) that are important for
>>> containers and microservices integrations. So with a little effort, we
>>> could make Synapse a container friendly product that suits any
>>> architectural style for doing the integration.
>>>
>>> So, should we consider positioning Synapse as an 'Integration Framework'
>>> or an 'Integration Product' that serves all architectural styles?
>>> Will that help us reactivate the project?
>>>
>>> Please share your thoughts.
>>>
>>> Thank you.
>>>
>>>
>>>
>>> -- Forwarded message -
>>> From: Isuru Udana 
>>> Date: Thu, Dec 12, 2019 at 7:03 AM
>>> Subject: Re: Positioning Synapse as an Integration Framework
>>> To: 
>>>
>>>
>>> I will open this discussion to the community to reach a wide audience.
>>>
>>> On Wed, Dec 11, 2019 at 5:20 AM Vanjikumaran Sivajothy <
>>> vanjikuma...@gmail.com> wrote:
>>>
>>>> I am not too sure about adopting the very abstract term Integration
>>>> Framework; However, I can assure that moving towards container-native
>>>> is a
>>>> logical move.
>>>> I can help on this to produce an initial set of artifacts.
>>>>
>>>>
>>>>
>>>> On Mon, Dec 2, 2019 at 4:23 PM Isuru Udana  wrote:
>>>>
>>>> > Hi PMC,
>>>> >
>>>> > It has been 12 years since Synapse was founded (2007-12-19). As we
>>>> all know
>>>> > in the last few years we did not have a good run. The activity of the
>>>> > project has significantly gone down and there is not much of a
>>>> contribution
>>>> > from the majority of the committers/PMC members.
>>>> >
>>>> > Also, ESB architectural style is no longer the preferred style for
>>>> doing
>>>> > the integration. The world has been moved towards container friendly
>>>> > products, microservices, and cloud-native technologies. However, the
>>>> > integration problem solved by the ESB architecture still exists and
>>>> handled
>>>> > by different entities.
>>>> >
>>>> > Even though Synapse is an ESB, it has most of the qualities (ex:
>>>> faster
>>>> > startup time, low resource consumption, etc.) that are important for
>>>> > containers and microservices integrations. So with a little effort, we
>>>> > could make Synapse a container friendly product that suits any
>>>> > architectural style for doing the integration.
>>>> >
>>>> > So, should we consider positioning Synapse as an 'Integration
>>>> Framework' or
>>>> > an 'Integration Product' that serves all architectural styles?
>>>> > Will that help us reactivate the project?
>>>> >
>>>> >
>>>> > --
>>>> > *Isuru Udana*
>>>> >
>>>> >
>>>> >
>>>> > *email: isud...@gmail.com  blog:
>>>> > http://mytecheye.blogspot.com/ <http://mytecheye.blogspot.com/>*
>>>> >
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Vanji
>>>>
>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Senior Technical Lead
>>>
>>>
>>>
>>>
>>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>>>  blog: http://mytecheye.blogspot.com/
>>> <http://mytecheye.blogspot.com/>*
>>>
>>>
>>>
>>>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 *

OpenJDK Support (was: Introducing Docker and K8S artifacts)

[Isuru Udana]

Hi All,

As we discussed, I tried to configure Jenkins to use OpenJDK 8 for our
Jenkins build. But unfortunately, it has been deprecated by the
infrastructure team[1].
Apache POI project has reported a Jira ticket[2] asking to put it back as
they require it.
I also commented on the same ticket mentioning our requirements. Let's wait
for few days to see whether we get a resolution.

[1]
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
[2] https://issues.apache.org/jira/browse/INFRA-19411


-- Forwarded message -
From: Isuru Udana 
Date: Wed, Nov 20, 2019 at 9:22 PM
Subject: Re: Introducing Docker and K8S artifacts
To: 


+1 for the idea. I think it's a good time to think about the overall
strategy of the project too.

For testing synapse in OpenJDK, I can configure Jenkins build to use
OpenJDK.

On Wed, Nov 20, 2019 at 11:07 AM Ravi Undupitiya 
wrote:

> I think this is a great idea. There was some discussion around using OSGi
> for containerisation, but in a World of docker and k8s a lot of the uses
> cases for OSGi will be catered for and I can only think of a very limited
> set of use cases for needing both.
>
> We should probably base off OpenJDK for this and given the recent Oracle
> licensing changes we should move to OpenJDK.
>
> On Wed, 20 Nov 2019 at 16:06, Vanjikumaran Sivajothy <
> vanjikuma...@gmail.com> wrote:
>
>> Hi Dev,
>>
>> Recently we moved the Apache synapse codebase to GitHub successfully and
>> started to merge the existing pull request after careful consideration.
>>
>> As the next step for synapse development, I would like to propose to
>> Introduce Docker and K8s artifacts for apache synapse to enable users to
>> use the Apache synapse in the container ecosystem.
>>
>> I have created few issues in jira tickets[1]; If anyone
>> interested pleases send a pull request
>>
>> [1]https://issues.apache.org/jira/browse/SYNAPSE-
>> --
>> Best Regards,
>> Vanji
>>
>

-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*





-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

Re: Introducing Docker and K8S artifacts

[Isuru Udana]

+1 for the idea. I think it's a good time to think about the overall
strategy of the project too.

For testing synapse in OpenJDK, I can configure Jenkins build to use
OpenJDK.

On Wed, Nov 20, 2019 at 11:07 AM Ravi Undupitiya 
wrote:

> I think this is a great idea. There was some discussion around using OSGi
> for containerisation, but in a World of docker and k8s a lot of the uses
> cases for OSGi will be catered for and I can only think of a very limited
> set of use cases for needing both.
>
> We should probably base off OpenJDK for this and given the recent Oracle
> licensing changes we should move to OpenJDK.
>
> On Wed, 20 Nov 2019 at 16:06, Vanjikumaran Sivajothy <
> vanjikuma...@gmail.com> wrote:
>
>> Hi Dev,
>>
>> Recently we moved the Apache synapse codebase to GitHub successfully and
>> started to merge the existing pull request after careful consideration.
>>
>> As the next step for synapse development, I would like to propose to
>> Introduce Docker and K8s artifacts for apache synapse to enable users to
>> use the Apache synapse in the container ecosystem.
>>
>> I have created few issues in jira tickets[1]; If anyone
>> interested pleases send a pull request
>>
>> [1]https://issues.apache.org/jira/browse/SYNAPSE-
>> --
>> Best Regards,
>> Vanji
>>
>

-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

[jira] [Resolved] (SYNAPSE-1104) Synapse transport locks when there is an exception within Clone Mediator

[Isuru Udana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana resolved SYNAPSE-1104.
--
Resolution: Fixed

Github pull request merged. 
Thanks for your contribution.

> Synapse transport locks when there is an exception within Clone Mediator
> 
>
> Key: SYNAPSE-1104
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1104
> Project: Synapse
>  Issue Type: Bug
>Reporter: Madhawa Kasun Gunasekara
>    Assignee: Isuru Udana
>Priority: Major
> Attachments: Fix_SYNAPSE-1104.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When there is an exception happens in the mediation, the exception handler 
> tries to read all the data from the input stream.
>  When the exception happens in a clone mediator, there seems to be the 
> InputStream is already read. however there is a following code, which is 
> indefinitely waits, as no more data is available.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1109) WSA:From header is missing when sending a request to an endpoint

[Isuru Udana Loku Narangoda (Jira)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda resolved SYNAPSE-1109.
-
Fix Version/s: 3.0.2
   Resolution: Fixed

> WSA:From header is missing when sending a request to an endpoint 
> -
>
> Key: SYNAPSE-1109
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1109
> Project: Synapse
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.0.1
>Reporter: Auke Schrijnen
>Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Fix For: 3.0.2
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When a From value is set in the message context (e.g. with 
> MessageContext.setFrom) before it is sent to an endpoint the value isn't used 
> in the resulting request. This is due to the fact that the 
> Axis2FlexibleMEPClient clones the message context before sending it and the 
> MessageHelper.clonePartially doesn't copy the From value from the source 
> message context to the cloned message context.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Synapse source is migrated to Github

[Isuru Udana]

Hi Vanji,

The infrastructure team is currently working on enabling Github integration
features to mailing lists and JIRA.
Once that is done, we'll receive emails for Github Pull Requests, comments,
etc.




On Mon, Aug 19, 2019 at 10:08 AM Vanjikumaran Sivajothy <
vanjikuma...@gmail.com> wrote:

> We were listening into comm...@synapse.apache.org for svn commits. What
> is the new chanel for the git repo?
>
> On Sun, Aug 18, 2019 at 10:26 AM Isuru Udana  wrote:
>
>> Hi All,
>>
>> We have migrated the Synapse codebase to Github[1].
>> This will encourage new contributors to make contributions as the Github
>> Pull Request model is much simpler than submitting a patch to svn based
>> codebase. Also, this will ease the reviewing fixes as well.
>>
>> With the Github move, we have configured the Jenkins build job to use
>> Github master branch as the source location.
>> Synapse site[2] is also updated to reflect these changes.
>>
>> For issue tracking, we will continue to use the JIRA system[3].
>>
>> [1] https://github.com/apache/synapse
>> [2] https://synapse.apache.org/dev/developer-guide.html
>> [3] http://issues.apache.org/jira/browse/SYNAPSE
>>
>> Thanks.
>>
>>
>>
>>
>> -- Forwarded message -
>> From: Isuru Udana 
>> Date: Fri, May 18, 2018 at 11:57 AM
>> Subject: Re: Migrate to git ?
>> To: 
>>
>>
>> Hi Madhawa,
>>
>> As you said even though we have a git repository, we haven't utilize it
>> yet.
>> We first need to get the next release out.
>> After that, I am +1 for moving the codebase to git.
>>
>> Thanks.
>>
>> On Thu, Apr 26, 2018 at 11:10 AM Madhawa Kasun Gunasekara <
>> madhaw...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> I believe we should migrate the synapse source code properly to the git
>>> [1]. WDYT?
>>>
>>> I would like to contribute.
>>>
>>> [1] https://github.com/apache/synapse
>>>
>>> Thanks,
>>> Madhawa
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Senior Technical Lead
>>
>>
>>
>>
>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>>  blog: http://mytecheye.blogspot.com/
>> <http://mytecheye.blogspot.com/>*
>>
>>
>>
>>
>>
>> --
>> *Isuru Udana*
>> Senior Technical Lead
>>
>>
>>
>>
>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
>>  blog: http://mytecheye.blogspot.com/
>> <http://mytecheye.blogspot.com/>*
>>
>>
>>
>>
>
> --
> Best Regards,
> Vanji
>


-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

Synapse source is migrated to Github

[Isuru Udana]

Hi All,

We have migrated the Synapse codebase to Github[1].
This will encourage new contributors to make contributions as the Github
Pull Request model is much simpler than submitting a patch to svn based
codebase. Also, this will ease the reviewing fixes as well.

With the Github move, we have configured the Jenkins build job to use
Github master branch as the source location.
Synapse site[2] is also updated to reflect these changes.

For issue tracking, we will continue to use the JIRA system[3].

[1] https://github.com/apache/synapse
[2] https://synapse.apache.org/dev/developer-guide.html
[3] http://issues.apache.org/jira/browse/SYNAPSE

Thanks.




-- Forwarded message -
From: Isuru Udana 
Date: Fri, May 18, 2018 at 11:57 AM
Subject: Re: Migrate to git ?
To: 


Hi Madhawa,

As you said even though we have a git repository, we haven't utilize it
yet.
We first need to get the next release out.
After that, I am +1 for moving the codebase to git.

Thanks.

On Thu, Apr 26, 2018 at 11:10 AM Madhawa Kasun Gunasekara <
madhaw...@gmail.com> wrote:

> Hi All,
>
> I believe we should migrate the synapse source code properly to the git
> [1]. WDYT?
>
> I would like to contribute.
>
> [1] https://github.com/apache/synapse
>
> Thanks,
> Madhawa
>


-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*





-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
 blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

[jira] [Commented] (SYNAPSE-1107) Remove dispatchers instantiation inside dispatchAndVerify Method

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853894#comment-16853894
 ] 

Isuru Udana Loku Narangoda commented on SYNAPSE-1107:
-

Committed revision 1860506. Thank you for your contribution.

> Remove dispatchers instantiation inside dispatchAndVerify Method 
> -
>
> Key: SYNAPSE-1107
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1107
> Project: Synapse
>  Issue Type: Improvement
>Reporter: Madhawa Gunasekara
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Attachments: Fix_SYNAPSE-1107.patch
>
>
> For the every rest request these dispatchers will be instantiated, It will 
> add a additional unnecessary latency for the request flow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1107) Remove dispatchers instantiation inside dispatchAndVerify Method

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda resolved SYNAPSE-1107.
-
   Resolution: Fixed
Fix Version/s: 3.0.2

> Remove dispatchers instantiation inside dispatchAndVerify Method 
> -
>
> Key: SYNAPSE-1107
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1107
> Project: Synapse
>  Issue Type: Improvement
>Reporter: Madhawa Gunasekara
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Fix For: 3.0.2
>
> Attachments: Fix_SYNAPSE-1107.patch
>
>
> For the every rest request these dispatchers will be instantiated, It will 
> add a additional unnecessary latency for the request flow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1048) Listenning IO Reactor worker threads are blocked If exception occured while pass throughing large messages.

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda resolved SYNAPSE-1048.
-
   Resolution: Fixed
Fix Version/s: (was: FUTURE)
   3.0.2

> Listenning IO Reactor worker threads are  blocked If exception occured while 
> pass throughing  large messages.
> -
>
> Key: SYNAPSE-1048
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1048
> Project: Synapse
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 1.1
>Reporter: isuru janith ranawaka
>Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Fix For: 3.0.2
>
> Attachments: SYNAPSE_1048.diff
>
>
> Listening IO Reactor worker threads could be blocked while pass through  
> large messages if exception occurred in the TargetHandler. Currently if 
> exception occurred then fault messages are  propagated to Fault Sequence but 
> does not inform weather it is a writer error or reader error which could be  
> caused IO worker threads  being spinning for condition in Pipe.flushContent() 
> . 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1048) Listenning IO Reactor worker threads are blocked If exception occured while pass throughing large messages.

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850247#comment-16850247
 ] 

Isuru Udana Loku Narangoda commented on SYNAPSE-1048:
-

Committed revision 1860309.

> Listenning IO Reactor worker threads are  blocked If exception occured while 
> pass throughing  large messages.
> -
>
> Key: SYNAPSE-1048
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1048
> Project: Synapse
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 1.1
>Reporter: isuru janith ranawaka
>Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Fix For: FUTURE
>
> Attachments: SYNAPSE_1048.diff
>
>
> Listening IO Reactor worker threads could be blocked while pass through  
> large messages if exception occurred in the TargetHandler. Currently if 
> exception occurred then fault messages are  propagated to Fault Sequence but 
> does not inform weather it is a writer error or reader error which could be  
> caused IO worker threads  being spinning for condition in Pipe.flushContent() 
> . 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Comment Edited] (SYNAPSE-1048) Listenning IO Reactor worker threads are blocked If exception occured while pass throughing large messages.

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850247#comment-16850247
 ] 

Isuru Udana Loku Narangoda edited comment on SYNAPSE-1048 at 5/29/19 12:09 AM:
---

Committed revision 1860309.

Thank you for your contribution. 


was (Author: isudana):
Committed revision 1860309.

> Listenning IO Reactor worker threads are  blocked If exception occured while 
> pass throughing  large messages.
> -
>
> Key: SYNAPSE-1048
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1048
> Project: Synapse
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 1.1
>Reporter: isuru janith ranawaka
>Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Fix For: FUTURE
>
> Attachments: SYNAPSE_1048.diff
>
>
> Listening IO Reactor worker threads could be blocked while pass through  
> large messages if exception occurred in the TargetHandler. Currently if 
> exception occurred then fault messages are  propagated to Fault Sequence but 
> does not inform weather it is a writer error or reader error which could be  
> caused IO worker threads  being spinning for condition in Pipe.flushContent() 
> . 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Assigned] (SYNAPSE-1048) Listenning IO Reactor worker threads are blocked If exception occured while pass throughing large messages.

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda reassigned SYNAPSE-1048:
---

Assignee: Isuru Udana Loku Narangoda  (was: Hiranya Jayathilaka)

> Listenning IO Reactor worker threads are  blocked If exception occured while 
> pass throughing  large messages.
> -
>
> Key: SYNAPSE-1048
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1048
> Project: Synapse
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 1.1
>Reporter: isuru janith ranawaka
>Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Fix For: FUTURE
>
> Attachments: SYNAPSE_1048.diff
>
>
> Listening IO Reactor worker threads could be blocked while pass through  
> large messages if exception occurred in the TargetHandler. Currently if 
> exception occurred then fault messages are  propagated to Fault Sequence but 
> does not inform weather it is a writer error or reader error which could be  
> caused IO worker threads  being spinning for condition in Pipe.flushContent() 
> . 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1075) HTTPS Load test for the 3.0 release

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda resolved SYNAPSE-1075.
-
Resolution: Done

> HTTPS Load test for the 3.0 release
> ---
>
> Key: SYNAPSE-1075
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1075
> Project: Synapse
>  Issue Type: Task
>  Components: Transports
>Reporter: Chanaka Fernando
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Attachments: EchoProxy.xml, synapse-https-100x1000.xml, 
> synapse-https-200x100.xml, synapse-https-300x100.xml, 
> synapse-https-400x100.xml, synapse-https-500x100.xml, 
> synapse-https-sender-100x100.xml, synapse-https-sender-200x100.xml, 
> synapse-https-sender-300x100.xml, synapse-https-sender-400x100.xml, 
> synapse-https-sender-500x100.xml, synapse-proxy-soapui-project.xml
>
>
> Need to carry out a load test for HTTPS listener and sender before the 
> release. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1094) Build Error :- Execution distribution-package of goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id '110243664' is too big

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850244#comment-16850244
 ] 

Isuru Udana Loku Narangoda commented on SYNAPSE-1094:
-

Can we close the issue?

> Build Error :- Execution distribution-package of goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id 
> '110243664' is too big
> ---
>
> Key: SYNAPSE-1094
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1094
> Project: Synapse
>  Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>Priority: Major
> Attachments: 
> SYNAPSE-1094,_build_error_due_to_the_limitation_in_the_plugin.patch
>
>
> {code}
> NFO] Apache Synapse - XAR Maven Plugin .. SUCCESS [  7.686 s]
> [INFO] Apache Synapse - Configuration Migrator  SUCCESS [  0.682 
> s]
> [INFO] Apache Synapse - Distribution .. FAILURE [ 14.471 
> s]
> [INFO] Apache Synapse - Package skeleton ZIP .. SKIPPED
> [INFO] Apache Synapse - Package archetype . SKIPPED
> [INFO] Apache Synapse - Integration ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-01-03T11:57:30-08:00
> [INFO] Final Memory: 122M/1005M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single 
> (distribution-package) on project synapse-distribution: Execution 
> distribution-package of goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id 
> '110243664' is too big ( > 2097151 ). Use STAR or POSIX extensions to 
> overcome this limit -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] 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/PluginExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :synapse-distribution
> {code}
> This issue due to the limitation in the maven plugin while building the tar 
> [1]. Patch is attached to resolve this issue.
> {code}
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T08:41:47-08:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
> {code}
> [1] https://issues.apache.org/jira/browse/MASSEMBLY-728
> [2] https://issues.apache.org/jira/browse/COMPRESS-290



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1101) Self Signed certificate expired

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda resolved SYNAPSE-1101.
-
Resolution: Fixed

> Self Signed certificate expired 
> 
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
>  Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired 
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar 
> 19 16:59:59 PDT 2018
>  at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1101) Self Signed certificate expired

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788995#comment-16788995
 ] 

Isuru Udana Loku Narangoda commented on SYNAPSE-1101:
-

Fixed with revision 1855156.

> Self Signed certificate expired 
> 
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
>  Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired 
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar 
> 19 16:59:59 PDT 2018
>  at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Reopened] (SYNAPSE-1101) Self Signed certificate expired

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda reopened SYNAPSE-1101:
-

Looks like issue is appearing again for some key-stores again. 

> Self Signed certificate expired 
> 
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
>  Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired 
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar 
> 19 16:59:59 PDT 2018
>  at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1094) Build Error :- Execution distribution-package of goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id '110243664' is too big

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781162#comment-16781162
 ] 

Isuru Udana Loku Narangoda commented on SYNAPSE-1094:
-

Hi Vanji,

Committed the patch to trunk in r1854555.
Should we update all the places which uses assembly plugin ? 


> Build Error :- Execution distribution-package of goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id 
> '110243664' is too big
> ---
>
> Key: SYNAPSE-1094
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1094
> Project: Synapse
>  Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Isuru Udana Loku Narangoda
>Priority: Major
> Attachments: 
> SYNAPSE-1094,_build_error_due_to_the_limitation_in_the_plugin.patch
>
>
> {code}
> NFO] Apache Synapse - XAR Maven Plugin .. SUCCESS [  7.686 s]
> [INFO] Apache Synapse - Configuration Migrator  SUCCESS [  0.682 
> s]
> [INFO] Apache Synapse - Distribution .. FAILURE [ 14.471 
> s]
> [INFO] Apache Synapse - Package skeleton ZIP .. SKIPPED
> [INFO] Apache Synapse - Package archetype . SKIPPED
> [INFO] Apache Synapse - Integration ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-01-03T11:57:30-08:00
> [INFO] Final Memory: 122M/1005M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single 
> (distribution-package) on project synapse-distribution: Execution 
> distribution-package of goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id 
> '110243664' is too big ( > 2097151 ). Use STAR or POSIX extensions to 
> overcome this limit -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] 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/PluginExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :synapse-distribution
> {code}
> This issue due to the limitation in the maven plugin while building the tar 
> [1]. Patch is attached to resolve this issue.
> {code}
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T08:41:47-08:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
> {code}
> [1] https://issues.apache.org/jira/browse/MASSEMBLY-728
> [2] https://issues.apache.org/jira/browse/COMPRESS-290



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Comment Edited] (SYNAPSE-1101) Self Signed certificate expired

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781167#comment-16781167
 ] 

Isuru Udana Loku Narangoda edited comment on SYNAPSE-1101 at 3/1/19 1:25 AM:
-

Looks like issue is appearing for some key-stores again. 


was (Author: isudana):
Looks like issue is appearing again for some key-stores again. 

> Self Signed certificate expired 
> 
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
>  Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired 
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar 
> 19 16:59:59 PDT 2018
>  at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Assigned] (SYNAPSE-1094) Build Error :- Execution distribution-package of goal org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id '110243664' is too big

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda reassigned SYNAPSE-1094:
---

Assignee: Vanjikumaran Sivajothy  (was: Isuru Udana Loku Narangoda)

> Build Error :- Execution distribution-package of goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id 
> '110243664' is too big
> ---
>
> Key: SYNAPSE-1094
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1094
> Project: Synapse
>  Issue Type: Bug
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>Priority: Major
> Attachments: 
> SYNAPSE-1094,_build_error_due_to_the_limitation_in_the_plugin.patch
>
>
> {code}
> NFO] Apache Synapse - XAR Maven Plugin .. SUCCESS [  7.686 s]
> [INFO] Apache Synapse - Configuration Migrator  SUCCESS [  0.682 
> s]
> [INFO] Apache Synapse - Distribution .. FAILURE [ 14.471 
> s]
> [INFO] Apache Synapse - Package skeleton ZIP .. SKIPPED
> [INFO] Apache Synapse - Package archetype . SKIPPED
> [INFO] Apache Synapse - Integration ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-01-03T11:57:30-08:00
> [INFO] Final Memory: 122M/1005M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single 
> (distribution-package) on project synapse-distribution: Execution 
> distribution-package of goal 
> org.apache.maven.plugins:maven-assembly-plugin:2.6:single failed: group id 
> '110243664' is too big ( > 2097151 ). Use STAR or POSIX extensions to 
> overcome this limit -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] 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/PluginExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :synapse-distribution
> {code}
> This issue due to the limitation in the maven plugin while building the tar 
> [1]. Patch is attached to resolve this issue.
> {code}
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T08:41:47-08:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
> {code}
> [1] https://issues.apache.org/jira/browse/MASSEMBLY-728
> [2] https://issues.apache.org/jira/browse/COMPRESS-290



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Resolved] (SYNAPSE-1101) Self Signed certificate expired

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda resolved SYNAPSE-1101.
-
Resolution: Fixed

> Self Signed certificate expired 
> 
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
>  Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired 
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar 
> 19 16:59:59 PDT 2018
>  at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1101) Self Signed certificate expired

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677043#comment-16677043
 ] 

Isuru Udana Loku Narangoda commented on SYNAPSE-1101:
-

Fixed with r1845940.

> Self Signed certificate expired 
> 
>
> Key: SYNAPSE-1101
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1101
> Project: Synapse
>  Issue Type: Task
>Reporter: Vanjikumaran Sivajothy
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
>
> build is failing due to certificate expired 
> {code}
> Caused by: java.security.cert.CertificateExpiredException: NotAfter: Mon Mar 
> 19 16:59:59 PDT 2018
>  at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
>  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:602)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Migrate to git ?

[Isuru Udana]

Hi Madhawa,

As you said even though we have a git repository, we haven't utilize it
yet.
We first need to get the next release out.
After that, I am +1 for moving the codebase to git.

Thanks.

On Thu, Apr 26, 2018 at 11:10 AM Madhawa Kasun Gunasekara <
madhaw...@gmail.com> wrote:

> Hi All,
>
> I believe we should migrate the synapse source code properly to the git
> [1]. WDYT?
>
> I would like to contribute.
>
> [1] https://github.com/apache/synapse
>
> Thanks,
> Madhawa
>


-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
<isud...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

[jira] [Deleted] (SYNAPSE-1099) HPE0-J79 PDF Test Dumps - Free HP HPE0-J79 Sample pdf questions

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda deleted SYNAPSE-1099:



> HPE0-J79 PDF Test Dumps - Free HP HPE0-J79 Sample pdf questions
> ---
>
> Key: SYNAPSE-1099
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1099
> Project: Synapse
>  Issue Type: Improvement
>Reporter: Kellein Milek
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Major
>
> *Valid HPE0-J79 Questions Dumps in addition to Ideas to Pass HPE0-J79 Exam in 
> First Attempt*    
> Finding the IT certification by passing the HPE0-J79 exams have become a 
> necessity of IT specialists these days to get stable jobs within their field. 
> But typically these HP HPE0-J79 exam refers to one of their most popular HP 
> Master ASE HPE0-J79 Test Dumps within the field of IT that so many experts 
> have been working hard for HPE0-J79 exam. These HPE0-J79 Test Dumps, however, 
> are sorted among the qualified professionals. That is exactly why our 
> HPE0-J79 Test Dumps come to be so much viral all around the world.
> *Latest HP HPE0-J79 Training Material - Here's What HP qualified To Say About 
> It*    
> The users should attempt not to rush to the HP HPE0-J79 exam before planning 
> for them to the fullest. They can put themselves in some complications while 
> operating for HPE0-J79 exam without HPE0-J79 dumps pdf for their HP Master 
> ASE Architecting Multi-Site HPE Storage Solutions test. The a lot more they 
> get ready for the HP HPE0-J79 certification exam from [HPE0-J79 new questions 
> provided by 
> CertificationsDesk.com|https://www.certificationsdesk.com/hp/real-HPE0-J79-exam-questions.html],
>  the more they can have the ability to know about HPE0-J79 PDF dumps and can 
> prepare yourself better for HP HPE0-J79 certification test. This is how it 
> can be helpful for the students to acquire done with HPE0-J79 certification 
> exam.
> *HP HPE0-J79 Practice Test and PDF Questions for Quick Achievement*
> There are numerous amazing HPE0-J79 new questions available with us online at 
> our site for preparing HP Master ASE HPE0-J79 certification exam. Our clients 
> can go through our HPE0-J79 Dumps to HP Architecting Multi-Site HPE Storage 
> Solutions test, so that it becomes actually very easy for them to attempt the 
> HPE0-J79 certification exam quickly. This is how these kinds of HPE0-J79 new 
> questions that we've been offering have become really very easy HPE0-J79 Test 
> Dumps for them. They ought to try solving as numerous HP HPE0-J79 practice 
> test software 
> *HP HPE0-J79 Questions Dumps - Hidden Advantages You Should Know*   
> The HPE0-J79 Test Dumps that are available at our site for organizing for 
> these HPE0-J79 sample questions certification test have always been 
> definitely very helpful for our clients one way or another for the 
> preparation of HP HPE0-J79. They could delight in solving their favourite 
> HPE0-J79 pdf questions website after preparing for HPE0-J79 certification 
> test with the aid of our software. This HP HPE0-J79 Test Dumps, however, can 
> help them to prepare HP HPE0-J79 certification exam and to make it through 
> their HPE0-J79 exam, so that their period don't get wasted and they don't 
> need to stress for the preparation of HPE0-J79 certification exam.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Closed] (SYNAPSE-1099) HPE0-J79 PDF Test Dumps - Free HP HPE0-J79 Sample pdf questions

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda closed SYNAPSE-1099.
---
Resolution: Invalid

> HPE0-J79 PDF Test Dumps - Free HP HPE0-J79 Sample pdf questions
> ---
>
> Key: SYNAPSE-1099
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1099
> Project: Synapse
>  Issue Type: Improvement
>Reporter: Kellein Milek
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Major
>
> *Valid HPE0-J79 Questions Dumps in addition to Ideas to Pass HPE0-J79 Exam in 
> First Attempt*    
> Finding the IT certification by passing the HPE0-J79 exams have become a 
> necessity of IT specialists these days to get stable jobs within their field. 
> But typically these HP HPE0-J79 exam refers to one of their most popular HP 
> Master ASE HPE0-J79 Test Dumps within the field of IT that so many experts 
> have been working hard for HPE0-J79 exam. These HPE0-J79 Test Dumps, however, 
> are sorted among the qualified professionals. That is exactly why our 
> HPE0-J79 Test Dumps come to be so much viral all around the world.
> *Latest HP HPE0-J79 Training Material - Here's What HP qualified To Say About 
> It*    
> The users should attempt not to rush to the HP HPE0-J79 exam before planning 
> for them to the fullest. They can put themselves in some complications while 
> operating for HPE0-J79 exam without HPE0-J79 dumps pdf for their HP Master 
> ASE Architecting Multi-Site HPE Storage Solutions test. The a lot more they 
> get ready for the HP HPE0-J79 certification exam from [HPE0-J79 new questions 
> provided by 
> CertificationsDesk.com|https://www.certificationsdesk.com/hp/real-HPE0-J79-exam-questions.html],
>  the more they can have the ability to know about HPE0-J79 PDF dumps and can 
> prepare yourself better for HP HPE0-J79 certification test. This is how it 
> can be helpful for the students to acquire done with HPE0-J79 certification 
> exam.
> *HP HPE0-J79 Practice Test and PDF Questions for Quick Achievement*
> There are numerous amazing HPE0-J79 new questions available with us online at 
> our site for preparing HP Master ASE HPE0-J79 certification exam. Our clients 
> can go through our HPE0-J79 Dumps to HP Architecting Multi-Site HPE Storage 
> Solutions test, so that it becomes actually very easy for them to attempt the 
> HPE0-J79 certification exam quickly. This is how these kinds of HPE0-J79 new 
> questions that we've been offering have become really very easy HPE0-J79 Test 
> Dumps for them. They ought to try solving as numerous HP HPE0-J79 practice 
> test software 
> *HP HPE0-J79 Questions Dumps - Hidden Advantages You Should Know*   
> The HPE0-J79 Test Dumps that are available at our site for organizing for 
> these HPE0-J79 sample questions certification test have always been 
> definitely very helpful for our clients one way or another for the 
> preparation of HP HPE0-J79. They could delight in solving their favourite 
> HPE0-J79 pdf questions website after preparing for HPE0-J79 certification 
> test with the aid of our software. This HP HPE0-J79 Test Dumps, however, can 
> help them to prepare HP HPE0-J79 certification exam and to make it through 
> their HPE0-J79 exam, so that their period don't get wasted and they don't 
> need to stress for the preparation of HPE0-J79 certification exam.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: [CVE-2017-15708] Apache Synapse Remote Code Execution Vulnerability

[Isuru Udana]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Update on this vulnerability

In Apache Synapse, by default no authentication is required for Java
Remote Method Invocation (RMI).
So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0,
1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be
performed by injecting specially crafted serialized objects.
And the presence of Apache Commons Collections 3.2.1
(commons-collections-3.2.1.jar) or previous versions in Synapse
distribution makes this exploitable.

To mitigate the issue, we need to limit RMI access to trusted users only.
To enforce authentication of users, we can configure a username and a
password by setting following two parameters in synapse.properties
file.

synapse.jmx.username
synapse.jmx.password

Further upgrading to 3.0.1 version will eliminate the risk of having
said Commons Collection version.
In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.

-BEGIN PGP SIGNATURE-
Comment: MacGPG2 - http://www.gpgtools.org/macgpg2.html

iQIzBAEBCgAdFiEE3kfhRbRVsOy2YlAnVEJWkuNs5sMFAlpa70AACgkQVEJWkuNs
5sM3+hAArF09ZnJnAb7iHhaacmV83NiJc0htg/Eal0ZwE6JVZD8qbFHFhuAgB5be
+lvryDqAwQiPaXdS/wDoG9GyYQQX2YJVngKas4MJdCjelYFICkXeEtFbqam4cutY
2kixB1Gn+q3lcqjxIGVL8TPKgImZ6Mg4bu3w7L24KXVujChvUFWmuFHj4EDOe3OG
StGQcHaGgQoL9HQUH8ciibT7HtjDd2gzkkdvhmxshOY51uEBQxwUzCP+UhagcA1/
xEZNfZ/PeVi34ipoc206Uw7ZRGiCpBoabMTtCpkrvzal+edsQdXMdXUumkwOs7bd
b85jVWPO02NsDb9fjJTfNvqsEu9iTUdMNRKLOENL3mT33yYF35UaLaxclVO26D4K
ma6EJv1ss50T7mEXr1JbbEe0FOZqY6BsR4U0HPDIgynV3NMqN5/KzsKAc+Jy6Wp0
uMAakbXepZW1zRbS+UFo5Ex67MAQDnp25xiwrwputTel13lAwz0gWQISxmSCRNV/
qL9c+dB20wbQMGeSvMhfqtgQprCE55MoCvb8FEI52zROfLpVtM1DtQzhG4vKYnvo
kXrTdvpIeFn9S80RoqZfTHJ8u2rW+AJqw7nbvfEXtMhp117yVAJQKtRyGls2tAFj
utuqPtSazQZvf6nZnjK4Um/VkWEnwxajLrFl9cnODJa9zu629/k=
=/Vec
-END PGP SIGNATURE-

On Sun, Dec 10, 2017 at 7:31 PM, Isuru Udana <isud...@apache.org> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> CVE-2017-15708: Apache Synapse Remote Code Execution Vulnerability
>
> Severity: Important
>
> Vendor:
> The Apache Software Foundation
>
> Versions Affected:
> 3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1
>
> Description:
>
> Due to the presence of Apache Commons Collections 3.2.1
> (commons-collections-3.2.1.jar) or previous versions,
> Apache Synapse 3.0.0 or all previous releases allows remote code
> execution attacks that can be performed by
> injecting specially crafted serialized objects.
>
> Mitigation:
> Upgrade to 3.0.1 version.
> In Synapse 3.0.1 version, Commons Collection has been updated to
> 3.2.2 version which contains
> the fix for the above mentioned vulnerability.
>
> Credit:
> This issue was discovered by QingTeng cloud Security of Minded Security
> Researcher jianan.huang
>
>
> References:
> https://commons.apache.org/proper/commons-collections/security-reports.html
>
> Isuru Udana
> VP, Apache Synapse
>
> -BEGIN PGP SIGNATURE-
> Comment: MacGPG2 - http://www.gpgtools.org/macgpg2.html
>
> iQIzBAEBCgAdFiEE3kfhRbRVsOy2YlAnVEJWkuNs5sMFAlotO40ACgkQVEJWkuNs
> 5sN+xg/+P/iHhK3JAULQy6JlLt7T2oUmd9EjEfpp6VimVTARPzywAzH39ZdeNEnq
> dd7eCjadE2CCR5QVcLNgTxyKIL6KDqOtBrJFksiZi5Q2kx0rMzbs1cz48POUd0NK
> DNFWngbLqMvY9kkkm7ioS3aXpZ99pdIpr9e11tqMj6ds2OOqUn5KpbEJvlBi3Htr
> QpD+Rp42myuHE6kHl5g9CR9fo42WyUvihuutpBv1+aWwR6CJaBSuN+H6tkrJQUqj
> StFk7nNG/RfsNHmlwCFORk3JYsaao8p1f4o4YTQAsaAu6u3frj29kt2RnSDyjt6m
> uQEkuRlmlb82xDh/3WxNbjoAIYGjrlEKEJxJtW6x0pZ9w3Hl7ccLRglclFmrenjx
> T0+aBF4S5DaYixaMZAS3OMFe86e+9MXLtdCUopWmq9Je+dDeLovfYvzTL6j4vyEF
> NsAfSpz9yJQ/e/3uYAyyaR31XoS5kmtQSDclGijR4YhPIc25P5/yVjwc63CNO2sv
> kb/wAecK+zVPJOIXYloW+IrLwUxmgz/UTd3Ogqg6xP+ClCTIIz4z9fsght0aULBV
> 0YR6bmzigYthMFWdFiQDsDvWYFXVyJjeyVFfyyxOUlUjIY5pqZq+moWYQJ90dV+B
> J3Bi10tFhyZBNzyAe1R4unBISx6WOE+wCdkoexTpmx6XGce63iU=
> =Z+d2
> -END PGP SIGNATURE-

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[CVE-2017-15708] Apache Synapse Remote Code Execution Vulnerability

[Isuru Udana]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

CVE-2017-15708: Apache Synapse Remote Code Execution Vulnerability

Severity: Important

Vendor:
The Apache Software Foundation

Versions Affected:
3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1

Description:

Due to the presence of Apache Commons Collections 3.2.1
(commons-collections-3.2.1.jar) or previous versions,
Apache Synapse 3.0.0 or all previous releases allows remote code
execution attacks that can be performed by
injecting specially crafted serialized objects.

Mitigation:
Upgrade to 3.0.1 version.
In Synapse 3.0.1 version, Commons Collection has been updated to
3.2.2 version which contains
the fix for the above mentioned vulnerability.

Credit:
This issue was discovered by QingTeng cloud Security of Minded Security
Researcher jianan.huang


References:
https://commons.apache.org/proper/commons-collections/security-reports.html

Isuru Udana
VP, Apache Synapse

-BEGIN PGP SIGNATURE-
Comment: MacGPG2 - http://www.gpgtools.org/macgpg2.html

iQIzBAEBCgAdFiEE3kfhRbRVsOy2YlAnVEJWkuNs5sMFAlotO40ACgkQVEJWkuNs
5sN+xg/+P/iHhK3JAULQy6JlLt7T2oUmd9EjEfpp6VimVTARPzywAzH39ZdeNEnq
dd7eCjadE2CCR5QVcLNgTxyKIL6KDqOtBrJFksiZi5Q2kx0rMzbs1cz48POUd0NK
DNFWngbLqMvY9kkkm7ioS3aXpZ99pdIpr9e11tqMj6ds2OOqUn5KpbEJvlBi3Htr
QpD+Rp42myuHE6kHl5g9CR9fo42WyUvihuutpBv1+aWwR6CJaBSuN+H6tkrJQUqj
StFk7nNG/RfsNHmlwCFORk3JYsaao8p1f4o4YTQAsaAu6u3frj29kt2RnSDyjt6m
uQEkuRlmlb82xDh/3WxNbjoAIYGjrlEKEJxJtW6x0pZ9w3Hl7ccLRglclFmrenjx
T0+aBF4S5DaYixaMZAS3OMFe86e+9MXLtdCUopWmq9Je+dDeLovfYvzTL6j4vyEF
NsAfSpz9yJQ/e/3uYAyyaR31XoS5kmtQSDclGijR4YhPIc25P5/yVjwc63CNO2sv
kb/wAecK+zVPJOIXYloW+IrLwUxmgz/UTd3Ogqg6xP+ClCTIIz4z9fsght0aULBV
0YR6bmzigYthMFWdFiQDsDvWYFXVyJjeyVFfyyxOUlUjIY5pqZq+moWYQJ90dV+B
J3Bi10tFhyZBNzyAe1R4unBISx6WOE+wCdkoexTpmx6XGce63iU=
=Z+d2
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: [VOTE] Release Apache Synapse 3.0.1

[Isuru Udana]

Did some smoke tests and found no issues.

Here is my +1 (binding).

Thanks.

On Mon, Dec 4, 2017 at 3:30 PM, Vanjikumaran Sivajothy <va...@apache.org>
wrote:

> This is a call for votes to release Apache Synapse 3.0.1
>
> Please review the distribution artifacts:
> https://dist.apache.org/repos/dist/dev/synapse/3.0.1/RC1/
>
> The nexus staging repository is available at:
> https://repository.apache.org/content/repositories/orgapachesynapse-1005/
>
> Updated site for this release is available at:
> https://svn.apache.org/repos/asf/synapse/site/3_0_1/index.html
>
> SVN Tag (r1817071):
> https://svn.apache.org/repos/asf/synapse/tags/Apache-Synapse-3.0.1/
>
> Public key:
> http://pgp.mit.edu/pks/lookup?op=get=0x4501F19E2A125326
>
> Issues Fixed:
> https://issues.apache.org/jira/projects/SYNAPSE/versions/12341670
>
> Instructions on how to validate distribution artifacts before voting:
> http://www.apache.org/dev/release.html#approving-a-release
>
>
>
> Best Regards,
> Vanji
>



-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
<isud...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

[jira] [Updated] (SYNAPSE-1050) Sample for message drop in Forward mediator

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda updated SYNAPSE-1050:

Fix Version/s: 3.0.1

> Sample for message drop in Forward mediator
> ---
>
> Key: SYNAPSE-1050
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1050
> Project: Synapse
>  Issue Type: Sub-task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
> Fix For: 3.0.1
>
> Attachments: SYNAPSE-1050.diff
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Reopened] (SYNAPSE-1050) Sample for message drop in Forward mediator

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda reopened SYNAPSE-1050:
-

> Sample for message drop in Forward mediator
> ---
>
> Key: SYNAPSE-1050
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1050
> Project: Synapse
>  Issue Type: Sub-task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
> Fix For: 3.0.1
>
> Attachments: SYNAPSE-1050.diff
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Closed] (SYNAPSE-1050) Sample for message drop in Forward mediator

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda closed SYNAPSE-1050.
---
Resolution: Fixed

> Sample for message drop in Forward mediator
> ---
>
> Key: SYNAPSE-1050
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1050
> Project: Synapse
>  Issue Type: Sub-task
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
> Fix For: 3.0.1
>
> Attachments: SYNAPSE-1050.diff
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1057) Spelling mistake and un handled exceptions

[Isuru Udana Loku Narangoda (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275822#comment-16275822
 ] 

Isuru Udana Loku Narangoda commented on SYNAPSE-1057:
-

Fixed in r1809547 

> Spelling mistake and un handled exceptions
> --
>
> Key: SYNAPSE-1057
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1057
> Project: Synapse
>  Issue Type: Bug
>  Components: Core
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>Priority: Minor
>  Labels: patch
> Fix For: 3.0.1
>
> Attachments: SYNAPSE1057.patch
>
>
> When DBLookup/DBreport exception happens, The flow doesn't go to 
> faultSequence as the handled exception. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Closed] (SYNAPSE-1095) Current Documentation is not mobile Friendly

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda closed SYNAPSE-1095.
---
Resolution: Fixed

> Current Documentation is not mobile Friendly 
> -
>
> Key: SYNAPSE-1095
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1095
> Project: Synapse
>  Issue Type: Improvement
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>  Labels: documentaion
> Fix For: 3.0.1
>
> Attachments: Mobile_Friendly.patch, Screen Shot 2017-01-04 at 2.36.21 
> PM.png
>
>
> Current Documentation is not mobile Friendly due the current 
> maven-fluido-skin. This issue can be resolved by upgrading to the version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Updated] (SYNAPSE-1057) Spelling mistake and un handled exceptions

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda updated SYNAPSE-1057:

Fix Version/s: (was: FUTURE)
   3.0.1

> Spelling mistake and un handled exceptions
> --
>
> Key: SYNAPSE-1057
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1057
> Project: Synapse
>  Issue Type: Bug
>  Components: Core
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>Priority: Minor
>  Labels: patch
> Fix For: 3.0.1
>
> Attachments: SYNAPSE1057.patch
>
>
> When DBLookup/DBreport exception happens, The flow doesn't go to 
> faultSequence as the handled exception. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Updated] (SYNAPSE-1095) Current Documentation is not mobile Friendly

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda updated SYNAPSE-1095:

Fix Version/s: 3.0.1

> Current Documentation is not mobile Friendly 
> -
>
> Key: SYNAPSE-1095
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1095
> Project: Synapse
>  Issue Type: Improvement
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>  Labels: documentaion
> Fix For: 3.0.1
>
> Attachments: Mobile_Friendly.patch, Screen Shot 2017-01-04 at 2.36.21 
> PM.png
>
>
> Current Documentation is not mobile Friendly due the current 
> maven-fluido-skin. This issue can be resolved by upgrading to the version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Reopened] (SYNAPSE-1095) Current Documentation is not mobile Friendly

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda reopened SYNAPSE-1095:
-

> Current Documentation is not mobile Friendly 
> -
>
> Key: SYNAPSE-1095
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1095
> Project: Synapse
>  Issue Type: Improvement
>Reporter: Vanjikumaran Sivajothy
>Assignee: Vanjikumaran Sivajothy
>  Labels: documentaion
> Attachments: Mobile_Friendly.patch, Screen Shot 2017-01-04 at 2.36.21 
> PM.png
>
>
> Current Documentation is not mobile Friendly due the current 
> maven-fluido-skin. This issue can be resolved by upgrading to the version 1.6



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Next Apache Synapse Release

[Isuru Udana]

Hi Vanji,

In jenkins we are still building on 1.7.

Yes, we should move to 1.8, let's raise a separate mail to discuss that
matter.

Thanks.

On Tue, Sep 12, 2017 at 10:23 AM, Vanjikumaran Sivajothy <
vanjikuma...@gmail.com> wrote:

> @Isuru, Are we still building on JDK 1.7?
>
> Can we completely move to 1.8 and use the JDK 1.8 feature for the upcoming
> development and improvements
>
> On Mon, Sep 11, 2017 at 8:32 PM, Asanka Dissanayake <asanka...@gmail.com>
> wrote:
>
>> Hi Isuru,
>> I kind a ported in to synapse and tested locally. Can code can be found
>> here.
>>
>> This is something I wrote more than a year ago. I am rewriting this using
>> java 8 features.
>>
>> code  can be found here
>> https://github.com/asanka88/apache-synapse
>>
>> Thanks,
>> Asanka
>>
>>
>> On Mon, Sep 11, 2017 at 11:21 PM, Isuru Udana <isud...@gmail.com> wrote:
>>
>>> Hi Asanka,
>>>
>>> On Tue, Sep 12, 2017 at 5:32 AM, Asanka Dissanayake <asanka...@gmail.com
>>> > wrote:
>>>
>>>> Hi Devs,
>>>> I see an item with
>>>>
>>>>- *PayloadFactory support with JSON*
>>>>
>>>>
>>>> I built something that can replace payload factory mediator and it has
>>>> much more features. Behind the scene it uses Velocity .
>>>>
>>>> https://github.com/asanka88/VelocityTemplateMediator
>>>>
>>>>
>>>> Have a look and let me know, I will port it to synapse.
>>>>
>>>
>>> Great, we will have a look and get back to you soon.
>>>
>>> Thanks.
>>>
>>>>
>>>> Thanks,
>>>> Asanka
>>>>
>>>>
>>>>
>>>> On Mon, Sep 11, 2017 at 1:48 PM, Vanjikumaran Sivajothy <
>>>> va...@apache.org> wrote:
>>>>
>>>>> Hey isuru,
>>>>>
>>>>> I have already started to work on couple of aspects focusing on
>>>>> improvements and bug fixings.
>>>>>
>>>>> Best regards,
>>>>> Vanji
>>>>>
>>>>> On Sun, Jul 30, 2017 at 9:46 AM, Isuru Udana <isud...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Are we in a position to resume the work for 3.1.0 ? Please let us
>>>>>> know your availability.
>>>>>>
>>>>>> On Thu, Jul 6, 2017 at 8:27 AM, Vanjikumaran Sivajothy <
>>>>>> vanjikuma...@gmail.com> wrote:
>>>>>>
>>>>>>> After the initial discussion, we did not move forward further. Let
>>>>>>> me start with applying my own patches and start to plan as you mention 
>>>>>>> for
>>>>>>> 3.1.0.
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Vanji
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jul 5, 2017 at 3:46 PM, Hiranya Jayathilaka <
>>>>>>> hiranya...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Has anybody made any progress towards this? Perhaps we can pick a
>>>>>>>> few items from Dushan's list and release as 3.1.0?
>>>>>>>>
>>>>>>>> On Thu, May 18, 2017 at 10:34 AM, Vanjikumaran Sivajothy <
>>>>>>>> va...@apache.org> wrote:
>>>>>>>>
>>>>>>>>> I am little hesitated to accept for full blown changes! It may
>>>>>>>>> slow down the release process :(
>>>>>>>>>
>>>>>>>>> Can we please select the Important items and then move on?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, May 16, 2017 at 10:37 PM Dushan Abeyruwan <
>>>>>>>>> dus...@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>> [re-send with apache.org]
>>>>>>>>>>
>>>>>>>>>> Hi All,
>>>>>>>>>>   I guess we should go with the theme of synapse 4.0. What I
>>>>>>>>>> would like to focus such as pretty much on the radical changes 
>>>>>>>>>> introduced
>>>>>>>>>> to synapse
>>>>>>>&

Re: Next Apache Synapse Release

[Isuru Udana]

Hi Asanka,

On Tue, Sep 12, 2017 at 5:32 AM, Asanka Dissanayake <asanka...@gmail.com>
wrote:

> Hi Devs,
> I see an item with
>
>- *PayloadFactory support with JSON*
>
>
> I built something that can replace payload factory mediator and it has
> much more features. Behind the scene it uses Velocity .
>
> https://github.com/asanka88/VelocityTemplateMediator
>
>
> Have a look and let me know, I will port it to synapse.
>

Great, we will have a look and get back to you soon.

Thanks.

>
> Thanks,
> Asanka
>
>
>
> On Mon, Sep 11, 2017 at 1:48 PM, Vanjikumaran Sivajothy <va...@apache.org>
> wrote:
>
>> Hey isuru,
>>
>> I have already started to work on couple of aspects focusing on
>> improvements and bug fixings.
>>
>> Best regards,
>> Vanji
>>
>> On Sun, Jul 30, 2017 at 9:46 AM, Isuru Udana <isud...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> Are we in a position to resume the work for 3.1.0 ? Please let us know
>>> your availability.
>>>
>>> On Thu, Jul 6, 2017 at 8:27 AM, Vanjikumaran Sivajothy <
>>> vanjikuma...@gmail.com> wrote:
>>>
>>>> After the initial discussion, we did not move forward further. Let me
>>>> start with applying my own patches and start to plan as you mention for
>>>> 3.1.0.
>>>>
>>>> Best Regards,
>>>> Vanji
>>>>
>>>>
>>>> On Wed, Jul 5, 2017 at 3:46 PM, Hiranya Jayathilaka <
>>>> hiranya...@gmail.com> wrote:
>>>>
>>>>> Has anybody made any progress towards this? Perhaps we can pick a few
>>>>> items from Dushan's list and release as 3.1.0?
>>>>>
>>>>> On Thu, May 18, 2017 at 10:34 AM, Vanjikumaran Sivajothy <
>>>>> va...@apache.org> wrote:
>>>>>
>>>>>> I am little hesitated to accept for full blown changes! It may slow
>>>>>> down the release process :(
>>>>>>
>>>>>> Can we please select the Important items and then move on?
>>>>>>
>>>>>>
>>>>>> On Tue, May 16, 2017 at 10:37 PM Dushan Abeyruwan <dus...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> [re-send with apache.org]
>>>>>>>
>>>>>>> Hi All,
>>>>>>>   I guess we should go with the theme of synapse 4.0. What I would
>>>>>>> like to focus such as pretty much on the radical changes introduced to
>>>>>>> synapse
>>>>>>>
>>>>>>>- The call mediator implementation (blocking and none blocking)
>>>>>>>and the depreciation of callout mediator. So, we have task now to 
>>>>>>> get the
>>>>>>>latest merge to SYNAPSE-975
>>>>>>><https://issues.apache.org/jira/browse/SYNAPSE-975>
>>>>>>>- Then we should bring the JSON changes done.
>>>>>>>   - JSONFormatter/JSONBuilder based top
>>>>>>>   of staxon  implementation 'org.apache.synapse.commons.st
>>>>>>>   axon.core.json'
>>>>>>>   - JSONPath in Filter, Switch, Property, Payload Factory and
>>>>>>>   Log mediators
>>>>>>>   - PayloadFactory support with JSON
>>>>>>>- *For-Each* mediator implementation
>>>>>>>- Introducing *HTTP EP *for RESTful invocations
>>>>>>>- SSLTunneling
>>>>>>>- We should bring JMSStore (I guess for the time being still we
>>>>>>>do support In memory store)
>>>>>>>- Should give priority on RESTful invocation rather focusing
>>>>>>>SOAP integrations much (so we need to select all the bugs reported 
>>>>>>> and
>>>>>>>fixed while adding addressing REST APIs, uri-template improvements 
>>>>>>> and
>>>>>>>expression evaluation changes)
>>>>>>>- If time permits, I would like to see the integration of *basic
>>>>>>>InboundEndpoint can merge with apache synapse* starts with HTTP
>>>>>>>inbound transport *@Chanaka is this feasible or will there be
>>>>>>>any dependencies from external?*
>>>>>>>- VFS related improvements such as provi

Re: Next Apache Synapse Release

[Isuru Udana]

>   'org.apache.synapse.commons.staxon.core.json'
>>>>>   - JSONPath in Filter, Switch, Property, Payload Factory and Log
>>>>>   mediators
>>>>>   - PayloadFactory support with JSON
>>>>>- *For-Each* mediator implementation
>>>>>- Introducing *HTTP EP *for RESTful invocations
>>>>>- SSLTunneling
>>>>>- We should bring JMSStore (I guess for the time being still we do
>>>>>support In memory store)
>>>>>- Should give priority on RESTful invocation rather focusing SOAP
>>>>>integrations much (so we need to select all the bugs reported and fixed
>>>>>while adding addressing REST APIs, uri-template improvements and 
>>>>> expression
>>>>>evaluation changes)
>>>>>- If time permits, I would like to see the integration of *basic
>>>>>InboundEndpoint can merge with apache synapse* starts with HTTP
>>>>>inbound transport *@Chanaka is this feasible or will there be any
>>>>>dependencies from external?*
>>>>>- VFS related improvements such as providing two new throttling
>>>>>    parameters, FileProcessCount and FileProcessInterval, which allow you 
>>>>> to
>>>>>control the number of files processed in each batch and time between
>>>>>batches.
>>>>>- Recent PTT related changes and improvements.
>>>>>
>>>>> There may be more we can add, but I guess still we have lots of merge
>>>>> and integrations to be done like writing test cases etc etc.
>>>>>
>>>>> I mean we can invite volunteers to do merge especially for Callout,
>>>>> HTTP-EPs, PayloadFactory and JSON improvements if possible Inbound
>>>>> integration to the next release. that's why I'm telling, we should do sort
>>>>> of radical release rather conventional release.
>>>>>
>>>>> Just drop your thoughts WDYT?
>>>>>
>>>>> Cheers,
>>>>> Dushan
>>>>>
>>>>> On Tue, May 16, 2017 at 8:21 PM, Ravi Undupitiya <r...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On 16 May 2017 at 15:28, Dushan Abeyruwan <dus...@apache.org> wrote:
>>>>>>
>>>>>>>  +1
>>>>>>>
>>>>>>> On Mon, May 15, 2017 at 9:28 PM, Chanaka Udaya Kumara Fernando <
>>>>>>> chanaka.leaders...@gmail.com> wrote:
>>>>>>>
>>>>>>>> +1 for a new release.
>>>>>>>>
>>>>>>>> On Mon, May 15, 2017 at 9:51 AM, prabath <prabathm...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Sun, May 14, 2017 at 2:31 PM, Isuru Udana <isud...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1.
>>>>>>>>>>
>>>>>>>>>> On Sun, May 14, 2017 at 3:02 AM, Vanjikumaran Sivajothy <
>>>>>>>>>> va...@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi folks,
>>>>>>>>>>>
>>>>>>>>>>> It's been a while since we released Apache Synapse 3.0, There
>>>>>>>>>>> are number of issues raised in the JIRA[1]. that includes New 
>>>>>>>>>>> Feature,
>>>>>>>>>>> Improvements, Bugs and Documentation. I would like to invite all of 
>>>>>>>>>>> the
>>>>>>>>>>> contributors to get participated in the upcoming release and make it
>>>>>>>>>>> successful again.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [1]https://issues.apache.org/jira/browse/SYNAPSE-1093?jql=pr
>>>>>>>>>>> oject%20%3D%20SYNAPSE%20AND%20resolution%20%3D%20Unresolved%
>>>>>>>>>>> 20ORDER%20BY%20priority%20DESC
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Isuru Udana*
>>>>>>>>>> Senior Technical Lead
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email:
>>>>>>>>>> isud...@gmail.com <isud...@gmail.com> blog: 
>>>>>>>>>> http://mytecheye.blogspot.com/
>>>>>>>>>> <http://mytecheye.blogspot.com/>*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Prabath Ariyarathna.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Mayhem Lab/RACE Lab;
>> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
>> E-mail: hira...@cs.ucsb.edu <hira...@wso2.com>;  Mobile: +1 (805)
>> 895-7443 <+1%20805-895-7443>
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>
>
>
> --
> Best Regards,
> Vanji
>



-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
<isud...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

Re: What is the JDK version used for Jenkin build?

[Isuru Udana]

As far as I remember, we had to upgrade the jdk version to 1.7 in jenkins
to fix some build failure.
I think we don't have to support 1.6 anymore.


On Wed, Jul 12, 2017 at 3:58 AM, Hiranya Jayathilaka <hiranya...@gmail.com>
wrote:

> Did we ever bump our minimum supported JDK version to 1.7? Or are we still
> supporting 1.6?
>
> On Mon, Jul 10, 2017 at 10:13 AM, Vanjikumaran Sivajothy <va...@apache.org
> > wrote:
>
>> As JDK 1.7 reached its end of life[1], Can we try to focus to move
>> towards with 1.8 or later ?
>>
>> [1]http://www.oracle.com/technetwork/java/javase/eol-135779.html
>>
>> On Mon, Jul 10, 2017 at 9:47 AM, Isuru Udana <isud...@apache.org> wrote:
>>
>>> Hi Vanji,
>>>
>>> JDK_1.7.0_79 (with unlimited security)
>>>
>>> On Mon, Jul 10, 2017 at 9:37 PM, Vanjikumaran Sivajothy <
>>> va...@apache.org> wrote:
>>>
>>>> Hi Isuru,
>>>>
>>>> $subject please.
>>>>
>>>
>>>
>>
>
>
> --
> Hiranya Jayathilaka
> Mayhem Lab/RACE Lab;
> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
> E-mail: hira...@cs.ucsb.edu <hira...@wso2.com>;  Mobile: +1 (805) 895-7443
> <+1%20805-895-7443>
> Blog: http://techfeast-hiranya.blogspot.com
>



-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
<isud...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

Re: What is the JDK version used for Jenkin build?

[Isuru Udana]

Hi Vanji,

JDK_1.7.0_79 (with unlimited security)

On Mon, Jul 10, 2017 at 9:37 PM, Vanjikumaran Sivajothy 
wrote:

> Hi Isuru,
>
> $subject please.
>

[jira] [Created] (SYNAPSE-1096) Synchronisation issue in callbacks in TimeoutHandler and CallbackReceiver

[Isuru Udana Loku Narangoda (JIRA)]

Isuru Udana Loku Narangoda created SYNAPSE-1096:
---

 Summary: Synchronisation issue in callbacks in TimeoutHandler and 
CallbackReceiver
 Key: SYNAPSE-1096
 URL: https://issues.apache.org/jira/browse/SYNAPSE-1096
 Project: Synapse
  Issue Type: Bug
Reporter: Isuru Udana Loku Narangoda
Assignee: Isuru Udana Loku Narangoda


Due to a synchronisation issue in callbacks in TimeoutHandler and 
CallbackReceiver,
when endpoint timeout happens there is a possibility of fault sequence is 
executed as well as outSequence. 





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Next Apache Synapse Release

[Isuru Udana]

+1.

On Sun, May 14, 2017 at 3:02 AM, Vanjikumaran Sivajothy <va...@apache.org>
wrote:

> Hi folks,
>
> It's been a while since we released Apache Synapse 3.0, There are number
> of issues raised in the JIRA[1]. that includes New Feature, Improvements,
> Bugs and Documentation. I would like to invite all of the contributors to
> get participated in the upcoming release and make it successful again.
>
>
> [1]https://issues.apache.org/jira/browse/SYNAPSE-1093?jql=
> project%20%3D%20SYNAPSE%20AND%20resolution%20%3D%
> 20Unresolved%20ORDER%20BY%20priority%20DESC
>
>
>
> --
> Sent from Gmail Mobile
>



-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
<isud...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

New Committer: Prabath Ariyarathna

[Isuru Udana]

The Project Management Committee (PMC) for Apache Synapse
has asked Prabath Ariyarathna to become a committer and a PMC member,
and we are pleased to announce that he has accepted.

Prabath has been very active in the Synapse project over the past year
especially for the synapse 3.0.0 release.

Welcome aboard Prabath. Looking forward to your continued contributions.

Thanks,
Isuru

-- 
*Isuru Udana*
Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
<isud...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

Re: [VOTE] Release Apache Synapse 3.0.0 Take 2

[Isuru Udana]

Did smoke tests and run integration tests with the pack. No issues found.

+1

On Sat, Dec 31, 2016 at 5:40 PM, Ravi Undupitiya <r...@apache.org> wrote:

> This is a call for votes to release Apache Synapse 3.0.0 (Take 2)
>
> Please review the distribution artifacts:
> https://dist.apache.org/repos/dist/dev/synapse/3.0.0/RC2/
>
> The nexus staging repository is available at:
> https://repository.apache.org/content/repositories/orgapachesynapse-1004
>
> Updated site for this release is available at:
> http://people.apache.org/~ravi/synapse/3.0.0/RC2/site/
>
> SVN Tag (r1776723):
> https://svn.apache.org/repos/asf/synapse/tags/3.0.0/
>
> Public key:
> http://pgp.mit.edu/pks/lookup?op=get=0xAE1FFE87ABBB3CC4
>
> Issues Fixed:
> https://goo.gl/RfzoCK (Apache Synapse JIRA Link)
>
> Instructions on how to validate distribution artifacts before voting:
> http://www.apache.org/dev/release.html#approving-a-release
>
>
> Thanks,
> Ravi
>



-- 
*Isuru Udana*
Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
<isud...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

[jira] [Updated] (SYNAPSE-1090) Update NOTICE for 3.0.0 release

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda updated SYNAPSE-1090:

Attachment: notice_updates_for_existing_entries.patch

> Update NOTICE for 3.0.0 release
> ---
>
> Key: SYNAPSE-1090
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1090
> Project: Synapse
>  Issue Type: Task
>Affects Versions: 3.0.0
>    Reporter: Isuru Udana Loku Narangoda
>    Assignee: Isuru Udana Loku Narangoda
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: notice_updates_for_existing_entries.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Created] (SYNAPSE-1090) Update NOTICE for 3.0.0 release

[Isuru Udana Loku Narangoda (JIRA)]

Isuru Udana Loku Narangoda created SYNAPSE-1090:
---

 Summary: Update NOTICE for 3.0.0 release
 Key: SYNAPSE-1090
 URL: https://issues.apache.org/jira/browse/SYNAPSE-1090
 Project: Synapse
  Issue Type: Task
Affects Versions: 3.0.0
Reporter: Isuru Udana Loku Narangoda
Assignee: Isuru Udana Loku Narangoda
Priority: Blocker
 Fix For: 3.0.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: [VOTE] Release Apache Synapse 3.0.0

[Isuru Udana]

NOTICE is outdated.

So -1.

On Fri, Dec 30, 2016 at 9:29 PM, Andreas Veithen <andreas.veit...@gmail.com>
wrote:

> 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 <r...@apache.org> wrote:
> > This is a call for votes to release Apache Synapse 3.0.0
> >
> > Please review the distribution artifacts:
> > https://dist.apache.org/repos/dist/dev/synapse/3.0.0/RC1/
> >
> > The nexus staging repository is available at:
> > https://repository.apache.org/content/repositories/orgapachesynapse-1003
> >
> > Updated site for this release is available at:
> > http://people.apache.org/~ravi/synapse/3.0.0/RC1/site/
> >
> > SVN Tag (r1776582):
> > https://svn.apache.org/repos/asf/synapse/tags/3.0.0/
> >
> > Public key:
> > http://pgp.mit.edu/pks/lookup?op=get=0xAE1FFE87ABBB3CC4
> >
> > Issues Fixed:
> > https://goo.gl/RfzoCK (Apache Synapse JIRA Link)
> >
> > Instructions on how to validate distribution artifacts before voting:
> > http://www.apache.org/dev/release.html#approving-a-release
> >
> >
> > Thanks,
> > Ravi
>
> -----
> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
> For additional commands, e-mail: dev-h...@synapse.apache.org
>
>


-- 
*Isuru Udana*
Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isud...@gmail.com
<isud...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

[jira] [Resolved] (SYNAPSE-1089) Update readme file for synapse 3.0.0 release

[Isuru Udana Loku Narangoda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNAPSE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isuru Udana Loku Narangoda resolved SYNAPSE-1089.
-
   Resolution: Fixed
Fix Version/s: 3.0.0

> Update readme file for synapse 3.0.0 release
> 
>
> Key: SYNAPSE-1089
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1089
> Project: Synapse
>  Issue Type: Task
>Reporter: Chanaka Fernando
>    Assignee: Isuru Udana Loku Narangoda
> Fix For: 3.0.0
>
> Attachments: updated_the_readme_for_synapse_3_0_0_release.patch
>
>
> README.txt, Notice and Building.txt files have outdated information. These 
> needs to be updated before the release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org