Hi,
The JavaScript execution in Synapse is performed via Rhino which has the
built in support for E4X. The Rhino implementation, however, does not
support direct mapping between Axiom elements and E4X objects. If such
mapping is enabled then we will be able to achieve better performance
and e
, and
any performance improvement will be very welcome.
Paul
On Mon, Jun 30, 2008 at 6:23 AM, Saliya Ekanayake <[EMAIL PROTECTED]> wrote:
Hi,
The JavaScript execution in Synapse is performed via Rhino which has the
built in support for E4X. The Rhino implementation, however, does not
sup
+1 for making Azeez a committer
Thanks
Saliya
Ruwan Linton wrote:
Folks,
Azeez has been contributing to the Apache Synapse for quite a while
now, and has been contributed a number of fixes and improvements to
the load balancing and clustering sections of synapse, including the
documents and
Hi all,
I am bit new to the script mediator. The synapse configuration language
mentions that we can define the which function to be executed in the
script if the script already exists (i.e. referred by a key). The script
can also be inlined according to the document, but in this case it
does
functions.. we also need someone to take the Script mediator to
support JDK 1.6 :-) !
asankha
Saliya Ekanayake wrote:
Hi all,
I am bit new to the script mediator. The synapse configuration
language mentions that we can define the which function to be
executed in the script
Agreeing with Eric and Ruwan, Synapse provides very easy method to do
remote debugging. Just use the -xdebug option and that's it. Use the
default configuration of the IDE altering just the port to 8000 and it
will get attached.
Run/Debug on Synapse code from the IDE is useful when you want to
Charith,
Have a look at [1] for a sample scenario with SMS and [2] for some
insight into sending SMS based on XML. IMHO I guess it would be nice to
have application level reliability in the case of notifying a user on an
event.
[1]
http://www.pymma.com/eng/content/download/620/3501/file/Soa
Hi,
At present Synapse may fail due to dangling references. As an example
consider a proxy service which refers to a sequence. If the sequence
definition is not there it will be a dangling reference and Synapse will
fail to mediate properly.
The following items are the possible items on whic
Hi all,
I have encountered two issues with sample 256 - using mail transport with
Synapse.
1. The configuration is wrong as it simply sends the response back to the
same mail address. Then, Synapse will again send that response mail back to
the service thinking it is a request.
2. When retrievin
"Unexpected character" (Woodstock 3.2.4: BasicStreamReader: line
2047).
Thanks,
Saliya
On Mon, May 4, 2009 at 10:22 AM, Saliya Ekanayake wrote:
> Hi all,
>
> I have encountered two issues with sample 256 - using mail transport with
> Synapse.
>
> 1. The configuration
recipient (the
configuration simply checks for the "from" address and send the
reply). So in fact I think it's not an error.
Thanks,
Saliya
On Mon, May 4, 2009 at 11:41 AM, Saliya Ekanayake wrote:
> Regarding issue 2, I think the reason is having a wrong input stream
I am using the snapshot.
thanks,
Saliya
On Mon, May 4, 2009 at 1:13 PM, Andreas Veithen
wrote:
> Saliya,
>
> Can you please tell us the version of Synapse you are using?
>
> Andreas
>
> On Mon, May 4, 2009 at 08:45, Saliya Ekanayake wrote:
>> Hi,
>>
>> I
e content type of the attachment will depend on the email
> client or operation system that is used.
>
> - Play with the transport.mail.ContentType property to override the
> content type of the message.
>
> Andreas
>
> On Mon, May 4, 2009 at 09:53, Saliya Ekanayake wrote:
>
wrote:
> Saliya,
>
> Did you try setting the transport.mail.ContentType property in the
> plain text case?
>
> Andreas
>
> On Fri, May 22, 2009 at 11:44, Saliya Ekanayake wrote:
>> Hi Andreas,
>>
>> I tried the suggested approach, yet was unsuccessful. In both plain
stribution (to be fixed).
Aha! this may have been the issue for getting a null subject for mail messages.
Thanks,
Saliya
>
> Andreas
>
> On Fri, May 22, 2009 at 20:20, Saliya Ekanayake wrote:
>> Hi,
>>
>> I didn't specifically set it. Anyway, while debugging I
Hi,
Yep, things worked out fine when I remove the geronimo jars.
Thanks for the support.
Saliya
On Mon, May 25, 2009 at 9:54 AM, Saliya Ekanayake wrote:
> Andreas,
>
> Thank you for the quick response and resolution. I will test this and confirm.
>
> On Sat, May 23, 2009 at 11
t;> WSO2 Inc.; http://wso2.org
>>>> email: ru...@wso2.com; cell: +94 77 341 3097
>>>> blog: http://ruwansblog.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.org
>>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>
>>
>
>
> --
> Ruwan Linton
> Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
--
Saliya Ekanayake
Software Engineer, WSO2 Inc. (http://www.wso2.com)
Apache foundation the rights to use the code).. then one of the comitters of
> the relevant project (Synapse, Axiom etc) will apply the patch to the
> codebase
>
> cheers
> asankha
>
> --
> Asankha C. Perera
> AdroitLogic, http://adroitlogic.org
> http://esbmagic.blogspot.com
>
>
>
--
Saliya Ekanayake
http://www.esaliya.blogspot.com
http://www.esaliya.wordpress.com
t; Thanks for pointing this out. It saves making a change to Axis2/Axiom.
>>
>> Congrats on being made a committer!
>>
>> Regards,
>> Bill
>>
>>
>> On Thu, Jun 11, 2009 at 6:42 AM, Saliya Ekanayake wrote:
>>
>>>
>>> Hi Bill,
gt; To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
> > For additional commands, e-mail: dev-h...@synapse.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
> For additional commands, e-mail: dev-h...@synapse.apache.org
>
>
--
Saliya Ekanayake
http://www.esaliya.blogspot.com
http://www.esaliya.wordpress.com
xpath = new AXIOMXPath("//hello/something");
> OMElement node = (OMElement) xpath.selectSingleNode(root);
> System.out.println(node == null);
> if (node != null) {
> System.out.println(node.getText());
> }
>
>Output
>
n't work. So my idea is to allow the endpoints to use an
> expression to pick the endpoint address.
>
> This may be valid or I might be missing something :). Your comments are
> welcome.
>
> Thanks,
> Supun..
>
> --
> Software Engineer, WSO2 Inc
> http
>> https://issues.apache.org/jira/browse/SYNAPSE-695
>>
>> Here is my +1 for the Heshan's committorship.
>>
>>
> +1
>
> thanks,
> Charith
>
>> Thanks,
>> Supun..
>>
>> ---------
>> To unsubscribe, e-mail: dev-unsub
[
https://issues.apache.org/jira/browse/SYNAPSE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saliya Ekanayake updated SYNAPSE-392:
-
Attachment: 20080707_fix.patch
The patch contains the fix to the issue raised here
Reporter: Saliya Ekanayake
If FORCE_HTTP_1.0 parameter is used in synapse.xml, the getRequest() method of
the org.apache.synapse.transport.nhttp.Axis2HttpRequest class will serialize
the underlying stream in order to find the content length of the payload. This
however, consumes the stream as well
[
https://issues.apache.org/jira/browse/SYNAPSE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saliya Ekanayake updated SYNAPSE-392:
-
Attachment: 20080724_fix.patch
The file here contains the fix for the next issue raised
Improve Synapse Memory Footprint under HTTP 1.0
---
Key: SYNAPSE-408
URL: https://issues.apache.org/jira/browse/SYNAPSE-408
Project: Synapse
Issue Type: Improvement
Reporter: Saliya
[
https://issues.apache.org/jira/browse/SYNAPSE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saliya Ekanayake updated SYNAPSE-408:
-
Priority: Minor (was: Major)
> Improve Synapse Memory Footprint under HTTP
[
https://issues.apache.org/jira/browse/SYNAPSE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617702#action_12617702
]
Saliya Ekanayake commented on SYNAPSE-408:
--
The alternative approach you
[
https://issues.apache.org/jira/browse/SYNAPSE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saliya Ekanayake updated SYNAPSE-412:
-
Attachment: 20080729_fix.patch
This contains the fix for the issue raised here.
Thanks
Reporter: Saliya Ekanayake
Priority: Minor
Attachments: 20080729_fix.patch
A proxy service in Synapse (say, myproxy) can be accessed via an HTTP GET call.
This, however, requires the user to type in the operation name after the proxy
name (e.g. http://localhost:8280/services
[
https://issues.apache.org/jira/browse/SYNAPSE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618957#action_12618957
]
Saliya Ekanayake commented on SYNAPSE-393:
--
I tried to recreate your issue
[
https://issues.apache.org/jira/browse/SYNAPSE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618961#action_12618961
]
Saliya Ekanayake commented on SYNAPSE-365:
--
Hi Keith,
This issue is now f
[
https://issues.apache.org/jira/browse/SYNAPSE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saliya Ekanayake reopened SYNAPSE-392:
--
The latest patch is still not applied to the code base.
Thanks,
Saliya
> An I/O er
[
https://issues.apache.org/jira/browse/SYNAPSE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619341#action_12619341
]
Saliya Ekanayake commented on SYNAPSE-408:
--
It seems that the latest patc
Dependency Management in Synapse
Key: SYNAPSE-532
URL: https://issues.apache.org/jira/browse/SYNAPSE-532
Project: Synapse
Issue Type: New Feature
Components: Core
Reporter: Saliya
[
https://issues.apache.org/jira/browse/SYNAPSE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saliya Ekanayake updated SYNAPSE-532:
-
Attachment: diag2.jpeg
diag1.jpeg
Proposed Design for Synapse
Inline schema definitions get lost
--
Key: SYNAPSE-535
URL: https://issues.apache.org/jira/browse/SYNAPSE-535
Project: Synapse
Issue Type: Bug
Components: Core
Reporter: Saliya Ekanayake
[
https://issues.apache.org/jira/browse/SYNAPSE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701110#action_12701110
]
Saliya Ekanayake commented on SYNAPSE-535:
--
I was able to debug through
Project: Synapse
Issue Type: Bug
Reporter: Saliya Ekanayake
Attachments: ep_null_check.patch
In SynapseConfiguration class under init() method it tries to initialize the
inline target endpoint of proxy services without checking the presence of such
endpoint
[
https://issues.apache.org/jira/browse/SYNAPSE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saliya Ekanayake updated SYNAPSE-538:
-
Attachment: ep_null_check.patch
The patch for the issue raised here.
Thanks,
Saliya
[
https://issues.apache.org/jira/browse/SYNAPSE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saliya Ekanayake resolved SYNAPSE-535.
--
Resolution: Fixed
I am resolving this since it's not a bug with Synapse rat
42 matches
Mail list logo
