Acknowledged
Thanks
Upul
On Sun, Jan 22, 2012 at 12:02 AM, Paul Fremantle wrote:
> The PMC has voted to invite the following committers to join the Synapse PMC:
>
> ajith
> asanka
> charith
> chathura_ce
> evanthika
> heshan
> hiranya
> kasun
> rajikak
> saminda
> sanjiva
> sanka
>
+1
Upul
On Fri, Sep 4, 2009 at 4:26 PM, Asankha C. Perera wrote:
> Hi All
>
> We have been waiting to make the 1.3 release for sometime now.. but
> mainly due to the dependency project releases it is still pending. As I
> think Ruwan is in a better position to get these releases out in time, I
>
+1
Upul
On Mon, Apr 20, 2009 at 3:24 PM, Asankha C. Perera wrote:
> Hi All
>
> Eric has been supporting Synapse for a very long time now, and has been
> contributing by testing, documentation and most recently bug fixes and
> enhancements / new feature implementations as well. I can confidently
+1
Upul
On Thu, Jun 5, 2008 at 2:53 PM, Ruwan Linton <[EMAIL PROTECTED]> wrote:
> Hi Devs,
>
> After figuring out the problem of some missing jars which caused the first
> VOTE to be retracted;
> this is the call for votes take-2 to release Synapse-1.2.
>
> Please review the signed artifacts:
>
+1
Upul
On Tue, May 13, 2008 at 11:15 AM, Ruwan Linton <[EMAIL PROTECTED]> wrote:
> Folks,
>
> I think we missed to invite one person to the dev community, who was
> helping us through out the full synapse life cycle on testing Synapse and
> reporting suggestions, improvements; she was Evanthika
[
https://issues.apache.org/jira/browse/SYNAPSE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-254.
-
Resolution: Fixed
Changing the address using for To, ReplyTo work only when the
address is of
[
https://issues.apache.org/jira/browse/SYNAPSE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-161.
-
Resolution: Fixed
Synapse will be using the latest rampart release
> Can't persuade Ra
+1
Upul
Yes, I will use the existing code for both. Thanks.
Upul
On Tue, Apr 8, 2008 at 4:20 AM, Andreas Veithen <[EMAIL PROTECTED]>
wrote:
> Upul,
>
> Is there a reason why the init method doesn't reuse the existing
> buildAppContext method?
>
> Andreas
>
>
> On 07 Apr 2008, at 11:17, [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/SYNAPSE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-208.
-
Resolution: Fixed
Creates Spring application context in the mediator init()
> Loads the Spr
[
https://issues.apache.org/jira/browse/SYNAPSE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-199.
-
Resolution: Fixed
Sample 100 works now in rampart, wss4j snapshots
> NullPointerException
[
https://issues.apache.org/jira/browse/SYNAPSE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585444#action_12585444
]
Upul Godage commented on SYNAPSE-254:
-
Fixed jms reply destination setting. Als
[
https://issues.apache.org/jira/browse/SYNAPSE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-253.
-
Resolution: Fixed
Null exception handled
> NullPointerException thrown when the OUT_O
Hi all,
Right now Synapse uses the ports, HTTP port 8080 and HTTPS port 8443 by
default. When Synapse is running with other applications such as Tomcat
servers etc. users have to change either one of these applications when
there is a conflict. It would be better if we use two unused ports for
Syn
[
https://issues.apache.org/jira/browse/SYNAPSE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-203.
-
Resolution: Fixed
converted port numbers to constants
> Refactored "magic num
[
https://issues.apache.org/jira/browse/SYNAPSE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-227.
-
Resolution: Fixed
Assignee: Upul Godage
There is a mediator which provides a simple
[
https://issues.apache.org/jira/browse/SYNAPSE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-170.
-
Resolution: Fixed
New mail transport sender does not have this problem.
> VFS transp
[
https://issues.apache.org/jira/browse/SYNAPSE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-236.
-
Resolution: Fixed
sql element text saved in cdata sections
> Store SQL statements in CDATA
[
https://issues.apache.org/jira/browse/SYNAPSE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage resolved SYNAPSE-238.
-
Resolution: Fixed
Assignee: Upul Godage
Now when a target/inSequence returns false
[
https://issues.apache.org/jira/browse/SYNAPSE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Upul Godage reassigned SYNAPSE-236:
---
Assignee: Upul Godage
> Store SQL statements in CDATA for DB mediat
I will revert the pom.xml to the earlier one for now. There must be wrong
dependency coming from this dependency.
Upul
Running org.apache.synapse.config.xml.IterateMediatorSerializationTest
Tests run: 6, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.485 sec
<<< FAILURE!
Running org.apache.
Hi,
If you are adding an element to the body element, you can use addChild()
etc.
If you are adding a header to the SOAP envelope then you can do something
like this.
SOAPHeaderBlock newBlock =
ctx.getEnvelope().getHeader().addHeaderBlock("userid",
ns);
newBlock.setText("text");
At that level, you can try installing Synapse as a Windows service and use
service start, stop shell level commands.
net start Synapse
net stop Synapse
Upul
On Feb 18, 2008 8:31 PM, ali_khan <[EMAIL PROTECTED]> wrote:
>
> Hi
> I have tried "o.a.synapse.ServerManager.stop()"
> but its not working
If you are using the SynapseServer as in the startup scripts files, you can
use the following code to do what happens inside the SynapseServer.main()
method instead.
import org.apache.synapse.ServerManager;
serverManager = ServerManager.getInstance();
serverManager.setAxis2Repolocation("repositor
Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Upul Godage
http://ws.apache.org/ns/synapse";>
http://localhost:9001/soap/SimpleStockQuot
Hi,
You can try this. This replaces the http://localhost:9000 to
http://upul:8081.
http://ws.apache.org/ns/synapse";>
http://upul:8081',
fn:substring-after(get-property('To'), 'http://localhost:9000'))"/>
Hope this helps.
Upul
On Feb 6, 2008 1:41 PM,
+1
Upul
On Feb 6, 2008 12:56 AM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> I'd like to propose Andreas Veithen as a committer on Synapse. Andreas
> has provided a number of patches, found some good areas for
> improvements, and I think would make an excellent committer.
>
> Here is my +1.
>
>
May be something like this will do.
http://ws.apache.org/ns/synapse";>
https://10.192.12.89',
get-property('To'))"/>
Upul
On Feb 4, 2008 2:07 PM, Venkatesan, Kumaran <
[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
> We are facing issue in routing requests. The requirement is t
+1 to release the code tagged as 1.1.1 as 1.1.2.
Upul
On Feb 1, 2008 7:45 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> We'll do a rebuild with the only change being the version number.
> So... in the interests of getting the vote started.
>
> Please vote to release the code tagged as 1.1.1 as
+1 Release these artifacts as Synapse 1.1.1
Upul
On Jan 24, 2008 3:33 PM, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
> We have now fixed the issue on Windows which prevented the "synapse.bat
> -sample " option from working. Also the sample Axis2 server runs even
> with long file names using t
+1 Release these artifacts as Synapse 1.1.1
Upul
31 matches
Mail list logo
