| tsaha |
Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 00:19 |
| Ruwan Linton |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 01:08 |
| tsaha |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 01:27 |
| Ruwan Linton |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 01:34 |
| Asankha C. Perera |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 02:27 |
| Ruwan Linton |
Changing the default service context path of Synapse |
Tue, 01 Jul, 04:18 |
| Gary Rudolph |
Re: Changing the default service context path of Synapse |
Tue, 01 Jul, 04:40 |
| Ruwan Linton |
Re: Changing the default service context path of Synapse |
Tue, 01 Jul, 05:20 |
| Asankha C. Perera |
Re: Changing the default service context path of Synapse |
Tue, 01 Jul, 05:47 |
| Paul Fremantle |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 06:04 |
| Pedro |
Re: a simple sample |
Tue, 01 Jul, 07:40 |
| Pavel Křehula |
Re: problem with http/1.0 |
Tue, 01 Jul, 13:01 |
| tsaha |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 17:02 |
| tsaha |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 17:15 |
| Ruwan Linton |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 17:58 |
| tsaha |
Re: Exploded vs Archived deployments of config meta data |
Tue, 01 Jul, 20:11 |
| Asanka Abeysinghe |
Problem with JMS --> FIX communication |
Tue, 01 Jul, 20:25 |
| Asanka Abeysinghe |
Problem with JMS --> FIX communication |
Tue, 01 Jul, 20:40 |
| Andreas Veithen |
Re: Problem with JMS --> FIX communication |
Tue, 01 Jul, 21:46 |
| lhard...@traversetechnologies.com |
=?UTF-8?Q?Re:=20Possible=20for=20Synapse=20to=20handle=20non-xml=20respo?= =?UTF-8?Q?nses=3F?= |
Tue, 01 Jul, 23:29 |
| lhard...@traversetechnologies.com |
=?UTF-8?Q?Re:=20Synapse=20as=20HTTP=20Proxy=3F?= |
Tue, 01 Jul, 23:30 |
| lhard...@traversetechnologies.com |
404, 304, 301, and everything else that isn't 200, 202, or 500 |
Tue, 01 Jul, 23:42 |
| Ruwan Linton |
Re: Possible for Synapse to handle non-xml responses? |
Wed, 02 Jul, 00:20 |
| Ruwan Linton |
Re: Synapse as HTTP Proxy? |
Wed, 02 Jul, 00:22 |
| Ruwan Linton |
Re: 404, 304, 301, and everything else that isn't 200, 202, or 500 |
Wed, 02 Jul, 00:31 |
| lhard...@traversetechnologies.com |
Re: 404, 304, 301, and everything else that isn't 200, 202, or 500 |
Wed, 02 Jul, 00:42 |
| Ruwan Linton |
Re: 404, 304, 301, and everything else that isn't 200, 202, or 500 |
Wed, 02 Jul, 00:48 |
| Asankha C. Perera |
Re: Exploded vs Archived deployments of config meta data |
Wed, 02 Jul, 04:23 |
| Scott Hoggarth |
Re: Exploded vs Archived deployments of config meta data |
Wed, 02 Jul, 14:14 |
| Gary Rudolph |
Re: Exploded vs Archived deployments of config meta data |
Wed, 02 Jul, 15:33 |
| Ruwan Linton |
Re: Exploded vs Archived deployments of config meta data |
Thu, 03 Jul, 04:36 |
| Asanka Abeysinghe |
Re: Problem with JMS --> FIX communication |
Thu, 03 Jul, 07:25 |
| Alexey Ousov |
Synapse non-standard usage - scheduler |
Thu, 03 Jul, 09:01 |
| Ruwan Linton |
[PROPOSAL] Synapse artifact jar files as OSGi bundles |
Thu, 03 Jul, 09:04 |
| Ruwan Linton |
Re: Synapse non-standard usage - scheduler |
Thu, 03 Jul, 09:14 |
| Wayne Keenan |
Re: [PROPOSAL] Synapse artifact jar files as OSGi bundles |
Thu, 03 Jul, 09:29 |
| Alexey Ousov |
Re: Synapse non-standard usage - scheduler |
Thu, 03 Jul, 09:35 |
| Paul Fremantle |
Re: [PROPOSAL] Synapse artifact jar files as OSGi bundles |
Thu, 03 Jul, 12:41 |
| Laurent CHARTIER |
[Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Thu, 03 Jul, 14:05 |
| Ruwan Linton |
Re: [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Thu, 03 Jul, 15:04 |
| Laurent CHARTIER |
RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Thu, 03 Jul, 15:09 |
| Asankha C. Perera |
Re: [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Thu, 03 Jul, 15:17 |
| Laurent CHARTIER |
RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Thu, 03 Jul, 15:24 |
| Ruwan Linton |
Re: RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Thu, 03 Jul, 15:24 |
| Ruwan Linton |
Re: RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Thu, 03 Jul, 15:31 |
| Laurent CHARTIER |
RE : RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Fri, 04 Jul, 11:47 |
| Ruwan Linton |
Re: RE : RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Sat, 05 Jul, 13:23 |
| Laurent CHARTIER |
RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Mon, 07 Jul, 08:52 |
| Asankha C. Perera |
Re: RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Mon, 07 Jul, 08:58 |
| Laurent CHARTIER |
RE : RE : RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Mon, 07 Jul, 09:15 |
| Ruwan Linton |
Re: RE : RE : RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Mon, 07 Jul, 09:34 |
| Laurent CHARTIER |
RE : RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Mon, 07 Jul, 10:50 |
| Laurent CHARTIER |
RE : RE : RE : RE : [Synapse 1.1.1] - F.A.Q. SOAP1.1 to SOAP1.2 |
Mon, 07 Jul, 11:11 |
| Asanka Abeysinghe |
Re: Problem with JMS --> FIX communication |
Mon, 07 Jul, 18:09 |
| Bertram....@entega-service.de |
webservice proxy uses fully qualified url for forwarding? |
Thu, 10 Jul, 13:39 |
| Asankha C. Perera |
Re: webservice proxy uses fully qualified url for forwarding? |
Thu, 10 Jul, 15:13 |
| Bertram....@entega-service.de |
Re: webservice proxy uses fully qualified url for forwarding? |
Fri, 11 Jul, 07:43 |
| Asankha C. Perera |
Re: webservice proxy uses fully qualified url for forwarding? |
Fri, 11 Jul, 07:53 |
| Bertram....@entega-service.de |
Re: webservice proxy uses fully qualified url for forwarding? |
Fri, 11 Jul, 09:55 |
| Asankha C. Perera |
Re: webservice proxy uses fully qualified url for forwarding? |
Fri, 11 Jul, 10:04 |
| tsaha |
JMSUtil does not set all JMS Connection properties specified in axis2.xml |
Sat, 12 Jul, 00:28 |
| Asankha C. Perera |
Re: JMSUtil does not set all JMS Connection properties specified in axis2.xml |
Sat, 12 Jul, 04:36 |
| Asankha C. Perera |
Re: webservice proxy uses fully qualified url for forwarding? |
Mon, 14 Jul, 04:36 |
| tsaha |
Re: JMSUtil does not set all JMS Connection properties specified in axis2.xml |
Mon, 14 Jul, 17:00 |
| tsaha |
Synapse-1.2 incorrectly sets the JMSReplyDestination Type |
Mon, 14 Jul, 20:34 |
| Ruwan Linton |
8280/8243 registered as default HTTP/HTTPS port numbers for synapse |
Tue, 15 Jul, 03:30 |
| Scott Hoggarth |
Sample Proxy of Long Running Service |
Tue, 15 Jul, 16:21 |
| tsaha |
Re: Sample Proxy of Long Running Service |
Tue, 15 Jul, 16:30 |
| Asankha C. Perera |
Re: Sample Proxy of Long Running Service |
Tue, 15 Jul, 16:35 |
| Ruwan Linton |
Re: Sample Proxy of Long Running Service |
Tue, 15 Jul, 16:38 |
| Asankha C. Perera |
Re: Sample Proxy of Long Running Service |
Tue, 15 Jul, 16:39 |
| Hubert, Eric |
Synapse is blocked and does not deliver responses |
Tue, 15 Jul, 17:06 |
| Qifeng....@csiro.au |
Problem of "chunked Transfer-Encoding forbidden" |
Wed, 16 Jul, 00:32 |
| Asankha C. Perera |
Re: Problem of "chunked Transfer-Encoding forbidden" |
Wed, 16 Jul, 05:42 |
| Olivier Ziller GMail Lists |
information needed on soapaction attribute of the clone mediator |
Wed, 16 Jul, 09:01 |
| Ruwan Linton |
Re: information needed on soapaction attribute of the clone mediator |
Wed, 16 Jul, 09:41 |
| Ruwan Linton |
Re: information needed on soapaction attribute of the clone mediator |
Wed, 16 Jul, 10:02 |
| Olivier Ziller |
Re: information needed on soapaction attribute of the clone mediator |
Wed, 16 Jul, 10:15 |
| Ruwan Linton |
Re: information needed on soapaction attribute of the clone mediator |
Wed, 16 Jul, 10:38 |
| Olivier Ziller |
Re: information needed on soapaction attribute of the clone mediator |
Wed, 16 Jul, 13:01 |
| Olivier Ziller |
chaining synapse servers |
Thu, 17 Jul, 07:43 |
| Paul Fremantle |
Re: chaining synapse servers |
Thu, 17 Jul, 08:24 |
| Olivier Ziller |
Re: chaining synapse servers |
Thu, 17 Jul, 08:34 |
| Asankha C. Perera |
Re: chaining synapse servers |
Thu, 17 Jul, 10:45 |
| Olivier Ziller |
Re: chaining synapse servers |
Thu, 17 Jul, 14:53 |
| Asankha C. Perera |
Re: chaining synapse servers |
Thu, 17 Jul, 16:14 |
| Alexey Ousov |
get-property('To') full url |
Thu, 17 Jul, 16:44 |
| Asankha C. Perera |
Re: get-property('To') full url |
Thu, 17 Jul, 17:16 |
| Alexey Ousov |
Re: get-property('To') full url |
Fri, 18 Jul, 02:50 |
| Evanthika Amarasiri |
Re: chaining synapse servers |
Fri, 18 Jul, 04:25 |
| Evanthika Amarasiri |
Re: chaining synapse servers |
Fri, 18 Jul, 05:29 |
| Paul Fremantle |
Re: get-property('To') full url |
Fri, 18 Jul, 06:17 |
| Olivier Ziller |
Re: chaining synapse servers |
Fri, 18 Jul, 14:11 |
| Olivier Ziller |
Re: chaining synapse servers |
Fri, 18 Jul, 14:29 |
| indika kumara |
Re: chaining synapse servers |
Sat, 19 Jul, 14:25 |
| Andreas Veithen |
Re: Problem with JMS --> FIX communication |
Sun, 20 Jul, 12:47 |
| Asankha C. Perera |
Re: Synapse is blocked and does not deliver responses |
Mon, 21 Jul, 02:32 |
| Evanthika Amarasiri |
Re: chaining synapse servers |
Mon, 21 Jul, 05:25 |
| Olivier Ziller |
Re: chaining synapse servers |
Mon, 21 Jul, 12:10 |
| Paul Fremantle |
Re: chaining synapse servers |
Mon, 21 Jul, 12:22 |