[Architecture] WSO2 Enterprise Integrator 6.1.1-update9 Released!
Hi all, The WSO2 Integration team is pleased to announce the release of Enterprise Integrator 6.1.1-update9. It is available for download from here <https://github.com/wso2/product-ei/releases/download/v6.1.1-update9/wso2ei-6.1.1-update9.zip> . *Tasks/Bug Fixes and Improvements* https://github.com/wso2/product-ei/issues?&q=is%3Aissue%20milestone%3A6.1.1-update9%20is%3Aclosed *List of Open Issues* https://wso2.org/jira/issues/?filter=13994 https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue *Mailing Lists* Join our mailing lists and correspond with the developers directly. Developer List : d...@wso2.org | Subscribe | Mail Archive WSO2 Architecture List: architecture@wso2.org User Forum : StackOverflow *How To Contribute* Your feedback is most welcome! *Reporting Issues* We encourage you to report issues, improvements and feature requests regarding WSO2 Integrator through WSO2 EI GIT Issues. ~ The WSO2 Integration Team ~ -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] AS4 support in EI
supported. >>>>>>>>- Only the *required* P-Mode Parameters are supported >>>>>>>>(According to [1]). >>>>>>>> >>>>>>>> >>>>>>>> *Supported P-Mode Parameters* >>>>>>>> >>>>>>>> >>>>>>>> PMode Parameter >>>>>>>> >>>>>>>> Supported or not >>>>>>>> >>>>>>>> PMode.ID >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Agreement >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.MEP >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.MEPbinding >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Initiator.Party >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Initiator.Role >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Initiator.Authorization.username >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Initiator.Authorization.password >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Responder.Party >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Responder.Role >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Responder.Authorization.username >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Responder.Authorization.password >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Protocol.Address >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Protocol.SOAPVersion >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.BusinessInfo.Service >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.BusinessInfo.Action >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.BusinessInfo.Properties[] >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.BusinessInfo.PayloadProfile[] >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.BusinessInfo.PayloadProfile.maxSize >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.ErrorHandling.Report.SenderErrorsTo >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.ErrorHandling.Report.ReceiverErrorsTo >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.ErrorHandling.Report.AsResponse >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.ErrorHandling.Report.ProcessErrorNotifyConsumer >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.ErrorHandling.Report.ProcessErrorNotifyProducer >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.ErrorHandling.Report.DeliveryFailuresNotifyProducer >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Security.WSSVersion >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Security.X509.Sign >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Security. X509.Encryption >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Security.UsernameToken >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Security.PModeAuthorize >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.Security.SendReceipt >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.Security.SendReceipt.NonRepudiation >>>>>>>> >>>>>>>> false >>>>>>>> >>>>>>>> PMode.PayloadService.CompressionType >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.ReceptionAwareness >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> PMode.ReceptionAwareness.Retry.Parameters >>>>>>>> >>>>>>>> true >>>>>>>> >>>>>>>> AS4 support in EI, will be introduced as a separate transport. >>>>>>>> >>>>>>>> [1] http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/ >>>>>>>> AS4-profile/v1.0/os/AS4-profile-v1.0-os.html >>>>>>>> [2] https://github.com/manoramahp/org.wso2.carbon.mediator.as4 >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Manorama >>>>>>>> -- >>>>>>>> Manorama Perera >>>>>>>> Software Engineer >>>>>>>> WSO2, Inc.; http://wso2.com/ >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Manorama Perera >>>>>>> Software Engineer >>>>>>> WSO2, Inc.; http://wso2.com/ >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Manorama Perera >>>>>> Software Engineer >>>>>> WSO2, Inc.; http://wso2.com/ >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Manorama Perera >>>>> Software Engineer >>>>> WSO2, Inc.; http://wso2.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Best Regards, >>>> >>>> Malaka Silva >>>> Associate Director / Architect >>>> M: +94 777 219 791 <+94%2077%20721%209791> >>>> Tel : 94 11 214 5345 >>>> Fax :94 11 2145300 <011%202%20145300> >>>> Skype : malaka.sampath.silva >>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>> Blog : http://mrmalakasilva.blogspot.com/ >>>> >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> https://wso2.com/signature >>>> http://www.wso2.com/about/team/malaka-silva/ >>>> <http://wso2.com/about/team/malaka-silva/> >>>> https://store.wso2.com/store/ >>>> >>>> Don't make Trees rare, we should keep them with care >>>> >>> >>> >>> >>> -- >>> Manorama Perera >>> Software Engineer >>> WSO2, Inc.; http://wso2.com/ >>> >> >> >> >> -- >> Kasun Indrasiri >> Director - Integration Architecture >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +1 650 450 2293 <(650)%20450-2293> >> Blog : http://kasunpanorama.blogspot.com/ >> > > > > -- > Manorama Perera > Software Engineer > WSO2, Inc.; http://wso2.com/ > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines
Hi Rasika,
We use the same implementation and use javax.script.*; even with the bsf
and bsf also provide the rhino16 engine. In script mediator we need to use
the Scriptable interface and that interface package name is different in
JDK7 and JDK8 when the script is executed. and also internal classes as the
implementation in JDK. There is no interface in javax.script to cast that
objects. In script mediator we use custom class binding with script and
that is the hard part we can handle. Please refer the setPayloadXML(Object
payload) in [1]. That is why we decided not to change the script engine and
used the same rhino16 engine. Then the script mediator behaviour is same in
any JDK version.
[1]
https://github.com/wso2/wso2-synapse/blob/master/modules/extensions/src/main/java/org/apache/synapse/mediators/bsf/ScriptMessageContext.java
Thanks,
Nuwanw
On Thu, May 5, 2016 at 11:49 AM, Rasika Perera wrote:
> @Nuwan and All,
>
> I am not very familiar with BSF. Besides Apache BSF does not appear to
> have active development. My suggestion is we should go with Scripting API(
> JSR223). This javax.script.* API is available on runtime(rt.jar).
>
> Any scripting language which implements it, we can support through third
> part libraries. List of scripting engines are listed in [1].
>
> How we invoke a particular scripting engine through Scripting API is;
>
> import javax.script.*;
>
> ScriptEngine nashornEngine = new
> ScriptEngineManager().getEngineByName("javascript");
> ScriptEngine groovyEngine = new
> ScriptEngineManager().getEngineByName("groovy");
>
>
> Only *difference* about Nashorn is that it available as an extension on
> JRE by default.
>
> @Ruwan,
>
> Please find inline comments.
>
> 1. This will cause any bugs in JS engine, or integration, to be reported
>> as WSO2 product issue. e.g. Historically similar integrations cause bugs
>> like [1] yield OOM in applications.
>
> IMO I think it doesn't matter whether internal or external library, when
> someone lacks parsing error trace it will always reported as a WSO2 product
> issue.
>
> 2. We can upgrade the JS library at our own discretion, for performance or
>> bugfixes if we use a library outside.
>
> Yes. This can be done for any JSR223 implementation.
>
> Incase of Nashorn vs. Rhino; Nashorn is more powerfull and fills the lack
> of security in Rhino.
> Nashorn brings a 2 to 10x performance boost over the former Rhino
> implementation, although it is still somewhat short of V8, the engine
> inside Chrome and Node.js. Please refer [2] for more details on comparison.
>
>
> [1] https://java.net/projects/scripting/sources/svn/show/trunk/engines
> [2]
> https://www.infoq.com/articles/nashorn
>
> On Thu, May 5, 2016 at 10:00 AM, Nuwan Wimalasekara
> wrote:
>
>> Hi Manuranga,
>>
>> if the script engine is loaded from bsf-all(rhino16),
>> org.mozilla.javascript.Context will be used. But script engine is loaded
>> from JDK, sun.org.mozilla.javascript.internal.Context is used and those are
>> available in JDK itself. Nashorn or Rhino7 does not depend any third part
>> library. It load all required classes from JDK it self. and also If we use
>> JDK to load the script engine, behaviour may also be changed according to
>> JDK we are running.
>>
>> Thanks,
>> Nuwanw
>>
>> On Wed, May 4, 2016 at 8:47 PM, Manuranga Perera wrote:
>>
>>> Hi Nuwan,
>>> Maybe `org.mozilla.javascript.Context` is the one you are looking for,
>>> not `sun.org.mozilla.javascript.internal.Context`?
>>>
>>> On Wed, May 4, 2016 at 11:13 AM, Nuwan Wimalasekara
>>> wrote:
>>>
>>>> Hi Manuranga and Rasika,
>>>>
>>>> Thanks for the reply. But this is a different one. Below are the
>>>> classes we can not use in our class since those are internal classes in JDK
>>>> and we can not compile a class with below imports since those are only
>>>> available in runtime.
>>>>
>>>> import sun.org.mozilla.javascript.internal.Context;
>>>> import sun.org.mozilla.javascript.internal.Scriptable;
>>>> import sun.org.mozilla.javascript.internal.ScriptableObject;
>>>> import sun.org.mozilla.javascript.internal.xml.XMLObject;
>>>>
>>>> Thanks,
>>>> Nuwanw
>>>>
>>>> On Wed, May 4, 2016 at 8:30 PM, Rasika Perera wrote:
>>>>
>>>>> Hi Nuwan and all,
>>>>>
>>>>> We also faced the same issue when accessing Nashorn on OSGi
>>>>> environment. To overcome the class-loading issues; you can modify system
>
Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines
Hi Manuranga,
if the script engine is loaded from bsf-all(rhino16),
org.mozilla.javascript.Context will be used. But script engine is loaded
from JDK, sun.org.mozilla.javascript.internal.Context is used and those are
available in JDK itself. Nashorn or Rhino7 does not depend any third part
library. It load all required classes from JDK it self. and also If we use
JDK to load the script engine, behaviour may also be changed according to
JDK we are running.
Thanks,
Nuwanw
On Wed, May 4, 2016 at 8:47 PM, Manuranga Perera wrote:
> Hi Nuwan,
> Maybe `org.mozilla.javascript.Context` is the one you are looking for,
> not `sun.org.mozilla.javascript.internal.Context`?
>
> On Wed, May 4, 2016 at 11:13 AM, Nuwan Wimalasekara
> wrote:
>
>> Hi Manuranga and Rasika,
>>
>> Thanks for the reply. But this is a different one. Below are the classes
>> we can not use in our class since those are internal classes in JDK and we
>> can not compile a class with below imports since those are only available
>> in runtime.
>>
>> import sun.org.mozilla.javascript.internal.Context;
>> import sun.org.mozilla.javascript.internal.Scriptable;
>> import sun.org.mozilla.javascript.internal.ScriptableObject;
>> import sun.org.mozilla.javascript.internal.xml.XMLObject;
>>
>> Thanks,
>> Nuwanw
>>
>> On Wed, May 4, 2016 at 8:30 PM, Rasika Perera wrote:
>>
>>> Hi Nuwan and all,
>>>
>>> We also faced the same issue when accessing Nashorn on OSGi environment.
>>> To overcome the class-loading issues; you can modify system bundle's
>>> package exports to include the Nashorn scripting API package(using Fragment
>>> Hosts approach suggested in [1]).
>>>
>>> Please refer "nashorn-osgi-fragment" module [2] in UUF.
>>>
>>> system.bundle;extension:=framework
>>> jdk.nashorn.api.scripting;
>>> version="${nashorn-osgi-fragment.version}"
>>>
>>> Thanks
>>>
>>> [1] https://github.com/mszu/nashorn-scripting-api-fragment
>>> [2]
>>> https://github.com/wso2/carbon-uuf/blob/master/nashorn-osgi-fragment/pom.xml
>>>
>>> On Wed, May 4, 2016 at 8:04 PM, Manuranga Perera wrote:
>>>
>>>> Hi Nuwan,
>>>> Is the limitation you are facing due to OSGi level class def not found
>>>> exceptions? We faced something slimier and that was due to Nashorn classes
>>>> not been exposed via OSGi. We created a fragment bundle for the system
>>>> bundle to solve this. Please contact Rasika if that's the case.
>>>>
>>>
>>>
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> M: +94 71 680 9060 E: rasi...@wso2.com
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines
Hi Manuranga and Rasika,
Thanks for the reply. But this is a different one. Below are the classes we
can not use in our class since those are internal classes in JDK and we can
not compile a class with below imports since those are only available in
runtime.
import sun.org.mozilla.javascript.internal.Context;
import sun.org.mozilla.javascript.internal.Scriptable;
import sun.org.mozilla.javascript.internal.ScriptableObject;
import sun.org.mozilla.javascript.internal.xml.XMLObject;
Thanks,
Nuwanw
On Wed, May 4, 2016 at 8:30 PM, Rasika Perera wrote:
> Hi Nuwan and all,
>
> We also faced the same issue when accessing Nashorn on OSGi environment.
> To overcome the class-loading issues; you can modify system bundle's
> package exports to include the Nashorn scripting API package(using Fragment
> Hosts approach suggested in [1]).
>
> Please refer "nashorn-osgi-fragment" module [2] in UUF.
>
> system.bundle;extension:=framework
> jdk.nashorn.api.scripting;
> version="${nashorn-osgi-fragment.version}"
>
> Thanks
>
> [1] https://github.com/mszu/nashorn-scripting-api-fragment
> [2]
> https://github.com/wso2/carbon-uuf/blob/master/nashorn-osgi-fragment/pom.xml
>
> On Wed, May 4, 2016 at 8:04 PM, Manuranga Perera wrote:
>
>> Hi Nuwan,
>> Is the limitation you are facing due to OSGi level class def not found
>> exceptions? We faced something slimier and that was due to Nashorn classes
>> not been exposed via OSGi. We created a fragment bundle for the system
>> bundle to solve this. Please contact Rasika if that's the case.
>>
>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Replacing current JS engine used in script mediator with new rhino and nashorn script engines
>>>>>>> M: +94 777 219 791 >>>>>>> Tel : 94 11 214 5345 >>>>>>> Fax :94 11 2145300 >>>>>>> Skype : malaka.sampath.silva >>>>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>>>>> Blog : http://mrmalakasilva.blogspot.com/ >>>>>>> >>>>>>> WSO2, Inc. >>>>>>> lean . enterprise . middleware >>>>>>> http://www.wso2.com/ >>>>>>> http://www.wso2.com/about/team/malaka-silva/ >>>>>>> <http://wso2.com/about/team/malaka-silva/> >>>>>>> https://store.wso2.com/store/ >>>>>>> >>>>>>> Save a tree -Conserve nature & Save the world for your future. Print >>>>>>> this email only if it is absolutely necessary. >>>>>>> >>>>>>> ___ >>>>>>> Architecture mailing list >>>>>>> Architecture@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanjikumaran Sivajothy >>>>>> *Associate Technical Lead* >>>>>> *WSO2 Inc. http://wso2.com <http://wso2.com/>* >>>>>> *+1-925-464-6816* >>>>>> [image: Facebook] <https://www.facebook.com/vanjikumaran> [image: >>>>>> Twitter] <https://twitter.com/vanjikumaran> [image: LinkedIn] >>>>>> <http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> [image: >>>>>> Blogger] <http://vanjikumaran.blogspot.com/> [image: SlideShare] >>>>>> <http://www.slideshare.net/vanjikumaran> >>>>>> >>>>>> This communication may contain privileged or other >>>>>> confidential information and is intended exclusively for the addressee/s. >>>>>> If you are not the intended recipient/s, or believe that you may >>>>>> have received this communication in error, please reply to the >>>>>> sender indicating that fact and delete the copy you received and in >>>>>> addition, you should not print, copy, re-transmit, disseminate, or >>>>>> otherwise use the information contained in this communication. >>>>>> Internet communications cannot be guaranteed to be timely, secure, error >>>>>> or virus-free. The sender does not accept liability for any errors >>>>>> or omissions >>>>>> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> Architecture@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Prabath Ariyarathna* >>>>> >>>>> *Associate Technical Lead* >>>>> >>>>> *WSO2, Inc. * >>>>> >>>>> *lean . enterprise . middleware * >>>>> >>>>> >>>>> *Email: prabat...@wso2.com * >>>>> >>>>> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>* >>>>> >>>>> *Flicker : https://www.flickr.com/photos/47759189@N08 >>>>> <https://www.flickr.com/photos/47759189@N08>* >>>>> >>>>> *Mobile: +94 77 699 4730 * >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> With regards, >> *Manu*ranga Perera. >> >> phone : 071 7 70 20 50 >> mail : m...@wso2.com >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, CEO & Chief Architect; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345) > x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 > blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva > Lean . Enterprise . Middleware > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
