Re: [Dev] [PRODUCT_EI] Class Loading issue with latest andes client

[Jagath Sisirakumara Ariyarathne]

Hi All,

Issue occurs with org.apache.commans.lang.* export at [1]. It should be an
import instead of export. Issue will be fixed in next andes release.

[1] - https://github.com/wso2/andes/blob/master/modules/orbit/
andes-client/pom.xml#L104

On Sun, Apr 2, 2017 at 4:39 PM, Hasitha Amal De Silva 
wrote:

> + We also tested and verified that Object messages can be produced and
> consumed fine with the current andes client (without fronting with the
> ESB).
>
> Thanks
>
> On Sun, Apr 2, 2017 at 4:35 PM, Hasitha Amal De Silva 
> wrote:
>
>> Hi Vijitha,
>>
>> We found a similar issue reported at [1], in which synapse-core is unable
>> to load a class from CacheMediator. It seems the fix here was to remove the
>> "resolution:=optional" line at the OSGI Import-Package section in the pom
>> of CacheMediator (refer [2]).
>>
>> I tried the same fix at the synapse-core and saw that the error does not
>> occur anymore. However, I'm still not sure how this scenario works with the
>> old andes-client. Maybe the carbon-kernel upgrade handles optional
>> resolutions in a different way ?
>>
>> @PrabathAr - any clue on this ?
>>
>> [1] : https://wso2.org/jira/browse/ESBJAVA-4878
>> [2] : https://github.com/wso2/carbon-mediation/pull/745/files#
>> diff-4873f9136db2279e0714fbf75dfbbd1aL51
>>
>> Thanks
>>
>> On Sat, Apr 1, 2017 at 5:15 PM, Indika Sampath  wrote:
>>
>>> I was able to reproduce the above issue in ESB 5.0.0 with
>>> andes-client-3.2.6.jar (beta release) as well. Exception says
>>> org.apache.synapse.message.store.impl.commons.StorableMessage cannot be
>>> found by andes_client. Basically what we getting is ByteBuffer as a message
>>> and do not maintain any specific format. I wonder the issue regard to
>>> kernel change (4.4.15) in the latest version. We need to further look into
>>> the issue to identify the exact root cause. Public JIRA[1] create to track
>>> down the issue.
>>>
>>> [1] https://wso2.org/jira/browse/MB-1923
>>>
>>> On Sat, Apr 1, 2017 at 10:37 AM, Nandika Jayawardana 
>>> wrote:
>>>
 Adding DEV

 Nandika

 On Fri, Mar 31, 2017 at 9:51 PM, Vijitha Ekanayake 
 wrote:

> Hi All,
>
> We Observe class loading issue with latest andes client (3.2.4) in
> MSMP scenarios. The issue occurs while consuming message from the
> message store where it continuously prints message[1]. I change the code a
> bit and got exact stack trace [2].It seems to be OSGI issue and this issue
> isn't there if we use previous andes client version(3.1.4).
>
> Did anyone come across this kind of OSGI issue before?
>
>
> [1].
>
> [2017-03-31 20:57:01,076] [EI-Core] ERROR - JmsConsumer
> [PaymentRequestJMSMessageStore-C-1] cannot receive message from
> store. Error:Could not deserialize message: 
> java.lang.ClassNotFoundException:
> org.apache.synapse.message.store.impl.commons.StorableMessage cannot
> be found by andes_client_3.2.4_1.0.0
>
> [2].
> javax.jms.MessageFormatException: Could not deserialize message:
> java.lang.ClassNotFoundException: org.apache.synapse.message.sto
> re.impl.commons.StorableMessage cannot be found by
> andes_client_3.2.4_1.0.0
> at org.wso2.andes.client.message.JMSObjectMessage.getObject(JMS
> ObjectMessage.java:154)
> at org.apache.synapse.message.store.impl.jms.JmsConsumer.receiv
> e(JmsConsumer.java:99)
> at org.apache.synapse.message.processor.impl.sampler.SamplingSe
> rvice.fetch(SamplingService.java:188)
> at org.apache.synapse.message.processor.impl.sampler.SamplingSe
> rvice.execute(SamplingService.java:120)
> at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAd
> apter.java:98)
> at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute
> (TaskQuartzJobAdapter.java:67)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executor
> s.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> Executor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.synapse.message.store.impl.commons.StorableMessage cannot
> be found by andes_client_3.2.4_1.0.0
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInter
> nal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(Bund
> leLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(Bund
> leLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa
> dClass(DefaultClassLoader.java:107)
> at 

[Dev] WSO2 Committers += Prabushi Samarakoon

[Jagath Sisirakumara Ariyarathne]

Hi All,

It's my pleasure to welcome Prabushi Samarakoon as a WSO2 Committer.

Prabushi has been a valuable contributor to WSO2 Dashboard Server and
Integration products. In recognition of her contribution, dedication and
commitment she has being voted as a WSO2 committer.

Prabushi, welcome aboard and keep up the good work.!

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Transform an xml with payload factory and xpath

[Jagath Sisirakumara Ariyarathne]

Hi Bhathiya,

If the number of  elements are static, we can use below config.



http://service.ws.um.carbon.wso2.org;>
$1
$2



http://service.ws.um.carbon.wso2.org"/>
http://service.ws.um.carbon.wso2.org"/>



Otherwise you might need to use XSLT transformation.

Thanks.

On Sun, Oct 30, 2016 at 11:33 PM, Bhathiya Jayasekara 
wrote:

> Hi devs,
>
> I have below XML in the message context.
>
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>   <*ns:getUserListOfRoleResponse* xmlns:ns="http://service.ws.
> um.carbon.wso2.org">
>  usersx
>  doctor
>   
>
> 
>
> Is it possible to transform this to below one, just with a payload factory
> (and xpath)?
>
>   <*ns:results* xmlns:ns="http://service.ws.um.carbon.wso2.org;>
>  usersx
>  doctor
>   
>
> Basically what I tried is this with different xpaths, but none of them
> gave me the expected output.
>
>  
> 
>$1
> 
> 
>http://service.ws.um.carbon.wso2.org;
> evaluator="xml" *expression="//ns:getUserListOfRoleResponse/node()"*/>
> 
>  
>
> Appreciate your help.
>
> Thanks,
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

[Jagath Sisirakumara Ariyarathne]

Hi,

While implementing swagger definition for uri-template based APIs, we have
following problem.

If we have a template like "/view/{symbol}", we need to define "symbol" as
a parameter in swagger definition. According to the swagger spec for
parameters[1], if it is a query or path parameter, then it is required to
have a type (string, number etc) for this parameter. But this information
is not available in existing synapse configurations of APIs. The possible
option is to provide all parameters as "string" as Maheeka mentioned
earlier.

Appreciate any thoughts on this.

[1] - http://swagger.io/specification/#parameterObject

Thanks.

On Tue, Sep 27, 2016 at 5:38 AM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi All,
>
> I have completed initial implementation for url-mapping based APIs.
> Attached sample API and its definitions. I am further working on supporting
> uri-templates based definitions.
>
> Thanks.
>
> On Thu, Sep 22, 2016 at 2:09 PM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> Hi,
>>
>> In this particular implementation for Integration Cloud, we planned to go
>> with an extension which uses existing information in synapse configurations
>> without updating synapse code base. Therefore as Maheeka mentioned in [1],
>> we are going to provide limited information at initial phase. But in long
>> run, we need to extend this to store all required API definitions in
>> synapse configurations.
>>
>> [1] - https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f233f2
>>
>> Thanks.
>>
>> On Thu, Sep 22, 2016 at 8:23 AM, Joseph Fonseka <jos...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> On Tue, Sep 20, 2016 at 4:18 PM, Maheeka Jayasuriya <mahe...@wso2.com>
>>> wrote:
>>>
>>>>
>>>> Please note these changes were done based on the level of information
>>>> we have on the API by referring to it's configuration. For example, we do
>>>> not have a way of determining the request format or uri parameter types and
>>>> content-types of the API. This will require further digging and analyzing
>>>> on the configuration.
>>>>
>>>
>>> Have you consider adding additional information as annotations/notes in
>>> the config. AFAIK we do not have a config to add annotations so currently
>>> we can define them as properties but going forward may be we can add some
>>> way to annotate synapse.
>>>
>>> In the longer run mostly synapse APIs will be generated out of swagger
>>> definitions thus having the ability to contain all the API definition
>>> information in the synapse file would be important.
>>>
>>> Thanks
>>> Jo
>>>
>>>
>>>>
>>>> Find the diff of these changes done to the Swagger definition at [4]
>>>>
>>>> To get the required information from the Rest API configuration we can
>>>> invoke RestApiAdminServices's getApiByName operation which returns the
>>>> following response [5] for an API created that has the PetStore resources.
>>>> We can identify the methods and uri-template and mappings from this
>>>> response.
>>>>
>>>> Please let know your thoughts.
>>>>
>>>> Thanks,
>>>> Maheeka
>>>>
>>>> [1] http://petstore.swagger.io/#/pet
>>>> [2] https://gist.github.com/maheeka/4eaedd2e2e0765959a4166865bf9adf9
>>>> [3] https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f233f2
>>>> [4] https://www.diffchecker.com/xEu0NSNz
>>>> [5] http://schemas.
>>>> xmlsoap.org/soap/envelope/">
>>>>
>>>>   http://org.apache.axis2/xsd;>
>>>>  http://api.rest.carbon.wso2.org/xsd; xmlns:xsi="http://www.w3.org/2
>>>> 001/XMLSchema-instance">
>>>> 
>>>> /pet
>>>> PetstoreAPI.xml
>>>> 
>>>> false
>>>> PetstoreAPI
>>>> -1
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>POST
>>>>PUT
>>>>
>>>>
>>>>0
>>>>
>>>>/
>>>>
>

Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

[Jagath Sisirakumara Ariyarathne]

Hi All,

I have completed initial implementation for url-mapping based APIs.
Attached sample API and its definitions. I am further working on supporting
uri-templates based definitions.

Thanks.

On Thu, Sep 22, 2016 at 2:09 PM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi,
>
> In this particular implementation for Integration Cloud, we planned to go
> with an extension which uses existing information in synapse configurations
> without updating synapse code base. Therefore as Maheeka mentioned in [1],
> we are going to provide limited information at initial phase. But in long
> run, we need to extend this to store all required API definitions in
> synapse configurations.
>
> [1] - https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f233f2
>
> Thanks.
>
> On Thu, Sep 22, 2016 at 8:23 AM, Joseph Fonseka <jos...@wso2.com> wrote:
>
>> Hi
>>
>> On Tue, Sep 20, 2016 at 4:18 PM, Maheeka Jayasuriya <mahe...@wso2.com>
>> wrote:
>>
>>>
>>> Please note these changes were done based on the level of information we
>>> have on the API by referring to it's configuration. For example, we do not
>>> have a way of determining the request format or uri parameter types and
>>> content-types of the API. This will require further digging and analyzing
>>> on the configuration.
>>>
>>
>> Have you consider adding additional information as annotations/notes in
>> the config. AFAIK we do not have a config to add annotations so currently
>> we can define them as properties but going forward may be we can add some
>> way to annotate synapse.
>>
>> In the longer run mostly synapse APIs will be generated out of swagger
>> definitions thus having the ability to contain all the API definition
>> information in the synapse file would be important.
>>
>> Thanks
>> Jo
>>
>>
>>>
>>> Find the diff of these changes done to the Swagger definition at [4]
>>>
>>> To get the required information from the Rest API configuration we can
>>> invoke RestApiAdminServices's getApiByName operation which returns the
>>> following response [5] for an API created that has the PetStore resources.
>>> We can identify the methods and uri-template and mappings from this
>>> response.
>>>
>>> Please let know your thoughts.
>>>
>>> Thanks,
>>> Maheeka
>>>
>>> [1] http://petstore.swagger.io/#/pet
>>> [2] https://gist.github.com/maheeka/4eaedd2e2e0765959a4166865bf9adf9
>>> [3] https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f233f2
>>> [4] https://www.diffchecker.com/xEu0NSNz
>>> [5] http://schemas.
>>> xmlsoap.org/soap/envelope/">
>>>
>>>   http://org.apache.axis2/xsd;>
>>>  http://api.rest.carbon.wso2.org/xsd; xmlns:xsi="http://www.w3.org/2
>>> 001/XMLSchema-instance">
>>> 
>>> /pet
>>> PetstoreAPI.xml
>>> 
>>> false
>>> PetstoreAPI
>>> -1
>>> 
>>>
>>>
>>>
>>>
>>>
>>>POST
>>>PUT
>>>
>>>
>>>0
>>>
>>>/
>>>
>>> 
>>> 
>>>
>>>
>>>
>>>
>>>
>>>POST
>>>DELETE
>>>GET
>>>
>>>
>>>0
>>>/{petId}
>>>
>>>
>>> 
>>> false
>>> false
>>>  
>>>   
>>>
>>> 
>>>
>>>
>>> Thanks,
>>>
>>> Maheeka Jayasuriya
>>> Senior Software Engineer
>>> Mobile : +9450661
>>>
>>
>>
>>
>> --
>>
>> --
>> *Joseph Fonseka*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 772 512 430
>> skype: jpfonseka
>>
>> * <http://lk.linkedin.com/in/rumeshbandara>*
>>
>>
>
>
> --
> Jagath Ariyarathne
> Technical Lead
> WSO2 Inc.  http://wso2.com/
> Email: jaga...@wso2.com
> Mob  : +94 77 386 7048
> <http://wso2.com/signature>
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
<http://wso2.com/signature>


TestApi.json
Description: application/json


TestApi.yaml
Description: application/yaml

http://ws.apache.org/ns/synapse;
 name="TestApi"
 context="/t/abc.com/test"
 hostname="localhost"
 port="8280">
   
   
   

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

[Jagath Sisirakumara Ariyarathne]

Hi,

In this particular implementation for Integration Cloud, we planned to go
with an extension which uses existing information in synapse configurations
without updating synapse code base. Therefore as Maheeka mentioned in [1],
we are going to provide limited information at initial phase. But in long
run, we need to extend this to store all required API definitions in
synapse configurations.

[1] - https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f233f2

Thanks.

On Thu, Sep 22, 2016 at 8:23 AM, Joseph Fonseka  wrote:

> Hi
>
> On Tue, Sep 20, 2016 at 4:18 PM, Maheeka Jayasuriya 
> wrote:
>
>>
>> Please note these changes were done based on the level of information we
>> have on the API by referring to it's configuration. For example, we do not
>> have a way of determining the request format or uri parameter types and
>> content-types of the API. This will require further digging and analyzing
>> on the configuration.
>>
>
> Have you consider adding additional information as annotations/notes in
> the config. AFAIK we do not have a config to add annotations so currently
> we can define them as properties but going forward may be we can add some
> way to annotate synapse.
>
> In the longer run mostly synapse APIs will be generated out of swagger
> definitions thus having the ability to contain all the API definition
> information in the synapse file would be important.
>
> Thanks
> Jo
>
>
>>
>> Find the diff of these changes done to the Swagger definition at [4]
>>
>> To get the required information from the Rest API configuration we can
>> invoke RestApiAdminServices's getApiByName operation which returns the
>> following response [5] for an API created that has the PetStore resources.
>> We can identify the methods and uri-template and mappings from this
>> response.
>>
>> Please let know your thoughts.
>>
>> Thanks,
>> Maheeka
>>
>> [1] http://petstore.swagger.io/#/pet
>> [2] https://gist.github.com/maheeka/4eaedd2e2e0765959a4166865bf9adf9
>> [3] https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f233f2
>> [4] https://www.diffchecker.com/xEu0NSNz
>> [5] http://schemas.
>> xmlsoap.org/soap/envelope/">
>>
>>   http://org.apache.axis2/xsd;>
>>  http://api.rest.carbon.wso2.org/xsd; xmlns:xsi="http://www.w3.org/2
>> 001/XMLSchema-instance">
>> 
>> /pet
>> PetstoreAPI.xml
>> 
>> false
>> PetstoreAPI
>> -1
>> 
>>
>>
>>
>>
>>
>>POST
>>PUT
>>
>>
>>0
>>
>>/
>>
>> 
>> 
>>
>>
>>
>>
>>
>>POST
>>DELETE
>>GET
>>
>>
>>0
>>/{petId}
>>
>>
>> 
>> false
>> false
>>  
>>   
>>
>> 
>>
>>
>> Thanks,
>>
>> Maheeka Jayasuriya
>> Senior Software Engineer
>> Mobile : +9450661
>>
>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * *
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

[Jagath Sisirakumara Ariyarathne]

Hi All,

In addition to above, swagger definitions will be provided in json and yaml
formats. Initially it will be done for json. Definitions can be taken from
URLs which has swagger.json and swagger.yaml as query string.

Example:

API Name is SampleAPI

*Json format*
http://localhost:8280:/SampleAPI?swagger.json
http://localhost:8280:/t/abc.com/SampleAPI?swagger.json

*Yaml format*
http://localhost:8280:/SampleAPI?swagger.yaml
http://localhost:8280:/t/abc.com/SampleAPI?swagger.yaml

In order to generate these definition, we are planning to use two new
HttpGetProcessor implementations which can be configured in carbon.xml.

Thanks.

On Tue, Sep 20, 2016 at 4:18 PM, Maheeka Jayasuriya 
wrote:

> Hi all,
>
> We are researching on supporting Swagger definitions for REST APIs in ESB.
> This implementation is quite different from what APIM offers. APIM offers a
> Swagger to API configuration generation where as what we need to do here is
> API configuration to Swagger definition generation.
>
> As for the first iteration, I think we can focus on the minimum Swagger
> support where as main focus will be only on the HTTP verb and the
> uri-template or url-mapping.
>
> Following is what I tested to compose a minimal Swagger Definition. I
> started off from the Swagger Pet Store Sample [1] which was reduced to [2]
> and moved on to create [3]. This is IMO the minimum required of a Swagger
> Definition. We can improve from this, but for the time being this would
> suffice the requirement of Integration Cloud.
>
> Please note that I have made the following changes to the original Swagger
> definition of PetStore in order to achieve the final Swagger definition for
> ESB.
>   - Remove descriptions, summary, tags, operationId, schema, basepath,
> definitions and security elements
>   - accept and produce application/json and application/xml as default
> content types for all resources
>   - Include a default response code
>   - Add body as parameter for all POST and PUT operations in addition to
> the uri parameters
>   - All parameters are considered format binary and type String by default
>
> Please note these changes were done based on the level of information we
> have on the API by referring to it's configuration. For example, we do not
> have a way of determining the request format or uri parameter types and
> content-types of the API. This will require further digging and analyzing
> on the configuration.
>
> Find the diff of these changes done to the Swagger definition at [4]
>
> To get the required information from the Rest API configuration we can
> invoke RestApiAdminServices's getApiByName operation which returns the
> following response [5] for an API created that has the PetStore resources.
> We can identify the methods and uri-template and mappings from this
> response.
>
> Please let know your thoughts.
>
> Thanks,
> Maheeka
>
> [1] http://petstore.swagger.io/#/pet
> [2] https://gist.github.com/maheeka/4eaedd2e2e0765959a4166865bf9adf9
> [3] https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f233f2
> [4] https://www.diffchecker.com/xEu0NSNz
> [5] http://schemas.
> xmlsoap.org/soap/envelope/">
>
>   http://org.apache.axis2/xsd;>
>  http://api.rest.carbon.wso2.org/xsd; xmlns:xsi="http://www.w3.org/
> 2001/XMLSchema-instance">
> 
> /pet
> PetstoreAPI.xml
> 
> false
> PetstoreAPI
> -1
> 
>
>
>
>
>
>POST
>PUT
>
>
>0
>
>/
>
> 
> 
>
>
>
>
>
>POST
>DELETE
>GET
>
>
>0
>/{petId}
>
>
> 
> false
> false
>  
>   
>
> 
>
>
> Thanks,
>
> Maheeka Jayasuriya
> Senior Software Engineer
> Mobile : +9450661
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

[Jagath Sisirakumara Ariyarathne]

Hi Rajith, Jayanga,

Thanks for your suggestions.

I managed to get it done by implementing a custom Wsdl Processor which
intercepts and output from axis2 Wsdl Processor and update URLs
accordingly. It can be applied to ESB by updating the following config in
carbon.xml. Therefore no change required in ESB code.

 

wsdl

org.wso2.carbon.core.transports.util.Wsdl11Processor




Thanks.

On Tue, Sep 6, 2016 at 8:18 PM, Rajith Vitharana <raji...@wso2.com> wrote:

> Hi Jagath,
>
> Can't you do something like
>
> 1) deploy the service
> 2) get wsdl
> 3) modify wsdl to use your custom endpoints
> 4) use that modified wsdl as publish wsdl(inline or as file)
>
> drawback would be, you will need to do this process every time you do some
> changes to the proxy
>
> Thanks,
>
> On 6 September 2016 at 18:39, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> HI Jayanga,
>>
>> I think "publishWSDL" can be used to modify operations exposed to the
>> client from ESB based on back-end service. In our case, it is required to
>> change the service address returned from the wsdl, generated from ESB proxy
>> service.
>>
>> Thanks.
>>
>> On Tue, Sep 6, 2016 at 4:48 PM, Jayanga Dissanayake <jaya...@wso2.com>
>> wrote:
>>
>>> Hi Maheeka/Jagath,
>>>
>>> Did you try using the "publishWSDL" option and publishing a custom WSDL
>>> with modified endpoints.
>>>
>>> Thanks,
>>> Jayanga.
>>>
>>> *Jayanga Dissanayake*
>>> Associate Technical Lead
>>> WSO2 Inc. - http://wso2.com/
>>> lean . enterprise . middleware
>>> email: jaya...@wso2.com
>>> mobile: +94772207259
>>> <http://wso2.com/signature>
>>>
>>> On Sun, Sep 4, 2016 at 9:19 AM, Jagath Sisirakumara Ariyarathne <
>>> jaga...@wso2.com> wrote:
>>>
>>>> HI Chanaka,
>>>>
>>>> Yes, we are looking for any configuration or extension we can implement
>>>> to achieve this which does not affect usual functionality of tenant mode.
>>>>
>>>> Thanks.
>>>>
>>>> On Sun, Sep 4, 2016 at 8:54 AM, Chanaka Fernando <chana...@wso2.com>
>>>> wrote:
>>>>
>>>>> If that is the case, then it makes sense to remove the "/t/abc.com"
>>>>> from the generated WSDL (as Jagath mentioned). Thanks everyone for the
>>>>> clarification. We should do this in a way that it does not affect the
>>>>> standalone mode tenant story.
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 4, 2016 at 8:26 AM, Maheeka Jayasuriya <mahe...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Chanaka,
>>>>>>
>>>>>> The app hostname contains the tenant domain and thus it is possible
>>>>>> to identify the the app uniquely and rewriting the URL without tenant
>>>>>> domain works.
>>>>>>
>>>>>> For example, SampleApp I created in maheeka.com domain would resolve
>>>>>> to hostname : maheeka-com-sampleapp.apps.cloud.wso2.com or might
>>>>>> have a custom URL as Amalka mentions above. Apps can be differentiated
>>>>>> because hostname is composed with tenant domain, app name and version.
>>>>>>
>>>>>> Thanks,
>>>>>> Maheeka
>>>>>>
>>>>>>
>>>>>> Maheeka Jayasuriya
>>>>>> Senior Software Engineer
>>>>>> Mobile : +9450661
>>>>>>
>>>>>> On Sun, Sep 4, 2016 at 8:09 AM, Amalka Subasinghe <ama...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> It is through HAProxy URL rewriting.
>>>>>>>
>>>>>>> User can invoke same proxy as following ways.
>>>>>>> http://tenantDomain-appName-version-wso2apps.com/HellpProxy
>>>>>>> http://tenantDomain-appName-wso2apps.com/HellpProxy
>>>>>>> http://custom-url/HellpProxy
>>>>>>>
>>>>>>> Then at the HAProxy level we have added a logic to rewrite above
>>>>>>> urls to
>>>>>>> http://tenantDomain-appName-version-wso2apps.com/services/t/
>>>>>>> tenantDomain/HellpProxy
>>>>>>>
>>>>>>>
>>>>>>

Re: [Dev] ISSUE IN CREATING PROXY SERVICE FOR HL7 IN ESB 5.0.0

[Jagath Sisirakumara Ariyarathne]

Hi Amutheezan,

The reason for the issue is that HL7MessagePublisherConfig uses incorrect
PublisherUtil. Could you please create a JIRA for this issue in [1].

[1] - https://wso2.org/jira/browse/ESBJAVA

Thanks.

On Fri, Sep 9, 2016 at 9:31 AM, Amutheezan Sivagnanam <amuthee...@wso2.com>
wrote:

> Hi,
> I faced some issues when sending message through HAPi Test Panel. I have
> attached the error_log related to that.
> Thanks,
>
> On Thu, Sep 8, 2016 at 3:43 PM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> Hi Amutheezan,
>>
>> You need to install HL7 feature version 4.6.6 for ESB 5.0.0. Seems it is
>> not there in feature repo and we will add it soon.
>>
>> Meantime, you can build it locally and add through a local repository in
>> ESB.
>>
>> Thanks.
>>
>> On Thu, Sep 8, 2016 at 12:08 PM, Amutheezan Sivagnanam <
>> amuthee...@wso2.com> wrote:
>>
>>> Hi,
>>> I redo every tasks from beginning and same error occurs as previous
>>> case. I have attached the errorlog and modified Axis2.xml file (for
>>> enabling HL7 transport).
>>> Thanks,
>>>
>>> On Thu, Sep 8, 2016 at 11:42 AM, Amutheezan Sivagnanam <
>>> amuthee...@wso2.com> wrote:
>>>
>>>> Hi,
>>>> I have attached the files for Error Occured While Creating the Proxy
>>>> Service and the corresponding proxy service file.
>>>> Thanks,
>>>>
>>>> On Thu, Sep 8, 2016 at 10:43 AM, Jagath Sisirakumara Ariyarathne <
>>>> jaga...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Could you please attach your proxy configuration and the complete
>>>>> carbon log file. By looking at the error, it is due to a missing class.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> On Wed, Sep 7, 2016 at 1:31 PM, Amutheezan Sivagnanam <
>>>>> amuthee...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>> I am doing HL7 Monitoring Solution Project, for part of initial study
>>>>>> I need to configure HL7 for DAS. For this I tried ESB 4.8.1 and ESB 
>>>>>> 4.9.0,
>>>>>> it successfully publish data to DAS, but when I tried with ESB 5.0.0, It
>>>>>> makes the proxy-service  which I used for other version(ESB 4.8.1, ESB
>>>>>> 4.9.0) to disabled. I have attached the "error log" which I received 
>>>>>> while
>>>>>> creating proxy-service.
>>>>>>
>>>>>> Regards,
>>>>>> S.Amutheezan
>>>>>> --
>>>>>> S.Amutheezan
>>>>>> *Software Engineering Intern*
>>>>>> Mobile : +94 76 771 1924
>>>>>> amuthee...@wso2.com
>>>>>> Public Profile : <https://www.facebook.com/AmuX93>
>>>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>>>>
>>>>>> <https://wso2.com/signature>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jagath Ariyarathne
>>>>> Technical Lead
>>>>> WSO2 Inc.  http://wso2.com/
>>>>> Email: jaga...@wso2.com
>>>>> Mob  : +94 77 386 7048
>>>>> <http://wso2.com/signature>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> S.Amutheezan
>>>> *Software Engineering Intern*
>>>> Mobile : +94 76 771 1924
>>>> amuthee...@wso2.com
>>>> Public Profile : <https://www.facebook.com/AmuX93>
>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>>
>>>> <https://wso2.com/signature>
>>>>
>>>
>>>
>>>
>>> --
>>> S.Amutheezan
>>> *Software Engineering Intern*
>>> Mobile : +94 76 771 1924
>>> amuthee...@wso2.com
>>> Public Profile : <https://www.facebook.com/AmuX93>
>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>
>>> <https://wso2.com/signature>
>>>
>>
>>
>>
>> --
>> Jagath Ariyarathne
>> Technical Lead
>> WSO2 Inc.  http://wso2.com/
>> Email: jaga...@wso2.com
>> Mob  : +94 77 386 7048
>> <http://wso2.com/signature>
>>
>
>
>
> --
> S.Amutheezan
> *Software Engineering Intern*
> Mobile : +94 76 771 1924
> amuthee...@wso2.com
> Public Profile : <https://www.facebook.com/AmuX93>
> <https://lk.linkedin.com/in/amutheezansivagnanam>
> <https://lk.linkedin.com/in/amutheezansivagnanam>
> <https://lk.linkedin.com/in/amutheezansivagnanam>
>
> <https://wso2.com/signature>
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ISSUE IN CREATING PROXY SERVICE FOR HL7 IN ESB 5.0.0

[Jagath Sisirakumara Ariyarathne]

Hi Amutheezan,

You need to install HL7 feature version 4.6.6 for ESB 5.0.0. Seems it is
not there in feature repo and we will add it soon.

Meantime, you can build it locally and add through a local repository in
ESB.

Thanks.

On Thu, Sep 8, 2016 at 12:08 PM, Amutheezan Sivagnanam <amuthee...@wso2.com>
wrote:

> Hi,
> I redo every tasks from beginning and same error occurs as previous case.
> I have attached the errorlog and modified Axis2.xml file (for enabling HL7
> transport).
> Thanks,
>
> On Thu, Sep 8, 2016 at 11:42 AM, Amutheezan Sivagnanam <
> amuthee...@wso2.com> wrote:
>
>> Hi,
>> I have attached the files for Error Occured While Creating the Proxy
>> Service and the corresponding proxy service file.
>> Thanks,
>>
>> On Thu, Sep 8, 2016 at 10:43 AM, Jagath Sisirakumara Ariyarathne <
>> jaga...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Could you please attach your proxy configuration and the complete carbon
>>> log file. By looking at the error, it is due to a missing class.
>>>
>>> Thanks,
>>>
>>> On Wed, Sep 7, 2016 at 1:31 PM, Amutheezan Sivagnanam <
>>> amuthee...@wso2.com> wrote:
>>>
>>>> Hi,
>>>> I am doing HL7 Monitoring Solution Project, for part of initial study I
>>>> need to configure HL7 for DAS. For this I tried ESB 4.8.1 and ESB 4.9.0, it
>>>> successfully publish data to DAS, but when I tried with ESB 5.0.0, It makes
>>>> the proxy-service  which I used for other version(ESB 4.8.1, ESB 4.9.0) to
>>>> disabled. I have attached the "error log" which I received while creating
>>>> proxy-service.
>>>>
>>>> Regards,
>>>> S.Amutheezan
>>>> --
>>>> S.Amutheezan
>>>> *Software Engineering Intern*
>>>> Mobile : +94 76 771 1924
>>>> amuthee...@wso2.com
>>>> Public Profile : <https://www.facebook.com/AmuX93>
>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>>>
>>>> <https://wso2.com/signature>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Jagath Ariyarathne
>>> Technical Lead
>>> WSO2 Inc.  http://wso2.com/
>>> Email: jaga...@wso2.com
>>> Mob  : +94 77 386 7048
>>> <http://wso2.com/signature>
>>>
>>
>>
>>
>> --
>> S.Amutheezan
>> *Software Engineering Intern*
>> Mobile : +94 76 771 1924
>> amuthee...@wso2.com
>> Public Profile : <https://www.facebook.com/AmuX93>
>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>> <https://lk.linkedin.com/in/amutheezansivagnanam>
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> S.Amutheezan
> *Software Engineering Intern*
> Mobile : +94 76 771 1924
> amuthee...@wso2.com
> Public Profile : <https://www.facebook.com/AmuX93>
> <https://lk.linkedin.com/in/amutheezansivagnanam>
> <https://lk.linkedin.com/in/amutheezansivagnanam>
> <https://lk.linkedin.com/in/amutheezansivagnanam>
>
> <https://wso2.com/signature>
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ISSUE IN CREATING PROXY SERVICE FOR HL7 IN ESB 5.0.0

[Jagath Sisirakumara Ariyarathne]

Hi,

Could you please attach your proxy configuration and the complete carbon
log file. By looking at the error, it is due to a missing class.

Thanks,

On Wed, Sep 7, 2016 at 1:31 PM, Amutheezan Sivagnanam 
wrote:

> Hi,
> I am doing HL7 Monitoring Solution Project, for part of initial study I
> need to configure HL7 for DAS. For this I tried ESB 4.8.1 and ESB 4.9.0, it
> successfully publish data to DAS, but when I tried with ESB 5.0.0, It makes
> the proxy-service  which I used for other version(ESB 4.8.1, ESB 4.9.0) to
> disabled. I have attached the "error log" which I received while creating
> proxy-service.
>
> Regards,
> S.Amutheezan
> --
> S.Amutheezan
> *Software Engineering Intern*
> Mobile : +94 76 771 1924
> amuthee...@wso2.com
> Public Profile : 
> 
> 
> 
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

[Jagath Sisirakumara Ariyarathne]

HI Jayanga,

I think "publishWSDL" can be used to modify operations exposed to the
client from ESB based on back-end service. In our case, it is required to
change the service address returned from the wsdl, generated from ESB proxy
service.

Thanks.

On Tue, Sep 6, 2016 at 4:48 PM, Jayanga Dissanayake <jaya...@wso2.com>
wrote:

> Hi Maheeka/Jagath,
>
> Did you try using the "publishWSDL" option and publishing a custom WSDL
> with modified endpoints.
>
> Thanks,
> Jayanga.
>
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259
> <http://wso2.com/signature>
>
> On Sun, Sep 4, 2016 at 9:19 AM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> HI Chanaka,
>>
>> Yes, we are looking for any configuration or extension we can implement
>> to achieve this which does not affect usual functionality of tenant mode.
>>
>> Thanks.
>>
>> On Sun, Sep 4, 2016 at 8:54 AM, Chanaka Fernando <chana...@wso2.com>
>> wrote:
>>
>>> If that is the case, then it makes sense to remove the "/t/abc.com"
>>> from the generated WSDL (as Jagath mentioned). Thanks everyone for the
>>> clarification. We should do this in a way that it does not affect the
>>> standalone mode tenant story.
>>>
>>>
>>>
>>> On Sun, Sep 4, 2016 at 8:26 AM, Maheeka Jayasuriya <mahe...@wso2.com>
>>> wrote:
>>>
>>>> Hi Chanaka,
>>>>
>>>> The app hostname contains the tenant domain and thus it is possible to
>>>> identify the the app uniquely and rewriting the URL without tenant domain
>>>> works.
>>>>
>>>> For example, SampleApp I created in maheeka.com domain would resolve
>>>> to hostname : maheeka-com-sampleapp.apps.cloud.wso2.com or might have
>>>> a custom URL as Amalka mentions above. Apps can be differentiated because
>>>> hostname is composed with tenant domain, app name and version.
>>>>
>>>> Thanks,
>>>> Maheeka
>>>>
>>>>
>>>> Maheeka Jayasuriya
>>>> Senior Software Engineer
>>>> Mobile : +9450661
>>>>
>>>> On Sun, Sep 4, 2016 at 8:09 AM, Amalka Subasinghe <ama...@wso2.com>
>>>> wrote:
>>>>
>>>>> It is through HAProxy URL rewriting.
>>>>>
>>>>> User can invoke same proxy as following ways.
>>>>> http://tenantDomain-appName-version-wso2apps.com/HellpProxy
>>>>> http://tenantDomain-appName-wso2apps.com/HellpProxy
>>>>> http://custom-url/HellpProxy
>>>>>
>>>>> Then at the HAProxy level we have added a logic to rewrite above urls
>>>>> to
>>>>> http://tenantDomain-appName-version-wso2apps.com/services/t/
>>>>> tenantDomain/HellpProxy
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 4, 2016 at 8:04 AM, Chanaka Fernando <chana...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I'm bit confused about how we differentiate the endpoints for
>>>>>> different tenants. I thought it was through this "/t/aa.com"
>>>>>> section. If I have a proxy called "HelloProxy" and you have the same 
>>>>>> proxy
>>>>>> (in your tenant), how are we going to differentiate? Is it from "host 
>>>>>> name"
>>>>>> section?
>>>>>>
>>>>>> http://cloud.integration.wso2.com/services/*t/chanaka.com/HelloProxy
>>>>>> <http://chanaka.com/HelloProxy>*
>>>>>> http://cloud.integration.wso2.com/services/*t/maheeka.com/HelloProxy
>>>>>> <http://maheeka.com/HelloProxy>*
>>>>>>
>>>>>> or
>>>>>>
>>>>>> http://*xxx.cloud.integration.wso2.com
>>>>>> <http://xxx.cloud.integration.wso2.com>*/services/HelloProxy
>>>>>> http://*yyy.cloud.integration.wso2.com
>>>>>> <http://yyy.cloud.integration.wso2.com>*/services/HelloProxy
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 4, 2016 at 7:28 AM, Maheeka Jayasuriya <mahe...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Chanaka,
>>>>>>>
>>>>>>> W

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

[Jagath Sisirakumara Ariyarathne]

HI Chanaka,

Yes, we are looking for any configuration or extension we can implement to
achieve this which does not affect usual functionality of tenant mode.

Thanks.

On Sun, Sep 4, 2016 at 8:54 AM, Chanaka Fernando <chana...@wso2.com> wrote:

> If that is the case, then it makes sense to remove the "/t/abc.com" from
> the generated WSDL (as Jagath mentioned). Thanks everyone for the
> clarification. We should do this in a way that it does not affect the
> standalone mode tenant story.
>
>
>
> On Sun, Sep 4, 2016 at 8:26 AM, Maheeka Jayasuriya <mahe...@wso2.com>
> wrote:
>
>> Hi Chanaka,
>>
>> The app hostname contains the tenant domain and thus it is possible to
>> identify the the app uniquely and rewriting the URL without tenant domain
>> works.
>>
>> For example, SampleApp I created in maheeka.com domain would resolve to
>> hostname : maheeka-com-sampleapp.apps.cloud.wso2.com or might have a
>> custom URL as Amalka mentions above. Apps can be differentiated because
>> hostname is composed with tenant domain, app name and version.
>>
>> Thanks,
>> Maheeka
>>
>>
>> Maheeka Jayasuriya
>> Senior Software Engineer
>> Mobile : +9450661
>>
>> On Sun, Sep 4, 2016 at 8:09 AM, Amalka Subasinghe <ama...@wso2.com>
>> wrote:
>>
>>> It is through HAProxy URL rewriting.
>>>
>>> User can invoke same proxy as following ways.
>>> http://tenantDomain-appName-version-wso2apps.com/HellpProxy
>>> http://tenantDomain-appName-wso2apps.com/HellpProxy
>>> http://custom-url/HellpProxy
>>>
>>> Then at the HAProxy level we have added a logic to rewrite above urls to
>>> http://tenantDomain-appName-version-wso2apps.com/services/t/
>>> tenantDomain/HellpProxy
>>>
>>>
>>>
>>> On Sun, Sep 4, 2016 at 8:04 AM, Chanaka Fernando <chana...@wso2.com>
>>> wrote:
>>>
>>>> I'm bit confused about how we differentiate the endpoints for different
>>>> tenants. I thought it was through this "/t/aa.com" section. If I have
>>>> a proxy called "HelloProxy" and you have the same proxy (in your tenant),
>>>> how are we going to differentiate? Is it from "host name" section?
>>>>
>>>> http://cloud.integration.wso2.com/services/*t/chanaka.com/HelloProxy
>>>> <http://chanaka.com/HelloProxy>*
>>>> http://cloud.integration.wso2.com/services/*t/maheeka.com/HelloProxy
>>>> <http://maheeka.com/HelloProxy>*
>>>>
>>>> or
>>>>
>>>> http://*xxx.cloud.integration.wso2.com
>>>> <http://xxx.cloud.integration.wso2.com>*/services/HelloProxy
>>>> http://*yyy.cloud.integration.wso2.com
>>>> <http://yyy.cloud.integration.wso2.com>*/services/HelloProxy
>>>>
>>>>
>>>> On Sun, Sep 4, 2016 at 7:28 AM, Maheeka Jayasuriya <mahe...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Chanaka,
>>>>>
>>>>> When we deploy a car file containing a proxy service, we need to show
>>>>> the WSDL for the proxy in integration cloud. The endpoints in the WSDL are
>>>>> composed with the host name of the app and the tenant suffix -
>>>>> t/tenantDomain, since we are doing the deployment in the tenant space.
>>>>>
>>>>> When we get a request as http://esb.wso2.com:8280/servi
>>>>> ces/HelloProxy.HelloProxyHttpSoap11Endpoint
>>>>> <http://jagatha-ThinkPad-T530:8280/services/t/aa.com/HelloProxy.HelloProxyHttpSoap11Endpoint>,
>>>>> it is actually rewritten to http://esb.wso2.com:8280/servi
>>>>> ces/t/aa.com/HelloProxy.HelloProxyHttpSoap11Endpoint
>>>>> <http://jagatha-ThinkPad-T530:8280/services/t/aa.com/HelloProxy.HelloProxyHttpSoap11Endpoint>
>>>>> by the HAProxy. Hence, requests are redirected to real tenant endpoint.
>>>>> However, this tenant information is not necessary to be known to the users
>>>>> when they use the WSDL to send a request. Hence the question whether it is
>>>>> possible to do $subject.
>>>>>
>>>>> Thanks,
>>>>> Maheeka
>>>>>
>>>>> Maheeka Jayasuriya
>>>>> Senior Software Engineer
>>>>> Mobile : +9450661
>>>>>
>>>>> On Sun, Sep 4, 2016 at 7:18 AM, Chanaka Fernando <chana...@wso2.com>
>>>>> wrote:
>>>>>

[Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

[Jagath Sisirakumara Ariyarathne]

Hi All,

When a Proxy (e.g. HelloProxy) is deployed in a tenant space (e.g abc.com)
in ESB, related wsdl will contain service definition as follows;


http://esb.wso2.com:8280/
services/t/aa.com/HelloProxy.HelloProxyHttpSoap11Endpoint

"/>


Is there a way to change the address in this definition, to make it without
the tenant ID like below, even though it is deployed in tenant space.


http://esb.wso2.com:8280/services/HelloProxy.
HelloProxyHttpSoap11Endpoint

"/>



Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Error in running a sample provided in the doc

[Jagath Sisirakumara Ariyarathne]

Hi Nadeesha,

Seems the payload received to the ESB '{name:WSO2}'does not contain double
quotes. Correct payload should be '{"name":"WSO2"}'.

Lets check wire logs to get it confirmed that ESB received correct payload.

Thanks.

On Wed, Aug 24, 2016 at 12:07 PM, Nadeesha Gamage  wrote:

> Hi all,
> I am referring to the following document [1], and have deployed the CAR
> file provided [2]. When I try to invoke the API using the provided curl
> command I get the following error. Can someone help to get this resolved.
>
> curl -X POST http://localhost:8280/stockquote/getQuote -d
> '{"name":"WSO2"}' -H "Content-Type:application/json"
>
>
> TID: [-1234] [] [2016-08-24 11:56:57,576]  INFO
> {org.apache.synapse.mediators.builtin.LogMediator} -  To:
> /stockquote/getQuote, MessageID: 
> urn:uuid:a688b5fd-4db3-46b2-9a7d-78797558de89,
> Direction: request, Payload: '{name:WSO2}' {org.apache.synapse.mediators.
> builtin.LogMediator}
> TID: [-1234] [] [2016-08-24 11:56:57,585] ERROR 
> {org.apache.synapse.util.xpath.SynapseJsonPath}
> -  #stringValueOf. Error evaluating JSON Path <$.name>. Returning empty
> result. Error>>> Invalid container object {org.apache.synapse.util.
> xpath.SynapseJsonPath}
> TID: [-1234] [] [2016-08-24 11:56:57,595] ERROR 
> {org.apache.axiom.om.impl.llom.OMSourcedElementImpl}
> -  Could not get parser from data source for element jsonObject
> {org.apache.axiom.om.impl.llom.OMSourcedElementImpl}
> javax.xml.stream.XMLStreamException
> at org.apache.synapse.commons.staxon.core.base.AbstractXMLStreamReader.
> initialize(AbstractXMLStreamReader.java:245)
> at org.apache.synapse.commons.staxon.core.json.JsonXMLStreamReader.(
> JsonXMLStreamReader.java:66)
> at org.apache.synapse.commons.staxon.core.json.JsonXMLInputFactory.
> createXMLStreamReader(JsonXMLInputFactory.java:165)
> at org.apache.synapse.commons.json.JsonUtil.getReader(JsonUtil.java:302)
> at org.apache.synapse.commons.json.JsonDataSource.getReader(
> JsonDataSource.java:153)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getDirectReader(
> OMSourcedElementImpl.java:225)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(
> OMSourcedElementImpl.java:254)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getChildren(
> OMSourcedElementImpl.java:859)
> at org.apache.synapse.commons.json.JsonUtil.removeIndentations(JsonUtil.
> java:417)
> at org.apache.synapse.commons.json.JsonUtil.removeIndentations(JsonUtil.
> java:425)
> at org.apache.synapse.commons.json.JsonUtil.removeJsonPayload(JsonUtil.
> java:731)
> at org.apache.synapse.mediators.transform.PayloadFactoryMediator.mediate(
> PayloadFactoryMediator.java:163)
> at org.apache.synapse.mediators.transform.PayloadFactoryMediator.mediate(
> PayloadFactoryMediator.java:104)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:89)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:59)
> at org.apache.synapse.mediators.base.SequenceMediator.mediate(
> SequenceMediator.java:158)
> at org.apache.synapse.rest.Resource.process(Resource.java:343)
> at org.apache.synapse.rest.API.process(API.java:399)
> at org.apache.synapse.rest.RESTRequestHandler.apiProcess(
> RESTRequestHandler.java:120)
> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(
> RESTRequestHandler.java:101)
> at org.apache.synapse.rest.RESTRequestHandler.process(
> RESTRequestHandler.java:69)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(
> Axis2SynapseEnvironment.java:304)
> at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(
> SynapseMessageReceiver.java:75)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.synapse.transport.passthru.ServerWorker.
> processNonEntityEnclosingRESTHandler(ServerWorker.java:325)
> at org.apache.synapse.transport.passthru.ServerWorker.
> processEntityEnclosingRequest(ServerWorker.java:371)
> at org.apache.synapse.transport.passthru.ServerWorker.run(
> ServerWorker.java:151)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> TID: [-1234] [] [2016-08-24 11:56:57,613] ERROR
> {org.apache.synapse.mediators.base.SequenceMediator} -  Error obtaining
> parser from data source:null {org.apache.synapse.mediators.
> base.SequenceMediator}
> java.lang.RuntimeException: Error obtaining parser from data source:null
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getDirectReader(
> OMSourcedElementImpl.java:230)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(
> OMSourcedElementImpl.java:254)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getChildren(
> OMSourcedElementImpl.java:859)
> at 

[Dev] carbon-mediation-4.6.5 Released

[Jagath Sisirakumara Ariyarathne]

Hi All,

Carbon-mediation 4.6.5 released.

org.wso2.carbon.mediation
carbon-mediation
4.6.5

Thanks.

-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB500] Invoking a secure proxy in a clustered set up

[Jagath Sisirakumara Ariyarathne]

Hi Pubudu,

Whenever you access a Https endpoint, you have to import back-end's
certificate to client-truststore. That is the default requirement if you
are using SSL between back-end and ESB.

Thanks.

On Mon, Aug 8, 2016 at 10:13 AM, Pubudu Priyashan  wrote:

> Hi ESB team,
>
> I have observed the following behaviour when invoking a secure proxy in a
> clustered setup which calls an external http endpoint [1] with ESB 5.0.0
> (Tested with RC1). Can you please inform if this behaviour is correct or
> are there any alternative methods?
>
> I have a secure proxy in my ESB cluster where it calls an external https
> endpoint [1]. When I invoked this in a single node in my local machine, it
> returned the response as expected. When I created the same secure proxy in
> a Cluster, I received this error [2]. I was able to get rid of this error
> by adding the certificate of the endpoint to client-truststore.jks file of
> each ESB node of the cluster.
>
> My question is, is this behaviour correct? Should we have to always add
> the https endpoint certificate every time we need to use an external
> endpoint in a secure proxy? Or is there another approach where we don't
> have to do this and not required to add the keys to client-truststore.jks
> and restart ESB nodes? This might not be convenient if we have a lot of
> https endpoints being called via a secure proxy in ESB. Can you please
> advice?
>
> Thanks!
>
> [1] https://demo5224632.mockable.io/test123
>
> [2] Exception in ESB worker node:-
>
> TID: [-1] [] [2016-08-04 05:34:33,682] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "GET /services/SecureP1
> HTTP/1.1[\r][\n]" {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "X-Forwarded-Host:
> wrk.esb500.wso2.com[\r][\n]" {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "X-Forwarded-Server:
> wrk.esb500.wso2.com[\r][\n]" {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "X-Forwarded-For:
> 10.100.7.95[\r][\n]" {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "Connection: upgrade[\r][\n]"
> {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,683] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "Host: ssl.esb500.com[\r][\n]"
> {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "Authorization: Basic
> YWRtaW5lc2I1MDA6ZXNiNTAwQERhcw==[\r][\n]" {org.apache.synapse.transport.
> http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "Cache-Control: no-cache[\r][\n]"
> {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "User-Agent: Mozilla/5.0 (X11; Linux
> x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116
> Safari/537.36[\r][\n]" {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "Postman-Token:
> 60dc8ef4-36b0-03bd-5841-7efad2189071[\r][\n]"
> {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,684] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "Accept: */*[\r][\n]"
> {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,685] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "Accept-Encoding: gzip, deflate,
> sdch[\r][\n]" {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,685] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "Accept-Language:
> en-US,en;q=0.8[\r][\n]" {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,685] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Listener I/O dispatcher-1 >> "[\r][\n]"
> {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,813] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Sender I/O dispatcher-1 << "CONNECT demo5224632.mockable.io:443
> HTTP/1.1[\r][\n]" {org.apache.synapse.transport.http.wire}
> TID: [-1] [] [2016-08-04 05:34:33,814] DEBUG 
> {org.apache.synapse.transport.http.wire}
> -  HTTPS-Sender I/O dispatcher-1 << "Host: 
> 

[Dev] [VOTE] Release WSO2 Enterprise Service Bus 5.0.0 RC2

[Jagath Sisirakumara Ariyarathne]

Hi All,

This is the 2nd Release Candidate of WSO2 Enterprise Service Bus 5.0.0

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.

*Source and distribution*

Run-time: *https://github.com/wso2/product-esb/releases/tag/v5.0.0-rc2
*
Tooling   : https://github.com/wso2/devstudio-tooling-esb/
releases/tag/v5.0.0-RC2
Analytics: https://github.com/wso2/analytics-esb/releases/tag/v5.0.0-rc2

Please vote as follows.
[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

Thanks,
- WSO2 ESB Team -
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Service Bus 5.0.0 RC1

[Jagath Sisirakumara Ariyarathne]

Hi All,

We will call off this vote due to the issue reported in [1] and will start
a new vote for ESB 5.0.0 RC2.

[1] - https://wso2.org/jira/browse/ESBJAVA-4333

Thanks.

On Tue, Aug 2, 2016 at 10:44 PM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi All,
>
> This is the 1st Release Candidate of WSO2 Enterprise Service Bus 5.0.0
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> *Source and distribution*
>
> Run-time: https://github.com/wso2/product-esb/releases/tag/v5.0.0-rc1
> Tooling   :
> https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-RC1
> Analytics:
> https://github.com/wso2/analytics-esb/releases/tag/v5.0.0-rc1
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 ESB Team -
> --
> Jagath Ariyarathne
> Technical Lead
> WSO2 Inc.  http://wso2.com/
> Email: jaga...@wso2.com
> Mob  : +94 77 386 7048
> <http://wso2.com/signature>
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Enterprise Service Bus 5.0.0 RC1

[Jagath Sisirakumara Ariyarathne]

Hi All,

This is the 1st Release Candidate of WSO2 Enterprise Service Bus 5.0.0

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.

*Source and distribution*

Run-time: https://github.com/wso2/product-esb/releases/tag/v5.0.0-rc1
Tooling   :
https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-RC1
Analytics: https://github.com/wso2/analytics-esb/releases/tag/v5.0.0-rc1

Please vote as follows.
[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

Thanks,
- WSO2 ESB Team -
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Carbon-mediation 4.6.2 Released

[Jagath Sisirakumara Ariyarathne]

Hi All,

Carbon-mediation 4.6.2 released.

org.wso2.carbon.mediation
carbon-mediation
4.6.2

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Axis2 Transport 1.1.1-wso2v5 Released

[Jagath Sisirakumara Ariyarathne]

Hi All,

Axis2 Transport version 1.1.1-wso2v5 Released.

org.apache.axis2.transport
axis2-transports
1.1.1-wso2v5


Thanks.

-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] [Tooling] Issue when deploying a CAPP to a remote ESB server

[Jagath Sisirakumara Ariyarathne]

Hi Chathurika,

This will be solved with the fix which we are going to apply for [1]. Issue
is that Dev Studio calls admin services with additional '/' and it will be
removed with the fix.

[1] - https://wso2.org/jira/browse/DEVTOOLESB-637

Thanks.

On Fri, Jul 22, 2016 at 6:54 PM, Chathurika De Silva 
wrote:

> Hi
>
> A similar issue exists for un-deploying a CAPP and the issue is reported
> as [1]. Would it be possible for us to get this fixed?
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-642
>
> Thank You
> Erandi
>
> On Wed, Jul 13, 2016 at 11:34 AM, Pubudu Priyashan 
> wrote:
>
>> Awesome. Thanks!
>>
>> Cheers,
>> Pubudu.
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>> On Wed, Jul 13, 2016 at 11:31 AM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Pubudu,
>>>
>>> We have already fixed this in the latest source and will share a pack
>>> soon.
>>>
>>> On Wed, Jul 13, 2016 at 11:13 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hello Viraj and DevStudio team,

 We have observed the issue logged at [1] while testing ESB tooling
 shipped with wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. Issue persists
 for both p2 repo as well as the pre-packaged Eclipse.

 Would it be possible for us to get this fix in with the next ESB pack
 released for testing? Thanks!


 [1] https://wso2.org/jira/browse/DEVTOOLESB-574

 Cheers,
 Pubudu D.P
 Senior Software Engineer - QA Team | WSO2 inc.
 Mobile : +94775464547

 Linkedin: https://uk.linkedin.com/in/pubududp
 Medium: https://medium.com/@pubududp


>>>
>>>
>>> --
>>> Thank you and Best Regards,
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>>
>>>
>>>
>>>
>>>
>>
>
>
> --
> *Chathurika Erandi*
> Senior Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 ESB 5.0.0-BETA2 Released!

[Jagath Sisirakumara Ariyarathne]

*WSO2 ESB 5.0.0-BETA2 Released*

ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA2 release.

The distribution is available to download at [1]. It contains improvements
and bug fixes [2].

[1] - https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA2
[2] -
https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10023=12362


*WSO2 **ESB Tooling 5.0.0**-BETA2 Released*

The distribution is available to download at [3]. It contains improvements
and bug fixes [4].

[3] -
https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-BETA2
[4] -
https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=11003=12389


*WSO2 **ESB Analytics 5.0.0**-BETA2 Released*

The distribution is available to download at [5]. It contains improvements
and bug fixes [6].

[5] - https://github.com/wso2/analytics-esb/releases/tag/v5.0.0-beta2
[6] -
https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=11002=12390


- WSO2 ESB Team -
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Carbon-mediation 4.6.1 Released

[Jagath Sisirakumara Ariyarathne]

Hi All,

Carbon-mediation 4.6.1 Released.

org.wso2.carbon.mediation
carbon-mediation
4.6.1

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Synapse-2.1.7-wso2v3 Released

[Jagath Sisirakumara Ariyarathne]

Hi All,

Please note $subject.

org.apache.synapse
Apache-Synapse
2.1.7-wso2v3

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] PRs to be merged in wso2-synapse and carbon-mediation

[Jagath Sisirakumara Ariyarathne]

Hi,

We are in the process of releasing wso2-synapse and carbon-mediation prior
to ESB 5.0.0 Beta2 release within next few days. If there any pending PRs
to be merged before that, please update in this thread.

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] "Error 403 - Forbidden" when session expires in admin console

[Jagath Sisirakumara Ariyarathne]

Hi Pubudu,

On Fri, Jul 8, 2016 at 5:29 PM, Pubudu Priyashan  wrote:

> [+Senduran]
>
> We have found the same issue [1] in ESB wso2esb-5.0.0-pre-RC2.zip pack.
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4741
>

This issue has been fixed by applying required filters in property file. We
will update the JIRA.

Thanks.

On Fri, Jul 8, 2016 at 6:35 PM, Dulanja Liyanage  wrote:

>
>
> On Thu, Jul 7, 2016 at 4:53 PM, Ayoma Wijethunga  wrote:
>
>> Hi All,
>>
>> Original issue reported by Hasintha is relevant to how we handle session
>> timeout conditions with CSRFGuard filter. We are working on this and will
>> update with a resolution.
>>
>
> The reason for this behavior is there's no session-existence check prior
> to the form POST. Before CSRFGuard this was not a problem, because, upon a
> failure due to session timeout one of the following would have happened:
>
>1. in the case of an ajaxprocessor - Request would be propagated to
>the respective admin service, and upon its session non-existence exception,
>will be redirected to the login page.
>2. in the case of a non-ajaxprocessor - CarbonSecuredHttpContext will
>redirect to the login page before hitting the actual jsp/servlet.
>
> Since CSRFGuard is a filter, it intercepts before either of the above
> happen and sends a 403 forbidden - because that's what it's supposed to do.
>
> There's a platform level javascript function called sessionAwareFunction
> (in main.js) that can be used for this. Registry Browser uses that. We have
> to send the actual operation we want to do as a callback function to
> sessionAwareFunction. It will initially do a session validity check
> via /carbon/admin/jsp/session-validate.jsp and then execute what we want to
> do.
>
> We tried to come up with a centralized solution for this, but failed.
> Therefore, this need to be fixed at product-level.
>
> Please let us know if you see a better solution for this.
>
>
>> In general CSRFGuard should work without any per-page modifications,
>> since we are using JavaScript based attribute injection and header based
>> protection for AJAX requests. However, there might be special cases in
>> which these methodologies fail. Such incidences should be handled
>> case-by-case and we will be adding all the special cases we identified in
>> to the "Integration Checklist" of [1].
>>
>> We had a short offline session with Shavantha on the issue he is facing
>> and identified that there are methods that use "
>> *document.createElement('form')*" JavaScript call to build forms
>> dynamically. Since CSRFGuard JavaScript will not be able to identify such
>> forms, it is necessary to add CSRF token manually. Please see the
>> screenshot attached which is the page source of [2]. In such situations it
>> is required to use JSP Taglib to add CSRF token as an additional parameter.
>> Please follow [1] for additional details.
>>
>> We can of cause arrange quick sessions with teams to check on any
>> edge-case issues they are facing, relevant to CSRFGuard.
>>
>> [1]
>> https://docs.google.com/document/d/1LV23-hD7q1BjsruUdvM5dO4j7pIuUpzR_EYLmdfOo6k/edit#heading=h.xqvmgi6xtm6f
>> [2]
>> https://localhost:9443/t/tenant.com/carbon/user/edit-user-roles.jsp?username=ADDOMAIN%2FAdministrator699=ADDOMAIN%2FAdministrator699
>>
>> Best Regards,
>> Ayoma.
>>
>> On Thu, Jul 7, 2016 at 11:35 AM, Shavantha Weerasinghe <
>> shavan...@wso2.com> wrote:
>>
>>> [+Dulanjan]
>>>
>>> Hi All
>>>
>>> When trying to add multiple roles to a user using a feature such as *Select
>>> all from page 1 to page 3* or clicking on a pagination number the same
>>> error comes and throws an error similar to[1]
>>>
>>> [1]
>>> [2016-07-07 11:34:37,139]  WARN - JavaLogger potential cross-site
>>> request forgery (CSRF) attack thwarted (user:, ip:127.0.0.1,
>>> method:POST, uri:/t/tenant.com/carbon/user/view-roles.jsp,
>>> error:required token is missing from the request)
>>>
>>>
>>> Regards,
>>> Shavantha Weerasinghe
>>> Senior Software Engineer QA
>>> WSO2, Inc.
>>> lean.enterprise.middleware.
>>> http://wso2.com
>>> http://wso2.org
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>>
>>>
>>> On Wed, Jul 6, 2016 at 4:10 PM, Hasintha Indrajee 
>>> wrote:
>>>
 Hi all,

 When trying to perform operations through admin console, once the
 session is expired we are getting a 403 from admin console. Seems like this
 occurs due to CSRF filter blocking the request since the session is no
 longer available at the server side.

 [2016-07-06 15:34:27,576]  WARN {org.owasp.csrfguard.log.JavaLogger} -
 potential cross-site request forgery (CSRF) attack thwarted
 (user:, ip:127.0.0.1, method:POST,
 uri:/carbon/userprofile/set-finish-ajaxprocessor.jsp, error:request token
 does not match session token)
 --
 Hasintha Indrajee
 WSO2, Inc.
 Mobile:+94 771892453


 

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Jagath Sisirakumara Ariyarathne]

Hi,

Tested with ESB 5.0.0-SNAPSHOT and executed integrated tests. No issues
observed.

[x] Stable - go ahead and release.

Thanks.

On Mon, Jul 4, 2016 at 10:56 PM, Hasitha Aravinda  wrote:

> Tested with BPS 3.6.0-SNAPSHOT. No issue found.
>
> [x] Stable - go ahead and release.
>
> Thanks,
> Hasitha.
>
> On Mon, Jul 4, 2016 at 6:42 PM, Kasun Bandara  wrote:
>
>> Hi all,
>>
>> I could successfully run IS test suit with the upgraded Kernel 4.4.7-
>> RC1. Hence +1 for the release.
>>
>> Thanks,
>> Kasun
>>
>> On Mon, Jul 4, 2016 at 5:35 PM, Chamalee De Silva 
>> wrote:
>>
>>> P.S. Test done base done API Manager 2.0.0 beta-2
>>>
>>> On Mon, Jul 4, 2016 at 5:33 PM, Chamalee De Silva 
>>> wrote:
>>>
 Hi,
 I tested the kernel 4.4.7 RC1 with

 MySQL 5.6 and  5.7,
 Oracle 11g,
 PostgreSQL 9.3

 and they worked without an issue.

 [x] Stable - go ahead and release.



 Thanks,
 Chamalee

 On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage 
 wrote:

> Hi,
>
> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
> issue related to this RC.
>
> *Note :* Feature repo not shown issue [1], introduced with kernel
> 4.4.6 is observed. Hope this will be fixed in a future release.
>
> [1] https://wso2.org/jira/browse/CARBON-15973
>
> Regards,
> Anupama
>
> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne <
> shash...@wso2.com> wrote:
>
>> Hi,
>>
>> I tested the kernal with following databases and no issues observed.
>>
>> Test Area:
>> Add/ Delete resource (inline text) and collection
>> Add/Remove user and role
>>
>> Databases:
>> mysql 5.5.
>> mysql 5.7
>> postgres 9.3
>> oracle 12c
>>
>> Regards,
>> Shashika
>>
>> Shashika Ubhayaratne
>> Associate Technical Lead - QA
>> WSO2 Inc: http://www.wso2.com/
>> Mobile: *+94773383831*
>>
>> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Hi all,
>>>
>>> I've tested the kernel with following databases and found no issues.
>>> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
>>> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>>>
>>> [x] Stable - go ahead and release.
>>>
>>> Regards,
>>> Aruna
>>> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake <
>>> jaya...@wso2.com> wrote:
>>>
 Hi Devs,

 This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.

 This release fixes the following issues:
 https://wso2.org/jira/issues/?filter=13113

 Please download and test your products with kernel 4.4.7 RC1 and
 vote. Vote will be open for 72 hours or as longer as needed.

 Source and binary distribution files:
 https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip

 http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip

 Maven staging repository
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025

 The tag to be voted upon :
 https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1

 [ ] Broken - do not release (explain why)
 [ ] Stable - go ahead and release

 Thank you
 Carbon Team​


 *Jayanga Dissanayake*
 Associate Technical Lead
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Anupama Pathirage
> Associate Technical Lead
> WSO2, Inc.  http://wso2.com/
> Email: anup...@wso2.com
> Mobile:+94 71 8273 979
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 

Re: [Dev] ESB 4.9.0 JSM client error

[Jagath Sisirakumara Ariyarathne]

Hi Ravi,

Seems activemq is used by GenericJMSClient [1] by default.

[1] -
https://github.com/wso2/product-esb/blob/master/modules/samples/product/src/main/java/samples/userguide/GenericJMSClient.java

Thanks.

On Tue, May 10, 2016 at 2:37 PM, Ravi Undupitiya <r...@wso2.com> wrote:

> Hi Aruna,
>
> ActiveMQ jars are not required to connect to MB. Would you happen to have
> ActiveMQ context factory set in some config file?
>
>
> On Tue, May 10, 2016 at 2:24 PM, Aruna Karunarathna <ar...@wso2.com>
> wrote:
>
>> Hi Jagath,
>>
>> Thanks for the reply, No I haven't setup ActiveMQ, instead I've followed
>> instructions in [1] to configure with WSO2MB, and it doesn't mention to add
>> ActiveMQ jars,
>>
>> After adding the mentioned jars resolved the issue.
>>
>> Isn't it better to add as a prerequisite before configuring MB?.
>>
>> [1].
>> https://docs.wso2.com/display/ESB490/Configure+with+WSO2+Message+Broker
>>
>> Regards,
>> Aruna
>>
>> On Tue, May 10, 2016 at 2:01 PM, Jagath Sisirakumara Ariyarathne <
>> jaga...@wso2.com> wrote:
>>
>>> Hi Aruna,
>>>
>>> Did you add required jar files to lib folder as mentioned in[1].
>>>
>>> [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
>>>
>>> Thanks.
>>>
>>> On Tue, May 10, 2016 at 1:39 PM, Aruna Karunarathna <ar...@wso2.com>
>>> wrote:
>>>
>>>> Hi ESB team,
>>>>
>>>> When trying to invoke the JMSClient [1] getting the below error. Seems
>>>> like the activemq jar is not present in the classpath.
>>>>
>>>>  ant jmsclient -Djms_type=pox -Djms_dest=dynamicQueues/StockQuoteProxy
>>>> -Djms_payload=MSFT
>>>> Buildfile: /home/aruna//wso2esb-4.9.0/samples/axis2Client/build.xml
>>>>
>>>> init:
>>>>
>>>> compile:
>>>>
>>>> jmsclient:
>>>>  [java] Exception in thread "main"
>>>> javax.naming.NoInitialContextException: Cannot instantiate class:
>>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is
>>>> java.lang.ClassNotFoundException:
>>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory]
>>>>  [java] at
>>>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
>>>>  [java] at
>>>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
>>>>  [java] at
>>>> javax.naming.InitialContext.init(InitialContext.java:242)
>>>>  [java] at
>>>> javax.naming.InitialContext.(InitialContext.java:216)
>>>>  [java] at samples.userguide.GenericJMSClient.connect(Unknown
>>>> Source)
>>>>  [java] at samples.userguide.GenericJMSClient.main(Unknown Source)
>>>>  [java] Caused by: java.lang.ClassNotFoundException:
>>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory
>>>>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>>>>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>>>>  [java] at java.security.AccessController.doPrivileged(Native
>>>> Method)
>>>>  [java] at
>>>> java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>>>>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>>>>  [java] at
>>>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>>>>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>>>>  [java] at java.lang.Class.forName0(Native Method)
>>>>  [java] at java.lang.Class.forName(Class.java:270)
>>>>  [java] at
>>>> com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:72)
>>>>  [java] at
>>>> com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:61)
>>>>  [java] at
>>>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
>>>>  [java] ... 5 more
>>>>  [java] Java Result: 1
>>>>
>>>> BUILD SUCCESSFUL
>>>>
>>>> [1]. https://docs.wso2.com/display/ESB490/JMS+Transactions
>>>>
>>>> Regards,
>>>> Aruna
>>>> --
>>>>
>>>> *Aruna Sujith Karunarathna *
>>>> WSO2, Inc | lean. enterprise. middleware.
>>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>>>

Re: [Dev] ESB 4.9.0 JSM client error

[Jagath Sisirakumara Ariyarathne]

Hi Aruna,

Did you add required jar files to lib folder as mentioned in[1].

[1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ

Thanks.

On Tue, May 10, 2016 at 1:39 PM, Aruna Karunarathna  wrote:

> Hi ESB team,
>
> When trying to invoke the JMSClient [1] getting the below error. Seems
> like the activemq jar is not present in the classpath.
>
>  ant jmsclient -Djms_type=pox -Djms_dest=dynamicQueues/StockQuoteProxy
> -Djms_payload=MSFT
> Buildfile: /home/aruna//wso2esb-4.9.0/samples/axis2Client/build.xml
>
> init:
>
> compile:
>
> jmsclient:
>  [java] Exception in thread "main"
> javax.naming.NoInitialContextException: Cannot instantiate class:
> org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is
> java.lang.ClassNotFoundException:
> org.apache.activemq.jndi.ActiveMQInitialContextFactory]
>  [java] at
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
>  [java] at
> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
>  [java] at javax.naming.InitialContext.init(InitialContext.java:242)
>  [java] at javax.naming.InitialContext.(InitialContext.java:216)
>  [java] at samples.userguide.GenericJMSClient.connect(Unknown Source)
>  [java] at samples.userguide.GenericJMSClient.main(Unknown Source)
>  [java] Caused by: java.lang.ClassNotFoundException:
> org.apache.activemq.jndi.ActiveMQInitialContextFactory
>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>  [java] at java.security.AccessController.doPrivileged(Native Method)
>  [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>  [java] at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>  [java] at java.lang.Class.forName0(Native Method)
>  [java] at java.lang.Class.forName(Class.java:270)
>  [java] at
> com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:72)
>  [java] at
> com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:61)
>  [java] at
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
>  [java] ... 5 more
>  [java] Java Result: 1
>
> BUILD SUCCESSFUL
>
> [1]. https://docs.wso2.com/display/ESB490/JMS+Transactions
>
> Regards,
> Aruna
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting SynapseException when try to execute ESB after building it from source

[Jagath Sisirakumara Ariyarathne]

Hi Prakhash,

Once you built the product-esb repo locally, ESB pack will be created in
below location.

product-esb/modules/distribution/target/wso2esb-.zip


Unzip the pack and execute wso2server.sh file inside /repository/bin/
folder.

Thanks.

On Sun, May 8, 2016 at 6:43 PM, Prakhash Sivakumar 
wrote:

> Hi all,
> I'm trying to build ESB from the source, I'm getting the following error
> when I try to execute ./wso2server.sh command inside
> product-esb/modules/p2-profile/target/wso2carbon-core-4.4.5/bin/ after the
> build.
>
> org.apache.synapse.SynapseException: The synapse.xml location ././
> ./repository/deployment/server/synapse-configs
> /default doesn't exist
> at
> org.apache.synapse.SynapseControllerFactory.handleFatal(SynapseControllerFactory.java:121)
> at
> org.apache.synapse.SynapseControllerFactory.validatePath(SynapseControllerFactory.java:113)
> at
> org.apache.synapse.SynapseControllerFactory.validate(SynapseControllerFactory.java:88)
> at
> org.apache.synapse.SynapseControllerFactory.createSynapseController(SynapseControllerFactory.java:44)
> at org.apache.synapse.ServerManager.init(ServerManager.java:103)
> at
> org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:451)
> at
> org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:196)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> I checked for the the required synapse.xml file, there are no any files
> inside the location
> (/modules/p2-profile/target/wso2carbon-core-4.4.5/repository/deployment/server/synapse-configs/default)
>
> I tried to change the location axis2.xml file where I found synapse
>
> 
> ./repository/deployment/server/synapse-configs
> 
>
> still it is not working.Please guide me to do changes in these
> configuration files to execute it correctly
>
> Thanks
>
>
> --
> Prakhash Sivakumar
> Software Engineer
> WSO2 Inc: http://wso2.com
> Mobile : +94771510080
> Blog : https://medium.com/@PrakhashS
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: [ESB] Regarding an Error message

[Jagath Sisirakumara Ariyarathne]

Hi Ravindi,

I think you can use aggregate mediator[1] to construct a single response
using results from each iteration and send to the client as a single
response.

[1] -
https://docs.wso2.com/display/ESB480/Sample+400%3A+Message+Splitting+and+Aggregating+the+Responses

Thanks.

On Fri, Mar 18, 2016 at 3:41 AM, Nuwan Wimalasekara  wrote:

> Hi Ravindi,
>
> Why are you using both send(in outSequence) and respond(in iterate)
> mediators?
>
> Thanks,
> Nuwanw
>
> On Thu, Mar 17, 2016 at 8:54 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Ravindi,
>>
>> AFAIU this error happens due to the client gets a HTTP 202 accept
>> response, generated by ESB before it sends the original response from the
>> backend. Therefore ESB can't send the original response to the client as it
>> has already sent a "HTTP 202 accept" response.
>>
>>
>> On Thu, Mar 17, 2016 at 8:30 PM, Ravindi De silva 
>> wrote:
>>
>>> Hi  all,
>>>
>>>
>>> I tried writing a proxy service in the ESB to get the project details
>>> from jira using getProject method and then create that project in redmine
>>> using createProject if it is not already created in it. I have used the
>>> jira and redmine connectors in ESB. The proxy I have written is shown in
>>> [1].
>>>
>>> When I send the request to the proxy using SoapUI I get an error [2].
>>> But the project of which the details were taken from jira if not present in
>>> redmine has been created in it. How can I fix the issue of getting an error
>>> ?
>>>
>>>
>>> [1]
>>> http://ws.apache.org/ns/synapse;
>>>name="newConnectJiraRedmine"
>>>transports="http,https"
>>>statistics="disable"
>>>trace="disable"
>>>startOnLoad="true">
>>>
>>>   
>>>  >> expression="json-eval($.responseType)"/>
>>>  
>>>  
>>>  
>>>  
>>>  
>>>  >> expression="json-eval($.authSourceId)"/>
>>>  
>>>  
>>>  >> expression="json-eval($.identifier)"/>
>>>  >> expression="json-eval($.description)"/>
>>>  
>>>  
>>>  
>>>  
>>>  >> expression="json-eval($.priorityId)"/>
>>>  
>>>  >> expression="json-eval($.categoryId)"/>
>>>  >> expression="json-eval($.fixedVersionId)"/>
>>>  >> expression="json-eval($.assignedToId)"/>
>>>  >> expression="json-eval($.parentIssueId)"/>
>>>  >> expression="json-eval($.customFields)"/>
>>>  >> expression="json-eval($.watcherUserIds)"/>
>>>  
>>>  
>>>  
>>>  
>>>  
>>>  
>>>  
>>>  
>>>  
>>>  
>>>  >> expression="json-eval($.activityId)"/>
>>>  
>>>  >> expression="json-eval($.attachmentId)"/>
>>>  
>>>  
>>>  
>>>  
>>>  >>expression="json-eval($.jiraProjectName)"
>>>scope="operation"/>
>>>  >> type="STRING"/>
>>>  >>value="ravindi123"
>>>scope="default"
>>>type="STRING"/>
>>>  >>value="http://192.168.57.131:8080;
>>>scope="default"
>>>type="STRING"/>
>>>  >>value="TESPROJ"
>>>scope="default"
>>>type="STRING"/>
>>>  >>value="http://anthonyrava.m.redmine.org/;
>>>scope="default"
>>>type="STRING"/>
>>>  >>value="7855e5ee84e3f97b02e23ea96f3d69f740399860"
>>>scope="default"
>>>type="STRING"/>
>>>  >> type="STRING"/>
>>>  
>>> {$ctx:username}
>>> {$ctx:password}
>>> {$ctx:uri}
>>>  
>>>  
>>> {$ctx:projectIdOrKey}
>>>  
>>>  
>>>  >> expression="json-eval($.description)"/>
>>>  
>>>  
>>> >> expression="get-property('jPName')"/>
>>> >> expression="get-property('jPDecscription')"/>
>>> >> expression="get-property('jPId')"/>
>>>  
>>>  
>>> {$ctx:apiUrl}
>>> {$ctx:apiKey}
>>> {$ctx:responseType}
>>>  
>>>  
>>>  >>   id="activityTypes"
>>>   expression="//projects"
>>>   sequential="true">
>>> 
>>>
>>>   
>>>   
>>>  >> expression="get-property('jPName')"/>
>>>  >> expression="//identifier"/>
>>>  >> expression="get-property('rPName')"/>
>>>   
>>>   >> xpath="get-property('jPName')=get-property('rPName')">
>>>  
>>> 
>>>  

[Dev] WSO2 ESB 4.10.0 - Milestone 2 Released!

[Jagath Sisirakumara Ariyarathne]

*WSO2 ESB 4.10.0-Milestone 2 Released*

ESB Team is pleased to announce the WSO2 ESB 4.10.0 - Milestone 2 Release.
It contains following new features and bug fixes.

*New Features & Improvements*

   - Mediation Flow Statistics Feature
   - Message Flow Tracing Feature

*All resolved Issues*

Bugs

   - [ESBJAVA-4317 ] - Request
   time out when sending a PATCH request as a tenant user
   - [ESBJAVA-4331 ] - GET
   requests for API, results in missing JSON empty array from backend
   responses via the NHTTP transport
   - [ESBJAVA-4365 ] - Error
   when using a dynamic sequence with File Inbound


Improvements

   - [ESBJAVA-4354 ] - Add
   default mediation debugger ports to synapse.properties


The distribution is available to download at [1].

[1] -
https://svn.wso2.org/repos/wso2/scratch/ESB/packs/4.10.0-Releases/4.10.0-M2/

- WSO2 ESB Team -
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC3

[Jagath Sisirakumara Ariyarathne]

Hi,

Built latest ESB pack with all integration tests. No issues observed.

[x] Stable - go ahead and release

Thanks.

On Mon, Dec 14, 2015 at 10:08 AM, Maheshakya Wijewardena <
mahesha...@wso2.com> wrote:

> Hi,
>
> I have built ML 1.1.0 Beta pack including all tests with kernel 4.4.3 RC3.
> No issues found.
>
> [x] Stable - Go ahead and release.
>
> Best regards.
>
> On Mon, Dec 14, 2015 at 8:21 AM, Hasitha Aravinda 
> wrote:
>
>> Hi
>>
>> I have tested BPS 3.5.1-SNAPSHOT with kernel 4.4.3
>> ​ RC3​
>> ​
>> . No issue found.
>>
>> [x] Stable - Go ahead and release.
>>
>> Thanks
>> Hasitha.
>>
>> On Fri, Dec 11, 2015 at 8:15 PM, Nipuni Perera  wrote:
>>
>>>
>>> Hi Devs,
>>>
>>> This is the RC3 release candidate of WSO2 Carbon Kernel 4.4.3.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12540
>>>
>>> Please download and test your products with kernel 4.4.3 RC3
>>> and vote. Vote will be open for 72 hours or as longer as needed.
>>>
>>> *​Source and binary distribution files:*
>>> http://svn.wso2.org/repos/wso2/people/nipuni/4.4.3-rc3/
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-168/
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.3-RC3
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thank you
>>> Carbon Team
>>>
>>> --
>>> Nipuni Perera
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> Email: nip...@wso2.com
>>> Git hub profile: https://github.com/nipuni
>>> Blog : http://nipunipererablog.blogspot.com/
>>> Mobile: +94 (71) 5626680
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>> Hasitha Aravinda,
>> Senior Software Engineer,
>> WSO2 Inc.
>> Email: hasi...@wso2.com
>> Mobile : +94 718 210 200
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Pruthuvi Maheshakya Wijewardena
> Software Engineer
> WSO2 : http://wso2.com/
> Email: mahesha...@wso2.com
> Mobile: +94711228855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Carbon-mediation-4.5.0 Released

[Jagath Sisirakumara Ariyarathne]

Hi,

Carbon-mediation-4.5.0 released.

org.wso2.carbon.mediation
carbon-mediation
4.5.0

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 ESB 4.10.0 - Milestone 1 Released!

[Jagath Sisirakumara Ariyarathne]

*WSO2 ESB 4.10.0-Milestone 1 Released*

ESB Team is pleased to announce the WSO2 ESB 4.10.0 - Milestone 1 Release.
It contains following new features and bug fixes.

*New Features & Improvements*

   - JMS 2.0 support
   - Mediation debugging capability


*All resolved Issues*

Bugs

   - [ESBJAVA-3832 ] - "ERROR -
   TaskQuartzJobAdapter Error in executing task: null
   java.util.EmptyStackException" observed when publishing jms messages when
   the backend is restarted
   - [ESBJAVA-4142 ] - First
   request sent for tenants (after tenant unloading/ server restart) fails.
   - [ESBJAVA-4195 ] -
   [Standalone] Forwarding MP with interval value < 1000 ms and cron
   expression does not worrk as expected
   - [ESBJAVA-4229 ] - Java Heap
   Space error for huge file processing with Smooks mediator
   - [ESBJAVA-4235 ] - VFS stops
   working when scanning directory for files to read
   - [ESBJAVA-4250 ] - Getting
   NPE time to time when using loadbalnce endpoint
   - [ESBJAVA-4318 ] - Caching
   issue for XML body with processing instructions
   - [ESBJAVA-4333 ] -
   IllegalStateException when accessing APIs of tenants


Improvements

   - [ESBJAVA-4346 ] -
   Persisting content into registry from the mediation Layer


Patches

   - [ESBJAVA-4231 ] - Load
   balanced endpoint sending an empty payload to the failover endpoint


The distribution is available to download at [1].

[1] -
https://svn.wso2.org/repos/wso2/scratch/ESB/packs/4.10.0-Releases/4.10.0-M1/

- WSO2 ESB Team -
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Axis2-transports-1.1.1-wso2v1 Released

[Jagath Sisirakumara Ariyarathne]

Hi,

Axis2-transports-1.1.1-wso2v1 Released.

org.apache.axis2.transport
axis2-transports
1.1.1-wso2v1

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What does WARN "Couldn't find the mediation statistics store for tenant id" means?

[Jagath Sisirakumara Ariyarathne]

Hi Ishara,

According to the code[1] this occurs when statistics is not enabled in
carbon.xml.

true

[1] -
https://github.com/wso2/carbon-mediation/blob/master/components/mediation-monitor/mediation-statistics/org.wso2.carbon.mediation.statistics/src/main/java/org/wso2/carbon/mediation/statistics/MediationStatisticsServiceComponent.java

Thanks.

On Thu, Nov 12, 2015 at 5:36 PM, Ishara Cooray  wrote:

> Hi,
> $Subject please.
>
> Here is the full console log related to the warning message.
>
> WARN
> {org.wso2.carbon.mediation.statistics.MediationStatisticsServiceComponent}
> -  Couldn't find the mediation statistics store for tenant id: 718
> {org.wso2.carbon.mediation.statistics.MediationStatisticsServiceComponent}
>
>
> Thanks.
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Carbon-mediation-4.4.11 released

[Jagath Sisirakumara Ariyarathne]

Hi,

Carbon-mediation-4.4.11 released.

org.wso2.carbon.mediation
carbon-mediation
4.4.11

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] ESB 4.10 - Revamping mediation statistics and message tracing

[Jagath Sisirakumara Ariyarathne]

Hi,

I think it is better to have both aggregated and per node views. We can
send raw data with the node ID and aggregation can be done at DAS level.

To identity ESB node uniquely, can we use "SynapseConfig.ServerName" in
axis2.xml?

Thanks.

On Wed, Nov 11, 2015 at 9:59 AM, Kasun Indrasiri <ka...@wso2.com> wrote:

> Isn't Stats and tracing are two independent tasks?
>
>
> On Wed, Nov 11, 2015 at 9:55 AM, Viraj Senevirathne <vir...@wso2.com>
> wrote:
>
>> Hi All,
>>
>> In a clustered environment should we collect statistics of worker nodes
>> separately or should we represent them together as a one cluster?
>>
>> We probably need both. Once aggregated view and per node view for each
> worker node. WDYT?
>
>>
>>
>> On Wed, Nov 11, 2015 at 9:53 AM, Jagath Sisirakumara Ariyarathne <
>> jaga...@wso2.com> wrote:
>>
>>> Hi Inosh,
>>>
>>> Will there be two UI configuration sections for above? Both mediation
>>> stats and message tracing require same set of configurations like, DAS
>>> receiver URL and user credentials. Wouldn't it be better if we let the user
>>> to configure this information in single place?
>>>
>>> Yes, we can use same window for those. However, I think we will require
>>> two separate configurations for stat and tracing.
>>>
>>> WDYT?
>>>
>>> On Wed, Nov 11, 2015 at 12:06 AM, Inosh Goonewardena <in...@wso2.com>
>>> wrote:
>>>
>>>> Hi Viraj,
>>>>
>>>> On Mon, Nov 9, 2015 at 3:45 PM, Viraj Senevirathne <vir...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> We are planning to removing following features as we are introducing
>>>>> new improved features that enhance and extend the existing functionality.
>>>>>
>>>>> ESB 4.10.0 release will not have following sections in the management
>>>>> console UI.
>>>>>
>>>>> *Monitoring Section*
>>>>>
>>>>>- Mediation Statistics
>>>>>- SOAP Tracer
>>>>>- Mediation Tracer
>>>>>- Message Flows
>>>>>
>>>>> *Configure Section *
>>>>>
>>>>>- Mediation Data Publishing
>>>>>- BAM Server Profile
>>>>>
>>>>>
>>>>> ESB 4.10.0 release will contain following additions to management
>>>>> console.
>>>>>
>>>>> *Configure Section*
>>>>>
>>>>>- Mediation Statistics Publishing Configuration
>>>>>- Tracing Data Publishing Configuration
>>>>>
>>>>> Will there be two UI configuration sections for above? Both mediation
>>>> stats and message tracing require same set of configurations like, DAS
>>>> receiver URL and user credentials. Wouldn't it be better if we let the user
>>>> to configure this information in single place?
>>>>
>>>>>
>>>>>-
>>>>>
>>>>> ESB will publish tracing and statistic data to the DAS and users can
>>>>> monitor mediation statistics and message tracing results from DAS 
>>>>> dashboard.
>>>>>
>>>>> Thank you,
>>>>>
>>>>> On Mon, Nov 9, 2015 at 3:15 PM, Kasun Indrasiri <ka...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> As part of the ongoing efforts for revamping mediation statistics and
>>>>>> message tracing in ESB, we have to get rid of most of the existing UIs 
>>>>>> and
>>>>>> configurations in the ESB management console.
>>>>>>
>>>>>> Jagath/Viraj : Can you please list down the areas that we gonna
>>>>>> remove from ESB 4.10 and the new additions to support tracing and stats.
>>>>>>
>>>>>> Thanks,
>>>>>> Kasun.
>>>>>> --
>>>>>> Kasun Indrasiri
>>>>>> Software Architect
>>>>>> WSO2, Inc.; http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> cell: +94 77 556 5206
>>>>>> Blog : http://kasunpanorama.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Viraj Senevirathne
>>>>> Software Engineer; WSO2, Inc.
>>>>>
>>>>> Mobile : +94 71 958 0269
>>>>> Email : vir...@wso2.com
>>>>>
>>>>> ___
>>>>> Architecture mailing list
>>>>> architect...@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks & Regards,
>>>>
>>>> Inosh Goonewardena
>>>> Associate Technical Lead- WSO2 Inc.
>>>> Mobile: +94779966317
>>>>
>>>> ___
>>>> Architecture mailing list
>>>> architect...@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Jagath Ariyarathne
>>> Technical Lead
>>> WSO2 Inc.  http://wso2.com/
>>> Email: jaga...@wso2.com
>>> Mob  : +94 77 386 7048
>>>
>>>
>>
>>
>> --
>> Viraj Senevirathne
>> Software Engineer; WSO2, Inc.
>>
>> Mobile : +94 71 958 0269
>> Email : vir...@wso2.com
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] ESB 4.10 - Revamping mediation statistics and message tracing

[Jagath Sisirakumara Ariyarathne]

Hi Inosh,

Will there be two UI configuration sections for above? Both mediation stats
and message tracing require same set of configurations like, DAS receiver
URL and user credentials. Wouldn't it be better if we let the user to
configure this information in single place?

Yes, we can use same window for those. However, I think we will require two
separate configurations for stat and tracing.

WDYT?

On Wed, Nov 11, 2015 at 12:06 AM, Inosh Goonewardena  wrote:

> Hi Viraj,
>
> On Mon, Nov 9, 2015 at 3:45 PM, Viraj Senevirathne 
> wrote:
>
>> Hi All,
>>
>> We are planning to removing following features as we are introducing new
>> improved features that enhance and extend the existing functionality.
>>
>> ESB 4.10.0 release will not have following sections in the management
>> console UI.
>>
>> *Monitoring Section*
>>
>>- Mediation Statistics
>>- SOAP Tracer
>>- Mediation Tracer
>>- Message Flows
>>
>> *Configure Section *
>>
>>- Mediation Data Publishing
>>- BAM Server Profile
>>
>>
>> ESB 4.10.0 release will contain following additions to management console.
>>
>> *Configure Section*
>>
>>- Mediation Statistics Publishing Configuration
>>- Tracing Data Publishing Configuration
>>
>> Will there be two UI configuration sections for above? Both mediation
> stats and message tracing require same set of configurations like, DAS
> receiver URL and user credentials. Wouldn't it be better if we let the user
> to configure this information in single place?
>
>>
>>-
>>
>> ESB will publish tracing and statistic data to the DAS and users can
>> monitor mediation statistics and message tracing results from DAS dashboard.
>>
>> Thank you,
>>
>> On Mon, Nov 9, 2015 at 3:15 PM, Kasun Indrasiri  wrote:
>>
>>> Hi,
>>>
>>> As part of the ongoing efforts for revamping mediation statistics and
>>> message tracing in ESB, we have to get rid of most of the existing UIs and
>>> configurations in the ESB management console.
>>>
>>> Jagath/Viraj : Can you please list down the areas that we gonna remove
>>> from ESB 4.10 and the new additions to support tracing and stats.
>>>
>>> Thanks,
>>> Kasun.
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> Viraj Senevirathne
>> Software Engineer; WSO2, Inc.
>>
>> Mobile : +94 71 958 0269
>> Email : vir...@wso2.com
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Thanks & Regards,
>
> Inosh Goonewardena
> Associate Technical Lead- WSO2 Inc.
> Mobile: +94779966317
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Synapse-2.1.4-wso2v1 Released

[Jagath Sisirakumara Ariyarathne]

Hi,

Please note $subject.

org.apache.synapse
Apache-Synapse
2.1.4-wso2v1

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Missing dependency when migrating ESB to Identity 5.0.0 from 4.5.6

[Jagath Sisirakumara Ariyarathne]

Hi,

We faced below dependency issue while updating identity version to 5.0.0
from 4.5.6.

Software being installed: STS Feature 5.0.0
(org.wso2.carbon.sts.feature.group 5.0.0)
 Missing requirement: openid4java 1.0.0.wso2v2 (openid4java 1.0.0.wso2v2)
requires 'package net.sf.ehcache [1.5.0,1.6.0)' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Identity Provider 5.0.0
(org.wso2.carbon.identity.provider 5.0.0)
  To: package org.openid4java [1.0.0,2.0.0)
 Cannot satisfy dependency:
  From: org.wso2.carbon.identity.sts.mgt 5.0.0
(org.wso2.carbon.identity.sts.mgt 5.0.0)
  To: package org.wso2.carbon.identity.provider [5.0.0,6.0.0)
 Cannot satisfy dependency:
  From: STS Feature 5.0.0 (org.wso2.carbon.sts.feature.group 5.0.0)
  To: org.wso2.carbon.sts.server.feature.group [5.0.0]
 Cannot satisfy dependency:
  From: STS Core Feature 5.0.0 (org.wso2.carbon.sts.server.feature.group
5.0.0)
  To: org.wso2.carbon.identity.sts.mgt [5.0.0]

How can we solve this issue?

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in carbon logs after changing carbon.kernel.version from 4.4.1 to 4.4.2

[Jagath Sisirakumara Ariyarathne]

Hi Carbon Team,

Any thought to figure out the issue is much appreciated.

Thanks.

On Wed, Oct 28, 2015 at 3:42 PM, Viraj Senevirathne  wrote:

> Hi All,
>
> We have upgraded the carbon version in ESB from 4.4.1 to 4.4.2. Then we
> have encountered following issue.
>
> *In carbon.kernel.version 4.4.1 and earlier carbon versions*
>
> TID: [-1234] [] [2015-10-23 16:43:26,614]  INFO
> {org.apache.synapse.mediators.builtin.LogMediator} -  To:
> /services/sendReciveProxy.sendReciveProxyHttpSoap11Endpoint, WSAction:
> urn:getQuote, SOAPAction: urn:getQuote, MessageID:
> urn:uuid:333b6811-04aa-4c6a-94fb-3edc4d56065d, Direction: request,
> Envelope:  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd="
> http://services.samples/xsd; xmlns:ser="http://services.samples
> ">
>   
>  
>  
> 
> IBM
>  
>   
>
> {org.apache.synapse.mediators.builtin.LogMediator}
>
> *Same log in carbon.kernel.version 4.4.2 *
>
> [2015-10-28 15:38:36,027]  INFO - LogMediator To:
> /services/callOutOnly.callOutOnlyHttpSoap11Endpoint, WSAction: urn:mediate,
> SOAPAction: urn:mediate, MessageID:
> urn:uuid:61f4b04c-0906-4228-975e-1b8f1be7450d, Direction: request,
> Envelope:  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/; xmlns:wsa="
> http://www.w3.org/2005/08/addressing;>_
> http://services.samples;>__
>  3.141593E0_4_
>IBM__
>  _   (Sanitized)
>
>
> As you can see all the new lines are replaced with _ .
>
> What could be the issue here?
>
> Thank you,
>
> --
> Viraj Senevirathne
> Software Engineer; WSO2, Inc.
>
> Mobile : +94 71 958 0269
> Email : vir...@wso2.com
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] EmptyStackException when resuming a paused message processor

[Jagath Sisirakumara Ariyarathne]

;>>>>>> }
>>>>>>>
>>>>>>> Within the above method following line causes the issue.
>>>>>>>
>>>>>>> PrivilegedCarbonContext.destroyCurrentContext();
>>>>>>>
>>>>>>> When this method is called, it will reset the *parentContextHolderStack
>>>>>>> *and the initial object push into the stack is destroyed. Then
>>>>>>> after tenant loading, within the
>>>>>>> MultitenantMessageReceiver.processRequest() method, it tries to end the
>>>>>>> tenant flow within finally block and try to pop the object which it 
>>>>>>> pushes
>>>>>>> early. But right now, we have a new context stack and it will throw the
>>>>>>> emptyStackException due to that.
>>>>>>>
>>>>>>> @Sameera/KasunG: Do we really need to use the following code segment
>>>>>>> within the above method?
>>>>>>>
>>>>>>>
>>>>>>> *PrivilegedCarbonContext.destroyCurrentContext();*
>>>>>>>
>>>>>>> I saw this method called within carbon-mediation components in 3
>>>>>>> different locations. AFAIU, we don't need to destroy the current context
>>>>>>> when we are accessing the ThreadLocalContext. Please share your thoughts
>>>>>>> such that we can fix this issue. Issue is fixed when I comment out the
>>>>>>> above line :)
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Chanaka
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 7, 2015 at 5:34 PM, Chanaka Fernando <chana...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Sameera/KasunG,
>>>>>>>>
>>>>>>>> I have debugged the code to find the root cause for this empty
>>>>>>>> stack exception. This is causing several other issues at the ESB layer.
>>>>>>>> What actually happens is that inside the
>>>>>>>> MultitenantMessageReceiver.processRequest() method, we have the 
>>>>>>>> following
>>>>>>>> code segment.
>>>>>>>>
>>>>>>>> try {
>>>>>>>> PrivilegedCarbonContext.startTenantFlow();
>>>>>>>> PrivilegedCarbonContext privilegedCarbonContext = 
>>>>>>>> PrivilegedCarbonContext.getThreadLocalCarbonContext();
>>>>>>>> privilegedCarbonContext.setTenantDomain(tenantDomain, true);
>>>>>>>> // this is to prevent non-blocking transports from sending 202
>>>>>>>> 
>>>>>>>> mainInMsgContext.getOperationContext().setProperty(Constants.RESPONSE_WRITTEN,
>>>>>>>>  "SKIP");
>>>>>>>>
>>>>>>>> ConfigurationContext tenantConfigCtx =
>>>>>>>>
>>>>>>>> TenantAxisUtils.getTenantConfigurationContext(tenantDomain,
>>>>>>>>
>>>>>>>>   mainConfigCtx);
>>>>>>>> if (tenantConfigCtx == null) {
>>>>>>>> // Throw AxisFault: Tenant does not exist
>>>>>>>> handleException(mainInMsgContext, new AxisFault("Tenant " + 
>>>>>>>> tenantDomain +
>>>>>>>> "  not 
>>>>>>>> found"));
>>>>>>>> return;
>>>>>>>> }
>>>>>>>>
>>>>>>>> if (mainInMsgContext.isDoingREST()) { // Handle REST requests
>>>>>>>> doREST(mainInMsgContext, to, tenantDomain, tenantConfigCtx, 
>>>>>>>> serviceAndOperation);
>>>>>>>> } else {
>>>>>>>> doSOAP(mainInMsgContext, tenantDomain, tenantConfigCtx, 
>>>>>>>> serviceAndOperation);
>>>>>>>> }
>>>>>>>> } finally {
>>>>>>>>  

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC6

[Jagath Sisirakumara Ariyarathne]

Hi All,

Following scenarios were tested in RC6 pack.

   - Dynamic SSL profiles
   - Apply custom profiles for senders/listeners
  - Updating key store/trust store at runtime
  - Profile re-loading from time interval and JMX
  - SSL and Mutual SSL connections with back-end
  - Enable/disable Mutual SSL with clients at runtime
   - Basic Performance Test
   - Https Inbound for both SSL and Mutual SSL

[+] Stable - go ahead and release

Thanks.

On Thu, Sep 10, 2015 at 12:50 PM, Nadeeshaan Gunasinghe  wrote:

> Hi all,
> I tested the following areas
>
> JMS Transport and inbound use cases in standalone and in a cluster
> - JMS consumer side transaction
> - JMS Dual Channel transaction
> - JMS Quad Channel transaction
>
> VFS Transport and inbound use case in standalone and in a cluster
>- File system to file system transactions
>- File system to ftp, ftp to file system transactions
>
> [+] Stable - go ahead and release
>
> Regards
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#14fb620b6ace39a8_>
> 
>   
> 
> Get a signature like this: Click here!
> 
>
> On Thu, Sep 10, 2015 at 1:16 AM, Chanaka Fernando 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 ESB 4.9.0 RC6 Release Vote
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12393
>>
>> Please download ESB 4.9.0 RC6 and test the functionality and vote. Vote
>> will be open for 72 hours or as needed.
>>
>> Source & binary distribution files:
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-068/org/wso2/esb/wso2esb/4.9.0/
>>
>> Maven staging repository:
>> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-068/
>>
>> The tag to be voted upon :
>> https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC6
>>
>>
>> [-] Broken - do not release (explain why)
>> [+] Stable - go ahead and release
>>
>> Thanks and Regards,
>> ~ WSO2 ESB Team ~
>>
>> --
>> --
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC4

[Jagath Sisirakumara Ariyarathne]

Hi All,

I have tested below functionalities in the RC4 pack.

   - Dynamic SSL Profiles
   - Sender profiles with back-end - SSL/Mutual SSL
  - Listener profiles with clients - SSL/Mutual SSL
  - Re-loading from time interval and JMX
   - Basic performance test

[X] Stable - go ahead and release

Thanks.

On Tue, Sep 8, 2015 at 5:40 PM, Senduran Balasubramaniyam <sendu...@wso2.com
> wrote:

> Hi All,
>
> I have tested the following in both standalone and cluster mode with
> tenants, and found no issues
>
>- Inmemeory MessageStore (in standalone mode)
>- JMS MessageStore
>- RabbitMQ MessageStore
>- JDBC MessageStore
>- Scheduled Message Forwarding Processor
>- Scheduled Failover Message Forwarding Processor
>- Message Sampling Processor
>
> [+] Stable - go ahead and release
>
> Thanks
> Senduran
>
>
> On Tue, Sep 8, 2015 at 1:08 AM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> WSO2 ESB 4.9.0 RC4 Release Vote
>>
>> This release fixes the following issues:
>> *https://wso2.org/jira/issues/?filter=12393
>> <https://wso2.org/jira/issues/?filter=12393>*
>>
>> Please download ESB 4.9.0 RC4 and test the functionality and vote. Vote will
>> be open for 72 hours or as needed.
>>
>> *Source & binary distribution files:*
>> *http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/org/wso2/esb/wso2esb/4.9.0-RC4/
>> <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/org/wso2/esb/wso2esb/4.9.0-RC4/>*
>>
>> *Maven staging repository:*
>> *http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/
>> <http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/>*
>>
>> *The tag to be voted upon :*
>> *https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC4
>> <https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC4>*
>>
>>
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>>
>> Thanks and Regards,
>> ~ WSO2 ESB Team ~
>>
>> --
>> Jagath Ariyarathne
>> Technical Lead
>> WSO2 Inc.  http://wso2.com/
>> Email: jaga...@wso2.com
>> Mob  : +94 77 386 7048
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Senduran *
> Software Engineer,
> WSO2, Inc.;  http://wso2.com/ <http://wso2.com/>
> Mobile: +94 77 952 6548
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 ESB 4.9.0 RC4

[Jagath Sisirakumara Ariyarathne]

Hi Devs,

WSO2 ESB 4.9.0 RC4 Release Vote

This release fixes the following issues:
*https://wso2.org/jira/issues/?filter=12393
*

Please download ESB 4.9.0 RC4 and test the functionality and vote. Vote will
be open for 72 hours or as needed.

*Source & binary distribution files:*
*http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/org/wso2/esb/wso2esb/4.9.0-RC4/
*

*Maven staging repository:*
*http://maven.wso2.org/nexus/content/repositories/orgwso2esb-058/
*

*The tag to be voted upon :*
*https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC4
*


[+] Stable - go ahead and release
[-] Broken - do not release (explain why)


Thanks and Regards,
~ WSO2 ESB Team ~

-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC1

[Jagath Sisirakumara Ariyarathne]

Hi,

I executed performance tests for basic scenarios with this pack. No issues
observed.

[X] Stable - go ahead and release

Thanks.

On Mon, Aug 24, 2015 at 10:27 PM, Chanaka Fernando chana...@wso2.com
wrote:

 Hi Devs,

 WSO2 ESB 4.9.0 RC1 Release Vote

 This release fixes the following issues:
 https://wso2.org/jira/browse/ESBJAVA-4093?filter=12363

 Please download ESB 490 RC1 and test the functionality and vote. Vote will
 be open for 72 hours or as needed.

 *Source  binary distribution files:*

 http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/org/wso2/esb/wso2esb/4.9.0-RC1/

 *Maven staging repository:*
 http://maven.wso2.org/nexus/content/repositories/orgwso2esb-051/

 *The tag to be voted upon :*
 https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC1


 [ ] Broken - do not release (explain why)
 [ ] Stable - go ahead and release


 Thanks and Regards,
 ~ WSO2 ESB Team ~

 --
 --
 Chanaka Fernando
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Carbon-mediation 4.4.4 Released

[Jagath Sisirakumara Ariyarathne]

Hi All,

org.wso2.carbon.mediation version 4.4.4 released.

groupIdorg.wso2.carbon.mediation/groupId
artifactIdcarbon-mediation/artifactId
version4.4.4/version


Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Synapse 2.1.3-wso2v7 Released!

[Jagath Sisirakumara Ariyarathne]

Hi All,

org.apache.synapse version 2.1.3-wso2v7 released.

groupIdorg.apache.synapse/groupId
artifactIdApache-Synapse/artifactId
version2.1.3-wso2v7/version


Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Axis2 Transport 1.1.0-wso2v16 Released!

[Jagath Sisirakumara Ariyarathne]

Hi All,

Axis2 Transport version 1.1.0-wso2v16 Released.

groupIdorg.apache.axis2.transport/groupId
artifactIdaxis2-transports/artifactId
version1.1.0-wso2v16/version


Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture] WSO2 ESB v4.9.0 Beta Released!

[Jagath Sisirakumara Ariyarathne]

*WSO2 ESB 4.9.0-BETA Released*

ESB team is pleased to announce the release of the WSO2 ESB 4.9.0-BETA .
This release includes following bug-fixes, improvements and features.

Bugs

   - [ESBJAVA-1148 https://wso2.org/jira/browse/ESBJAVA-1148] -
   [Scheduled Tasks] UI issues if cron expression is faulty
   - [ESBJAVA-1903 https://wso2.org/jira/browse/ESBJAVA-1903] - Malformed
   XML not being detected in VFS Proxy
   - [ESBJAVA-2063 https://wso2.org/jira/browse/ESBJAVA-2063] -
   [intermittent] wso2statistics.request.received.time is null in the IN
   MessageContext
   - [ESBJAVA-2089 https://wso2.org/jira/browse/ESBJAVA-2089] - XQuery
   mediator, Target value cannot be removed from the UI, but only with source
   view
   - [ESBJAVA-2165 https://wso2.org/jira/browse/ESBJAVA-2165] - VFS
   Transport: Sample 254: Placing an incorrect xml not moving to Failure folder
   - [ESBJAVA-2225 https://wso2.org/jira/browse/ESBJAVA-2225] - One way
   operations are failing for tenant's proxy/api in stratos esb
   - [ESBJAVA-2251 https://wso2.org/jira/browse/ESBJAVA-2251] - Context
   sensitive Help should contain details for HTTP end point
   - [ESBJAVA-2254 https://wso2.org/jira/browse/ESBJAVA-2254] - QoS
   properties do not get synchronized properly to worker nodes
   - [ESBJAVA-2290 https://wso2.org/jira/browse/ESBJAVA-2290] - ESB 4.6 -
   DBLookup mediator not working in UI mode
   - [ESBJAVA-2302 https://wso2.org/jira/browse/ESBJAVA-2302] - [ESB 4.7]
   Design view error for DB* Mediators when datasource(postgres) is added
   - [ESBJAVA-2330 https://wso2.org/jira/browse/ESBJAVA-2330] - Couldn't
   send a request to Tenant main sequence
   - [ESBJAVA-2348 https://wso2.org/jira/browse/ESBJAVA-2348] - End point
   getting suppended
   - [ESBJAVA-2351 https://wso2.org/jira/browse/ESBJAVA-2351] - [ESB 4.7]
   Message Stores in C-App deployed with errors
   - [ESBJAVA-2450 https://wso2.org/jira/browse/ESBJAVA-2450] - JMS
   Message Store Edit Message Store name (switching to source view and vise
   verse)
   - [ESBJAVA-2461 https://wso2.org/jira/browse/ESBJAVA-2461] - Printing
   an unnecessary log in the console when browsing connector operations
   - [ESBJAVA-2531 https://wso2.org/jira/browse/ESBJAVA-2531] -
   [Intermittent] NPE and blank page when save  close while editing the proxy
   - [ESBJAVA-2534 https://wso2.org/jira/browse/ESBJAVA-2534] - If you
   change a the endpoint of a target in a clone mediator all the targets get
   saved with that endpoint
   - [ESBJAVA-2536 https://wso2.org/jira/browse/ESBJAVA-2536] - Filter
   mediator UI(Design View) failed to load configuration once xpath contain
   get-property() function
   - [ESBJAVA-2539 https://wso2.org/jira/browse/ESBJAVA-2539] - ERROR -
   JDBCLogsDAO Failed to update log batch records returned when starting the
   servers after switching databases
   - [ESBJAVA-2641 https://wso2.org/jira/browse/ESBJAVA-2641] - When a
   Non-existing Local Entry is Found in Proxy Deployment, Attempt to Deploy
   the Local Entry Fails Next Time
   - [ESBJAVA-2663 https://wso2.org/jira/browse/ESBJAVA-2663] -
   WstxParsingException: Illegal to have multiple roots (start tag in epilog?)
   occurs when backend service is inactive in PTT
   - [ESBJAVA-2668 https://wso2.org/jira/browse/ESBJAVA-2668] - Connector
   deployment in tenant mode not working in Windows environment
   - [ESBJAVA-2674 https://wso2.org/jira/browse/ESBJAVA-2674] - Update
   help content on message store/message processor according to the new changes
   - [ESBJAVA-2759 https://wso2.org/jira/browse/ESBJAVA-2759] - Deployed
   Message store and Message Processor details does not showing on the CApp
   dashboard
   - [ESBJAVA-2763 https://wso2.org/jira/browse/ESBJAVA-2763] - Observing
   ERROR - CarbonDeploymentSchedulerTask Error while running deployment
   scheduler.. java.lang.NullPointerException
   - [ESBJAVA-2791 https://wso2.org/jira/browse/ESBJAVA-2791] - Observing
   Errors on worker nodes when Activate and Deactivate message processors on
   cluster setup
   - [ESBJAVA-2800 https://wso2.org/jira/browse/ESBJAVA-2800] -
   WSO2-ESB-4.5.0-SamplesSetup.pdf document inside samples folder should be
   WSO2-ESB-4.8.0-SamplesSetup.pdf
   - [ESBJAVA-2812 https://wso2.org/jira/browse/ESBJAVA-2812] - the
   protocol if http the source view for API shows as 1 and for https the
   source view shows as 2
   - [ESBJAVA-2833 https://wso2.org/jira/browse/ESBJAVA-2833] - JMS
   message selectors cannot be specified at the ui
   - [ESBJAVA-2840 https://wso2.org/jira/browse/ESBJAVA-2840] - Wso2 esb
   4.8.0 is not working for repository rule or saved rule
   - [ESBJAVA-2865 https://wso2.org/jira/browse/ESBJAVA-2865] -
   Sanitizing generated temp files by WSO2 ESB XSLT Mediator
   - [ESBJAVA-2897 https://wso2.org/jira/browse/ESBJAVA-2897] - hl7 flow
   does not seem to work if the proxy created on esb is secured with ex:user
   name token
   - [ESBJAVA-2901 https://wso2.org/jira/browse/ESBJAVA-2901] - Faulty
   

[Dev] Synapse 2.1.3-wso2v6 Released!

[Jagath Sisirakumara Ariyarathne]

Hi All,

org.apache.synapse version 2.1.3-wso2v6 released.

groupIdorg.apache.synapse/groupId
artifactIdApache-Synapse/artifactId
version2.1.3-wso2v6/version

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Axis2 Transport 1.1.0-wso2v15 Released!

[Jagath Sisirakumara Ariyarathne]

Hi All,

Axis2 Transport version 1.1.0-wso2v15 Released.

groupIdorg.apache.axis2.transport/groupId
artifactIdaxis2-transports/artifactId
version1.1.0-wso2v15/version

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please release the staging repo for carbon-commons

[Jagath Sisirakumara Ariyarathne]

Hi Supun,

We need below PR[1] merged before carbon-deployment release.

[1] - https://github.com/wso2/carbon-deployment/pull/104

Thanks.

On Wed, Aug 5, 2015 at 9:51 AM, Supun Malinga sup...@wso2.com wrote:

 Hi Chanaka,

 We haven't started the carbon-deployment release yet since we have to do
 it after multitenancy release.. I think we can start working on that today..

 thanks,

 On Wed, Aug 5, 2015 at 9:42 AM, Chanaka Fernando chana...@wso2.com
 wrote:

 Hi Supun,

 We will test the carbon-commons repo[1] with the ESB and let you know.
 Could you please share the staging repo for the carbon-deployment also if
 there is any?

 [1]
 http://maven.wso2.org/nexus/content/repositories/orgwso2carboncommons-001/

 Thanks,
 Chanaka

 On Wed, Aug 5, 2015 at 9:25 AM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 Verified carbon-deployment.

 We still use carbon-commons user mgt components.
 @Johann we would need a carbon-identity release since we have moved user
 mgt stuff into identity. Can we do this after commons is released ?.

 thanks,

 On Tue, Aug 4, 2015 at 6:59 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 Guys can you build your respective repos pointing to the staging repo
 and verify this ?.
 I will look into carbon-deployment and product-as.

 thanks,

 On Tue, Aug 4, 2015 at 6:56 PM, KasunG Gajasinghe kas...@wso2.com
 wrote:

 Hi Supun,

 Closed the repo, please verify -
 http://maven.wso2.org/nexus/content/repositories/orgwso2carboncommons-001/

 On Tue, Aug 4, 2015 at 6:54 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 $subject pls.

 thanks,
 --
 Supun Malinga,

 Senior Software Engineer,
 WSO2 Inc.
 http://wso2.com
 email: sup...@wso2.com sup...@wso2.com
 mobile: +94 (0)71 56 91 321




 --

 *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
 email: kasung AT spamfree wso2.com
 linked-in: http://lk.linkedin.com/in/gajasinghe
 blog: http://kasunbg.org






 --
 Supun Malinga,

 Senior Software Engineer,
 WSO2 Inc.
 http://wso2.com
 email: sup...@wso2.com sup...@wso2.com
 mobile: +94 (0)71 56 91 321




 --
 Supun Malinga,

 Senior Software Engineer,
 WSO2 Inc.
 http://wso2.com
 email: sup...@wso2.com sup...@wso2.com
 mobile: +94 (0)71 56 91 321




 --
 --
 Chanaka Fernando
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com






 --
 Supun Malinga,

 Senior Software Engineer,
 WSO2 Inc.
 http://wso2.com
 email: sup...@wso2.com sup...@wso2.com
 mobile: +94 (0)71 56 91 321

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Issue when using secure vault with ESB 4.9.0

[Jagath Sisirakumara Ariyarathne]

Hi Niranjan,

I followed below steps to secure passwords in axis2.xml keystores with ESB
4.9.0-BETA-SNAPSHOT built with cipher tool 1.0.0-wso2v3.

1. Added axis2 configuration entries to cipher-tool.properties file.

Axis2.Https.Listener.TrustStore.Password=repository/conf/axis2/axis2.xml//axisconfig/transportReceiver[@name='https']/parameter[@name='truststore']/TrustStore/Password,false
Axis2.Https.Listener.KeyStore.Password=repository/conf/axis2/axis2.xml//axisconfig/transportReceiver[@name='https']/parameter[@name='keystore']/KeyStore/Password,false

2. Executed cipher text configuration command ./ciphertool.sh -Dconfigure.
It updated axis2.xml with given aliases.

parameter locked=false name=truststore

TrustStore


Locationrepository/resources/security/client-truststore.jks/Location

TypeJKS/Type

Password
svns:secretAlias=Axis2.Https.Listener.TrustStore.Passwordpassword/Password

/TrustStore
/parameter

3. But encrypted keys updated in cipher-text.properties file only for
existing entries. Not for the new axis2 entries configured above.
4. Also ESB gives error java.io.IOException: Keystore was tampered with,
or password was incorrect at startup.

Is there any missing in my procedure?

Also I experienced below error when running integration tests in ESB 4.9.0
with kernel 4.4.1 RC1. It did not occur with kernel 4.4.0. Would it be due
to any missing information in catalina-server.xml?

INFO  [org.wso2.carbon.integration.common.extensions.utils.ServerLogReader]
- org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference
a node in a context where it does not exist.
INFO  [org.wso2.carbon.integration.common.extensions.utils.ServerLogReader]
- at org.apache.xerces.dom.AttributeMap.internalRemoveNamedItem(Unknown
Source)
INFO  [org.wso2.carbon.integration.common.extensions.utils.ServerLogReader]
- at org.apache.xerces.dom.AttributeMap.removeNamedItem(Unknown Source)
INFO  [org.wso2.carbon.integration.common.extensions.utils.ServerLogReader]
- at
org.wso2.carbon.tomcat.internal.ServerManager.init(ServerManager.java:85)


Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Extract SSL certificate information from org.apache.http.nio.reactor.ssl.SSLIOSession

[Jagath Sisirakumara Ariyarathne]

Hi,

I am working on JIRA issue[1] and need to extract SSL session's
certificate from
SSLIOSession and set it to Axis2MessageContext. With the patch done in[2],
we can obtain this from ssl.client.auth.cert.X509 attribute in
httpcore-nio_4.2.3.


But the latest ESB 4.9.0 is using httpcore-nio_4.3.3. Rather than updating
in httpcore-nio, we can get this information directly from SSLIOSession at
ServerWorker level and set it to message context. Is there any problem with
this approach?

[1] - https://wso2.org/jira/browse/ESBJAVA-3857
[2] - https://wso2.org/jira/browse/ESBJAVA-2390

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Extract SSL certificate information from org.apache.http.nio.reactor.ssl.SSLIOSession

[Jagath Sisirakumara Ariyarathne]

Thanks Asela. I will proceed with the change.


On Mon, Jul 20, 2015 at 1:20 PM, Asela Pathberiya as...@wso2.com wrote:

 On Mon, Jul 20, 2015 at 12:44 PM, Jagath Sisirakumara Ariyarathne
 jaga...@wso2.com wrote:
  Hi,
 
  I am working on JIRA issue[1] and need to extract SSL session's
 certificate
  from SSLIOSession and set it to Axis2MessageContext. With the patch done
  in[2], we can obtain this from ssl.client.auth.cert.X509 attribute in
  httpcore-nio_4.2.3.
 
  But the latest ESB 4.9.0 is using httpcore-nio_4.3.3. Rather than
 updating
  in httpcore-nio, we can get this information directly from SSLIOSession
 at
  ServerWorker level and set it to message context. Is there any problem
 with
  this approach?

 Yes. It would be fine.. If it is available for Axis2 handlers.. AFAIK,
 this property is read by Axis2 handlers (rampart)..

 Thanks,
 Asela.

 
  [1] - https://wso2.org/jira/browse/ESBJAVA-3857
  [2] - https://wso2.org/jira/browse/ESBJAVA-2390
 
  Thanks.
  --
  Jagath Ariyarathne
  Technical Lead
  WSO2 Inc.  http://wso2.com/
  Email: jaga...@wso2.com
  Mob  : +94 77 386 7048
 



 --
 Thanks  Regards,
 Asela

 ATL
 Mobile : +94 777 625 933
  +358 449 228 979

 http://soasecurity.org/
 http://xacmlinfo.org/




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon-deployment 4.4.2 Release date

[Jagath Sisirakumara Ariyarathne]

Hi Sameera,

Following PR needs to be merged before the release.

https://github.com/wso2/carbon-deployment/pull/104

Thanks.

On Fri, Jul 10, 2015 at 11:23 AM, Sameera Jayasoma same...@wso2.com wrote:

 Hi Kasun,

 We will work on this.

 Sameera.


 On Thu, Jul 9, 2015 at 9:41 AM, Kasun Indrasiri ka...@wso2.com wrote:

 Hi Kernel team,

 We are blocked on ESB beta release because of not having service
 activation/deactivation. There is no point of adding this to AS without
 adding this to ESB (this feature is mostly used with ESB than AS). So, can
 we please get a carbon-deployment release based-on kernel 4.4 with this
 feature.


 On Mon, Jul 6, 2015 at 12:10 PM, Kasun Indrasiri ka...@wso2.com wrote:

 Hi,

 Any updates on this?

 On Wed, Jun 24, 2015 at 11:59 AM, Kasun Indrasiri ka...@wso2.com
 wrote:

 We probably need a release of carbon-deployment earlier than that,
 because ESB GA release is planned on mid July. Most of the service
 activation/deactivation features will be mainly used with Proxy service.

 On Wed, Jun 24, 2015 at 11:22 AM, Jayanga Dissanayake jaya...@wso2.com
  wrote:

 Hi Prabath,

 Carbon-deployment 4.4.2 will be released on mid July, in parallel with
 WSO2AS RC releases.
 Changes related to proxy service Activate/Deactivate feature is
 merged into master branch and available in 4.4.2-SNAPSHOT

 Thanks,
 Jayanga.


 *Jayanga Dissanayake*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

 On Wed, Jun 24, 2015 at 11:14 AM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Carbon Team.

 We are planning to release proxy service Activate/Deactivate feature
 with the ESB 4.9 release and AFAIK it has already been added to the
 carbon-deployment 4.4.2-SNAPSHOT.
 When you plan to release it?


 Thanks.
 --

 *Prabath Ariyarathna*

 *Associate Technical Lead*

 *WSO2, Inc. *

 *lean . enterprise . middleware *


 *Email: prabat...@wso2.com 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 *









 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/




 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/




 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/




 --
 Sameera Jayasoma,
 Software Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://blog.sameera.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 0094776364456

 Lean . Enterprise . Middleware




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge PR[1] for JIRA issues [2] and [3].

[1] - https://github.com/wso2/wso2-synapse/pull/251
[2] - https://wso2.org/jira/browse/ESBJAVA-3891
[3] - https://wso2.org/jira/browse/ESBJAVA-3892

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Automation Test coverage of ESB 4.9.0 new features

[Jagath Sisirakumara Ariyarathne]

Hi Asanthi,

Automated test cases for following feature can be found in [1].

   - Dynamic SSL Profiles for sender and listener

[1] - https://github.com/wso2/product-esb/pull/203

Thanks.

On Fri, Jul 10, 2015 at 11:34 AM, Chanaka Fernando chana...@wso2.com
wrote:

 Hi Asanthi,

 Updated the RM with automation test details for following. This has
 already been merged and available in the product-esb integration tests.


- Support HTTP Patch


 On Fri, Jul 10, 2015 at 10:12 AM, Asanthi Kulasinghe asan...@wso2.com
 wrote:

 Hi  ESB Team,

 We are currently in the process of analyzing gaps between ESB 4.9.0
 manually executed and automated test cases.
 As a start we are looking into to the automation test case coverage of
 4.9.0 specific new features.
 Out of the feature list from [1] we couldn't find automation tests for
 some of the features mentioned below.

 *Features with automation tests*

- Add RabbitMQ transport receiver/sender
- Persisting Messages from ESB Message Store {jdbc storage to work
with MSSQL}
- Supporting Class mediators in Stratos
- OCSP/CRL Validation at Transport Listener
- Enabling HTTP Cache Control headers (Etag, etc)
- Coordination support for Message Stores and Processors
- For-each mediator
- Inbound Endpoints :

- Inbound HL7 Endpoint
- HTTP Inbound Endpoint
- HTTPS Inbound Endpoint
- HTTPS Inbound Endpoint
- CXF WS-RM Inbound Endpoint
- JMS
- File
- Custom

 *Features without automation tests*

- Dynamic SSL Profiles for sender and listener
- Support HTTP Patch
- HTTP HEAD Method support for REST API's
- Inbound Endpoints:

   - Kafka support in ESB
   - MQTT Inbound transport

 To my understanding there are tests for some of the above features that
 are yet to be merged.
 Could you please confirm the accuracy of the above lists (automation test
 availability)  and reason for the absence of automation tests for certain
 features  (Eg:  Not yet merged,  Automation is not possible  etc)

 [1] https://redmine.wso2.com/versions/43


 Thanks  Regards
 *Asanthi Kulasinghe*
 WSO2 Inc; http://www.wso2.com/.
 Mobile: +94777355522



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 --
 Chanaka Fernando
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 Release Testing Update

[Jagath Sisirakumara Ariyarathne]

Hi QA Team,

Please find latest ESB 4.9.0 pack in location[1]. It has fix for below
mentioned critical issue and several other L2 issues.

   - ESBJAVA-3888 https://wso2.org/jira/browse/ESBJAVA-3888

[1] -
https://svn.wso2.org/repos/wso2/scratch/ESB/packs/10072015/wso2esb-4.9.0-ALPHA4.zip

   1.
  Thanks.


On Tue, Jul 7, 2015 at 2:49 PM, Jagath Sisirakumara Ariyarathne 
jaga...@wso2.com wrote:

 Hi Sandapa.

 Following critical issues fixed in this pack with few other L2 issues.

1. ESBJAVA-3860 https://wso2.org/jira/browse/ESBJAVA-3860
2. ESBJAVA-3869 https://wso2.org/jira/browse/ESBJAVA-3869
3. ESBJAVA-3287 https://wso2.org/jira/browse/ESBJAVA-3287
4. ESBJAVA-3102 https://wso2.org/jira/browse/ESBJAVA-3102
5. ESBJAVA-3626 https://wso2.org/jira/browse/ESBJAVA-3626

 Thanks.

 On Tue, Jul 7, 2015 at 2:34 PM, Sandapa Handakumbura sand...@wso2.com
 wrote:

 Hi Jagath,
 Any critical fixes in this pack?



 On Tue, Jul 7, 2015 at 1:24 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi QA Team,

 Please find the latest ESB 4.9.0 pack for testing in below location[1].

 [1] -
 https://svn.wso2.org/repos/wso2/scratch/ESB/packs/07072015/wso2esb-4.9.0-ALPHA3.zip


 Thanks.

 On Tue, Jun 30, 2015 at 11:05 AM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 HI Jagath.

 Seems. this is not java8 issue. Same issue occurred in the java7 as
 well according to the JIRA[1] you mentioned.  I think PR has not merged to
 the carbon-commons yet. I will remove duplicate JIRA.


 [1] - https://wso2.org/jira/browse/ESBJAVA-3734

 On Tue, Jun 30, 2015 at 10:56 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Prabath,

 I think this has a JIRA[1] already. Could you please verify.

 [1] - https://wso2.org/jira/browse/ESBJAVA-3734


 Thanks.

 On Tue, Jun 30, 2015 at 10:52 AM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi All.

 I noticed one issue while doing further testing on java8 compilation
 issue. If we click Main-- message_store first then Configuration
 --DataSources giving blank page if we click message_store first then
 DataStore give and blank page. I created separate JIRA[1] for track this
 issue and I will fix it soon.


 [1] = https://wso2.org/jira/browse/ESBJAVA-3859

 Thanks.

 On Tue, Jun 30, 2015 at 10:09 AM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Thanks Jagath. We will use this pack for testing and will verify the
 Java 8 issue as well.

 Regards,
 Sandapa

 On Tue, Jun 30, 2015 at 10:04 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi QA Team,

 Please find latest ESB pack for testing in svn location[1]. This
 contains major bug fix for Java 8 environment issue.

 [1] - https://svn.wso2.org/repos/wso2/scratch/ESB/packs/30062015/


 Thanks.

 On Mon, Jun 29, 2015 at 3:09 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Isuru,

 I will send it from the latest build today.

 Thanks.

 On Mon, Jun 29, 2015 at 3:05 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi JagathA,

 We need to provide a new pack for QA with this change.

 Thanks.

 On Mon, Jun 29, 2015 at 2:59 PM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Isuru.

 Already fixed the JSP compilation issue in the Java 8 and sent
 the PR[1].

 [1] = https://github.com/wso2/product-esb/pull/201

 Thanks.

 On Wed, Jun 24, 2015 at 6:37 PM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Isuru.

 I'm currently working on that issue. I talked to Kasun G about
 this issue and he gave suggestion to update tomcat orbit bundle. I 
 will
 check this solution and update you.

 Thanks

 On Wed, Jun 24, 2015 at 6:13 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi PrabathAR,

 I believe we test this when we are implementing java8 support.

 Can you please look into these issues? There should be a
 common issue for all UIs.

 Thanks.

 On Wed, Jun 24, 2015 at 3:16 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,
 When using Java 8 (jdk1.8.0_45), many pages (APIs, Inbound
 Endpoints, Add custom proxy, Master source view, etc..) of 
 ESB4.9.0 gives
 dead pages. Public jira for this Blocking issue is reported at 
 [1].

 [1] https://wso2.org/jira/browse/ESBJAVA-3836

 Regards,
 Sandapa


 On Mon, Jun 22, 2015 at 1:15 PM, Isuru Udana isu...@wso2.com
  wrote:

 Hi Sandapa,

 Thanks for the update mail.
 We will provide a new pack today from the jenkins builder.

 Thanks.

 On Mon, Jun 22, 2015 at 12:37 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,

 During past couple of weeks we tested the new
 features(listed below) in ESB4.9.0-Alpha pack and has done the 
 initial
 round of testing for 80% of those. Some features have blocking 
 issues and
 hence cannot be tested comprehensively. ESB team is currently 
 fixing the
 reported issues and we're planning to verify the fixes and 
 continue blocked
 areas in Beta pack.

 Inbound Endpoint support in multi-tenant environments
 - HTTP Inbound Endpoint
 - JMS Inbound Endpoint
 - VFS Inbound Endpoint

Re: [Dev] ESB 4.9.0 Release Testing Update

[Jagath Sisirakumara Ariyarathne]

Hi QA Team,

Please find the latest ESB 4.9.0 pack for testing in below location[1].

[1] -
https://svn.wso2.org/repos/wso2/scratch/ESB/packs/07072015/wso2esb-4.9.0-ALPHA3.zip


Thanks.

On Tue, Jun 30, 2015 at 11:05 AM, Prabath Ariyarathna prabat...@wso2.com
wrote:

 HI Jagath.

 Seems. this is not java8 issue. Same issue occurred in the java7 as well
 according to the JIRA[1] you mentioned.  I think PR has not merged to the
 carbon-commons yet. I will remove duplicate JIRA.


 [1] - https://wso2.org/jira/browse/ESBJAVA-3734

 On Tue, Jun 30, 2015 at 10:56 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Prabath,

 I think this has a JIRA[1] already. Could you please verify.

 [1] - https://wso2.org/jira/browse/ESBJAVA-3734


 Thanks.

 On Tue, Jun 30, 2015 at 10:52 AM, Prabath Ariyarathna prabat...@wso2.com
  wrote:

 Hi All.

 I noticed one issue while doing further testing on java8 compilation
 issue. If we click Main-- message_store first then Configuration
 --DataSources giving blank page if we click message_store first then
 DataStore give and blank page. I created separate JIRA[1] for track this
 issue and I will fix it soon.


 [1] = https://wso2.org/jira/browse/ESBJAVA-3859

 Thanks.

 On Tue, Jun 30, 2015 at 10:09 AM, Sandapa Handakumbura sand...@wso2.com
  wrote:

 Thanks Jagath. We will use this pack for testing and will verify the
 Java 8 issue as well.

 Regards,
 Sandapa

 On Tue, Jun 30, 2015 at 10:04 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi QA Team,

 Please find latest ESB pack for testing in svn location[1]. This
 contains major bug fix for Java 8 environment issue.

 [1] - https://svn.wso2.org/repos/wso2/scratch/ESB/packs/30062015/


 Thanks.

 On Mon, Jun 29, 2015 at 3:09 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Isuru,

 I will send it from the latest build today.

 Thanks.

 On Mon, Jun 29, 2015 at 3:05 PM, Isuru Udana isu...@wso2.com wrote:

 Hi JagathA,

 We need to provide a new pack for QA with this change.

 Thanks.

 On Mon, Jun 29, 2015 at 2:59 PM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Isuru.

 Already fixed the JSP compilation issue in the Java 8 and sent the
 PR[1].

 [1] = https://github.com/wso2/product-esb/pull/201

 Thanks.

 On Wed, Jun 24, 2015 at 6:37 PM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Isuru.

 I'm currently working on that issue. I talked to Kasun G about
 this issue and he gave suggestion to update tomcat orbit bundle. I 
 will
 check this solution and update you.

 Thanks

 On Wed, Jun 24, 2015 at 6:13 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi PrabathAR,

 I believe we test this when we are implementing java8 support.
 Can you please look into these issues? There should be a common
 issue for all UIs.

 Thanks.

 On Wed, Jun 24, 2015 at 3:16 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,
 When using Java 8 (jdk1.8.0_45), many pages (APIs, Inbound
 Endpoints, Add custom proxy, Master source view, etc..) of ESB4.9.0 
 gives
 dead pages. Public jira for this Blocking issue is reported at [1].

 [1] https://wso2.org/jira/browse/ESBJAVA-3836

 Regards,
 Sandapa


 On Mon, Jun 22, 2015 at 1:15 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi Sandapa,

 Thanks for the update mail.
 We will provide a new pack today from the jenkins builder.

 Thanks.

 On Mon, Jun 22, 2015 at 12:37 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,

 During past couple of weeks we tested the new features(listed
 below) in ESB4.9.0-Alpha pack and has done the initial round of 
 testing for
 80% of those. Some features have blocking issues and hence cannot 
 be tested
 comprehensively. ESB team is currently fixing the reported issues 
 and we're
 planning to verify the fixes and continue blocked areas in Beta 
 pack.

 Inbound Endpoint support in multi-tenant environments
 - HTTP Inbound Endpoint
 - JMS Inbound Endpoint
 - VFS Inbound Endpoint
 - CXF WS-RM Inbound Endpoint
 - HL7 Inbound Endpoint
 Coordination support for Message Stores and Processors
 For-each Mediator
 JDBC Message Store
 RabbitMQ Transport
 Dynamic SSLProfiles for sender and listener
 Coordination support for Scheduled Tasks.
 Enabling HTTP Cache Control headers (Etag)
 Kafka support in ESB (Experimental)


 Applying QOS for services and other ESB related new
 features(Indbound endpoints etc) are currently being tested with 
 Developer
 Studio 3.8.0 - M5.

 We will continue testing rest of the new features and the core
 features in ESB 4.9.0 Alpha pack.

 @Shashika and Asanthi,
 Please add if I have missed anything important.

 Thanks,
 Sandapa

 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M

Re: [Dev] ESB 4.9.0 Release Testing Update

[Jagath Sisirakumara Ariyarathne]

Hi Sandapa.

Following critical issues fixed in this pack with few other L2 issues.

   1. ESBJAVA-3860 https://wso2.org/jira/browse/ESBJAVA-3860
   2. ESBJAVA-3869 https://wso2.org/jira/browse/ESBJAVA-3869
   3. ESBJAVA-3287 https://wso2.org/jira/browse/ESBJAVA-3287
   4. ESBJAVA-3102 https://wso2.org/jira/browse/ESBJAVA-3102
   5. ESBJAVA-3626 https://wso2.org/jira/browse/ESBJAVA-3626

Thanks.

On Tue, Jul 7, 2015 at 2:34 PM, Sandapa Handakumbura sand...@wso2.com
wrote:

 Hi Jagath,
 Any critical fixes in this pack?



 On Tue, Jul 7, 2015 at 1:24 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi QA Team,

 Please find the latest ESB 4.9.0 pack for testing in below location[1].

 [1] -
 https://svn.wso2.org/repos/wso2/scratch/ESB/packs/07072015/wso2esb-4.9.0-ALPHA3.zip


 Thanks.

 On Tue, Jun 30, 2015 at 11:05 AM, Prabath Ariyarathna prabat...@wso2.com
  wrote:

 HI Jagath.

 Seems. this is not java8 issue. Same issue occurred in the java7 as well
 according to the JIRA[1] you mentioned.  I think PR has not merged to the
 carbon-commons yet. I will remove duplicate JIRA.


 [1] - https://wso2.org/jira/browse/ESBJAVA-3734

 On Tue, Jun 30, 2015 at 10:56 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Prabath,

 I think this has a JIRA[1] already. Could you please verify.

 [1] - https://wso2.org/jira/browse/ESBJAVA-3734


 Thanks.

 On Tue, Jun 30, 2015 at 10:52 AM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi All.

 I noticed one issue while doing further testing on java8 compilation
 issue. If we click Main-- message_store first then Configuration
 --DataSources giving blank page if we click message_store first then
 DataStore give and blank page. I created separate JIRA[1] for track this
 issue and I will fix it soon.


 [1] = https://wso2.org/jira/browse/ESBJAVA-3859

 Thanks.

 On Tue, Jun 30, 2015 at 10:09 AM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Thanks Jagath. We will use this pack for testing and will verify the
 Java 8 issue as well.

 Regards,
 Sandapa

 On Tue, Jun 30, 2015 at 10:04 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi QA Team,

 Please find latest ESB pack for testing in svn location[1]. This
 contains major bug fix for Java 8 environment issue.

 [1] - https://svn.wso2.org/repos/wso2/scratch/ESB/packs/30062015/


 Thanks.

 On Mon, Jun 29, 2015 at 3:09 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Isuru,

 I will send it from the latest build today.

 Thanks.

 On Mon, Jun 29, 2015 at 3:05 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi JagathA,

 We need to provide a new pack for QA with this change.

 Thanks.

 On Mon, Jun 29, 2015 at 2:59 PM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Isuru.

 Already fixed the JSP compilation issue in the Java 8 and sent
 the PR[1].

 [1] = https://github.com/wso2/product-esb/pull/201

 Thanks.

 On Wed, Jun 24, 2015 at 6:37 PM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Isuru.

 I'm currently working on that issue. I talked to Kasun G about
 this issue and he gave suggestion to update tomcat orbit bundle. I 
 will
 check this solution and update you.

 Thanks

 On Wed, Jun 24, 2015 at 6:13 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi PrabathAR,

 I believe we test this when we are implementing java8 support.

 Can you please look into these issues? There should be a common
 issue for all UIs.

 Thanks.

 On Wed, Jun 24, 2015 at 3:16 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,
 When using Java 8 (jdk1.8.0_45), many pages (APIs, Inbound
 Endpoints, Add custom proxy, Master source view, etc..) of 
 ESB4.9.0 gives
 dead pages. Public jira for this Blocking issue is reported at 
 [1].

 [1] https://wso2.org/jira/browse/ESBJAVA-3836

 Regards,
 Sandapa


 On Mon, Jun 22, 2015 at 1:15 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi Sandapa,

 Thanks for the update mail.
 We will provide a new pack today from the jenkins builder.

 Thanks.

 On Mon, Jun 22, 2015 at 12:37 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,

 During past couple of weeks we tested the new
 features(listed below) in ESB4.9.0-Alpha pack and has done the 
 initial
 round of testing for 80% of those. Some features have blocking 
 issues and
 hence cannot be tested comprehensively. ESB team is currently 
 fixing the
 reported issues and we're planning to verify the fixes and 
 continue blocked
 areas in Beta pack.

 Inbound Endpoint support in multi-tenant environments
 - HTTP Inbound Endpoint
 - JMS Inbound Endpoint
 - VFS Inbound Endpoint
 - CXF WS-RM Inbound Endpoint
 - HL7 Inbound Endpoint
 Coordination support for Message Stores and Processors
 For-each Mediator
 JDBC Message Store
 RabbitMQ Transport
 Dynamic SSLProfiles for sender and listener
 Coordination support for Scheduled Tasks.
 Enabling HTTP Cache Control headers (Etag)
 Kafka support in ESB (Experimental)


 Applying QOS for services and other ESB related new
 features(Indbound

[Dev] [ESB] EmptyStackException when resuming a paused message processor

[Jagath Sisirakumara Ariyarathne]

Hi,

I am working on [1] and found that the cause of the exception mentioned
below is in the code segment in
org.wso2.carbon.context.internal.CarbonContextDataHolder
in carbon.utils.

public void endTenantFlow() {

StackCarbonContextDataHolder carbonContextDataHolders =
parentContextHolderStack.get();
if (carbonContextDataHolders != null) {
currentContextHolder.set(carbonContextDataHolders.pop());
}
}

*Exception :*

java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:102)
at java.util.Stack.pop(Stack.java:84)
at 
org.wso2.carbon.context.internal.CarbonContextDataHolder.endTenantFlow(CarbonContextDataHolder.java:1291)
at 
org.wso2.carbon.context.PrivilegedCarbonContext.endTenantFlow(PrivilegedCarbonContext.java:75)
at 
org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:69)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Issue occurs when it tries to pop elements from
carbonContextDataHolders stack when it is empty.

Is it a possible scenario that this stack being empty and shouldn't it
be handled at CarbonContextDataHolder (check isEmpty in stack)?

[1] - https://wso2.org/jira/browse/ESBJAVA-3832

Thanks

-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] EmptyStackException when resuming a paused message processor

[Jagath Sisirakumara Ariyarathne]

Hi Carbon Team,

Please review and merge the PR[1] to fix the JIRA[2].

[1] - https://github.com/wso2/carbon4-kernel/pull/285
[2] - https://wso2.org/jira/browse/ESBJAVA-3832

Thanks.

On Tue, Jul 7, 2015 at 5:47 PM, Kasun Indrasiri ka...@wso2.com wrote:

 Yeah, we should always check for an empty stack.

 On Tue, Jul 7, 2015 at 5:17 PM, Malaka Silva mal...@wso2.com wrote:

 I think we need to check isEmpty as well.

 On Tue, Jul 7, 2015 at 3:41 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi,

 I am working on [1] and found that the cause of the exception mentioned
 below is in the code segment in 
 org.wso2.carbon.context.internal.CarbonContextDataHolder
 in carbon.utils.

 public void endTenantFlow() {

 StackCarbonContextDataHolder carbonContextDataHolders = 
 parentContextHolderStack.get();
 if (carbonContextDataHolders != null) {
 currentContextHolder.set(carbonContextDataHolders.pop());
 }
 }

 *Exception :*

 java.util.EmptyStackException
 at java.util.Stack.peek(Stack.java:102)
 at java.util.Stack.pop(Stack.java:84)
 at 
 org.wso2.carbon.context.internal.CarbonContextDataHolder.endTenantFlow(CarbonContextDataHolder.java:1291)
 at 
 org.wso2.carbon.context.PrivilegedCarbonContext.endTenantFlow(PrivilegedCarbonContext.java:75)
 at 
 org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:69)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)

 Issue occurs when it tries to pop elements from carbonContextDataHolders 
 stack when it is empty.

 Is it a possible scenario that this stack being empty and shouldn't it be 
 handled at CarbonContextDataHolder (check isEmpty in stack)?

 [1] - https://wso2.org/jira/browse/ESBJAVA-3832

 Thanks

 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 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/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] EmptyStackException when resuming a paused message processor

[Jagath Sisirakumara Ariyarathne]

Hi Sameera,

I will check it and update.

Thanks.

On Wed, Jul 8, 2015 at 11:10 AM, Sameera Jayasoma same...@wso2.com wrote:

 Hi Jagath,

 Can you debug and see whey the stack becomes empty? Thats a serious
 problem. Stack should be become empty here.

 Checking whether the stack is empty will stop the error log, but it
 doesn't fix the actual problem here.

 On Wed, Jul 8, 2015 at 10:50 AM, Sameera Jayasoma same...@wso2.com
 wrote:

 I understand, but we need to understand why that stack becomes empty.
 AFAIK, if we follow the proper APIs, stack should not become empty

 On Tue, Jul 7, 2015 at 5:47 PM, Kasun Indrasiri ka...@wso2.com wrote:

 Yeah, we should always check for an empty stack.

 On Tue, Jul 7, 2015 at 5:17 PM, Malaka Silva mal...@wso2.com wrote:

 I think we need to check isEmpty as well.

 On Tue, Jul 7, 2015 at 3:41 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi,

 I am working on [1] and found that the cause of the exception
 mentioned below is in the code segment in org
 .wso2.carbon.context.internal.CarbonContextDataHolder in carbon.utils.

 public void endTenantFlow() {

 StackCarbonContextDataHolder carbonContextDataHolders = 
 parentContextHolderStack.get();
 if (carbonContextDataHolders != null) {
 currentContextHolder.set(carbonContextDataHolders.pop());
 }
 }

 *Exception :*

 java.util.EmptyStackException
   at java.util.Stack.peek(Stack.java:102)
   at java.util.Stack.pop(Stack.java:84)
   at 
 org.wso2.carbon.context.internal.CarbonContextDataHolder.endTenantFlow(CarbonContextDataHolder.java:1291)
   at 
 org.wso2.carbon.context.PrivilegedCarbonContext.endTenantFlow(PrivilegedCarbonContext.java:75)
   at 
 org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:69)
   at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)

 Issue occurs when it tries to pop elements from carbonContextDataHolders 
 stack when it is empty.

 Is it a possible scenario that this stack being empty and shouldn't it be 
 handled at CarbonContextDataHolder (check isEmpty in stack)?

 [1] - https://wso2.org/jira/browse/ESBJAVA-3832

 Thanks

 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 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/

 Save a tree -Conserve nature  Save the world for your future. Print
 this email only if it is absolutely necessary.

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Sameera Jayasoma,
 Software Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://blog.sameera.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 0094776364456

 Lean . Enterprise . Middleware




 --
 Sameera Jayasoma,
 Software Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://blog.sameera.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 0094776364456

 Lean . Enterprise . Middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge PR[1].

[1] - https://github.com/wso2/product-esb/pull/203


Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 Release Testing Update

[Jagath Sisirakumara Ariyarathne]

Hi Isuru,

I will send it from the latest build today.

Thanks.

On Mon, Jun 29, 2015 at 3:05 PM, Isuru Udana isu...@wso2.com wrote:

 Hi JagathA,

 We need to provide a new pack for QA with this change.

 Thanks.

 On Mon, Jun 29, 2015 at 2:59 PM, Prabath Ariyarathna prabat...@wso2.com
 wrote:

 Hi Isuru.

 Already fixed the JSP compilation issue in the Java 8 and sent the PR[1].

 [1] = https://github.com/wso2/product-esb/pull/201

 Thanks.

 On Wed, Jun 24, 2015 at 6:37 PM, Prabath Ariyarathna prabat...@wso2.com
 wrote:

 Hi Isuru.

 I'm currently working on that issue. I talked to Kasun G about this
 issue and he gave suggestion to update tomcat orbit bundle. I will check
 this solution and update you.

 Thanks

 On Wed, Jun 24, 2015 at 6:13 PM, Isuru Udana isu...@wso2.com wrote:

 Hi PrabathAR,

 I believe we test this when we are implementing java8 support.
 Can you please look into these issues? There should be a common issue
 for all UIs.

 Thanks.

 On Wed, Jun 24, 2015 at 3:16 PM, Sandapa Handakumbura sand...@wso2.com
  wrote:

 Hi,
 When using Java 8 (jdk1.8.0_45), many pages (APIs, Inbound Endpoints,
 Add custom proxy, Master source view, etc..) of ESB4.9.0 gives dead pages.
 Public jira for this Blocking issue is reported at [1].

 [1] https://wso2.org/jira/browse/ESBJAVA-3836

 Regards,
 Sandapa


 On Mon, Jun 22, 2015 at 1:15 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Sandapa,

 Thanks for the update mail.
 We will provide a new pack today from the jenkins builder.

 Thanks.

 On Mon, Jun 22, 2015 at 12:37 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,

 During past couple of weeks we tested the new features(listed below)
 in ESB4.9.0-Alpha pack and has done the initial round of testing for 
 80% of
 those. Some features have blocking issues and hence cannot be tested
 comprehensively. ESB team is currently fixing the reported issues and 
 we're
 planning to verify the fixes and continue blocked areas in Beta pack.

 Inbound Endpoint support in multi-tenant environments
 - HTTP Inbound Endpoint
 - JMS Inbound Endpoint
 - VFS Inbound Endpoint
 - CXF WS-RM Inbound Endpoint
 - HL7 Inbound Endpoint
 Coordination support for Message Stores and Processors
 For-each Mediator
 JDBC Message Store
 RabbitMQ Transport
 Dynamic SSLProfiles for sender and listener
 Coordination support for Scheduled Tasks.
 Enabling HTTP Cache Control headers (Etag)
 Kafka support in ESB (Experimental)


 Applying QOS for services and other ESB related new
 features(Indbound endpoints etc) are currently being tested with 
 Developer
 Studio 3.8.0 - M5.

 We will continue testing rest of the new features and the core
 features in ESB 4.9.0 Alpha pack.

 @Shashika and Asanthi,
 Please add if I have missed anything important.

 Thanks,
 Sandapa

 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --

 *Prabath Ariyarathna*

 *Associate Technical Lead*

 *WSO2, Inc. *

 *lean . enterprise . middleware *


 *Email: prabat...@wso2.com 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 *








 --

 *Prabath Ariyarathna*

 *Associate Technical Lead*

 *WSO2, Inc. *

 *lean . enterprise . middleware *


 *Email: prabat...@wso2.com 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 *








 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 Release Testing Update

[Jagath Sisirakumara Ariyarathne]

Hi QA Team,

Please find latest ESB pack for testing in svn location[1]. This contains
major bug fix for Java 8 environment issue.

[1] - https://svn.wso2.org/repos/wso2/scratch/ESB/packs/30062015/


Thanks.

On Mon, Jun 29, 2015 at 3:09 PM, Jagath Sisirakumara Ariyarathne 
jaga...@wso2.com wrote:

 Hi Isuru,

 I will send it from the latest build today.

 Thanks.

 On Mon, Jun 29, 2015 at 3:05 PM, Isuru Udana isu...@wso2.com wrote:

 Hi JagathA,

 We need to provide a new pack for QA with this change.

 Thanks.

 On Mon, Jun 29, 2015 at 2:59 PM, Prabath Ariyarathna prabat...@wso2.com
 wrote:

 Hi Isuru.

 Already fixed the JSP compilation issue in the Java 8 and sent the PR[1].

 [1] = https://github.com/wso2/product-esb/pull/201

 Thanks.

 On Wed, Jun 24, 2015 at 6:37 PM, Prabath Ariyarathna prabat...@wso2.com
  wrote:

 Hi Isuru.

 I'm currently working on that issue. I talked to Kasun G about this
 issue and he gave suggestion to update tomcat orbit bundle. I will check
 this solution and update you.

 Thanks

 On Wed, Jun 24, 2015 at 6:13 PM, Isuru Udana isu...@wso2.com wrote:

 Hi PrabathAR,

 I believe we test this when we are implementing java8 support.
 Can you please look into these issues? There should be a common issue
 for all UIs.

 Thanks.

 On Wed, Jun 24, 2015 at 3:16 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,
 When using Java 8 (jdk1.8.0_45), many pages (APIs, Inbound Endpoints,
 Add custom proxy, Master source view, etc..) of ESB4.9.0 gives dead 
 pages.
 Public jira for this Blocking issue is reported at [1].

 [1] https://wso2.org/jira/browse/ESBJAVA-3836

 Regards,
 Sandapa


 On Mon, Jun 22, 2015 at 1:15 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Sandapa,

 Thanks for the update mail.
 We will provide a new pack today from the jenkins builder.

 Thanks.

 On Mon, Jun 22, 2015 at 12:37 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,

 During past couple of weeks we tested the new features(listed
 below) in ESB4.9.0-Alpha pack and has done the initial round of 
 testing for
 80% of those. Some features have blocking issues and hence cannot be 
 tested
 comprehensively. ESB team is currently fixing the reported issues and 
 we're
 planning to verify the fixes and continue blocked areas in Beta pack.

 Inbound Endpoint support in multi-tenant environments
 - HTTP Inbound Endpoint
 - JMS Inbound Endpoint
 - VFS Inbound Endpoint
 - CXF WS-RM Inbound Endpoint
 - HL7 Inbound Endpoint
 Coordination support for Message Stores and Processors
 For-each Mediator
 JDBC Message Store
 RabbitMQ Transport
 Dynamic SSLProfiles for sender and listener
 Coordination support for Scheduled Tasks.
 Enabling HTTP Cache Control headers (Etag)
 Kafka support in ESB (Experimental)


 Applying QOS for services and other ESB related new
 features(Indbound endpoints etc) are currently being tested with 
 Developer
 Studio 3.8.0 - M5.

 We will continue testing rest of the new features and the core
 features in ESB 4.9.0 Alpha pack.

 @Shashika and Asanthi,
 Please add if I have missed anything important.

 Thanks,
 Sandapa

 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --

 *Prabath Ariyarathna*

 *Associate Technical Lead*

 *WSO2, Inc. *

 *lean . enterprise . middleware *


 *Email: prabat...@wso2.com 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 *








 --

 *Prabath Ariyarathna*

 *Associate Technical Lead*

 *WSO2, Inc. *

 *lean . enterprise . middleware *


 *Email: prabat...@wso2.com 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 *








 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 Release Testing Update

[Jagath Sisirakumara Ariyarathne]

Hi Prabath,

I think this has a JIRA[1] already. Could you please verify.

[1] - https://wso2.org/jira/browse/ESBJAVA-3734


Thanks.

On Tue, Jun 30, 2015 at 10:52 AM, Prabath Ariyarathna prabat...@wso2.com
wrote:

 Hi All.

 I noticed one issue while doing further testing on java8 compilation
 issue. If we click Main-- message_store first then Configuration
 --DataSources giving blank page if we click message_store first then
 DataStore give and blank page. I created separate JIRA[1] for track this
 issue and I will fix it soon.


 [1] = https://wso2.org/jira/browse/ESBJAVA-3859

 Thanks.

 On Tue, Jun 30, 2015 at 10:09 AM, Sandapa Handakumbura sand...@wso2.com
 wrote:

 Thanks Jagath. We will use this pack for testing and will verify the Java
 8 issue as well.

 Regards,
 Sandapa

 On Tue, Jun 30, 2015 at 10:04 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi QA Team,

 Please find latest ESB pack for testing in svn location[1]. This
 contains major bug fix for Java 8 environment issue.

 [1] - https://svn.wso2.org/repos/wso2/scratch/ESB/packs/30062015/


 Thanks.

 On Mon, Jun 29, 2015 at 3:09 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Isuru,

 I will send it from the latest build today.

 Thanks.

 On Mon, Jun 29, 2015 at 3:05 PM, Isuru Udana isu...@wso2.com wrote:

 Hi JagathA,

 We need to provide a new pack for QA with this change.

 Thanks.

 On Mon, Jun 29, 2015 at 2:59 PM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Isuru.

 Already fixed the JSP compilation issue in the Java 8 and sent the
 PR[1].

 [1] = https://github.com/wso2/product-esb/pull/201

 Thanks.

 On Wed, Jun 24, 2015 at 6:37 PM, Prabath Ariyarathna 
 prabat...@wso2.com wrote:

 Hi Isuru.

 I'm currently working on that issue. I talked to Kasun G about this
 issue and he gave suggestion to update tomcat orbit bundle. I will check
 this solution and update you.

 Thanks

 On Wed, Jun 24, 2015 at 6:13 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi PrabathAR,

 I believe we test this when we are implementing java8 support.
 Can you please look into these issues? There should be a common
 issue for all UIs.

 Thanks.

 On Wed, Jun 24, 2015 at 3:16 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,
 When using Java 8 (jdk1.8.0_45), many pages (APIs, Inbound
 Endpoints, Add custom proxy, Master source view, etc..) of ESB4.9.0 
 gives
 dead pages. Public jira for this Blocking issue is reported at [1].

 [1] https://wso2.org/jira/browse/ESBJAVA-3836

 Regards,
 Sandapa


 On Mon, Jun 22, 2015 at 1:15 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi Sandapa,

 Thanks for the update mail.
 We will provide a new pack today from the jenkins builder.

 Thanks.

 On Mon, Jun 22, 2015 at 12:37 PM, Sandapa Handakumbura 
 sand...@wso2.com wrote:

 Hi,

 During past couple of weeks we tested the new features(listed
 below) in ESB4.9.0-Alpha pack and has done the initial round of 
 testing for
 80% of those. Some features have blocking issues and hence cannot 
 be tested
 comprehensively. ESB team is currently fixing the reported issues 
 and we're
 planning to verify the fixes and continue blocked areas in Beta 
 pack.

 Inbound Endpoint support in multi-tenant environments
 - HTTP Inbound Endpoint
 - JMS Inbound Endpoint
 - VFS Inbound Endpoint
 - CXF WS-RM Inbound Endpoint
 - HL7 Inbound Endpoint
 Coordination support for Message Stores and Processors
 For-each Mediator
 JDBC Message Store
 RabbitMQ Transport
 Dynamic SSLProfiles for sender and listener
 Coordination support for Scheduled Tasks.
 Enabling HTTP Cache Control headers (Etag)
 Kafka support in ESB (Experimental)


 Applying QOS for services and other ESB related new
 features(Indbound endpoints etc) are currently being tested with 
 Developer
 Studio 3.8.0 - M5.

 We will continue testing rest of the new features and the core
 features in ESB 4.9.0 Alpha pack.

 @Shashika and Asanthi,
 Please add if I have missed anything important.

 Thanks,
 Sandapa

 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --

 *Prabath Ariyarathna*

 *Associate Technical Lead*

 *WSO2, Inc. *

 *lean . enterprise . middleware *


 *Email: prabat...@wso2.com 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 *








 --

 *Prabath Ariyarathna*

 *Associate Technical Lead*

 *WSO2, Inc. *

 *lean . enterprise . middleware

[Dev] Latest ESB 4.9.0 build for testing

[Jagath Sisirakumara Ariyarathne]

Hi QA Team,

Latest Jenkins daily build ESB pack has been uploaded to below location[1]
for testing. You can use it to continue ESB 4.9.0 testing and validate
fixes which are already done.

[1] - https://svn.wso2.org/repos/wso2/scratch/ESB/packs/22062015/

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

Please ignore previous PR and find the new PR[1] below to master branch.

[1] - https://github.com/wso2/carbon-mediation/pull/226

Thanks.

On Mon, Jun 15, 2015 at 12:11 PM, Jagath Sisirakumara Ariyarathne 
jaga...@wso2.com wrote:

 Hi,

 Please review and merge PR[1] to fix JIRA issue[2].

 [1] - https://github.com/wso2/carbon-mediation/pull/87
 [2] - https://wso2.org/jira/browse/ESBJAVA-3761

 Thanks.
 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge PR[1] to fix JIRA issue[2].

[1] - https://github.com/wso2/carbon-mediation/pull/87
[2] - https://wso2.org/jira/browse/ESBJAVA-3761

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge PR[1] for JIRA issue[2].

[1] - https://github.com/wso2/carbon-mediation/pull/225
[2] - https://wso2.org/jira/browse/ESBJAVA-3717

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] XML Comments support in ESB configurations - Dev Studio update

[Jagath Sisirakumara Ariyarathne]

Hi Viraj,

Comments list is added to AbstractMediator since it was implemented in few
mediators at the initial implementation. But going forward, as you
mentioned, it would be better if we define it in Mediator interface.

@Kasun, Isuru, We can define getCommentsList() and setCommentsList() in
Mediator interface. Then it should be implemented in all mediator classes
even though it is not used in some of classes. Appreciate your feedback
here.

Thanks.

On Mon, Jun 15, 2015 at 7:55 PM, Viraj Rajaguru vi...@wso2.com wrote:

 Hi Jagath,

 Currenlty org.apache.synapse.mediators.AbstractMediator.getCommentsList()
 and
 org.apache.synapse.mediators.AbstractMediator.setCommentsList(ListString)
 methods haven't been defined in org.apache.synapse.Mediator interface. Did
 we do this intentionally ?

 It will be more convenient for us to have these two methods in
 org.apache.synapse.Mediator interface because we are relying on
 org.apache.synapse.Mediator interface to manipulate generic attributes such
 as shortDescription in our code. Is it possible to define these methods
 in the org.apache.synapse.Mediator interface ?

 Thanks,
 Viraj.

 On Sun, May 10, 2015 at 10:01 PM, Viraj Rajaguru vi...@wso2.com wrote:

 Hi Jagath,

 Thanks for informing us. We will use latest Synapse and Carbon libraries
 which contain this fix and do the relevant changes in DevS side to
 incorporate this feature.

 Thanks,
 Viraj.



 On Sun, May 10, 2015 at 6:47 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi DS Team,

 XML comments support in ESB configurations has been implemented to fix
 the Jira [1] with related documentation in [2].

 [1] - https://wso2.org/jira/browse/ESBJAVA-3673
 [2] -
 https://docs.google.com/document/d/1SRHBiCdXsZvvTDeX0qONzag8qbBRzh7ks9xNywyNrXA/edit#heading=h.6a7z1ncf8cph


 Could you please do the needful to incorporate changes required in Dev
 Studio editors for the $subject.

 Related PRs for synapse and carbon-mediation sources can be found in
 [3],[4];

 [3] - https://github.com/wso2/wso2-synapse/pull/137
 [4] - https://github.com/wso2/carbon-mediation/pull/105


 Thanks.
 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




 --
 Viraj Rajaguru
 Senior Software Engineer
 WSO2 Inc. : http://wso2.com

 Mobile: +94 77 3683068






 --
 Viraj Rajaguru
 Senior Software Engineer
 WSO2 Inc. : http://wso2.com

 Mobile: +94 77 3683068






-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge PR[1] for JIRA issue [2].

[1] - https://github.com/wso2/carbon-mediation/pull/208
[2] - https://wso2.org/jira/browse/ESBJAVA-3742


Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge PR[1] for JIRA issue[2].

[1] - https://github.com/wso2/wso2-synapse/pull/220
[2] - https://wso2.org/jira/browse/ESBJAVA-3735

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Gmail Connector code - missing dependencies

[Jagath Sisirakumara Ariyarathne]

Hi,

I downloaded latest git code from repo[1] for Gmail Connector. In the pom
file, there are two dependencies mentioned with local paths as follows;

[1] -
https://github.com/wso2/esb-connectors/tree/master/gmail/gmail-connector/gmail-connector-1.0.0/gmail

dependency

groupIdcom.google.code/groupId

artifactIdjava-gmail-imap/artifactId

version1.4.4-gm-ext-0.5/version

scopesystem/scope

systemPath
${basedir}/src/main/resources/lib/java-gmail-imap-1.4.4-gm-ext-0.5.jar/
systemPath

/dependency
dependency

groupIdcom.google.code/groupId

artifactIdsamples.oauth2/artifactId

version1.0.0/version

scopesystem/scope

systemPath
${basedir}/src/main/resources/lib/samples.oauth2-0.0.1-SNAPSHOT.jar/
systemPath

/dependency

But these mentioned files are not there in the repo.

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Gmail Connector code - missing dependencies

[Jagath Sisirakumara Ariyarathne]

Hi Sriashalya,

Thanks for the information. I will use new connector code.

Thanks.

On Fri, May 15, 2015 at 1:57 PM, Sriashalya Srivathsan asha...@wso2.com
wrote:

 Hi Jagath,
 I think you may got the wrong one. We have our new gmail connector with a
 new name gmailRest.You can find it in the following link[1].

 https://github.com/wso2/esb-connectors/tree/master/gmailRest/gmailRest-connector/gmailRest-connector-1.0.0/org.wso2.carbon.connector/src/main/resources/lib

 Thank you.

 On Fri, May 15, 2015 at 1:46 PM, Sriashalya Srivathsan asha...@wso2.com
 wrote:

 Hi Jagath,

 when you want to send the attachment,you need those jars in that
 location.
 Since sending attachment was failed through the REST, we included the
 direct transaction through the SMTP.

 Thank you.

 On Fri, May 15, 2015 at 1:35 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi,

 I downloaded latest git code from repo[1] for Gmail Connector. In the
 pom file, there are two dependencies mentioned with local paths as follows;

 [1] -
 https://github.com/wso2/esb-connectors/tree/master/gmail/gmail-connector/gmail-connector-1.0.0/gmail

 dependency

 groupIdcom.google.code/groupId

 artifactIdjava-gmail-imap/artifactId

 version1.4.4-gm-ext-0.5/version

 scopesystem/scope

 systemPath
 ${basedir}/src/main/resources/lib/java-gmail-imap-1.4.4-gm-ext-0.5.jar/
 systemPath

 /dependency
 dependency

 groupIdcom.google.code/groupId

 artifactIdsamples.oauth2/artifactId

 version1.0.0/version

 scopesystem/scope

 systemPath
 ${basedir}/src/main/resources/lib/samples.oauth2-0.0.1-SNAPSHOT.jar/
 systemPath

 /dependency

 But these mentioned files are not there in the repo.

 Thanks.
 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




 --
 Regards
 S.Sriashalya,
 WSO2 *Inc*.
 lean . enterprise . middleware




 --
 Regards
 S.Sriashalya,
 WSO2 *Inc*.
 lean . enterprise . middleware




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Gmail Connector code - missing dependencies

[Jagath Sisirakumara Ariyarathne]

Hi Sriashalya,

Is there any documentation about new additions/updates in this new
implementation?

Thanks.

On Fri, May 15, 2015 at 2:06 PM, Jagath Sisirakumara Ariyarathne 
jaga...@wso2.com wrote:

 Hi Sriashalya,

 Thanks for the information. I will use new connector code.

 Thanks.

 On Fri, May 15, 2015 at 1:57 PM, Sriashalya Srivathsan asha...@wso2.com
 wrote:

 Hi Jagath,
 I think you may got the wrong one. We have our new gmail connector with a
 new name gmailRest.You can find it in the following link[1].

 https://github.com/wso2/esb-connectors/tree/master/gmailRest/gmailRest-connector/gmailRest-connector-1.0.0/org.wso2.carbon.connector/src/main/resources/lib

 Thank you.

 On Fri, May 15, 2015 at 1:46 PM, Sriashalya Srivathsan asha...@wso2.com
 wrote:

 Hi Jagath,

 when you want to send the attachment,you need those jars in that
 location.
 Since sending attachment was failed through the REST, we included the
 direct transaction through the SMTP.

 Thank you.

 On Fri, May 15, 2015 at 1:35 PM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi,

 I downloaded latest git code from repo[1] for Gmail Connector. In the
 pom file, there are two dependencies mentioned with local paths as follows;

 [1] -
 https://github.com/wso2/esb-connectors/tree/master/gmail/gmail-connector/gmail-connector-1.0.0/gmail

 dependency

 groupIdcom.google.code/groupId

 artifactIdjava-gmail-imap/artifactId

 version1.4.4-gm-ext-0.5/version

 scopesystem/scope

 systemPath
 ${basedir}/src/main/resources/lib/java-gmail-imap-1.4.4-gm-ext-0.5.jar
 /systemPath

 /dependency
 dependency

 groupIdcom.google.code/groupId

 artifactIdsamples.oauth2/artifactId

 version1.0.0/version

 scopesystem/scope

 systemPath
 ${basedir}/src/main/resources/lib/samples.oauth2-0.0.1-SNAPSHOT.jar/
 systemPath

 /dependency

 But these mentioned files are not there in the repo.

 Thanks.
 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




 --
 Regards
 S.Sriashalya,
 WSO2 *Inc*.
 lean . enterprise . middleware




 --
 Regards
 S.Sriashalya,
 WSO2 *Inc*.
 lean . enterprise . middleware




 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge PRs

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge PRs [1],[2] related to Jira issue [3].

[1] - https://github.com/wso2/wso2-synapse/pull/137
[2] - https://github.com/wso2/carbon-mediation/pull/105
[3] - https://wso2.org/jira/browse/ESBJAVA-3673

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] XML Comments support in ESB configurations - Dev Studio update

[Jagath Sisirakumara Ariyarathne]

Hi DS Team,

XML comments support in ESB configurations has been implemented to fix the
Jira [1] with related documentation in [2].

[1] - https://wso2.org/jira/browse/ESBJAVA-3673
[2] -
https://docs.google.com/document/d/1SRHBiCdXsZvvTDeX0qONzag8qbBRzh7ks9xNywyNrXA/edit#heading=h.6a7z1ncf8cph


Could you please do the needful to incorporate changes required in Dev
Studio editors for the $subject.

Related PRs for synapse and carbon-mediation sources can be found in
[3],[4];

[3] - https://github.com/wso2/wso2-synapse/pull/137
[4] - https://github.com/wso2/carbon-mediation/pull/105


Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge pull request [1].

[1] - https://github.com/wso2/product-esb/pull/135

Thanks,
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and Merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

Please review and merge the PR [1] for Jira issue [2].

[1] - https://github.com/wso2/wso2-synapse/pull/154
[2] - https://wso2.org/jira/browse/ESBJAVA-3647

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] Integration Tests for Dynamic SSL Profiles in ESB

[Jagath Sisirakumara Ariyarathne]

Hi Krishantha,

New feature of loading Custom SSL Profiles at run-time has been implemented
in ESB for the next release. It requires loading of new configurations and
keystore files to the ESB at run-time without restarting the application.
Documentation [1] contains more details and sample configuration scenarios.

[1] -
https://docs.google.com/a/wso2.com/document/d/1atcHDJdHQx5ElQOy0-MfmUkE2knau4SaWa0ijKtcxtI/edit#

As per the offline discussion we had, could you please let me know the
possibility of incorporating integration test cases for this using the
testing framework?

Thanks,
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi Sameera,

This PR contains a new functionality required for the mentioned redmine
issue [1]. This feature will be included in ESB 4.9.0 release.

Is there any possibility to get above changes merged to an upcoming patch
of carbon kernel or what would be the procedure to get this released?

Thanks.

On Tue, Apr 7, 2015 at 1:36 PM, Jagath Sisirakumara Ariyarathne 
jaga...@wso2.com wrote:

 Hi Carbon Team,

 Please review and merge [1] related to the redmine issue [2].

 [1] - https://github.com/wso2/carbon4-kernel/pull/198
 [2] - https://redmine.wso2.com/issues/3686

 Thanks.
 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge PR

[Jagath Sisirakumara Ariyarathne]

Hi Carbon Team,

Please review and merge [1] related to the redmine issue [2].

[1] - https://github.com/wso2/carbon4-kernel/pull/198
[2] - https://redmine.wso2.com/issues/3686

Thanks.
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please Review and Merge PR

[Jagath Sisirakumara Ariyarathne]

Hi,

$subject [1] to fix the Validate Mediator UI issue.

[1] - https://github.com/wso2/carbon-mediation/pull/87


Thanks.

On Mon, Mar 23, 2015 at 10:25 PM, Jagath Sisirakumara Ariyarathne 
jaga...@wso2.com wrote:

 Hi Maheeka,

 Thanks for the support and I will do required changes and check.

 On Mon, Mar 23, 2015 at 6:42 PM, Maheeka Jayasuriya mahe...@wso2.com
 wrote:

 Correction : All variables that get assigned with value.getExpression()
 now needs to be changed to SynapsePath, if they are still declared as
 SynapseXPath or they need to be casted to SynapseXPath.

 Thanks,
 Maheeka

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Mon, Mar 23, 2015 at 6:11 PM, Maheeka Jayasuriya mahe...@wso2.com
 wrote:

 Hi Jagath,

 As discussed, there seems Value class has been changed to contain a
 SynapsePath instead of SynapseXPath [1]. So all variables that get assigned
 with value.getExpression() now needs to be changed to SynapseXPath, if
 they are still using SynapsePath.

 This will have to be fixed.

 [1]
 https://github.com/wso2/wso2-synapse/blob/a14ab065f00bf8a267562787a32e511ff5da6b4e/modules/core/src/main/java/org/apache/synapse/mediators/Value.java

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Sun, Mar 22, 2015 at 8:31 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Maheeka,

 I created a sequence and tried to add validate mediator. But cannot
 save it and gives the error.

 [image: Inline image 4]

 Thanks.

 On Sun, Mar 22, 2015 at 8:21 AM, Maheeka Jayasuriya mahe...@wso2.com
 wrote:

 Seems to be so Jagath. What's the mediator that you have used?


 On Thursday, March 19, 2015, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi,

 When I built and run wso2esb-4.9.0-M8-SNAPSHOT pack, it gives below
 type conversion error while opening validate mediator design view and it
 does not show configurations window.

 org.apache.jasper.JasperException: Unable to compile class for JSP:

 An error occurred at line: 102 in the jsp file:
 /validate-mediator/edit-mediator.jsp
 Type mismatch: cannot convert from SynapsePath to SynapseXPath
 99:
 100: if (schemaKey != null) {
 101: showValue =
 schemaKey.getKeyValue();
 102: synapseXPath =
 schemaKey.getExpression();
 103:
 104: isStaticKey =
 showValue != null  !.equals(showValue);
 105:



 Is this due to a source versions mismatch? I used develop branches to
 build the product.

 Thanks.

 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048



 --
 Sent from Gmail Mobile




 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048






 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB] Error in Validate Mediator Configuration UI

[Jagath Sisirakumara Ariyarathne]

Hi Maheeka,

Thanks for the support and I will do required changes and check.

On Mon, Mar 23, 2015 at 6:42 PM, Maheeka Jayasuriya mahe...@wso2.com
wrote:

 Correction : All variables that get assigned with value.getExpression()
 now needs to be changed to SynapsePath, if they are still declared as
 SynapseXPath or they need to be casted to SynapseXPath.

 Thanks,
 Maheeka

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Mon, Mar 23, 2015 at 6:11 PM, Maheeka Jayasuriya mahe...@wso2.com
 wrote:

 Hi Jagath,

 As discussed, there seems Value class has been changed to contain a
 SynapsePath instead of SynapseXPath [1]. So all variables that get assigned
 with value.getExpression() now needs to be changed to SynapseXPath, if
 they are still using SynapsePath.

 This will have to be fixed.

 [1]
 https://github.com/wso2/wso2-synapse/blob/a14ab065f00bf8a267562787a32e511ff5da6b4e/modules/core/src/main/java/org/apache/synapse/mediators/Value.java

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Sun, Mar 22, 2015 at 8:31 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi Maheeka,

 I created a sequence and tried to add validate mediator. But cannot save
 it and gives the error.

 [image: Inline image 4]

 Thanks.

 On Sun, Mar 22, 2015 at 8:21 AM, Maheeka Jayasuriya mahe...@wso2.com
 wrote:

 Seems to be so Jagath. What's the mediator that you have used?


 On Thursday, March 19, 2015, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi,

 When I built and run wso2esb-4.9.0-M8-SNAPSHOT pack, it gives below
 type conversion error while opening validate mediator design view and it
 does not show configurations window.

 org.apache.jasper.JasperException: Unable to compile class for JSP:

 An error occurred at line: 102 in the jsp file:
 /validate-mediator/edit-mediator.jsp
 Type mismatch: cannot convert from SynapsePath to SynapseXPath
 99:
 100: if (schemaKey != null) {
 101: showValue =
 schemaKey.getKeyValue();
 102: synapseXPath =
 schemaKey.getExpression();
 103:
 104: isStaticKey =
 showValue != null  !.equals(showValue);
 105:



 Is this due to a source versions mismatch? I used develop branches to
 build the product.

 Thanks.

 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048



 --
 Sent from Gmail Mobile




 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048






-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Malithi Edirisinghe

[Jagath Sisirakumara Ariyarathne]

Congratulations Malithi..!!!

On Sun, Mar 22, 2015 at 10:24 AM, Milinda Perera milin...@wso2.com wrote:

 Congratz Malithi ... :)

 On Sun, Mar 22, 2015 at 8:39 AM, Milan Perera mi...@wso2.com wrote:

 Congratz Malithi...!!!

 On Sat, Mar 21, 2015 at 8:29 PM, Rasika Perera rasi...@wso2.com wrote:

 Congratz Malithi!!!

 On Fri, Mar 20, 2015 at 7:38 PM, Isura Karunaratne is...@wso2.com
 wrote:

 Congratulations Malithi...!!

 On Fri, Mar 20, 2015 at 8:36 AM, Hasintha Indrajee hasin...@wso2.com
 wrote:

 Congratulations Malithi...!!

 On Fri, Mar 20, 2015 at 9:19 AM, Asok Perera as...@wso2.com wrote:

 Congratz Malithi !!!

 *Asok Aravinda Perera*
 Software Engineer
 WSO2, Inc.;http://wso2.com/
 http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2Fsa=Dsntz=1usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ
 lean.enterprise.middleware

 Mobile: +94722241032

 On Fri, Mar 20, 2015 at 6:38 PM, Gayan Gunawardana ga...@wso2.com
 wrote:

 Congratzzz Malithiii...

 On Fri, Mar 20, 2015 at 5:13 PM, Keerthika Mahendralingam 
 keerth...@wso2.com wrote:

 Congratz Malithi!!!

 On Fri, Mar 20, 2015 at 5:10 PM, Elilmatha Sivanesan 
 elilma...@wso2.com wrote:

 Congratz Malithi

 On Fri, Mar 20, 2015 at 5:08 PM, Madusanka Premaratne 
 madusan...@wso2.com wrote:

 Congrats Malithi.!!!

 On Fri, Mar 20, 2015 at 5:03 PM, Dinithi De Silva 
 dinit...@wso2.com wrote:

 Congratz Malithi...

 On Fri, Mar 20, 2015 at 3:57 PM, Himasha Guruge 
 himas...@wso2.com wrote:

 Congrats Malithi!!

 On Fri, Mar 20, 2015 at 3:54 PM, Thanuja Jayasinghe 
 than...@wso2.com wrote:

 Congratz Malithi...

 On Fri, Mar 20, 2015 at 3:04 PM, Johann Nallathamby 
 joh...@wso2.com wrote:

 Hi All,

 It's my pleasure to announce Malithi Edirisinghe as a WSO2
 Committer. Malithi has been a valuable contributor for WSO2
 Identity Server product, and in recognition of her contribution 
 to WSO2,
 she has been voted as a WSO2 Committer.

 Malithi, congratulations and keep up the good work!

 Thanks  Regards.

 --

 *Johann Dilantha Nallathamby*
 Associate Technical Lead  Product Lead of WSO2 Identity
 Server
 Integration Technologies Team
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - *+9476950*
 Blog - *http://nallaa.wordpress.com
 http://nallaa.wordpress.com*

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Thanuja Lakmal*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 *lean.enterprise.middleware*
 Mobile: +94715979891 +94758009992

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Himasha Guruge
 *Software Engineer*
 WS*O2* *Inc.*
 Mobile: +94 777459299
 himas...@wso2.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Dinithi De Silva*
 Associate Software Engineer, WSO2 Inc.
 m:+94716667655 | e:dinit...@wso2.com | w: www.wso2.com
 | a: #20, Palm Grove, Colombo 03

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Madusanka Premaratne* | Associate Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 835 70 73| Work: +94 112 145 345
 Email: madusan...@wso2.com | Web: www.wso2.com

 [image: Facebook] https://www.facebook.com/maduzanka [image:
 Twitter] https://twitter.com/rmmpremaratne [image: Google Plus]
 https://plus.google.com/u/0/+MadusankaPremaratnemaduz/about/p/pub
  [image: Linkedin] http://lk.linkedin.com/in/madusanka/ [image:
 Instagram] http://instagram.com/madusankapremaratne [image:
 Skype] http://@rmmpremaratne


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *S.Elilmatha*
 Associate  Software Engineer,

 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 Mobile 0779842221.


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 dev-requ...@wso2.org
 Keerthika Mahendralingam
 Associate Software Engineer
 Mobile :+94 (0) 776 121144
 keerth...@wso2.com
 WSO2, Inc.
 lean . enterprise . middleware

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Gayan Gunawardana
 Software Engineer; WSO2 Inc.; http://wso2.com/
 Email: ga...@wso2.com
 Mobile: +94 (71) 8020933

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Hasintha Indrajee
 Software Engineer
 WSO2, Inc.
 Mobile:+94 771892453


 ___
 Dev mailing list
 Dev@wso2.org
 

Re: [Dev] [DEV][ESB] Error in Validate Mediator Configuration UI

[Jagath Sisirakumara Ariyarathne]

Hi Maheeka,

I created a sequence and tried to add validate mediator. But cannot save it
and gives the error.

[image: Inline image 4]

Thanks.

On Sun, Mar 22, 2015 at 8:21 AM, Maheeka Jayasuriya mahe...@wso2.com
wrote:

 Seems to be so Jagath. What's the mediator that you have used?


 On Thursday, March 19, 2015, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi,

 When I built and run wso2esb-4.9.0-M8-SNAPSHOT pack, it gives below type
 conversion error while opening validate mediator design view and it does
 not show configurations window.

 org.apache.jasper.JasperException: Unable to compile class for JSP:

 An error occurred at line: 102 in the jsp file:
 /validate-mediator/edit-mediator.jsp
 Type mismatch: cannot convert from SynapsePath to SynapseXPath
 99:
 100: if (schemaKey != null) {
 101: showValue =
 schemaKey.getKeyValue();
 102: synapseXPath =
 schemaKey.getExpression();
 103:
 104: isStaticKey = showValue
 != null  !.equals(showValue);
 105:



 Is this due to a source versions mismatch? I used develop branches to
 build the product.

 Thanks.

 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048



 --
 Sent from Gmail Mobile




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][ESB] Error in Validate Mediator Configuration UI

[Jagath Sisirakumara Ariyarathne]

Hi,

When I built and run wso2esb-4.9.0-M8-SNAPSHOT pack, it gives below type
conversion error while opening validate mediator design view and it does
not show configurations window.

org.apache.jasper.JasperException: Unable to compile class for JSP:

An error occurred at line: 102 in the jsp file:
/validate-mediator/edit-mediator.jsp
Type mismatch: cannot convert from SynapsePath to SynapseXPath
99:
100: if (schemaKey != null) {
101: showValue =
schemaKey.getKeyValue();
102: synapseXPath =
schemaKey.getExpression();
103:
104: isStaticKey = showValue !=
null  !.equals(showValue);
105:



Is this due to a source versions mismatch? I used develop branches to build
the product.

Thanks.

-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Updating wso2esb-4.9.0-M8-SNAPSHOT with Synapse Core from develop branch

[Jagath Sisirakumara Ariyarathne]

Hi Maheeka,

As you mentioned, I updated carbon-mediation version 4.3.3-SNAPSHOT
(develop branch version) in product-esb pom file and it is working fine now.

Thanks for the support.

On Tue, Mar 17, 2015 at 9:30 AM, Maheeka Jayasuriya mahe...@wso2.com
wrote:

 Hi Jagath,

 I have followed the same steps and it works for me. I updated,
 synapse.version2.1.3-wso2v3-SNAPSHOT/synapse.version in both
 product-esb and carbon-mediation pom files. Additionally I have updated
 carbon-mediation version as well, since I did changes to that too, but this
 should work.

 Thanks,
 Maheeka

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Tue, Mar 17, 2015 at 9:17 AM, Jagath Sisirakumara Ariyarathne 
 jaga...@wso2.com wrote:

 Hi,

 I did some updates in synapse core using develop branch. To test it with wso2
 esb-4.9.0-M8-SNAPSHOT pack, i followed below steps according to [1].

- Built synapse core from develop branch.
(synapse-core-2.1.3-wso2v3-SNAPSHOT)
- Updated new synapse version in carbon-mediation and product-esb pom
files. (develop branches of both)
- Built both carbon-mediation and product-esb.

 But the new synapse core library is not there in newly built ESB pack.
 Still the old version synapse-core-2.1.3.wso2v2 can be found and I cannot
 start ESB with synapse-core-2.1.3-wso2v3-SNAPSHOT.

 Is the above procedure correct and anything I missed there?

 [1] - https://www.mail-archive.com/dev@wso2.org/msg41770.html

 Thanks

 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev





-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Identify Comment Nodes in an XML document using Axiom 1.2.14 API

[Jagath Sisirakumara Ariyarathne]

Hi,

I have a requirement to $subject.

E.g. Below is a sample XML document.

sequence
   !-- Start Comment--
   in
log category=DEBUG/log
   /in
   out
  log category=DEBUG/log
   /out
   !-- End comment --
/sequence


Requirement is to retrieve below nodes only.

!-- Start Comment--
!-- End comment --


One implementation would be iterating through all XML Nodes and identify
nodes which has type COMMENT_NODE. We can use method
OMContainer.getChildren()
which returns all nodes in the document.

Is there any other method of doing this in Axiom, rather than going through
all nodes?

Thanks
-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Dinesh J Weerakkody

[Jagath Sisirakumara Ariyarathne]

Congratulations Dinesh!...

On Thu, Mar 12, 2015 at 9:45 AM, Thilini Cooray thili...@wso2.com wrote:

 Congratulations, Dinesh.

 On Thu, Mar 12, 2015 at 9:42 AM, Chanuka Dissanayake chan...@wso2.com
 wrote:

 Congratulations Dinesh..!

 On Thu, Mar 12, 2015 at 9:40 AM, Thusitha Thilina Dayaratne 
 thusit...@wso2.com wrote:

 Congratulations Dinesh ..!

 On Thu, Mar 12, 2015 at 8:59 AM, Lasitha Wattaladeniya 
 lasit...@wso2.com wrote:

 Congratulations Dinesh :) !

 On Thu, Mar 12, 2015 at 8:53 AM, Vijitha Ekanayake vijit...@wso2.com
 wrote:

 Congratulations Dinesh !!!

 On Thu, Mar 12, 2015 at 8:41 AM, Tharik Kanaka tha...@wso2.com
 wrote:

 Congratulations Dinesh

 On Thu, Mar 12, 2015 at 8:33 AM, Ravindra Ranwala ravin...@wso2.com
 wrote:

 Congratulations Dinesh !

 On Thu, Mar 12, 2015 at 8:30 AM, Chamalee De Silva 
 chama...@wso2.com wrote:

 congrats!

 On Thu, Mar 12, 2015 at 8:24 AM, Abimaran Kugathasan 
 abima...@wso2.com wrote:

 Congrats!

 On Thu, Mar 12, 2015 at 8:17 AM, Nuwan Dias nuw...@wso2.com
 wrote:

 Hi,

 It is with great pleasure we welcome DineshW as a WSO2 Committer.
 @Dinesh, congratulations and keep up the good work!

 Thanks,
 NuwanD.

 --
 Nuwan Dias

 Associate Tech Lead - WSO2, Inc. http://wso2.com
 email : nuw...@wso2.com
 Phone : +94 777 775 729

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Thanks
 Abimaran Kugathasan

 Software Engineer | WSO2 Inc
 Data  APIs Technologies Team
 Mobile : +94 773922820

 http://stackoverflow.com/users/515034
 http://lk.linkedin.com/in/abimaran
 http://www.lkabimaran.blogspot.com/
 https://github.com/abimaran  https://twitter.com/abimaran


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --

 Chamalee De Silva

 Software Engineer | WSO2

 E:chama...@wso2.com nirosh...@wso2.com
 M :0711540738| http://wso2.com http://wso2.com/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Ravindra Ranwala
 Software Engineer
 WSO2, Inc: http://wso2.com
 http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg
 Mobile: +94714198770


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --

 *Tharik Kanaka* | Associate Software Engineer

 WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka

 Email: tha...@wso2.com | Web: www.wso2.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Vijitha Ekanayake
 Software Engineer*, *WSO2, Inc.; http://wso2.com/
 Mobile : +94 777 24 73 39 | +94 718 74 44 08
 lean.enterprise.middleware

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Lasitha Wattaladeniya
 Software Engineer
 WSO2, Inc. | http://wso2.com
 lean. enterprise. middleware

 Mobile : +94719397528
 Blog : techreadme.blogspot.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Thusitha Dayaratne
 Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 Mobile  +94712756809
 Blog  alokayasoya.blogspot.com
 Abouthttp://about.me/thusithathilina


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Chanuka Dissanayake
 *Software Engineer | **WSO2 Inc.*; http://wso2.com

 Mobile: +94 71 33 63 596
 Email: chan...@wso2.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Best Regards,

 *Thilini Cooray*
 Software Engineer
 Mobile : +94 (0) 774 570 112 %2B94%20%280%29%20773%20451194
 E-mail : thili...@wso2.com

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Irham Iqbal

[Jagath Sisirakumara Ariyarathne]

Congratulations Irham

On Tue, Mar 10, 2015 at 1:29 PM, Dimuthu De Lanerolle dimut...@wso2.com
wrote:

 Congratz Irham !!!

 On Tue, Mar 10, 2015 at 1:27 PM, Saneth Dharmakeerthi sane...@wso2.com
 wrote:

 Congratulations Irham...

 Thanks and Best Regards,

 Saneth Dharmakeerthi
 Senior Software Engineer
 WSO2, Inc.
 Mobile: +94772325511

 On Tue, Mar 10, 2015 at 1:23 PM, Malintha Adikari malin...@wso2.com
 wrote:

 Congratulations Irham!

 On Tue, Mar 10, 2015 at 7:51 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi all,

 It's my pleasure to welcome Irham Iqbal as a WSO2 Committer.

 Irham, welcome aboard and keep up the good work!

 Thanks,
 Krishantha.

 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Malintha Adikari*
  Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 Mobile: +94 71 2312958
 Blog:http://malinthas.blogspot.com
 Page:   http://about.me/malintha

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Dimuthu De Lanerolle
 Software Engineer
 WSO2 Inc.
 lean . enterprise . middlewear.
 http://wso2.com/
 Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSDL2Java returns java.lang.NoClassDefFoundError: javax/wsdl/WSDLException

[Jagath Sisirakumara Ariyarathne]

Hi Rasika,

Check whether correct jar files there in below configuration paths as
mentioned in Service Stub pom.

path id=wsdl2java.classpath
pathelement
location=${settings.localRepository}/org/apache/ws/commons/axiom/wso2/axiom/1.2.11.wso2v4/axiom-1.2.11.wso2v4.jar/
pathelement
location=${settings.localRepository}/org/apache/axis2/wso2/axis2-client/1.6.1.wso2v10/axis2-client-1.6.1.wso2v10.jar
/
pathelement
location=${settings.localRepository}/org/apache/axis2/wso2/axis2/1.6.1.wso2v10/axis2-1.6.1.wso2v10.jar
/
/path

Thanks.

On Mon, Mar 2, 2015 at 4:06 PM, Rasika Perera rasi...@wso2.com wrote:

 ​Hi all,

 I am following [1] tutorial. I have placed the WSDL on the class-path.
 When trying to create the stub using `wsdl2java` it returns following error.

 [INFO] --- maven-antrun-plugin:1.1:run (source-code-generation) @
 org.wso2.carbon.employee.mgt.stub ---
 [INFO] Executing tasks
  [java] Exception in thread main *java.lang.NoClassDefFoundError:
 javax/wsdl/WSDLException*
  [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
  [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
  [java] Caused by: java.lang.ClassNotFoundException:
 javax.wsdl.WSDLException
  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
  [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
  [java] at java.security.AccessController.doPrivileged(Native Method)
  [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
  [java] at
 sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
  [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
  [java] ... 2 more
  [java] Java Result: 1
 [INFO] Executed tasks

 I have added the dependencies for axis2, axiom and wsdl4j. For further
 reference pom.xml of the sub-project is attached.

 Appreciate any help to solve this error.

 [1]
 http://wso2.com/library/tutorials/2014/03/how-to-write-a-wso2-carbon-component/
 ​


 --
 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

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev