[
https://issues.apache.org/jira/browse/SYNAPSE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12775112#action_12775112
]
Supun Kamburugamuva commented on SYNAPSE-595:
-
HI Asanka,
I agree with you
on proxy services didn't
make me comfortable, it is confusing to the users.
Thanks,
Ruwan
On Mon, Nov 9, 2009 at 1:42 PM, Supun Kamburugamuva supu...@gmail.comwrote:
On Mon, Nov 9, 2009 at 1:27 PM, Hiranya Jayathilaka hiranya...@gmail.com
wrote:
+1
Looks good to me but can we please change
Hi Ruwan,
I know everyone was busy. As you know, I never forced anybody to apply
patches or anything like that :). Or I never even complained about something
like that. But as a community it is not good to leave the patches behind.
That is all I wanted to point out :).
Thanks,
Supun..
On Tue,
to preserve the original
order.
Also any serializer/factory-deserializer-pair would need to implement
this.
Maybe others have already discussed about this at design time? Any input
from the devs early involved?
Regards,
Eric
--
*From:* Supun
Hi all,
Ability to call one service, then use that result to call another service
and so on is a very important feature in any ESB. But this is hard to
implement in the current Synapse configuration language unless we are using
something like callout mediator.
But with a simple improvement we
Hi Eric,
I thought about this a bit further. Synapse runs on an object model. Not on
a XML configuration. As far as I understood this was the original goal. Also
it makes sense. The synapse configuration can be created using XML or may be
spring or may be pure programming. At the synapse object
[
https://issues.apache.org/jira/browse/SYNAPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774867#action_12774867
]
Supun Kamburugamuva commented on SYNAPSE-593:
-
Yes I thought about
+1,
Actually there was a patch to property mediator implementing this same
functionality. But I seemed nobody cared to look at it :)
Thanks,
Supun..
On Mon, Nov 9, 2009 at 10:58 AM, Hiranya Jayathilaka
hiranya...@gmail.comwrote:
Hi Folks,
Currently the property mediator sets all property
https://issues.apache.org/jira/browse/SYNAPSE-458
It only implemented support for boolean properties.
Thanks,
Supun..
On Mon, Nov 9, 2009 at 11:39 AM, Hiranya Jayathilaka
hiranya...@gmail.comwrote:
On Mon, Nov 9, 2009 at 11:32 AM, Supun Kamburugamuva supu...@gmail.comwrote:
+1,
Actually
Issue Type: Bug
Components: Transports
Reporter: Supun Kamburugamuva
The nhttp transport connection pool uses double checked locking when it
releases a connection. But double checked locking is not a recommended practice
in Java and its use is avoided. Simply because
[
https://issues.apache.org/jira/browse/SYNAPSE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-595:
Attachment: SYNAPSE-595.patch
Attaching a patch that removes the double check
(existing and your suggestions) so that we can
compare... And also how much services can your approach chain? ... if
it is more than two , what will be the configuration? - could it
become similar to the existing approach?
Thanks
Indika
On Mon, Nov 9, 2009 at 11:45 AM, Supun Kamburugamuva supu
On Mon, Nov 9, 2009 at 12:25 PM, Hiranya Jayathilaka
hiranya...@gmail.comwrote:
Hi Supun,
On Mon, Nov 9, 2009 at 11:54 AM, Supun Kamburugamuva supu...@gmail.comwrote:
Yes, I didn't want to say we need to apply that patch now. That patch
should have being applied a long time ago
On Mon, Nov 9, 2009 at 1:12 PM, Hiranya Jayathilaka hiranya...@gmail.comwrote:
On Mon, Nov 9, 2009 at 12:45 PM, Supun Kamburugamuva supu...@gmail.comwrote:
On Mon, Nov 9, 2009 at 12:25 PM, Hiranya Jayathilaka
hiranya...@gmail.com wrote:
Hi Supun,
On Mon, Nov 9, 2009 at 11:54 AM
: Core
Reporter: Supun Kamburugamuva
If a receiving sequence is specified for send mediator, the response can be
directed to this sequence. This way we can achieve service chaining with normal
non-blocking transport calls.
I'm attaching a patch that introduce this feature. Please have
[
https://issues.apache.org/jira/browse/SYNAPSE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-593:
Attachment: synapse_service_chaining.patch
A patch attached.
Specifying
[
https://issues.apache.org/jira/browse/SYNAPSE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774635#action_12774635
]
Supun Kamburugamuva commented on SYNAPSE-591:
-
Hi Indika,
Thanks for looking
[
https://issues.apache.org/jira/browse/SYNAPSE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774637#action_12774637
]
Supun Kamburugamuva commented on SYNAPSE-591:
-
One other point is I can
Hi,
If we submit a URL with a space synapse nhttp transport goes in to an
infinite loop. This is caused by a null point exception. I've created a Jira
and submitted a patch. This error case (invalid HTTP request) should be
handled by HTTP core NIO and it shouldn't propegate to nhttp transport
[
https://issues.apache.org/jira/browse/SYNAPSE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-591:
Attachment: SYNAPSE-591.patch
Attaching a patch
Adding a new mediator
[
https://issues.apache.org/jira/browse/SYNAPSE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12765114#action_12765114
]
Supun Kamburugamuva commented on SYNAPSE-591:
-
This issue is related
[
https://issues.apache.org/jira/browse/SYNAPSE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-592:
Attachment: SYNAPSE-592.patch
Attaching a simple fix that checks this buffer
Project: Synapse
Issue Type: Bug
Reporter: Supun Kamburugamuva
Attachments: SYNAPSE-592.patch
I've submitted an invalid url (a url with a space) to synapse. When this
happens NIO transport goes to an infinite loop. It shows the following
exception repeatedly
[
https://issues.apache.org/jira/browse/SYNAPSE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762857#action_12762857
]
Supun Kamburugamuva commented on SYNAPSE-588:
-
Yes, I've thought about
[
https://issues.apache.org/jira/browse/SYNAPSE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762084#action_12762084
]
Supun Kamburugamuva commented on SYNAPSE-588:
-
Hi Adnreas,
Here is the use
Issue Type: New Feature
Reporter: Supun Kamburugamuva
At the moment property mediator just set the value. This value can be direct as
well as coming from evaluating a xpath expression. If this value can be matched
against a regular expression and the matching string can be set
[
https://issues.apache.org/jira/browse/SYNAPSE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-588:
Attachment: SYNAPSE-588.patch
Attaching a patch that extends the property
[
https://issues.apache.org/jira/browse/SYNAPSE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-588:
Attachment: SYNAPSE-588-DOC.patch
Extending property mediator to set properties
[
https://issues.apache.org/jira/browse/SYNAPSE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12761139#action_12761139
]
Supun Kamburugamuva commented on SYNAPSE-588:
-
Not exactly sure about
[
https://issues.apache.org/jira/browse/SYNAPSE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12761141#action_12761141
]
Supun Kamburugamuva commented on SYNAPSE-588:
-
Attached a document patch
JMS Two way sample
--
Key: SYNAPSE-582
URL: https://issues.apache.org/jira/browse/SYNAPSE-582
Project: Synapse
Issue Type: Improvement
Reporter: Supun Kamburugamuva
Introduce a new sample to use JMS transport
[
https://issues.apache.org/jira/browse/SYNAPSE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-582:
Attachment: SYNAPSE-582.patch
Attaching a sample the uses jms transport
[
https://issues.apache.org/jira/browse/SYNAPSE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-575:
Attachment: SYNAPSE-575.patch
I'm attaching a patch that improves the callout
Hi,
I think this is the price that we have to pay for enabling dynamic behavior.
If the ESB is under huge load and we synchronize these methods it won't
scale anyway.
Having two threads load the same resource is tolerable if one thread doesn't
access the resource while it is initialized halfway
On Wed, Sep 9, 2009 at 10:27 PM, Hiranya Jayathilaka
hiranya...@gmail.comwrote:
On Wed, Sep 9, 2009 at 7:52 PM, Supun Kamburugamuva supu...@gmail.comwrote:
Hi,
I think this is the price that we have to pay for enabling
dynamic behavior. If the ESB is under huge load and we synchronize
[
https://issues.apache.org/jira/browse/SYNAPSE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751778#action_12751778
]
Supun Kamburugamuva commented on SYNAPSE-577:
-
We've tested this with the WSO2
[
https://issues.apache.org/jira/browse/SYNAPSE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751779#action_12751779
]
Supun Kamburugamuva commented on SYNAPSE-577:
-
I also think just checking
[
https://issues.apache.org/jira/browse/SYNAPSE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751780#action_12751780
]
Supun Kamburugamuva commented on SYNAPSE-577:
-
Seems this is solved
[
https://issues.apache.org/jira/browse/SYNAPSE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-579:
Attachment: SYNAPSE-579.patch
Attaching a patch that generates a unique name
[
https://issues.apache.org/jira/browse/SYNAPSE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-579:
Attachment: SYNAPSE-579.patch
Generating a unique name for annonymous endpoints
[
https://issues.apache.org/jira/browse/SYNAPSE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-579:
Attachment: (was: SYNAPSE-579.patch)
Generating a unique name for annonymous
I have attached a patch. SYNAPSE-579.
In this patch it generates a unique id for anonymous endpoints in a
clustered environment.
Supun..
On Wed, Sep 2, 2009 at 11:50 PM, Supun Kamburugamuva supu...@gmail.comwrote:
Hi all,
With the new code for a endpoint to work in a clustered environment
[
https://issues.apache.org/jira/browse/SYNAPSE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12750319#action_12750319
]
Supun Kamburugamuva commented on SYNAPSE-577:
-
Seems the patch I've provided
Improving WSDL endpoint to pick Rest case
-
Key: SYNAPSE-578
URL: https://issues.apache.org/jira/browse/SYNAPSE-578
Project: Synapse
Issue Type: Improvement
Reporter: Supun Kamburugamuva
[
https://issues.apache.org/jira/browse/SYNAPSE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-578:
Attachment: synapse-578.patch
Attaching a patch
Improving WSDL endpoint to pick
[
https://issues.apache.org/jira/browse/SYNAPSE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12748289#action_12748289
]
Supun Kamburugamuva commented on SYNAPSE-549:
-
In the addressing header
[
https://issues.apache.org/jira/browse/SYNAPSE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-549:
Attachment: synapse-549_1.patch
Re-attaching with Ruwans suggestion.
Implement
On Mon, Aug 24, 2009 at 3:57 AM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Folks,
I was trying to implement the hot deployment and hot update of the synapse
artifacts as per my proposal the to the list sometime back using the axis2
deployers. But due to some restrictions and the architecture
[
https://issues.apache.org/jira/browse/SYNAPSE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12747312#action_12747312
]
Supun Kamburugamuva commented on SYNAPSE-549:
-
Please review and let me know
[
https://issues.apache.org/jira/browse/SYNAPSE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva reopened SYNAPSE-572:
-
The patch I've submitted doesn't address the problem with double checked
locking
[
https://issues.apache.org/jira/browse/SYNAPSE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-572:
Attachment: synapse-572_1.patch
This patch solves the problem of double checking
[
https://issues.apache.org/jira/browse/SYNAPSE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746408#action_12746408
]
Supun Kamburugamuva commented on SYNAPSE-572:
-
Yes we can combine these two
[
https://issues.apache.org/jira/browse/SYNAPSE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-572:
Description: With the current code multiple threads can create the XSLT
template
[
https://issues.apache.org/jira/browse/SYNAPSE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-572:
Attachment: synapse-572.patch
XSLT Mediator possibility of creating multiple
Issue Type: Improvement
Reporter: Supun Kamburugamuva
Attachments: synapse-572.patch
With the current code multiple threads can create the XSLT template after
seeing that the cache has expired. Also we are always doing a synchronization
for creating the template which can
Hi,
I'm referring to XSLT mediator code where XSLT template is created. With the
current code multiple threads can create the template after seeing that the
cache has expired. Also we are always doing a synchronization for creating
the template which can be costly. I've created a jira and attached
Jira is https://issues.apache.org/jira/browse/SYNAPSE-572
https://issues.apache.org/jira/browse/SYNAPSE-572Supun.
On Thu, Aug 20, 2009 at 5:28 AM, Supun Kamburugamuva supu...@gmail.comwrote:
Hi,
I'm referring to XSLT mediator code where XSLT template is created. With
the current code multiple
[
https://issues.apache.org/jira/browse/SYNAPSE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-572:
Component/s: Core
XSLT Mediator possibility of creating multiple Templates
Hi,
On Wed, Jul 22, 2009 at 8:20 AM, indika kumara indika.k...@gmail.comwrote:
Ruwan , It is not reactors that proportional to the users , but all
resources consumes by reactors. Did you see java doc from
‘AbstractMultiworkerIOReactor’.
javadoc
*Usually it is recommended to have one
Hi,
I've built a fresh synapse from the trunk. When I try to start Synapse I got
the following errors. The I commented out the mail and vfs transports from
axis2.xml and it started successfully. Any ideas why this is happening?
2009-07-14 15:21:51,265 [-] [WrapperSimpleAppMain] FATAL
Now it is working, Thank you.
Supun.
On Tue, Jul 14, 2009 at 3:52 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
My fault. I will fix this ASAP.
Andreas
On Tue, Jul 14, 2009 at 11:52, Supun Kamburugamuvasupu...@gmail.com
wrote:
Hi,
I've built a fresh synapse from the trunk. When I
, IMHO the LB or FO should be
transparent to the user. Therefore, the user should not know the inside
details.
Thanks,
Saliya
On Fri, Jun 26, 2009 at 11:00 AM, Supun Kamburugamuva supu...@gmail.com
wrote:
Hi all,
I got this idea and I thought of asking it from the community
, the user should not know the inside details.
Sorry I didn't get you..
Thanks
Supun.
Thanks,
Saliya
On Fri, Jun 26, 2009 at 11:00 AM, Supun Kamburugamuva
supu...@gmail.comwrote:
Hi all,
I got this idea and I thought of asking it from the community.
I think it is better to have
Hi all,
I got this idea and I thought of asking it from the community.
I think it is better to have the flexibility to change an endpoint address
dynamically. At the moment we can achieve this with DefaultEndpoint or using
a send mediator without an Endpoint. In both these cases we can change
Hi all,
This error occurs when we do a serialize call before doing a
serializeAndConsume method of Envelope. In the debug mode we are serializing
the Envelope in the SynapseCallbackReceiver. Then we call
serializeAndConsume in the HTTPCoreNIOSender. This causes the XML to be
serialized
AspectConfiguration not set to the default sequences
Key: SYNAPSE-556
URL: https://issues.apache.org/jira/browse/SYNAPSE-556
Project: Synapse
Issue Type: Bug
Reporter: Supun
[
https://issues.apache.org/jira/browse/SYNAPSE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-556:
Attachment: SYNAPSE-556.patch
I've attached a patch.
AspectConfiguration
[
https://issues.apache.org/jira/browse/SYNAPSE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-553:
Attachment: (was: SYNAPSE-553.patch)
Allow XML elements to be specified
[
https://issues.apache.org/jira/browse/SYNAPSE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-553:
Attachment: SYNAPSE-553.patch
Hi Andreas,
Thanks for the suggestion. I've
[
https://issues.apache.org/jira/browse/SYNAPSE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-553:
Attachment: (was: SYNAPSE-553-2.patch)
Allow XML elements to be specified
[
https://issues.apache.org/jira/browse/SYNAPSE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-553:
Attachment: SYNAPSE-553.patch
Allow XML elements to be specified as faule detail
[
https://issues.apache.org/jira/browse/SYNAPSE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-553:
Attachment: (was: SYNAPSE-553.patch)
Allow XML elements to be specified
[
https://issues.apache.org/jira/browse/SYNAPSE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713422#action_12713422
]
Supun Kamburugamuva commented on SYNAPSE-553:
-
Thanks for pointing this out
[
https://issues.apache.org/jira/browse/SYNAPSE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-553:
Attachment: SYNAPSE-553.patch
I've attached a modified patch. In this patch
: Improvement
Components: Core
Reporter: Supun Kamburugamuva
At the moment FaultMediator doesn't allow XML elements to e specified as Fault
details
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online
any XML content.
Andreas
On Mon, May 25, 2009 at 07:56, Supun Kamburugamuva supu...@gmail.com
wrote:
There are many ways of specifying details in the fault mediator. At the
moment we specify expresion as an attribute, and detail text as text of
the
detail element. If we introduce
[
https://issues.apache.org/jira/browse/SYNAPSE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-553:
Attachment: SYNAPSE-553.patch
I've attached a patch
Allow XML elements
. introducing an
optional attribute.
I would like to know what the community prefers.
Thanks,
Supun..
On Sun, May 24, 2009 at 5:32 PM, Supun Kamburugamuva supu...@gmail.comwrote:
Yes, I would like to provide a patch and I'm working on it.
Thanks,
Supun
On Sat, May 23, 2009 at 7:40 AM, Ruwan Linton
Sorry, small correction in the previous mail: I want to specify an element
as the fault detail not a SOAP element.
Thanks,
Supun..
On Fri, May 22, 2009 at 2:31 PM, Supun Kamburugamuva supu...@gmail.comwrote:
Hi,
I want to specify a SOAP element as the fault detail using
If we build the Axis service from the WSDL, I think it is reusable across
multiple requests. So we do not need to create the service for each
request.
Synapse client side gets the whole SOAP envelope. At this point synapse
doesn't know about the operation. Only way we can find out the operation
#getOperationBySOAPAction and
AxisService#getOperationByMessageElementQName to find the operation.
So we can easily find the operation without invoking the dispatchers.
Andreas
On Fri, May 15, 2009 at 08:26, Supun Kamburugamuva supu...@gmail.com
wrote:
If we build the Axis service from
endpoint.
WDYT?
Thanks,
Supun..
On Wed, May 6, 2009 at 9:12 AM, Supun Kamburugamuva supu...@gmail.comwrote:
Andreas,
Axis2 traverse the WSDL and attach the policies to the description
hierachy. At the run time it caculates the policy. But this method is not
possible with Synapse, since we
Hi all,
WSDL endpoint has port and service as configuration parameters. From this
information we can find the service, port and binding from the WSDL. But
this information is not enough to find the operation. Because of this we
cannot calculate the complete policy when operation level and message
, 2009 at 13:21, Supun Kamburugamuva supu...@gmail.com
wrote:
Hi all,
WSDL endpoint has port and service as configuration parameters. From this
information we can find the service, port and binding from the WSDL. But
this information is not enough to find the operation. Because of this we
). This is now fixed, but
sample 56 is still not working correctly: the response from the sample
Axis2 server is received by Synapse, but never sent back to the
client.
Andreas
On Sat, May 2, 2009 at 05:41, Supun Kamburugamuva supu...@gmail.com
wrote:
Hi all,
I was trying to run sample
Thanks for the pointer.
Supun.
On Sat, May 2, 2009 at 10:48 AM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Supun, alternatively you could build with the -U option.
Thanks,
Ruwan
On Sat, May 2, 2009 at 8:11 AM, Supun Kamburugamuva supu...@gmail.comwrote:
I got a compile error while trying
[
https://issues.apache.org/jira/browse/SYNAPSE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-539:
Attachment: SYNAPSE-539.patch
I have attached a patch for the improvement
I have attached a patch. The changes goes in to EndpointDefinition.java,
WSDL11EndpointBuilder.java, Axis2FlexibleMepClient.java and
SynapseConstants.java. These are highly specialized changes for this
scenario only.
Thanks,
Supun..
On Fri, May 1, 2009 at 9:13 AM, Ruwan Linton
[
https://issues.apache.org/jira/browse/SYNAPSE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705292#action_12705292
]
Supun Kamburugamuva commented on SYNAPSE-541:
-
Hi Ruwan,
Send mediator
[
https://issues.apache.org/jira/browse/SYNAPSE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-541:
Component/s: Endpoints
WSDL endpoints not working
[
https://issues.apache.org/jira/browse/SYNAPSE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Kamburugamuva updated SYNAPSE-541:
Attachment: WSDLEndpoint.patch
I have attaches a simple fix for the WSDL
Hi all,
In WSDL endpoints Synapse doesn't load the security policies and RM policies
from the WSDL. At the moment we have to specify these
policies separately, even if the policies are specified in the WSDL. It will
be better if Synapse loads these policies from the WSDL itself. I would like
to
: Endpoints
Reporter: Supun Kamburugamuva
In WSDL endpoints Synapse doesn't load the security policies and RM policies
from the WSDL. At the moment we have to specify these policies separately, even
if the policies are specified in the WSDL.
--
This message is automatically
Is there a scenario where request is a hessian message and reply is a SOAP
message?
Supun.
On Mon, Mar 16, 2009 at 9:56 PM, indika kumara indika.k...@gmail.comwrote:
Hi All
I am sorry as I just look at this only now. Just putting my concerns.
I actually don’t like for setting http code
If setting 200 in case of a Hessian fault is a must, why don't we do it in
the HessianMessageFormatter? My be I'm missing something :)
Thanks,
Supun.
On Sun, Mar 15, 2009 at 4:05 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
Just throwing an idea into the discussion: What about an Axis2
. Message formatters should be protocol independent (even if they
have access to the full MessageContext).
2. Probably when the message formatter is invoked, it is already too
late to set the HTTP status code.
Andreas
On Sun, Mar 15, 2009 at 16:17, Supun Kamburugamuva supu...@gmail.com
wrote
[
https://issues.apache.org/jira/browse/SYNAPSE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12682058#action_12682058
]
Supun Kamburugamuva commented on SYNAPSE-383:
-
As for my understanding, mod_jk
[
https://issues.apache.org/jira/browse/SYNAPSE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680806#action_12680806
]
Supun Kamburugamuva commented on SYNAPSE-383:
-
AFAIK AJP allows Tomcat
Hi all,
There are two files with the same name with a one capital letter different.
Because of this I cannot get a SVN update in Windows.
Regards,
Supun.
--
Software Engineer, WSO2 Inc
http://wso2.org
Web Services with Axis2/C http://wsaxc.blospot.com
201 - 299 of 299 matches
Mail list logo
