from:"Riyafa Abdul Hameed"

Re: [Dev] Queues in WSO2

2018-08-05 Thread Riyafa Abdul Hameed

Hi,

You can use the JMS transport of WSO2 EI for the purpose as well using any
message broker that supports JMS protocol:
https://docs.wso2.com/display/EI630/JMS+Transport

Thanks,
Riyafa

On Wed, Aug 1, 2018 at 8:43 AM Shakila Sasikaran  wrote:

> Hi Aman,
>
> Yes, you can use WSO2 Message Broker
> <https://wso2.com/products/message-broker/> or the broker profile of WSO2 
> Enterprise
> Integrator <https://wso2.com/integration> as the message broker. And you
> can publish the message to the queue from WSO2 ESB or WSO2 EI. Please find
> more information on the documentation [1].
>
> [1] https://docs.wso2.com/display/MB300/Integrating+WSO2+ESB
>
> Thanks
>
> On Tue, Jul 31, 2018 at 3:53 PM, Aman Singh 
> wrote:
>
>> Hi Shakila,
>>
>> Can I use Queues in WSO2 to pass/store message? If yes, which mediator
>> does I need to refer?
>>
>> Your help are always appreciated.
>>
>> Thank you,
>> Aman.
>>
>
>
>
> --
> Shakila Sasikaran
> Software Engineer
> Mobile :+94 (0) 77 526 6848
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com 
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unsubscribe

2018-07-26 Thread Riyafa Abdul Hameed

Hi,

You need to send a mail to dev-requ...@wso2.org with subject as unsubscribe
to be unsubscribed from this list.

[1] https://wso2.com/mail/

Thanks,
Riyafa

On Mon, Jul 23, 2018 at 7:09 PM Kartik A  wrote:

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


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com 
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] VFS FTP connection timeout settings

2018-05-10 Thread Riyafa Abdul Hameed

Hi Norberto,

Can you please report an issue here[1] with a complete example on how to
reproduce. Please include a sample proxy and the logs generated. Also
include details on how to enable the logs you generated. We shall look into
it.

[1] https://github.com/wso2/product-ei/issues

Thanks,
Riyafa

On Wed, May 9, 2018 at 3:03 PM Fernandes, Norberto <
nfern...@jaguarlandrover.com> wrote:

> Hi,
>
> Riyafa, I am using EI 6.2.0.
>
> Thishani, On the proxy I defined the maxRetryCount and reconnectTimeout
> like:
>
> 
>ftp://:xx...@10.xxx.206
> /QA/J?transport.vfs.ReconnectTimeout=10transport.vfs.MaxRetryCount=5>
>
> If you notice on the log that I sent, these parameters are defined and
> printed by the VFSOutTransportInfo. But I don't think these parameters are
> sent to the vfs ftp provider classes.
> Or there are other set of parameters to set it. But I could not find any
> documentation on these.
>
> Regards,
> Norberto
>
>
>
> On 9 May 2018 at 05:25, Thishani Lucas <thish...@wso2.com> wrote:
>
>> Hi Norberto,
>>
>> As you can see from the code [1], these logs are printed if there's a
>> number format exp. How did you define the MaxRetryCount and
>> ReconnectTimeout?
>>
>> [1]
>> https://github.com/wso2/wso2-commons-vfs/blob/2.2.x/commons-vfs2/src/main/java/org/apache/commons/vfs2/provider/ftp/FtpClientFactory.java#L140
>>
>> Thanks,
>> Thishani
>>
>> On Wed, May 9, 2018 at 5:48 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Which version of ESB/EI are you using?
>>>
>>> Regards,
>>> Riyafa
>>>
>>> On Tue, 8 May 2018, 20:11 Fernandes, Norberto, <
>>> nfern...@jaguarlandrover.com> wrote:
>>>
>>>> Hi team,
>>>>
>>>> I have a proxy that is sending data using the vfs transport and ftp
>>>> protocol.
>>>> I have this logging when I enable the logging.
>>>>
>>>> TID: [-1234] [] [2018-05-08 15:11:18,818] DEBUG
>>>> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  Using the
>>>> fileURI: ftp://userQA:pas...@10.xxx.xx.xxx
>>>> /QA/AXES/XXion_Test.csv?transport.v
>>>>
>>>> fs.ReconnectTimeout=10=5
>>>> {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>>>>
>>>> TID: [-1234] [] [2018-05-08 15:11:18,818] DEBUG
>>>> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  Using the
>>>> maxRetryCount  : 5 {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>>>>
>>>> TID: [-1234] [] [2018-05-08 15:11:18,818] DEBUG
>>>> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  Using the
>>>> reconnectionTimeout : 1
>>>> {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>>>>
>>>> TID: [-1234] [] [2018-05-08 15:11:18,819] DEBUG
>>>> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  Using the
>>>> append : false
>>>> {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>>>>
>>>> TID: [-1234] [] [2018-05-08 15:11:18,819] DEBUG
>>>> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  File locking
>>>>   : OFF {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>>>>
>>>> TID: [-1234] [] [2018-05-08 15:11:18,819]  WARN
>>>> {org.apache.commons.vfs2.provider.ftp.FtpClientFactory$FtpConnectionFactory}
>>>> -  Invalid connection timeout null. Set the connectionTimeout as 5000.
>>>> (default) {org.apache.com
>>>>
>>>> mons.vfs2.provider.ftp.FtpClientFactory$FtpConnectionFactory}
>>>>
>>>> TID: [-1234] [] [2018-05-08 15:11:18,819]  WARN
>>>> {org.apache.commons.vfs2.provider.ftp.FtpClientFactory$FtpConnectionFactory}
>>>> -  Invalid connection retry count null. Set the connectionRetryCount
>>>> as 5. (default) {org.apache
>>>>
>>>> .commons.vfs2.provider.ftp.FtpClientFactory$FtpConnectionFactory}
>>>>
>>>>
>>>> I have the RecoonectTimeout and the MaxRetryCount settings defined. But
>>>> the apache commons vfs class indicates that the connection timeout and
>>>> retry count is not defined.
>>>>
>>>> How can I defined these parameters?
>>>>
>>>> Regards,
>>>> Norberto
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2

Re: [Dev] VFS FTP connection timeout settings

2018-05-08 Thread Riyafa Abdul Hameed

Hi,

Which version of ESB/EI are you using?

Regards,
Riyafa

On Tue, 8 May 2018, 20:11 Fernandes, Norberto, 
wrote:

> Hi team,
>
> I have a proxy that is sending data using the vfs transport and ftp
> protocol.
> I have this logging when I enable the logging.
>
> TID: [-1234] [] [2018-05-08 15:11:18,818] DEBUG
> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  Using the fileURI
>   : ftp://userQA:pas...@10.xxx.xx.xxx
> /QA/AXES/XXion_Test.csv?transport.v
>
> fs.ReconnectTimeout=10=5
> {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>
> TID: [-1234] [] [2018-05-08 15:11:18,818] DEBUG
> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  Using the
> maxRetryCount  : 5 {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>
> TID: [-1234] [] [2018-05-08 15:11:18,818] DEBUG
> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  Using the
> reconnectionTimeout : 1
> {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>
> TID: [-1234] [] [2018-05-08 15:11:18,819] DEBUG
> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  Using the append
>   : false {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>
> TID: [-1234] [] [2018-05-08 15:11:18,819] DEBUG
> {org.apache.synapse.commons.vfs.VFSOutTransportInfo} -  File locking
> : OFF {org.apache.synapse.commons.vfs.VFSOutTransportInfo}
>
> TID: [-1234] [] [2018-05-08 15:11:18,819]  WARN
> {org.apache.commons.vfs2.provider.ftp.FtpClientFactory$FtpConnectionFactory}
> -  Invalid connection timeout null. Set the connectionTimeout as 5000.
> (default) {org.apache.com
>
> mons.vfs2.provider.ftp.FtpClientFactory$FtpConnectionFactory}
>
> TID: [-1234] [] [2018-05-08 15:11:18,819]  WARN
> {org.apache.commons.vfs2.provider.ftp.FtpClientFactory$FtpConnectionFactory}
> -  Invalid connection retry count null. Set the connectionRetryCount as
> 5. (default) {org.apache
>
> .commons.vfs2.provider.ftp.FtpClientFactory$FtpConnectionFactory}
>
>
> I have the RecoonectTimeout and the MaxRetryCount settings defined. But
> the apache commons vfs class indicates that the connection timeout and
> retry count is not defined.
>
> How can I defined these parameters?
>
> Regards,
> Norberto
>
> ___
> 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

Re: [Dev] Cache mediator not working good for storing json responses.

2018-04-08 Thread Riyafa Abdul Hameed

Hi,

The EI 6.2.0 has been released[1]. Can you test with the cache mediator and
let us know if the issue persists?

[1] https://wso2.com/integration/install/download/?type=downloader

Regards,
Riyafa

On Sat, Apr 7, 2018 at 12:59 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> Hi  Shakila *,*
>
> Yes for this* mock backend which returns a simple JSON payload , even
> I didn't get the mentioned error. *
> But when i am trying with our
> *backend service which is returning a big json response of about 2000
> lines. *
> *The backend response contains some "$id": "2", "$type": "A.B, C.D", some
> nested arrays etc..  *
> With Regards,
> Aditya
>
>
>
> On Thu, Apr 5, 2018 at 8:54 AM, Shakila Sasikaran <shak...@wso2.com>
> wrote:
>
>> Hi Aditya,
>>
>> I tested your API configuration with a mock backend which returns a
>> simple JSON payload and I didn't get the mentioned error. Please find the
>> configurations [2].
>>
>> [1]
>> {
>> "test": "test"
>> }
>>
>> [2]
>> API:
>> http://ws.apache.org/ns/synapse; name="cacheAPI2"
>> context="/cache2">
>>
>>   
>>  
>> 
>>  
>>  > hashGenerator="org.wso2.carbon.mediator.cache.digest.REQUESTHASHGenerator"
>> timeout="5000" maxMessageSize="1">
>> 
>>  
>>  
>> 
>>  
>>  > scope="default" type="STRING"/>
>>  
>> 
>>  
>>  
>> 
>>  
>>  > type="STRING"/>
>>  
>> 
>>  
>>  
>>  
>>   
>>   
>>   
>>
>> 
>>
>> Endpoint:
>> http://ws.apache.org/ns/synapse; name="AgreementEP">
>>http://www.mocky.io/v2/5ac4b2ae2f2a00f5fb42
>> <http://www.mocky.io/v2/5ac4b2ae2f2a00f5fb42>*" method="get">
>>   
>>  1.0
>>   
>>   
>>  0
>>  0
>>   
>>
>> 
>>
>> Thanks
>>
>> On Wed, Apr 4, 2018 at 10:25 PM, aditya shivankar <
>> shivankar.adit...@gmail.com> wrote:
>>
>>> Respected Sir/Madam,
>>>
>>> If you are able to store any json response into cache. Using any freely
>>> available rest service on net. Please share me the api example.
>>>
>>> Thanks and Regards,
>>> Aditya
>>>
>>> On Wed, Apr 4, 2018 at 10:22 PM, aditya shivankar <
>>> shivankar.adit...@gmail.com> wrote:
>>>
>>>> Respected Sir/Madam,
>>>>
>>>> I am using wso2ei 6.1.1 .
>>>>
>>>> The backend service is returning a big json response of about 2000
>>>> lines. If I remove cache mediator both finder and collector from above
>>>> service.  I am able to receive the backend response in wso2ei api service.
>>>> The backend response contains some "$id": "2", "$type": "A.B, C.D",
>>>> some nested arrays etc..
>>>>
>>>> With Regards,
>>>> Aditya
>>>>
>>>>
>>>> On Wed, Apr 4, 2018 at 5:15 PM, Riyafa Abdul Hameed <riy...@wso2.com>
>>>> wrote:
>>>>
>>>>> This is similar to this issue[1]. Which version are you using?
>>>>>
>>>>> [1] https://wso2.org/jira/browse/ESBJAVA-4318
>>>>>
>>>>> On Wed, Apr 4, 2018 at 5:07 PM, Thishani Lucas <thish...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Aditya,
>>>>>>
>>>>>> Could you please elaborate more about the response sent by the
>>>>>> backend? What kind of message type does it send?
>>>>>>
>>>>>> Thanks,
>>>>>> Thishani
>>>>>>
>>>>>> On Wed, Apr 4, 2018 at 4:26 PM, aditya shivankar <
>>>>>> shivankar.adit...@gmail.com> wrote:
>>>>>>
>>>>>>> Respected Madam,
>>>>>>>
>>>>>>> Tried adding ">>>>>> action="remove"/>".
>>>>>>>
>>>>>>> But still got the same erro

Re: [Dev] Cache mediator not working good for storing json responses.

2018-04-04 Thread Riyafa Abdul Hameed

This is similar to this issue[1]. Which version are you using?

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

On Wed, Apr 4, 2018 at 5:07 PM, Thishani Lucas <thish...@wso2.com> wrote:

> Hi Aditya,
>
> Could you please elaborate more about the response sent by the backend?
> What kind of message type does it send?
>
> Thanks,
> Thishani
>
> On Wed, Apr 4, 2018 at 4:26 PM, aditya shivankar <
> shivankar.adit...@gmail.com> wrote:
>
>> Respected Madam,
>>
>> Tried adding "> action="remove"/>".
>>
>> But still got the same error. Plus the rest service i am using is not
>> returning empty response, tested it.
>>
>> 
>> http://ws.apache.org/ns
>> /synapse">
>> 
>> 
>> 
>> 
>> 
>>
>> > maxMessageSize="1" scope="per-host" timeout="5000">
>> 
>> 
>> 
>>
>> 
>> 
>> 
>> > type="STRING" value="1392"/>
>> > action="remove"/>
>> 
>> 
>> 
>> 
>> 
>> 
>> > value="true"/>
>> 
>> 
>> 
>>
>> 
>>
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> With Regards,
>> Aditya
>>
>>
>> On Wed, Apr 4, 2018 at 4:16 PM, Thivya Mahenthirarasa <thi...@wso2.com>
>> wrote:
>>
>>> Hi Adiya,
>>>
>>> According to the logs, you are receiving 202 accepted success code, that
>>> means  the response cached for the Endpoint might returning an empty
>>> body.
>>>
>>>  Could you please add the following property before cache mediator in
>>> order to return the body from the cache to the Endpoint.
>>>
>>>
>>>  
>>>
>>>
>>> Try out the solution and let us know whether you could able to sort out the 
>>> exception
>>>
>>>
>>>
>>> Regards,
>>>
>>> Thivya
>>>
>>>
>>> On Wed, Apr 4, 2018 at 3:58 PM, aditya shivankar <
>>> shivankar.adit...@gmail.com> wrote:
>>>
>>>> Respected Sir/Madam,
>>>>
>>>> Below is my api :
>>>>
>>>> 
>>>> http://ws.apache.org/ns
>>>> /synapse">
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>
>>>> >>> maxMessageSize="1" scope="per-host" timeout="5000">
>>>> 
>>>> 
>>>> 
>>>>
>>>> 
>>>> 
>>>> 
>>>> >>> type="STRING" value="1392"/>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> >>> value="true"/>
>>>> 
>>>> 
>>>> 
>>>>
>>>> 
>>>>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>
>>>> and my endpoint :
>>>>
>>>> 
>>>> http://ws.apache.org/ns/synapse;>
>>>> 
>>>> 
>>>>
>>>>
>>>> Getting below error :
>>>>
>>>> ERROR - CacheMediator Error setting response envelope from cache :
>>>> mediation.cache_key
>>>> javax.xml.soap.SOAPException: org.apache.axiom.om.OMException: SOAP
>>>> message MUST NOT contain Processing Instructions(PI)
>>>>
>>>> Please find logs attached.
>>>>
>>>> With Regards,
>>>> Aditya
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Thivya Mahenthirarasa*
>>>
>>> *Software Engineer -Support Team | WSO2*
>>>
>>>
>>> *Email: thi...@wso2.com <thi...@wso2.com>*
>>>
>>> *Mobile: +94766461966 <http://wso2.com/signature>*
>>> *Web: http://wso2.com <http://wso2.com>*
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> *Thishani Lucas*
> *Software Engineer*
> *WSO2 Lanka (Private) Limited**: http://wso2.com <http://wso2.com/>*
> *lean.enterprise.middle-ware*
>
> *Tel: +94 77 2556931 *
>
> *LinkedIn: https://www.linkedin.com/in/thishani-lucas/
> <https://www.linkedin.com/in/thishani-lucas/>*
>
> <http://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.2.0 RC2

2018-03-17 Thread Riyafa Abdul Hameed

/v6.2.0-rc2
>>>>> <https://github.com/wso2/product-ei/tree/v6.2.0-rc2>*
>>>>>
>>>>> Please vote as follows:
>>>>> [+] Stable - go ahead and release
>>>>> [-] Broken - do not release (explain why)
>>>>>
>>>>> ~The WSO2 Integration Team~
>>>>>
>>>>>
>>>>> --
>>>>> Himasha Guruge
>>>>> Senior Software Engineer
>>>>> WS*O2* *Inc.*
>>>>> Mobile: +94 777459299 <+94%2077%20745%209299>
>>>>> himas...@wso2.com
>>>>>
>>>>> ___
>>>>> Architecture mailing list
>>>>> architect...@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Malaka.
>>>> --
>>>> Malaka Gangananda - Software Engineer | WSO2
>>>> Email : mala...@wso2.com
>>>> Mobile : +94713564340 <071%20356%204340>
>>>> Web : http://wso2.com
>>>>   <http://wso2.com/signature>
>>>>
>>>> ___
>>>> Architecture mailing list
>>>> architect...@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Nandika Jayawardana
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Mathuriga Thavarajah*
>> Software Engineer
>> WSO2 Inc. - http ://wso2.com
>>
>> Email : mathur...@wso2.com
>> Mobile  : +94778191300 <+94%2077%20819%201300>
>>
>>
>>
>> *[image: http://wso2.com/signature] <http://wso2.com/signature>*
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Regards,
>
> *Thishani Lucas*
> *Software Engineer*
> *WSO2 Lanka (Private) Limited**: http://wso2.com <http://wso2.com/>*
> *lean.enterprise.middle-ware*
>
> *Tel: +94 77 2556931 <+94%2077%20255%206931> *
>
> *LinkedIn: https://www.linkedin.com/in/thishani-lucas/
> <https://www.linkedin.com/in/thishani-lucas/>*
>
> <http://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EI] Getting empty cached response

2018-01-31 Thread Riyafa Abdul Hameed

d3252
> 00[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "cacheKey: -27-21-649412412586-85-97-
> 8340-52-11-819416[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "cache-control: no-cache[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "Content-Type: application/json; charset=UTF-8[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "Date: Thu, 01 Feb 2018 05:44:45 GMT[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "Transfer-Encoding: chunked[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "17[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "{"msg":"Hello Worldaa"}[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "0[\r][\n]"
>
> [2018-02-01 11:14:45,846] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-1 << "[\r][\n]"
>
> [2018-02-01 11:14:51,035] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 >> "GET /services/connectMockito HTTP/1.1[\r][\n]"
>
> [2018-02-01 11:14:51,036] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 >> "Host: keerthikas-macbook-pro.local:8280[\r][\n]"
>
> [2018-02-01 11:14:51,036] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 >> "User-Agent: curl/7.54.0[\r][\n]"
>
> [2018-02-01 11:14:51,036] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 >> "Accept: */*[\r][\n]"
>
> [2018-02-01 11:14:51,037] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 >> "Content-Type: application/json[\r][\n]"
>
> [2018-02-01 11:14:51,037] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 >> "[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "HTTP/1.1 200 OK[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "access-control-allow-origin: *[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "X-Cloud-Trace-Context: 8321c3bfbcd3e65e547803b2ed3252
> 00[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "cacheKey: -27-21-649412412586-85-97-
> 8340-52-11-819416[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "cache-control: no-cache[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "Content-Type: application/json; charset=UTF-8[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "Date: Thu, 01 Feb 2018 05:44:51 GMT[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "Transfer-Encoding: chunked[\r][\n]"
>
> [2018-02-01 11:14:51,045] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "[\r][\n]"
>
> [2018-02-01 11:14:51,046] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "0[\r][\n]"
>
> [2018-02-01 11:14:51,046] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-2 << "[\r][\n]"--
> <dev-requ...@wso2.org>
> Keerthika Mahendralingam
> Software Engineer
> Mobile :+94 (0) 776 121144 <+94%2077%20612%201144>
> keerth...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>



-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] "Payload could not be written as JSON" error when using call mediator in blocking mode

2018-01-29 Thread Riyafa Abdul Hameed

Hi,

This is regarding the issue[1]. This occurs because the json stream is not
set in the MessageContext before the call mediator in blocking mode tries
to call the JsonFormatter.
We are setting the json stream only when building the message. Is there a
specific reason for setting it only when building the message? Can't we set
it before building the message? If this is set as soon as the message comes
in the issue could be resolved.

Or other option would be to set the json stream in the call mediator for
blocking mode which is not the best option.

For call mediator in non-blocking mode the message goes through the pass
through transport and hence has no issues, but when in blocking mode the
message formatter is called. Can someone explain why this difference in
behavior for the two modes of the same mediator?

[1]https://github.com/wso2/product-ei/issues/1805

Thanks,
Riyafa

-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unable to cache the response

2018-01-29 Thread Riyafa Abdul Hameed

t;
> [2018-01-29 14:28:39,015] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 << "[\r][\n]"
>
> [2018-01-29 14:28:39,582] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "HTTP/1.1 200 OK[\r][\n]"
>
> [2018-01-29 14:28:39,582] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "cache-control: no-cache[\r][\n]"
>
> [2018-01-29 14:28:39,582] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "access-control-allow-origin: *[\r][\n]"
>
> [2018-01-29 14:28:39,582] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "Content-Type: application/json; charset=UTF-8[\r][\n]"
>
> [2018-01-29 14:28:39,582] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "X-Cloud-Trace-Context: 4e909d0476e6249930df95cc5b5489
> 9a[\r][\n]"
>
> [2018-01-29 14:28:39,582] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "Date: Mon, 29 Jan 2018 08:58:39 GMT[\r][\n]"
>
> [2018-01-29 14:28:39,583] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "Server: Google Frontend[\r][\n]"
>
> [2018-01-29 14:28:39,583] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "Content-Length: 27[\r][\n]"
>
> [2018-01-29 14:28:39,583] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "[\r][\n]"
>
> [2018-01-29 14:28:39,583] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "{[\n]"
>
> [2018-01-29 14:28:39,583] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> " "msg": "Hello Worldaa"[\n]"
>
> [2018-01-29 14:28:39,583] [EI-Core] DEBUG - wire HTTP-Sender I/O
> dispatcher-4 >> "}"
>
> [2018-01-29 14:28:39,587] [EI-Core]  INFO - LogMediator To:
> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: ,
> MessageID: urn:uuid:b6b34d4e-e9c0-4228-afb6-54fc74fc2e03, Direction:
> response, Envelope:  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;><
> soapenv:Body>Hello Worldaa soapenv:Body>
>
> [2018-01-29 14:28:39,590] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "HTTP/1.1 200 OK[\r][\n]"
>
> [2018-01-29 14:28:39,590] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "access-control-allow-origin: *[\r][\n]"
>
> [2018-01-29 14:28:39,590] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "X-Cloud-Trace-Context: 4e909d0476e6249930df95cc5b5489
> 9a[\r][\n]"
>
> [2018-01-29 14:28:39,590] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "messageType: application/json[\r][\n]"
>
> [2018-01-29 14:28:39,590] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "cacheKey: -83912422-79-114-92-101-8043-
> 26-695-56120-127[\r][\n]"
>
> [2018-01-29 14:28:39,590] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "cache-control: no-cache[\r][\n]"
>
> [2018-01-29 14:28:39,590] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "Content-Type: application/json; charset=UTF-8[\r][\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "Date: Mon, 29 Jan 2018 08:58:39 GMT[\r][\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "Transfer-Encoding: chunked[\r][\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "Connection: keep-alive[\r][\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "[\r][\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "1b[\r][\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "{[\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << " "msg": "Hello Worldaa"[\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "}[\r][\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "0[\r][\n]"
>
> [2018-01-29 14:28:39,591] [EI-Core] DEBUG - wire HTTP-Listener I/O
> dispatcher-6 << "[\r][\n]"
>
> Thanks,
> Keerthika.
> --
> <dev-requ...@wso2.org>
> Keerthika Mahendralingam
> Software Engineer
> Mobile :+94 (0) 776 121144 <+94%2077%20612%201144>
> keerth...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>



-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] //jsonOject and $ are printing different jsons (different data content) at same location in API.

2018-01-29 Thread Riyafa Abdul Hameed

Hi,

Your issue has been fixed and shall be included in future releases.

Thanks,
Riyafa

On Fri, Jan 19, 2018 at 1:39 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> Respected SirThis issue does not exist in wso2ei-6.1.1
> But is present in  wso2ei-6.1.1-update7 wso2ei-6.1.1-update16 I cannot
> migrate to older version because I am using some fixes which are done in
> wso2ei-6.1.1-update7.
> Raised issue ://jsonOject and $ are printing different jsons (different
> data content) at same location in API #1771
> With Regards,Aditya
>
> On Fri, Jan 19, 2018 at 10:28 AM, aditya shivankar <
> shivankar.adit...@gmail.com> wrote:
>
>> Please provide the link to download the latest version wso2 EI.
>>
>> With Regards,
>> Aditya
>>
>> On Fri, Jan 19, 2018 at 10:18 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Hi Aditya,
>>>
>>> We observed this behavior. As I mentioned in my previous reply can you
>>> report an issue?
>>>
>>> Regards,
>>> Riyafa
>>>
>>> On Fri, Jan 19, 2018 at 10:09 AM, aditya shivankar <
>>> shivankar.adit...@gmail.com> wrote:
>>>
>>>> Hi ,
>>>>
>>>> My Question is while printing //jsonObject  I am able to print enriched
>>>> value tag "Value" as well.
>>>>
>>>> But while printing $ "value" element is missing . While both logs are
>>>> printed at same location in flow.
>>>>
>>>>
>>>> Log print of *//jsonObjec*t after enrichment:
>>>>
>>>> 
>>>> d8ccf265-6651-468f-8d1f-d935c3c7d857
>>>> 57
>>>> *PartyId*
>>>> 
>>>>
>>>> Log print of* json-eval($) *at same place after enrichment : *Value
>>>> tag missing*
>>>>
>>>> {
>>>> "a": "d8ccf265-6651-468f-8d1f-d935c3c7d857",
>>>> "b": "57"
>>>>
>>>> }
>>>>
>>>>
>>>> My Question is *not *why we are printing xml for //jsonObject.
>>>> Please guide.
>>>> I think *$* and *//jsonObject *or *$body* are representation of same
>>>> object just in different formats, at any point in flow.
>>>> Then why //jsonOject and $ are printing different jsons at same
>>>> location in API.
>>>>
>>>> Thanks,
>>>> Aditya
>>>>
>>>> On Fri, Jan 19, 2018 at 9:35 AM, Senduran Balasubramaniyam <
>>>> sendu...@wso2.com> wrote:
>>>>
>>>>> Hi Aditya,
>>>>>
>>>>> //jsonObject is an XPATH expression. When you apply an XPATH
>>>>> evaluation on a JSON, ESB / EI internally convert the JSON to XML, that's
>>>>> why you are seeing XML for //jsonObject xpath evaluation.
>>>>> Since you are sending a JSON payload it is good to use $ (which is a
>>>>> JSON path)
>>>>>
>>>>> Regards
>>>>> Senduran
>>>>>
>>>>> On Fri, Jan 19, 2018 at 3:28 AM, aditya shivankar <
>>>>> shivankar.adit...@gmail.com> wrote:
>>>>>
>>>>>> Respected Sir,
>>>>>>
>>>>>> //jsonOject and $ are printing different jsons at same location in
>>>>>> API.
>>>>>>
>>>>>> Are not both suppose to have latest json payload,
>>>>>>
>>>>>> //jsonObject - latest json payload in xml format
>>>>>>
>>>>>> $ -  latest json payload in json format ?
>>>>>>
>>>>>> Input json:
>>>>>>
>>>>>> {
>>>>>> "token": "d8ccf265-6651-468f-8d1f-d935c3c7d857",
>>>>>> "partyId": "2920394"
>>>>>>
>>>>>>
>>>>>> }
>>>>>>
>>>>>> Log print of //jsonObject after enrichment:
>>>>>>
>>>>>> 
>>>>>> d8ccf265-6651-468f-8d1f-d935c3c7d857
>>>>>> 57
>>>>>> PartyId
>>>>>> 
>>>>>>
>>>>>> Log print of json-eval($) at same place after enrichment : Value tag
>>>>>> missing
>>>>>>
>>>>>> {
>>>>>>

Re: [Dev] [RRT] Empty response is getting cached in APIM

2018-01-23 Thread Riyafa Abdul Hameed

Hi,

It was required to support native JSON in the cache mediator and hence we
had to use the JsonStreamBuilder. At the time of releasing it was mentioned
that APIM still uses JsonBuilder and I created an issue[1] to address this
if required.

[1] https://github.com/wso2/product-ei/issues/916

Thanks,
Riyafa

On Tue, Jan 23, 2018 at 3:00 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
wrote:

> Great,
>
> Thanks,
> sanjeewa.
>
> On Tue, Jan 23, 2018 at 2:59 PM, Bhathiya Jayasekara <bhath...@wso2.com>
> wrote:
>
>> Hi Sanjeewa,
>>
>> This is already done in 2.2.0[1].
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-5529
>>
>> Thanks,
>> Bhathiya
>>
>> On Tue, Jan 23, 2018 at 1:50 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
>> wrote:
>>
>>> Even if we have workflow usecase we should be able to use JsonStreamBuilder
>>> with workaround we tried recently.
>>> There is no harm with this change and we should consider making 
>>> JsonStreamBuilder
>>> default when we do APIM 2.2.0 release.
>>> Please add this to 2.2 product development branch.
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> On Tue, Jan 23, 2018 at 12:59 PM, Harsha Kumara <hars...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Tue, Jan 23, 2018 at 10:27 AM, Keerthika Mahendralingam <
>>>> keerth...@wso2.com> wrote:
>>>>
>>>>> HI All,
>>>>>
>>>>> When we use the latest version of cache mediator implementation with
>>>>> APIM, an empty response is getting cached instead of JSON message. But all
>>>>> headers are getting cached correctly. When I debugged the code, I found
>>>>> that response body is set to null in [1].
>>>>>
>>>>> As Riyafa suggested when I changed the JSON message builder as
>>>>> JsonStreamBuilder instead of JsonBuilder its worked as expected.
>>>>>
>>>>> Is there any specific reason for using JsonBuilder instead of
>>>>> JsonStreamBuilder? Can I go with this approach?
>>>>>
>>>> There are many instances which we have suggest to use
>>>>  JsonStreamBuilder in APIM usecases and it's the defualt builder in the EI.
>>>> We had a limitation using this when workflows enabled but there is a
>>>> workaround. Hence it's fine to use JsonStreamBuilder.
>>>>
>>>>>
>>>>> Any suggestion on this?
>>>>>
>>>>> [1]. https://github.com/wso2/carbon-mediation/blob/master/co
>>>>> mponents/mediators/cache/org.wso2.carbon.mediator.cache/src/
>>>>> main/java/org/wso2/carbon/mediator/cache/CacheMediator.java#L359
>>>>>
>>>>> Thanks,
>>>>> Keerthika.
>>>>>
>>>>> --
>>>>> <dev-requ...@wso2.org>
>>>>> Keerthika Mahendralingam
>>>>> Software Engineer
>>>>> Mobile :+94 (0) 776 121144 <+94%2077%20612%201144>
>>>>> keerth...@wso2.com
>>>>> WSO2, Inc.
>>>>> lean . enterprise . middleware
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Harsha Kumara
>>>> Software Engineer, WSO2 Inc.
>>>> Mobile: +94775505618 <077%20550%205618>
>>>> Blog:harshcreationz.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779 <071%20306%208779>
>>>
>>> <http://sanjeewamalalgoda.blogspot.com/>blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>> <http://sanjeewamalalgoda.blogspot.com/>
>>>
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com <http://wso2.com>*
>>
>> *Phone: +94715478185 <071%20547%208185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> <http://www.linkedin.com/in/bhathiyaj>*
>> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>*
>> *Blog: http://movingaheadblog.blogspot.com
>> <http://movingaheadblog.blogspot.com/>*
>>
>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779 <+94%2071%20306%208779>
>
> <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.
> blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
>
>
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] //jsonOject and $ are printing different jsons (different data content) at same location in API.

2018-01-18 Thread Riyafa Abdul Hameed

Hi Aditya,

We observed this behavior. As I mentioned in my previous reply can you
report an issue?

Regards,
Riyafa

On Fri, Jan 19, 2018 at 10:09 AM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> Hi ,
>
> My Question is while printing //jsonObject  I am able to print enriched
> value tag "Value" as well.
>
> But while printing $ "value" element is missing . While both logs are
> printed at same location in flow.
>
>
> Log print of *//jsonObjec*t after enrichment:
>
> 
> d8ccf265-6651-468f-8d1f-d935c3c7d857
> 57
> *PartyId*
> 
>
> Log print of* json-eval($) *at same place after enrichment : *Value tag
> missing*
>
> {
> "a": "d8ccf265-6651-468f-8d1f-d935c3c7d857",
> "b": "57"
>
> }
>
>
> My Question is *not *why we are printing xml for //jsonObject.
> Please guide.
> I think *$* and *//jsonObject *or *$body* are representation of same
> object just in different formats, at any point in flow.
> Then why //jsonOject and $ are printing different jsons at same location
> in API.
>
> Thanks,
> Aditya
>
> On Fri, Jan 19, 2018 at 9:35 AM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Hi Aditya,
>>
>> //jsonObject is an XPATH expression. When you apply an XPATH evaluation
>> on a JSON, ESB / EI internally convert the JSON to XML, that's why you are
>> seeing XML for //jsonObject xpath evaluation.
>> Since you are sending a JSON payload it is good to use $ (which is a JSON
>> path)
>>
>> Regards
>> Senduran
>>
>> On Fri, Jan 19, 2018 at 3:28 AM, aditya shivankar <
>> shivankar.adit...@gmail.com> wrote:
>>
>>> Respected Sir,
>>>
>>> //jsonOject and $ are printing different jsons at same location in API.
>>>
>>> Are not both suppose to have latest json payload,
>>>
>>> //jsonObject - latest json payload in xml format
>>>
>>> $ -  latest json payload in json format ?
>>>
>>> Input json:
>>>
>>> {
>>> "token": "d8ccf265-6651-468f-8d1f-d935c3c7d857",
>>> "partyId": "2920394"
>>>
>>>
>>> }
>>>
>>> Log print of //jsonObject after enrichment:
>>>
>>> 
>>> d8ccf265-6651-468f-8d1f-d935c3c7d857
>>> 57
>>> PartyId
>>> 
>>>
>>> Log print of json-eval($) at same place after enrichment : Value tag
>>> missing
>>>
>>> {
>>> "a": "d8ccf265-6651-468f-8d1f-d935c3c7d857",
>>> "b": "57"
>>>
>>> }
>>>
>>>
>>> Please find attached Rest api "sample.xml"
>>>
>>>
>>> I am facing this issue , when I have to assign current json payload, to
>>> one element of new json I created in payload factory.
>>>
>>> Inside payloadFactory I defined something like this:
>>> {
>>>  "a" : $1 ,
>>>  "b":"thampi"
>>> }
>>>
>>> In args,
>>>
>>> Type :Expression , Value:$ , evaluator: json
>>>
>>> But it is assigning the payload which was present before
>>> enrichment.which is wrong .
>>>
>>> Please guide.
>>>
>>>
>>>
>>> .
>>>
>>> [image: Inline image 2]
>>>
>>>
>>> Thanks,
>>> Aditya
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Senduran *
>> Senior Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ <http://wso2.com/>
>> Mobile: +94 77 952 6548 <+94%2077%20952%206548>
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] //jsonOject and $ are printing different jsons (different data content) at same location in API.

2018-01-18 Thread Riyafa Abdul Hameed

Hi Aditya,

We tested your scenario and observed that the log and the payload factory
are missing the "value"  part. Can you please report an issue on this[1].
Please make sure to indicate the complete steps to reproduce by including
the synapse configurations. Can  you also check if the issue occurs in the
latest milestone release[2] also before reporting the issue?

[1] https://github.com/wso2/product-ei/issues
[2] https://github.com/wso2/product-ei/releases

Thanks,
Riyafa

On Fri, Jan 19, 2018 at 9:35 AM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:

> Hi Aditya,
>
> //jsonObject is an XPATH expression. When you apply an XPATH evaluation on
> a JSON, ESB / EI internally convert the JSON to XML, that's why you are
> seeing XML for //jsonObject xpath evaluation.
> Since you are sending a JSON payload it is good to use $ (which is a JSON
> path)
>
> Regards
> Senduran
>
> On Fri, Jan 19, 2018 at 3:28 AM, aditya shivankar <
> shivankar.adit...@gmail.com> wrote:
>
>> Respected Sir,
>>
>> //jsonOject and $ are printing different jsons at same location in API.
>>
>> Are not both suppose to have latest json payload,
>>
>> //jsonObject - latest json payload in xml format
>>
>> $ -  latest json payload in json format ?
>>
>> Input json:
>>
>> {
>> "token": "d8ccf265-6651-468f-8d1f-d935c3c7d857",
>> "partyId": "2920394"
>>
>>
>> }
>>
>> Log print of //jsonObject after enrichment:
>>
>> 
>> d8ccf265-6651-468f-8d1f-d935c3c7d857
>> 57
>> PartyId
>> 
>>
>> Log print of json-eval($) at same place after enrichment : Value tag
>> missing
>>
>> {
>> "a": "d8ccf265-6651-468f-8d1f-d935c3c7d857",
>> "b": "57"
>>
>> }
>>
>>
>> Please find attached Rest api "sample.xml"
>>
>>
>> I am facing this issue , when I have to assign current json payload, to
>> one element of new json I created in payload factory.
>>
>> Inside payloadFactory I defined something like this:
>> {
>>  "a" : $1 ,
>>  "b":"thampi"
>> }
>>
>> In args,
>>
>> Type :Expression , Value:$ , evaluator: json
>>
>> But it is assigning the payload which was present before enrichment.which
>> is wrong .
>>
>> Please guide.
>>
>>
>>
>> .
>>
>> [image: Inline image 2]
>>
>>
>> Thanks,
>> Aditya
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Senduran *
> Senior Software Engineer,
> WSO2, Inc.;  http://wso2.com/ <http://wso2.com/>
> Mobile: +94 77 952 6548 <+94%2077%20952%206548>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing the cache mediator

2017-11-12 Thread Riyafa Abdul Hameed

Hi Milinda,

Here are some implementation details:





   - The message comes to the cache finder
   - A hash value is generated
   - This hash value is used to check if a cacheable response is there in
   the guava cache. If there's none create a new one
   - Check if the payload is null of this cacheableResponse object
   - if not null respond with the payload
   - If null add the CacheableResponse object to messageContext and
   continue to the next mediator
   - In this case when the response goes to collector store the payload in
   the CachableResponse object.


Thanks,

Riyafa

On Fri, Aug 18, 2017 at 3:43 PM, Milinda Perera <milin...@wso2.com> wrote:

> Hi Riyafa,
>
> What I expect is to find some implementation details without going through
> the code. For example, what kind of data structure used to store cached
> messages, whether there is a single data structure available to hold all
> cached messages or whether there is cached message holder per service,
> Whether messages are encoded to some other format, etc. If we have a little
> high-level diagram (no need to very complex one with tiny details, just
> expressing implementation details, that require attention) expressing that
> information, that will be great. Some examples [1][2].
>
> Does the documentation contain implementation information (if so that will
> be great) or documentation for WSO2 EI docs?
>
> [1] mail:AS4 support in EI
> [2] mail:[Architecture] MB4 active-passive clustering implementation
>
> Thanks,
> Milinda
>
> On Fri, Aug 18, 2017 at 1:47 PM, Riyafa Abdul Hameed <riy...@wso2.com>
> wrote:
>
>> Hi Milinda,
>>
>> What kind of diagram do you expect?
>> I would soon be writing the documentation on this and will be sharing
>> with everyone.
>>
>> Thanks.
>> Riyafa
>>
>> On Fri, Aug 18, 2017 at 1:39 PM, Milinda Perera <milin...@wso2.com>
>> wrote:
>>
>>> Hi Riyafa,
>>>
>>> Can you share some design diagram if it is possible to get some idea of
>>> current implementation?
>>>
>>> Thanks,
>>> Milinda
>>>
>>> On Mon, Jul 10, 2017 at 4:40 PM, Riyafa Abdul Hameed <riy...@wso2.com>
>>> wrote:
>>>
>>>> Dear all,
>>>>
>>>> I came up with the following configurations for the cache mediator
>>>> rewrite:
>>>>
>>>>> >>>> [scope=(per-host | per-mediator)] collector=(true | false)
>>>>> [maxMessageSize="in-bytes"] HTTPMethodToCache = (GET | POST)]>
>>>>>
>>>>>   
>>>>>
>>>>> (mediator)+
>>>>>
>>>>>   ?
>>>>>
>>>>>   
>>>>>
>>>>> 
>>>>>
>>>>
>>>> As I have mentioned in the requirements doc[1], the only reason we are
>>>> allowing responses to POST messages to be cached is because POST is the
>>>> only method used in SOAP implementations. Now having looked at the
>>>> implementation details further I understand that it is possible to identify
>>>> whether a request is soap or not without having it externally configured.
>>>> So my question is whether the configuration "HTTPMethodToCache" is actually
>>>> required because it can be internally processed whether request is SOAP or
>>>> REST and then cache accordingly.
>>>>
>>>>
>>>> [1] https://docs.google.com/document/d/1iPtArrW6C-VgzAzjjSsLmG9a
>>>> qAFEubmFgNkQhoDvqz8/edit
>>>>
>>>>
>>>> Thank you.
>>>>
>>>> Yours sincerely,
>>>>
>>>> Riyafa
>>>>
>>>>
>>>> On Thu, Jul 6, 2017 at 9:50 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>>>> wrote:
>>>>
>>>>> Thank you for the suggestions Rajkumar.
>>>>>
>>>>>
>>>>> On Thu, Jul 6, 2017 at 6:57 AM, Rajkumar Rajaratnam <
>>>>> rajkum...@wso2.com> wrote:
>>>>>
>>>>>> Also the existing cache mediator doesn't honor the cache ID as per my
>>>>>> testing sometimes back (not sure it's fixed though). It means caching 
>>>>>> works
>>>>>> globally, not at cache mediator instance level.
>>>>>>
>>>>>> If we can't correlate a finder with a collector (using cache mediator
>>>>>> ID), then we are going to hit memory issues.
>>>>>>
>>>>>> Here is the reason

Re: [Dev] Fixing the cache mediator

2017-08-18 Thread Riyafa Abdul Hameed

Hi Milinda,

What kind of diagram do you expect?
I would soon be writing the documentation on this and will be sharing with
everyone.

Thanks.
Riyafa

On Fri, Aug 18, 2017 at 1:39 PM, Milinda Perera <milin...@wso2.com> wrote:

> Hi Riyafa,
>
> Can you share some design diagram if it is possible to get some idea of
> current implementation?
>
> Thanks,
> Milinda
>
> On Mon, Jul 10, 2017 at 4:40 PM, Riyafa Abdul Hameed <riy...@wso2.com>
> wrote:
>
>> Dear all,
>>
>> I came up with the following configurations for the cache mediator
>> rewrite:
>>
>>> >> [scope=(per-host | per-mediator)] collector=(true | false)
>>> [maxMessageSize="in-bytes"] HTTPMethodToCache = (GET | POST)]>
>>>
>>>   
>>>
>>> (mediator)+
>>>
>>>   ?
>>>
>>>   
>>>
>>> 
>>>
>>
>> As I have mentioned in the requirements doc[1], the only reason we are
>> allowing responses to POST messages to be cached is because POST is the
>> only method used in SOAP implementations. Now having looked at the
>> implementation details further I understand that it is possible to identify
>> whether a request is soap or not without having it externally configured.
>> So my question is whether the configuration "HTTPMethodToCache" is actually
>> required because it can be internally processed whether request is SOAP or
>> REST and then cache accordingly.
>>
>>
>> [1] https://docs.google.com/document/d/1iPtArrW6C-VgzAzjjSsLmG9a
>> qAFEubmFgNkQhoDvqz8/edit
>>
>>
>> Thank you.
>>
>> Yours sincerely,
>>
>> Riyafa
>>
>>
>> On Thu, Jul 6, 2017 at 9:50 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Thank you for the suggestions Rajkumar.
>>>
>>>
>>> On Thu, Jul 6, 2017 at 6:57 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
>>> wrote:
>>>
>>>> Also the existing cache mediator doesn't honor the cache ID as per my
>>>> testing sometimes back (not sure it's fixed though). It means caching works
>>>> globally, not at cache mediator instance level.
>>>>
>>>> If we can't correlate a finder with a collector (using cache mediator
>>>> ID), then we are going to hit memory issues.
>>>>
>>>> Here is the reason.
>>>>
>>>> Let's say we have two APIs - location and exchange.
>>>>
>>>>1. /location API response size is 10 MB and we have 100 different
>>>>responses
>>>>2. /exchange API response size is 1MB and we have 1000 different
>>>>responses
>>>>
>>>> If we want to enable response caching for these two APIs, if we can
>>>> correlate a finder with a collector (i.e if we support caching at cache
>>>> mediator instance level), then I can allocate 100*10 + 1000*1 = 2000 MB
>>>> memory to the JVM in addition to our recommended memory settings, so that
>>>> it will never go OOM.
>>>>
>>>> If we can't correlate a finder with a collector (i.e, if we support
>>>> global caching), then I have to allocate 1100 * 10 = 11000 MB memory. See I
>>>> have to use additional 9000 MB if we don't honor cache ID. It's not
>>>> practical and efficient because memory is expensive - so it doesn't scale.
>>>>
>>>> Can we fix this issue and honor cache ID please in the next EI release?
>>>>
>>>
>>> Yes we need to honor this as you suggest and I shall include it in the
>>> requirements document.
>>>
>>>>
>>>> On Wed, Jul 5, 2017 at 9:18 PM, Rajkumar Rajaratnam <rajkum...@wso2.com
>>>> > wrote:
>>>>
>>>>> Is this going to be a rewrite or improvement to existing cache
>>>>> mediator? If this is a rewrite, will it be included in next EI release?
>>>>>
>>>> Yes it's going to be a rewrite. We hope to include it in the EI 6.2.x
>>> release.
>>>
>>>>
>>>>> Also can we also implement cache eviction as part of this effort?
>>>>>
>>>>> Ideally, we should be able to configure how many maximum responses we
>>>>> can cache (not sure whether it's there already, it was not working
>>>>> sometimes back) and what's the maximum message size (it's already there) 
>>>>> we
>>>>> can cache to avoid OOM. Then we need to have cache evi

Re: [Dev] Problem with response EI 6.1.1

2017-07-24 Thread Riyafa Abdul Hameed

Hi,

The recommended way is to call a sequences[1] if you want to do some logic
in the mediation but invoking proxy in another proxy is not wrong. Please
share your proxy service so that it can be reproduced.

[1] https://docs.wso2.com/display/EI611/Mediation+Sequences

Regards,
Riyafa

On Mon, Jul 24, 2017 at 2:47 PM, Melodias <osbtestmail...@gmail.com> wrote:

> Hi dev,
> I have flow: proxyA invoke proxyB and proxyB invoke backend. In this
> scenario I have timeout on proxyA. When I invoke proxyB I received a
> response.
>
> Is it a problem with invoke proxy by proxy in EI 6.1.1?
>
>
>
> --
> View this message in context: http://wso2-oxygen-tank.10903.
> n7.nabble.com/Problem-with-response-EI-6-1-1-tp150540.html
> Sent from the WSO2 Development mailing list archive at Nabble.com.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Synapse] Best way to get an String representation of an OMElement

2017-07-24 Thread Riyafa Abdul Hameed

Hi all,

I have another question on synapse.

What is the best way to get an String representation of an OMElement? I
used the OMElement.toString() method but the documentation says about this
method:

"This is a convenience method only. This will basically serialize the given
OMElement to a String but will build the OMTree in the memory"

Is there a better solution for converting an OMElement to a String? I was
thinking of first serializing into a ByteStream and then converting to
String. I am not sure which one would be more efficient.
Any suggestions?

Thank you.
Riyafa

-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Synapse]Efficiently check the size of SoapEnvelope of org.apache.synapse.MessageContext

2017-07-24 Thread Riyafa Abdul Hameed

Hi all,

I have a question regarding synapse for which I could not get help from
stackoverflow[1]

I would like to check the message size of a SoapEnvelope of
org.apache.synapse.MessageContext to see if it exceeds a certain maximum
size. Currently it is done the following manner:

   if (maxMessageSize > 0) {
FixedByteArrayOutputStream fbaos = new
FixedByteArrayOutputStream(maxMessageSize);
try {

MessageHelper.cloneSOAPEnvelope(synCtx.getEnvelope()).serialize(fbaos);
} catch (XMLStreamException e) {
handleException("Error in checking the message size",
e, synCtx);
} catch (SynapseException syne) {
synLog.traceOrDebug("Message size exceeds the upper
bound for caching, request will not be cached");
return;
} finally {
try {
fbaos.close();
} catch (IOException e) {
handleException("Error occurred while closing the
FixedByteArrayOutputStream ", e, synCtx);
}
}
}

In this case I have to serialize the envelope before checking the size
which I don't think is the most efficient way to do this. In my case I have
to check message size before all other implementations. Is there a more
efficient way to do this?

Please kindly provide the solution for the question either on stackoverflow
or here.


[1]
https://stackoverflow.com/questions/45229700/efficiently-check-the-size-of-soapenvelope-of-org-apache-synapse-messagecontext
Thank you.
Riyafa

-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Taking a list of values as input to a mediator configuration

2017-07-14 Thread Riyafa Abdul Hameed

Hi Sudharma,

Thank you for the quick reply. Yes the values need to be trimmed to make
sure there are no whitespaces at the beginning or ends.



On Fri, Jul 14, 2017 at 12:08 PM, Riyafa Abdul Hameed <riy...@wso2.com>
wrote:

> Hi Asanka,
>
> The question is not about the cache mediator. It is about the standard way
> of including a list of values in a configuration parameter in a custom
> mediator.
> As to answer your question, by the requirements[1], it should be possible
> for us to allow the user to specify a list of headers which he does not
> want to hashed like the "timestamp" header because hashing it would mean
> all request messages would give a different hash.
>
> [1] https://docs.google.com/document/d/1iPtArrW6C-
> VgzAzjjSsLmG9aqAFEubmFgNkQhoDvqz8/edit
>
> On Fri, Jul 14, 2017 at 12:02 PM, Asanka Abeyweera <asank...@wso2.com>
> wrote:
>
>> Hi Riyafa,
>>
>> Can't we remove the unwanted headers before pushing to cache so that we
>> don't have to use "headersToExcludeInHash" in cache mediator?
>>
>> On Fri, Jul 14, 2017 at 11:53 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I am creating a custom mediator and one of the configuration parameters
>>> would have to take as input a list of values. What is the best or standard
>>> way to do this? I plan to take in string with comma separated values and
>>> split it by the commas and then trim it to get the values in the list.
>>> Would that work?
>>>
>>> To elaborate more consider the syntax for cache mediator:
>>>
>>> >> [scope=(per-host | per-mediator)] collector=(true | false)
>>> [maxMessageSize="in-bytes"] hTTPMethodToCache = (GET | POST)]
>>>
>>> headersToExcludeInHash=”comma separated list of headers”>
>>>
>>>   
>>>
>>>     (mediator)+
>>>
>>>   ?
>>>
>>>   
>>>
>>> 
>>>
>>>
>>> if the value for the "headersToExcludeInHash" needs to be a list, is it
>>> correct to take as input a list of comma separated values in a single
>>> string?
>>>
>>>
>>> Thank you.
>>>
>>> Yours faithfully,
>>>
>>> Riyafa
>>>
>>> --
>>> Riyafa Abdul Hameed
>>> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>>>
>>> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>>> <http://twitter.com/Riyafa1>
>>>
>>> _______
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Asanka Abeyweera
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Phone: +94 712228648 <+94%2071%20222%208648>
>> Blog: a5anka.github.io
>>
>> <https://wso2.com/signature>
>>
>
>
>
> --
> Riyafa Abdul Hameed
> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>
> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
> <http://twitter.com/Riyafa1>
>



-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Taking a list of values as input to a mediator configuration

2017-07-14 Thread Riyafa Abdul Hameed

Hi Asanka,

The question is not about the cache mediator. It is about the standard way
of including a list of values in a configuration parameter in a custom
mediator.
As to answer your question, by the requirements[1], it should be possible
for us to allow the user to specify a list of headers which he does not
want to hashed like the "timestamp" header because hashing it would mean
all request messages would give a different hash.

[1]
https://docs.google.com/document/d/1iPtArrW6C-VgzAzjjSsLmG9aqAFEubmFgNkQhoDvqz8/edit

On Fri, Jul 14, 2017 at 12:02 PM, Asanka Abeyweera <asank...@wso2.com>
wrote:

> Hi Riyafa,
>
> Can't we remove the unwanted headers before pushing to cache so that we
> don't have to use "headersToExcludeInHash" in cache mediator?
>
> On Fri, Jul 14, 2017 at 11:53 AM, Riyafa Abdul Hameed <riy...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I am creating a custom mediator and one of the configuration parameters
>> would have to take as input a list of values. What is the best or standard
>> way to do this? I plan to take in string with comma separated values and
>> split it by the commas and then trim it to get the values in the list.
>> Would that work?
>>
>> To elaborate more consider the syntax for cache mediator:
>>
>> > [scope=(per-host | per-mediator)] collector=(true | false)
>> [maxMessageSize="in-bytes"] hTTPMethodToCache = (GET | POST)]
>>
>> headersToExcludeInHash=”comma separated list of headers”>
>>
>>   
>>
>> (mediator)+
>>
>>   ?
>>
>>   
>>
>> 
>>
>>
>> if the value for the "headersToExcludeInHash" needs to be a list, is it
>> correct to take as input a list of comma separated values in a single
>> string?
>>
>>
>> Thank you.
>>
>> Yours faithfully,
>>
>> Riyafa
>>
>> --
>> Riyafa Abdul Hameed
>> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>>
>> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>> <http://twitter.com/Riyafa1>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Asanka Abeyweera
> Senior Software Engineer
> WSO2 Inc.
>
> Phone: +94 712228648 <+94%2071%20222%208648>
> Blog: a5anka.github.io
>
> <https://wso2.com/signature>
>



-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Taking a list of values as input to a mediator configuration

2017-07-14 Thread Riyafa Abdul Hameed

Hi,

I am creating a custom mediator and one of the configuration parameters
would have to take as input a list of values. What is the best or standard
way to do this? I plan to take in string with comma separated values and
split it by the commas and then trim it to get the values in the list.
Would that work?

To elaborate more consider the syntax for cache mediator:



  

(mediator)+

  ?

  




if the value for the "headersToExcludeInHash" needs to be a list, is it
correct to take as input a list of comma separated values in a single
string?


Thank you.

Yours faithfully,

Riyafa

-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing the cache mediator

2017-07-10 Thread Riyafa Abdul Hameed

Dear all,

I came up with the following configurations for the cache mediator rewrite:

>  [scope=(per-host | per-mediator)] collector=(true | false)
> [maxMessageSize="in-bytes"] HTTPMethodToCache = (GET | POST)]>
>
>   
>
> (mediator)+
>
>   ?
>
>   
>
> 
>

As I have mentioned in the requirements doc[1], the only reason we are
allowing responses to POST messages to be cached is because POST is the
only method used in SOAP implementations. Now having looked at the
implementation details further I understand that it is possible to identify
whether a request is soap or not without having it externally configured.
So my question is whether the configuration "HTTPMethodToCache" is actually
required because it can be internally processed whether request is SOAP or
REST and then cache accordingly.


[1]
https://docs.google.com/document/d/1iPtArrW6C-VgzAzjjSsLmG9aqAFEubmFgNkQhoDvqz8/edit


Thank you.

Yours sincerely,

Riyafa


On Thu, Jul 6, 2017 at 9:50 AM, Riyafa Abdul Hameed <riy...@wso2.com> wrote:

> Thank you for the suggestions Rajkumar.
>
>
> On Thu, Jul 6, 2017 at 6:57 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>> Also the existing cache mediator doesn't honor the cache ID as per my
>> testing sometimes back (not sure it's fixed though). It means caching works
>> globally, not at cache mediator instance level.
>>
>> If we can't correlate a finder with a collector (using cache mediator
>> ID), then we are going to hit memory issues.
>>
>> Here is the reason.
>>
>> Let's say we have two APIs - location and exchange.
>>
>>1. /location API response size is 10 MB and we have 100 different
>>responses
>>2. /exchange API response size is 1MB and we have 1000 different
>>responses
>>
>> If we want to enable response caching for these two APIs, if we can
>> correlate a finder with a collector (i.e if we support caching at cache
>> mediator instance level), then I can allocate 100*10 + 1000*1 = 2000 MB
>> memory to the JVM in addition to our recommended memory settings, so that
>> it will never go OOM.
>>
>> If we can't correlate a finder with a collector (i.e, if we support
>> global caching), then I have to allocate 1100 * 10 = 11000 MB memory. See I
>> have to use additional 9000 MB if we don't honor cache ID. It's not
>> practical and efficient because memory is expensive - so it doesn't scale.
>>
>> Can we fix this issue and honor cache ID please in the next EI release?
>>
>
> Yes we need to honor this as you suggest and I shall include it in the
> requirements document.
>
>>
>> On Wed, Jul 5, 2017 at 9:18 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
>> wrote:
>>
>>> Is this going to be a rewrite or improvement to existing cache mediator?
>>> If this is a rewrite, will it be included in next EI release?
>>>
>> Yes it's going to be a rewrite. We hope to include it in the EI 6.2.x
> release.
>
>>
>>> Also can we also implement cache eviction as part of this effort?
>>>
>>> Ideally, we should be able to configure how many maximum responses we
>>> can cache (not sure whether it's there already, it was not working
>>> sometimes back) and what's the maximum message size (it's already there) we
>>> can cache to avoid OOM. Then we need to have cache eviction in place to
>>> evict some cached items when cache is full, in-order to give space for most
>>> recent responses.
>>>
>>> I guess configuring the maximum responses is currently available and we
> shall consider your suggestions in the rewrite.
>
>> Thanks.
>>>
>>> On Wed, Jul 5, 2017 at 6:02 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>> Please find the requirements doc below:
>>>> https://docs.google.com/document/d/1iPtArrW6C-VgzAzjjSsLmG9a
>>>> qAFEubmFgNkQhoDvqz8/edit?usp=sharing
>>>> Any suggestions would be highly appreciated.
>>>> Thank you.
>>>> Riyafa
>>>>
>>>> On Tue, Jul 4, 2017 at 5:37 PM, Riyafa Abdul Hameed <riy...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Thank you for the suggestions. Yes the mediator should also work with
>>>>> the call mediator.
>>>>>
>>>>> Further on a discussion with the APIM team I have identified the
>>>>> following issues which points to requiring a rewrite of the cache 
>>>>> mediator:
>>>

Re: [Dev] Fixing the cache mediator

2017-07-05 Thread Riyafa Abdul Hameed

Thank you for the suggestions Rajkumar.


On Thu, Jul 6, 2017 at 6:57 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
wrote:

> Also the existing cache mediator doesn't honor the cache ID as per my
> testing sometimes back (not sure it's fixed though). It means caching works
> globally, not at cache mediator instance level.
>
> If we can't correlate a finder with a collector (using cache mediator ID),
> then we are going to hit memory issues.
>
> Here is the reason.
>
> Let's say we have two APIs - location and exchange.
>
>1. /location API response size is 10 MB and we have 100 different
>responses
>2. /exchange API response size is 1MB and we have 1000 different
>responses
>
> If we want to enable response caching for these two APIs, if we can
> correlate a finder with a collector (i.e if we support caching at cache
> mediator instance level), then I can allocate 100*10 + 1000*1 = 2000 MB
> memory to the JVM in addition to our recommended memory settings, so that
> it will never go OOM.
>
> If we can't correlate a finder with a collector (i.e, if we support global
> caching), then I have to allocate 1100 * 10 = 11000 MB memory. See I have
> to use additional 9000 MB if we don't honor cache ID. It's not practical
> and efficient because memory is expensive - so it doesn't scale.
>
> Can we fix this issue and honor cache ID please in the next EI release?
>

Yes we need to honor this as you suggest and I shall include it in the
requirements document.

>
> On Wed, Jul 5, 2017 at 9:18 PM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>> Is this going to be a rewrite or improvement to existing cache mediator?
>> If this is a rewrite, will it be included in next EI release?
>>
> Yes it's going to be a rewrite. We hope to include it in the EI 6.2.x
release.

>
>> Also can we also implement cache eviction as part of this effort?
>>
>> Ideally, we should be able to configure how many maximum responses we can
>> cache (not sure whether it's there already, it was not working sometimes
>> back) and what's the maximum message size (it's already there) we can cache
>> to avoid OOM. Then we need to have cache eviction in place to evict some
>> cached items when cache is full, in-order to give space for most recent
>> responses.
>>
>> I guess configuring the maximum responses is currently available and we
shall consider your suggestions in the rewrite.

> Thanks.
>>
>> On Wed, Jul 5, 2017 at 6:02 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Hi,
>>> Please find the requirements doc below:
>>> https://docs.google.com/document/d/1iPtArrW6C-VgzAzjjSsLmG9a
>>> qAFEubmFgNkQhoDvqz8/edit?usp=sharing
>>> Any suggestions would be highly appreciated.
>>> Thank you.
>>> Riyafa
>>>
>>> On Tue, Jul 4, 2017 at 5:37 PM, Riyafa Abdul Hameed <riy...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Thank you for the suggestions. Yes the mediator should also work with
>>>> the call mediator.
>>>>
>>>> Further on a discussion with the APIM team I have identified the
>>>> following issues which points to requiring a rewrite of the cache mediator:
>>>>
>>>>1.
>>>>
>>>>Current cache mediator[1] caches responses for all the HTTP Request
>>>>Methods which include GET, POST, PUT and DELETE. Ideally a cache 
>>>> mediator
>>>>should cache only the response for GET method and caching for POST 
>>>> method
>>>>should be configurable (because POST is the only method used in SOAP
>>>>implementations). The caching for PUT and DELETE methods should be
>>>>completely omitted. The reason for caching responses only for GET is
>>>>because in the REST world other methods (POST, PUT and DELETE) are used 
>>>> for
>>>>creating, modifying or deleting existing records and hence the response
>>>>would only mention the success or failure of the request. Caching these
>>>>responses is meaningless and error prone.
>>>>2.
>>>>
>>>>Current cache mediator caches all the responses whether they are
>>>>success or failure responses. Ideally the mediator should cache only
>>>>success (200 OK) responses and not the failures
>>>>3.
>>>>
>>>>Current mediator hashes the payload (both DOMHASHGenerator and
>>>>REQUESTHASHGenerator) which is a huge overhe

Re: [Dev] Fixing the cache mediator

2017-07-05 Thread Riyafa Abdul Hameed

Hi,
Please find the requirements doc below:
https://docs.google.com/document/d/1iPtArrW6C-VgzAzjjSsLmG9aqAFEubmFgNkQhoDvqz8/edit?usp=sharing
Any suggestions would be highly appreciated.
Thank you.
Riyafa

On Tue, Jul 4, 2017 at 5:37 PM, Riyafa Abdul Hameed <riy...@wso2.com> wrote:

> Hi all,
>
> Thank you for the suggestions. Yes the mediator should also work with the
> call mediator.
>
> Further on a discussion with the APIM team I have identified the following
> issues which points to requiring a rewrite of the cache mediator:
>
>1.
>
>Current cache mediator[1] caches responses for all the HTTP Request
>Methods which include GET, POST, PUT and DELETE. Ideally a cache mediator
>should cache only the response for GET method and caching for POST method
>should be configurable (because POST is the only method used in SOAP
>implementations). The caching for PUT and DELETE methods should be
>completely omitted. The reason for caching responses only for GET is
>because in the REST world other methods (POST, PUT and DELETE) are used for
>creating, modifying or deleting existing records and hence the response
>would only mention the success or failure of the request. Caching these
>responses is meaningless and error prone.
>2.
>
>Current cache mediator caches all the responses whether they are
>success or failure responses. Ideally the mediator should cache only
>success (200 OK) responses and not the failures
>3.
>
>Current mediator hashes the payload (both DOMHASHGenerator and
>REQUESTHASHGenerator) which is a huge overhead for messages with larger
>bodies. The mediator should hash only the recipient (To) address of the
>request and the HTTP headers which can be easily handled when only
>responses for GET methods are hashed. Payload should be hashed only if PUT
>method is configured.
>4.
>
>Current mediator does not allow configurations for omitting certain
>headers when hashing. For example there’s no point in hashing the timestamp
>header--it will almost always be different from message to message.
>5.
>
>The current mediator does not honor the http headers[2]. For example
>the max-age header specifies the maximum time in seconds that the fetched
>response is allowed to be reused from the time of the request. Although
>cache timeout is allowed to be configured this header is not honored when
>it is specified in a message.
>6.
>
>Although it is possible to set the maximum number of elements to be
>cached in bytes it might result in this set value exceeding the available
>memory at runtime.
>7.
>
>The current mediator does not invoke the handleResponseInFlow or
>handleResponseOutFlow methods in handlers[3]
>
>
>
> [1] https://docs.wso2.com/display/EI611/Cache+Mediator
>
> [2] https://developers.google.com/web/fundamentals/performance/
> optimizing-content-efficiency/http-caching
>
> [3] https://docs.wso2.com/display/EI611/Writing+a+Synapse+Handler
>
> On Tue, Jul 4, 2017 at 4:28 PM, Isuru Udana <isu...@wso2.com> wrote:
>
>> Hi,
>>
>> On Tue, Jul 4, 2017 at 3:10 PM, Vijitha Ekanayake <vijit...@wso2.com>
>> wrote:
>>
>>> Hi Riyafa,
>>>
>>> Apart from the issues that you have mentioned, we may need to consider
>>> following points while refactoring the cache mediator implementation.
>>>
>>> 1). Verify the cache mediator functionality with different configuration
>>> parameters and fix if there is anything broken.
>>> 2). Implement a mechanism to support caching when using the call
>>> mediator.
>>> 3). Feasibility to introduce native JSON caching support to cache
>>> mediator.
>>> 4). Feasibility to introduce service level caching which isn't support
>>> at the moment.
>>>
>> IMO, service level caching is not a requirement as long as we can achieve
>> all the requirements through the Cache Mediator.
>>
>> Thanks.
>>
>>>
>>>
>>> Thanks.
>>>
>>>
>>> On Tue, Jul 4, 2017 at 12:06 PM, Riyafa Abdul Hameed <riy...@wso2.com>
>>> wrote:
>>>
>>>> Dear all,
>>>>
>>>> By going through the issues faced by the customers in the past I
>>>> discovered the following issues:
>>>>
>>>>1. Continue the execution on cache hit. Reported as an issue in
>>>>github[1]
>>>>2. Issue in processing JSON array (payload) with a single element
>>>>when response caching is enabled where expec

Re: [Dev] Fixing the cache mediator

2017-07-04 Thread Riyafa Abdul Hameed

Hi all,

Thank you for the suggestions. Yes the mediator should also work with the
call mediator.

Further on a discussion with the APIM team I have identified the following
issues which points to requiring a rewrite of the cache mediator:

   1.

   Current cache mediator[1] caches responses for all the HTTP Request
   Methods which include GET, POST, PUT and DELETE. Ideally a cache mediator
   should cache only the response for GET method and caching for POST method
   should be configurable (because POST is the only method used in SOAP
   implementations). The caching for PUT and DELETE methods should be
   completely omitted. The reason for caching responses only for GET is
   because in the REST world other methods (POST, PUT and DELETE) are used for
   creating, modifying or deleting existing records and hence the response
   would only mention the success or failure of the request. Caching these
   responses is meaningless and error prone.
   2.

   Current cache mediator caches all the responses whether they are success
   or failure responses. Ideally the mediator should cache only success (200
   OK) responses and not the failures
   3.

   Current mediator hashes the payload (both DOMHASHGenerator and
   REQUESTHASHGenerator) which is a huge overhead for messages with larger
   bodies. The mediator should hash only the recipient (To) address of the
   request and the HTTP headers which can be easily handled when only
   responses for GET methods are hashed. Payload should be hashed only if PUT
   method is configured.
   4.

   Current mediator does not allow configurations for omitting certain
   headers when hashing. For example there’s no point in hashing the timestamp
   header--it will almost always be different from message to message.
   5.

   The current mediator does not honor the http headers[2]. For example the
   max-age header specifies the maximum time in seconds that the fetched
   response is allowed to be reused from the time of the request. Although
   cache timeout is allowed to be configured this header is not honored when
   it is specified in a message.
   6.

   Although it is possible to set the maximum number of elements to be
   cached in bytes it might result in this set value exceeding the available
   memory at runtime.
   7.

   The current mediator does not invoke the handleResponseInFlow or
   handleResponseOutFlow methods in handlers[3]

[1] https://docs.wso2.com/display/EI611/Cache+Mediator

[2]
https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching

[3] https://docs.wso2.com/display/EI611/Writing+a+Synapse+Handler

On Tue, Jul 4, 2017 at 4:28 PM, Isuru Udana <isu...@wso2.com> wrote:

> Hi,
>
> On Tue, Jul 4, 2017 at 3:10 PM, Vijitha Ekanayake <vijit...@wso2.com>
> wrote:
>
>> Hi Riyafa,
>>
>> Apart from the issues that you have mentioned, we may need to consider
>> following points while refactoring the cache mediator implementation.
>>
>> 1). Verify the cache mediator functionality with different configuration
>> parameters and fix if there is anything broken.
>> 2). Implement a mechanism to support caching when using the call
>> mediator.
>> 3). Feasibility to introduce native JSON caching support to cache
>> mediator.
>> 4). Feasibility to introduce service level caching which isn't support at
>> the moment.
>>
> IMO, service level caching is not a requirement as long as we can achieve
> all the requirements through the Cache Mediator.
>
> Thanks.
>
>>
>>
>> Thanks.
>>
>>
>> On Tue, Jul 4, 2017 at 12:06 PM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Dear all,
>>>
>>> By going through the issues faced by the customers in the past I
>>> discovered the following issues:
>>>
>>>1. Continue the execution on cache hit. Reported as an issue in
>>>github[1]
>>>2. Issue in processing JSON array (payload) with a single element
>>>when response caching is enabled where expected response is:
>>>
>>> [
>>>{
>>>   "msg":"Hello",
>>>   "services":[
>>>  "elec",
>>>  "patrol"
>>>   ],
>>>   "test":"World."
>>>},
>>>{
>>>   "msg":"Hi",
>>>   "services":[
>>>  "water"
>>>   ],
>>>   "test":"Sri Lanka."
>>>}
>>> ]
>>>
>>> but received response is:
>>>
>>> [
>>> { "msg": "Hello", "services": [ "elec", &q

[Dev] Fixing the cache mediator

2017-07-04 Thread Riyafa Abdul Hameed

Dear all,

By going through the issues faced by the customers in the past I discovered
the following issues:

   1. Continue the execution on cache hit. Reported as an issue in github[1]
   2. Issue in processing JSON array (payload) with a single element when
   response caching is enabled where expected response is:

[
   {
  "msg":"Hello",
  "services":[
 "elec",
 "patrol"
  ],
  "test":"World."
   },
   {
  "msg":"Hi",
  "services":[
 "water"
  ],
  "test":"Sri Lanka."
   }
]

but received response is:

[
{ "msg": "Hello", "services": [ "elec", "patrol" ], "test": "World." }

,
{ "msg": "Hi", "services": "water", "test": "Sri Lanka." }

]

This issue has been fixed in the carbon mediation[2].

   3.  When a xml body with processing instructions is stored in
cache and sent back as json it fails with an exception. Issue was reported
in 2015 and already has a fix in current EI.

Since the last two issues have been already fixed, I would like to know
what other issues if any needs to be addressed and if a complete rewrite of
the cache mediator would be required.

[1] https://github.com/wso2/product-ei/issues/695

[2]
https://github.com/riyafa/carbon-mediation/commit/7aaf597988a333e1cad36dc0b5057e24fb779a5c


Thank you.

Riyafa

-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

2017-06-18 Thread Riyafa Abdul Hameed

>
>>>>>>>>>>>>>> On Mon, Jun 5, 2017 at 9:26 AM, Kevin Ratnasekera <
>>>>>>>>>>>>>> ke...@wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Hasitha,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Great progress so far, since the coding period have already
>>>>>>>>>>>>>>> started, we need to plan things ahead and come up with a proper 
>>>>>>>>>>>>>>> milestone
>>>>>>>>>>>>>>> plan before we proceed anything further. Will it be possible 
>>>>>>>>>>>>>>> you to join a
>>>>>>>>>>>>>>> meeting within this week?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> @malaka Can you please suggest possible time for you to have
>>>>>>>>>>>>>>> a meeting?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>> Kevin
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, May 29, 2017 at 10:34 AM, Hasitha Jayasundara <
>>>>>>>>>>>>>>> hasithajayasunda...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have updated the sample MQ-Client [1] to establish SSL
>>>>>>>>>>>>>>>> connections with IBM WebSphere MQ. Still carry on the research 
>>>>>>>>>>>>>>>> with the
>>>>>>>>>>>>>>>> provided links about the IBM specific options that can be 
>>>>>>>>>>>>>>>> added other than
>>>>>>>>>>>>>>>> SSL and will update the thread with the findings as soon as
>>>>>>>>>>>>>>>> possible.Working on
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "Can we check if it is possible to have an alternative way
>>>>>>>>>>>>>>>> to set SSL details other than system properties with IBM MQ 
>>>>>>>>>>>>>>>> client
>>>>>>>>>>>>>>>> libraries.The reason for that is we are limiting our self
>>>>>>>>>>>>>>>> to one set of properties per JVM. eg: System.setProperty("
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> which discussed in the previous thread.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [1] https://github.com/hasithajayasundara/IBM-MQ-client
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, May 23, 2017 at 7:12 AM, Malaka Silva <
>>>>>>>>>>>>>>>> mal...@wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Hasitha,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Sounds good. It'll be good if you can come up with the
>>>>>>>>>>>>>>>>> list of IBM specific options.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, May 23, 2017 at 7:08 AM, Hasitha Jayasundara <
>>>>>>>>>>>>>>>>> hasithajayasunda...@gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I tried to implem

Re: [Dev] Error when running the newest build of MB-4

2017-05-31 Thread Riyafa Abdul Hameed

Hi All,

For the moment we will create the folder by adding it to the bin.xml of
MB-4. Also I have created an issue regarding this:
https://github.com/wso2/carbon-deployment/issues/261

Thank you.
Riyafa

On Wed, May 31, 2017 at 10:58 AM, Niranjan Karunanandham <niran...@wso2.com>
wrote:

> Hi Riyafa,
>
> This issue is happening because the deployment folder is not present in
> the product. As a workaround you can create it using the product repo
> bin.xml. Can you create a git issue for this in the carbon-deployment repo?
> The fix is to create the folder when the feature is installed.
>
> Regards,
> Nira
>
> On Wed, May 31, 2017 at 10:54 AM, Gihan Anuruddha <gi...@wso2.com> wrote:
>
>> Hi,
>>
>> This is a know issue. Can you please create an issue in here[1].
>>
>> [1] - https://github.com/wso2/carbon-deployment
>>
>> Regards,
>> Gihan
>>
>> On Wed, May 31, 2017 at 9:32 AM, Pamod Sylvester <pa...@wso2.com> wrote:
>>
>>> (+) KasunG
>>>
>>> On Wed, May 31, 2017 at 9:27 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I built MB-4 from the 4.x.x branch of product-mb[1] and ran it by
>>>> extracting 'wso2mb-4.0.0-SNAPSHOT.zip' from ''/product-mb/product/target'.
>>>> I get the following error during execution of carbon.sh from the bin 
>>>> folder:
>>>>
>>>>> ERROR 
>>>>> {org.wso2.carbon.deployment.engine.internal.DeploymentEngineListenerComponent}
>>>>> - Could not initialize carbon deployment engine
>>>>> org.wso2.carbon.deployment.engine.exception.DeploymentEngineException:
>>>>> Cannot find repository : /home/riyafa/Documents/Workspa
>>>>> ce/product-mb/product/target/wso2mb-4.0.0-SNAPSHOT/deployment
>>>>> at org.wso2.carbon.deployment.engine.internal.DeploymentEngine.
>>>>> start(DeploymentEngine.java:103)
>>>>> at org.wso2.carbon.deployment.engine.internal.DeploymentEngineL
>>>>> istenerComponent.onAllRequiredCapabilitiesAvailable(Deployme
>>>>> ntEngineListenerComponent.java:212)
>>>>> at org.wso2.carbon.kernel.internal.startupresolver.StartupCompo
>>>>> nentManager.lambda$notifySatisfiableComponents$51(StartupCom
>>>>> ponentManager.java:238)
>>>>> at java.util.ArrayList.forEach(ArrayList.java:1249)
>>>>> at org.wso2.carbon.kernel.internal.startupresolver.StartupCompo
>>>>> nentManager.notifySatisfiableComponents(StartupComponentMana
>>>>> ger.java:224)
>>>>> at org.wso2.carbon.kernel.internal.startupresolver.StartupOrder
>>>>> Resolver$1.run(StartupOrderResolver.java:204)
>>>>> at java.util.TimerThread.mainLoop(Timer.java:555)
>>>>> at java.util.TimerThread.run(Timer.java:505)
>>>>>
>>>>
>>>> The current product-mb is written over C5 and I am not sure if it's an
>>>> issue with C5. When I create a deployment folder in the
>>>> wso2mb-4.0.0-SNAPSHOT folder and rerun product-mb the error goes away. Any
>>>> highlight on the above issue would be of help.
>>>>
>>>> Thank you.
>>>> Riyafa
>>>>
>>>>
>>>> [1] https://github.com/wso2/product-mb/tree/4.x.x/product
>>>>
>>>> --
>>>> Riyafa Abdul Hameed
>>>> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>>>>
>>>> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
>>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>>>> <http://twitter.com/Riyafa1>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Pamod Sylvester *
>>>
>>> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
>>> cell: +94 77 7779495 <077%20777%209495>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> W.G. Gihan Anuruddha
>> Associate Technical Lead | WSO2, Inc.
>> M: +94772272595
>>
>
>
>
> --
>
>
> *Niranjan Karunanandham*
> Associate Technical Lead - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error when running the newest build of MB-4

2017-05-30 Thread Riyafa Abdul Hameed

Hi,

I built MB-4 from the 4.x.x branch of product-mb[1] and ran it by
extracting 'wso2mb-4.0.0-SNAPSHOT.zip' from ''/product-mb/product/target'.
I get the following error during execution of carbon.sh from the bin folder:

> ERROR
> {org.wso2.carbon.deployment.engine.internal.DeploymentEngineListenerComponent}
> - Could not initialize carbon deployment engine
> org.wso2.carbon.deployment.engine.exception.DeploymentEngineException:
> Cannot find repository :
> /home/riyafa/Documents/Workspace/product-mb/product/target/wso2mb-4.0.0-SNAPSHOT/deployment
> at
> org.wso2.carbon.deployment.engine.internal.DeploymentEngine.start(DeploymentEngine.java:103)
> at
> org.wso2.carbon.deployment.engine.internal.DeploymentEngineListenerComponent.onAllRequiredCapabilitiesAvailable(DeploymentEngineListenerComponent.java:212)
> at
> org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager.lambda$notifySatisfiableComponents$51(StartupComponentManager.java:238)
> at java.util.ArrayList.forEach(ArrayList.java:1249)
> at
> org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager.notifySatisfiableComponents(StartupComponentManager.java:224)
> at
> org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver$1.run(StartupOrderResolver.java:204)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
>

The current product-mb is written over C5 and I am not sure if it's an
issue with C5. When I create a deployment folder in the
wso2mb-4.0.0-SNAPSHOT folder and rerun product-mb the error goes away. Any
highlight on the above issue would be of help.

Thank you.
Riyafa


[1] https://github.com/wso2/product-mb/tree/4.x.x/product

-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

2017-05-18 Thread Riyafa Abdul Hameed

Hi,

See if this blog post could be of help:
https://riyafa.wordpress.com/2016/02/21/sample-java-client-for-websphere-mq-consumer-and-producer/

Regards,
Riyafa

On Thu, May 18, 2017 at 9:13 PM, Malaka Silva <mal...@wso2.com> wrote:

> Hi Hasitha,
>
> You can find sample code done for IBM MQ 7.5. Here ESB acts as the
> consumer.
>
> What is required to do is ESB act as the consumer and producer for IBM MQ
> 8.0.
>
> Let me know if something is not clear?
>
> [1] https://github.com/wso2-attic/esb-connectors/pull/483/files
>
> On Tue, May 16, 2017 at 9:39 PM, Hasitha Jayasundara <
> hasithajayasunda...@gmail.com> wrote:
>
>> Hi ayya,
>>
>> As we discussed today can you provide me some materials to get more
>> familiar with IBM MQ 8.0?
>>
>> thanks
>>
>> --
>> *D.M.Hasitha Nadishan Jayasundara*
>> *Department of Electronic and Telecommunication Engineering*
>> University of Moratuwa
>> *mobile:* *+94711959266 <071%20195%209266>*
>> *blogspot*: learnjavawithisla.blogspot.com/  *email:*
>> hasithajayasunda...@gmail.com
>> <https://www.facebook.com/hasitha.nadishan.3>
>> <https://twitter.com/HNadishan>
>> <https://lk.linkedin.com/in/hasithajayasundara>
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Associate Director / Architect
> M: +94 777 219 791 <+94%2077%20721%209791>
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> https://wso2.com/signature
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Don't make Trees rare, we should keep them with care
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Fathima Dilhasha

2017-05-17 Thread Riyafa Abdul Hameed

Congratulations...

On Tue, May 16, 2017 at 8:43 AM, Yasima Dewmini <yas...@wso2.com> wrote:

> Congratz Dilhasha! :)
>
> On Mon, May 15, 2017 at 11:34 AM, Isuru Wimalasundera <isu...@wso2.com>
> wrote:
>
>> Hi All
>>
>> It's my pleasure to welcome Fathima Dilhasha as a WSO2 Committer.
>>
>> Dilhasha has been a valuable contributor to WSO2 cloud team.  In
>> recognition of her contribution, dedication and commitment she has been
>> voted as a WSO2 committer.
>>
>> Dilhasha, welcome aboard and keep up the good work !!!
>>
>> Thank You
>>
>> --
>> *Isuru Wimalasundera*
>> Associate Technical Lead;
>> WSO2 Cloud; http://cloud.wso2.com
>> WSO2, Inc.; http://wso2.com,
>> mobile: +94 77 920 5641
>> Blog : http://isurupw.blogspot.com/
>> <http://isurupw.blogspot.com/>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> http://wso2.com/signatureYasima Dewmini
> Software Engineer, WSO2, Inc.
> Email: yas...@wso2.com
> Mobile: +94713117081 <+94%2071%20311%207081>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Riyafa Abdul Hameed
Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>

Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while building ESB using java 8 and maven 3.3

2016-03-21 Thread Riyafa Abdul Hameed

Hi,

The exact error was:

*Installation failed.

One or more certificates rejected. Cannot proceed with installation.*

As suggested in [1] I used a fresh copy of JDK and successfully built the
ESB.

[1] http://mail.wso2.org/mailarchive/dev/2014-November/039151.html

Thank you,
Riyafa

On Mon, Mar 21, 2016 at 9:32 AM, Riyafa Abdul Hameed <riy...@wso2.com>
wrote:

> Hi,
>
> I was able to successfully build the ESB using java 7 when
> wso2-axis2-transports, wso2-synapse, carbon-mediation were all built using
> java 7.
> But when I try to build the ESB using java 8 when all the other
> dependencies also were built using java 8 I get the following error:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.4:materialize-product
> (creating-worker-profile) on project wso2esb-p2-profile: Cannot generate P2
> metadata: P2 publisher return code was 13 -> [Help
> 1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.wso2.maven:carbon-p2-plugin:1.5.4:materialize-product
> (creating-worker-profile) on project wso2esb-p2-profile: Cannot generate P2
> metadataat
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)at
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)at
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:197)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)at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)Caused
> by: org.apache.maven.plugin.MojoExecutionException: Cannot generate P2
> metadataat
> org.wso2.maven.p2.MaterializeProductMojo.execute(MaterializeProductMojo.java:106)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 moreCaused by: org.apache.maven.plugin.MojoFailureException: P2
> publisher return code was 13at
> org.wso2.maven.p2.MaterializeProductMojo.deployRepository(MaterializeProductMojo.java:182)
> at
> org.wso2.maven.p2.MaterializeProductMojo.execute(MaterializeProductMojo.java:101)
> ... 22 more*
>
> I am not using eclipse as in issue[1]. I built a direct clone from wso2
> repo[2]
> I have used a clean repo and tried building all again and get the same
> error with java 8.
>
> Please kindly help.
>
>
> [1] http://mail.wso2.org/mailarchive/dev/2014-July/033811.html
> [2] https://github.com/wso2/product-esb.git
>
> Thank you.
> Riyafa
> --
> Riyafa Abdul Hameed
> Software Engineering intern, WSO2
>
> Email: riy...@wso2.com
> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
> <http://twitter.com/Riyafa1>
>



-- 
Riyafa Abdul Hameed
Software Engineering intern, WSO2

Email: riy...@wso2.com
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error while building ESB using java 8 and maven 3.3

2016-03-20 Thread Riyafa Abdul Hameed

Hi,

I was able to successfully build the ESB using java 7 when
wso2-axis2-transports, wso2-synapse, carbon-mediation were all built using
java 7.
But when I try to build the ESB using java 8 when all the other
dependencies also were built using java 8 I get the following error:
































*Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.4:materialize-product
(creating-worker-profile) on project wso2esb-p2-profile: Cannot generate P2
metadata: P2 publisher return code was 13 -> [Help
1]org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.wso2.maven:carbon-p2-plugin:1.5.4:materialize-product
(creating-worker-profile) on project wso2esb-p2-profile: Cannot generate P2
metadataat
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)at
org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)at
org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)at
org.apache.maven.cli.MavenCli.main(MavenCli.java:197)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)at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)Caused
by: org.apache.maven.plugin.MojoExecutionException: Cannot generate P2
metadataat
org.wso2.maven.p2.MaterializeProductMojo.execute(MaterializeProductMojo.java:106)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 moreCaused by: org.apache.maven.plugin.MojoFailureException: P2
publisher return code was 13at
org.wso2.maven.p2.MaterializeProductMojo.deployRepository(MaterializeProductMojo.java:182)
at
org.wso2.maven.p2.MaterializeProductMojo.execute(MaterializeProductMojo.java:101)
... 22 more*

I am not using eclipse as in issue[1]. I built a direct clone from wso2
repo[2]
I have used a clean repo and tried building all again and get the same
error with java 8.

Please kindly help.


[1] http://mail.wso2.org/mailarchive/dev/2014-July/033811.html
[2] https://github.com/wso2/product-esb.git

Thank you.
Riyafa
-- 
Riyafa Abdul Hameed
Software Engineering intern, WSO2

Email: riy...@wso2.com
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-29 Thread Riyafa Abdul Hameed

 Hi,

Thank you very much for the reply. I will try it out and contact you if I
run into any trouble.

Thanks again.

Yours sincerely,

Riyafa Abdul Hameed

On 29 February 2016 at 10:20, Sajini De Silva <saj...@wso2.com> wrote:

> Hi Riyafa,
>
> In IBM MQ, SSL can be enabled for a channel and there can be many channel
> for a particular queue manager. In order to enable SSL you have to have a
> keystore and a truststore for both your java client and MQ. You can create
> these using keytool in java. After that you have to generate certificates
> for both of your client and MQ using keytool command. Then you have to
> import MQ's certificate to client trust store and client's certificate to
> MQ's trust store. (This is done for mutual authentication).
>
> SSL can be configured for IBM MQ via MQ Explorer. You can refer [1] to
> understand how SSL can be configured for a particular channel in queue
> manager.
>
> Please ask if you came across any other problem.
>
> [1]
> http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.explorer.doc/e_ssl_security.htm
>
> Thank you
>
> On Sun, Feb 28, 2016 at 6:20 PM, Riyafa Abdul Hameed <
> riyafa...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>> I have tried and failed to understand how to incorporate SSL and
>> authentication into the java client. I have referred many websites
>> Eg.[1],[2].[3] and referred IBM knowledge center, but could not understand
>> how SSL and authentication works on queue managers. I know I should figure
>> this out myself, but I did my best and couldn't figure it out. Can you
>> please help out if possible?
>>
>> The main thing I don't understand is what should go into C:\Program Files
>> (x86)\IBM\WebSphere MQ\qmgrs\SSLQMGR\ssl\key directory? (where SSLQMGR is
>> the name of a queue manager I created) I found this[4] site speaking of it.
>> But, I am not sure I understand anything much there. Maybe it is because I
>> am not an expert in SSL certificates and keystores being a newbie. Can you
>> please help out in some way?
>> If you would show me some way to follow I hope I would be able to figure
>> it out.
>>
>> Further I am planning to improve my knowledge on connectors in the coming
>> week.
>>
>> [1]
>> http://www.ibm.com/developerworks/websphere/library/techarticles/0510_fehners/0510_fehners.html
>> [2] https://docs.oracle.com/cd/E19509-01/820-3503/ggfad/index.html
>> [3]
>> http://stackoverflow.com/questions/2692070/connecting-to-a-websphere-mq-in-java-with-ssl-keystore
>> [4]
>> http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.sec.doc/q010090_.htm
>>
>> Thank you.
>>
>> Yours sincerely,
>> Riyafa Abdul Hameed
>>
>> On 23 February 2016 at 05:40, Riyafa Abdul Hameed <
>> riyafa...@cse.mrt.ac.lk> wrote:
>>
>>> Hi,
>>> I suppose then it would be better to use the polling custom-inbound
>>> endpoint. I will try to understand ssl and authentication feature and
>>> report back.
>>>
>>> Thank you.
>>>
>>> Yours sincerely,
>>> Riyafa
>>>
>>>
>>> On 22 February 2016 at 07:02, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Hi Riyafa ,
>>>>
>>>> I guess you can implement it using one of those types. One issue is
>>>> event based type is going to be introduce with ESB 5.0.0. Next wso2 esb
>>>> version. If you use this this feature will not work with previous versions
>>>> on esbs.
>>>>
>>>> I think you can adjust Get-message
>>>>  
>>>> behavior using WaitInterval
>>>>  parameter and do polling or event-based. [1]
>>>>
>>>> However there may be issues with client libraries when waiting for long
>>>> periods. We first need to do a r of the behavior from library when there
>>>> are no messages for a long period. Based on that we should decide the
>>>> correct approach.
>>>>
>>>> Also it is important to include SSL and authentication into this
>>>> feature.
>>>>
>>>> [1]
>>>> https://www-01.ibm.com/support/knowledgecenter/SSB23S_1.1.0.12/gtpc2/mqgmost.html
>>>>
>>>> On Sun, Feb 21, 2016 at 6:58 PM, Riyafa Abdul Hameed <
>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Can you please suggest if it would be appropriate to use an event
>>>>> based custom inbound endpoint in this case so that I would learn more

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-28 Thread Riyafa Abdul Hameed

Hi,

I have tried and failed to understand how to incorporate SSL and
authentication into the java client. I have referred many websites
Eg.[1],[2].[3] and referred IBM knowledge center, but could not understand
how SSL and authentication works on queue managers. I know I should figure
this out myself, but I did my best and couldn't figure it out. Can you
please help out if possible?

The main thing I don't understand is what should go into C:\Program Files
(x86)\IBM\WebSphere MQ\qmgrs\SSLQMGR\ssl\key directory? (where SSLQMGR is
the name of a queue manager I created) I found this[4] site speaking of it.
But, I am not sure I understand anything much there. Maybe it is because I
am not an expert in SSL certificates and keystores being a newbie. Can you
please help out in some way?
If you would show me some way to follow I hope I would be able to figure it
out.

Further I am planning to improve my knowledge on connectors in the coming
week.

[1]
http://www.ibm.com/developerworks/websphere/library/techarticles/0510_fehners/0510_fehners.html
[2] https://docs.oracle.com/cd/E19509-01/820-3503/ggfad/index.html
[3]
http://stackoverflow.com/questions/2692070/connecting-to-a-websphere-mq-in-java-with-ssl-keystore
[4]
http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.sec.doc/q010090_.htm

Thank you.

Yours sincerely,
Riyafa Abdul Hameed

On 23 February 2016 at 05:40, Riyafa Abdul Hameed <riyafa...@cse.mrt.ac.lk>
wrote:

> Hi,
> I suppose then it would be better to use the polling custom-inbound
> endpoint. I will try to understand ssl and authentication feature and
> report back.
>
> Thank you.
>
> Yours sincerely,
> Riyafa
>
>
> On 22 February 2016 at 07:02, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Riyafa ,
>>
>> I guess you can implement it using one of those types. One issue is event
>> based type is going to be introduce with ESB 5.0.0. Next wso2 esb version.
>> If you use this this feature will not work with previous versions on esbs.
>>
>> I think you can adjust Get-message
>>  
>> behavior using WaitInterval
>>  parameter and do polling or event-based. [1]
>>
>> However there may be issues with client libraries when waiting for long
>> periods. We first need to do a r of the behavior from library when there
>> are no messages for a long period. Based on that we should decide the
>> correct approach.
>>
>> Also it is important to include SSL and authentication into this feature.
>>
>> [1]
>> https://www-01.ibm.com/support/knowledgecenter/SSB23S_1.1.0.12/gtpc2/mqgmost.html
>>
>> On Sun, Feb 21, 2016 at 6:58 PM, Riyafa Abdul Hameed <
>> riyafa...@cse.mrt.ac.lk> wrote:
>>
>>> Hi,
>>>
>>> Can you please suggest if it would be appropriate to use an event based
>>> custom inbound endpoint in this case so that I would learn more about it?
>>>
>>> Thank you.
>>>
>>> Yours sincerely,
>>> Riyafa
>>>
>>> On 21 February 2016 at 18:09, Rajjaz Mohammed <raj...@wso2.com> wrote:
>>>
>>>> Hi Riyafa,
>>>> You no need to follow exactly as same as in [1]. it's just an try of
>>>> one developer so you can try your own way.
>>>>
>>>> [1]
>>>> https://github.com/Kirishanthy/IBM-MQ-Client/blob/master/ibmmqClient/src/main/java/MQProducerSSL.java
>>>>
>>>> On Sun, Feb 21, 2016 at 5:38 PM, Riyafa Abdul Hameed <
>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>> *Reporting progress:*
>>>>> This week I learned about inbound endpoints and how to use them. I did
>>>>> some searching and found that two types of custom inbound endpoints are
>>>>> suitable as consumer for IBM MQ:
>>>>>
>>>>> 1. Polling custom inbound endpoint
>>>>> 2. Event based custom inbound endpoint
>>>>>
>>>>> As for the first one I have found that code have been written to
>>>>> achieve this[1]. As for the second I think it is more appropriate to use 
>>>>> it
>>>>> when " the number of messages arriving on the queues is unpredictable. In
>>>>> this case if polling is used, applications could be consuming system
>>>>> resources even when there are no messages to retrieve." I have found in 
>>>>> [2]
>>>>> and [3] about triggers. I have not tried any of those yet. I will do so
>>>>> hopefully in the near future.
>>>>>
>>>>> Further I went

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-23 Thread Riyafa Abdul Hameed

Hi,
I suppose then it would be better to use the polling custom-inbound
endpoint. I will try to understand ssl and authentication feature and
report back.

Thank you.

Yours sincerely,
Riyafa


On 22 February 2016 at 07:02, Malaka Silva <mal...@wso2.com> wrote:

> Hi Riyafa ,
>
> I guess you can implement it using one of those types. One issue is event
> based type is going to be introduce with ESB 5.0.0. Next wso2 esb version.
> If you use this this feature will not work with previous versions on esbs.
>
> I think you can adjust Get-message
>  
> behavior using WaitInterval
>  parameter and do polling or event-based. [1]
>
> However there may be issues with client libraries when waiting for long
> periods. We first need to do a r of the behavior from library when there
> are no messages for a long period. Based on that we should decide the
> correct approach.
>
> Also it is important to include SSL and authentication into this feature.
>
> [1]
> https://www-01.ibm.com/support/knowledgecenter/SSB23S_1.1.0.12/gtpc2/mqgmost.html
>
> On Sun, Feb 21, 2016 at 6:58 PM, Riyafa Abdul Hameed <
> riyafa...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>> Can you please suggest if it would be appropriate to use an event based
>> custom inbound endpoint in this case so that I would learn more about it?
>>
>> Thank you.
>>
>> Yours sincerely,
>> Riyafa
>>
>> On 21 February 2016 at 18:09, Rajjaz Mohammed <raj...@wso2.com> wrote:
>>
>>> Hi Riyafa,
>>> You no need to follow exactly as same as in [1]. it's just an try of one
>>> developer so you can try your own way.
>>>
>>> [1]
>>> https://github.com/Kirishanthy/IBM-MQ-Client/blob/master/ibmmqClient/src/main/java/MQProducerSSL.java
>>>
>>> On Sun, Feb 21, 2016 at 5:38 PM, Riyafa Abdul Hameed <
>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> *Reporting progress:*
>>>> This week I learned about inbound endpoints and how to use them. I did
>>>> some searching and found that two types of custom inbound endpoints are
>>>> suitable as consumer for IBM MQ:
>>>>
>>>> 1. Polling custom inbound endpoint
>>>> 2. Event based custom inbound endpoint
>>>>
>>>> As for the first one I have found that code have been written to
>>>> achieve this[1]. As for the second I think it is more appropriate to use it
>>>> when " the number of messages arriving on the queues is unpredictable. In
>>>> this case if polling is used, applications could be consuming system
>>>> resources even when there are no messages to retrieve." I have found in [2]
>>>> and [3] about triggers. I have not tried any of those yet. I will do so
>>>> hopefully in the near future.
>>>>
>>>> Further I went through the code provided in [1] and found that I have
>>>> created the consumer and the producer in the same way as in the above code.
>>>> But I didn't understand how to use ssl with the queue manager[4]. I will
>>>> try to understand that as well.
>>>>
>>>> That is what I have done this week. Please inform me whether my
>>>> approach is correct and what else I could do.
>>>>
>>>> [1]https://github.com/search?q=user%3AKirishanthy+ibm-mq
>>>> [2]
>>>> https://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.dev.doc/q026910_.htm
>>>> [3]
>>>> http://stackoverflow.com/questions/26840204/ibm-websphere-mq-triggering-issue
>>>> [4]
>>>> https://github.com/Kirishanthy/IBM-MQ-Client/blob/master/ibmmqClient/src/main/java/MQProducerSSL.java
>>>>
>>>> Thank you.
>>>>
>>>> Yours sincerely,
>>>> Riyafa
>>>>
>>>> On 14 February 2016 at 16:46, Riyafa Abdul Hameed <
>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Thank you for the reply. I shall follow the links you sent and report
>>>>> progress.
>>>>>
>>>>> Thanks again,
>>>>> Riyafa
>>>>>
>>>>> On 13 February 2016 at 20:45, Rajjaz Mohammed <raj...@wso2.com> wrote:
>>>>>
>>>>>> Hi Riyafa,
>>>>>> Good to hear, first learn how wso2 ESB custom inbound works[1][2].
>>>>>> And there is a thread regarding IBM MQ Inbound/Connector[3] already so 
>

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-21 Thread Riyafa Abdul Hameed

Hi,

Can you please suggest if it would be appropriate to use an event based
custom inbound endpoint in this case so that I would learn more about it?

Thank you.

Yours sincerely,
Riyafa

On 21 February 2016 at 18:09, Rajjaz Mohammed <raj...@wso2.com> wrote:

> Hi Riyafa,
> You no need to follow exactly as same as in [1]. it's just an try of one
> developer so you can try your own way.
>
> [1]
> https://github.com/Kirishanthy/IBM-MQ-Client/blob/master/ibmmqClient/src/main/java/MQProducerSSL.java
>
> On Sun, Feb 21, 2016 at 5:38 PM, Riyafa Abdul Hameed <
> riyafa...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>>
>>
>> *Reporting progress:*
>> This week I learned about inbound endpoints and how to use them. I did
>> some searching and found that two types of custom inbound endpoints are
>> suitable as consumer for IBM MQ:
>>
>> 1. Polling custom inbound endpoint
>> 2. Event based custom inbound endpoint
>>
>> As for the first one I have found that code have been written to achieve
>> this[1]. As for the second I think it is more appropriate to use it when "
>> the number of messages arriving on the queues is unpredictable. In this
>> case if polling is used, applications could be consuming system resources
>> even when there are no messages to retrieve." I have found in [2] and [3]
>> about triggers. I have not tried any of those yet. I will do so hopefully
>> in the near future.
>>
>> Further I went through the code provided in [1] and found that I have
>> created the consumer and the producer in the same way as in the above code.
>> But I didn't understand how to use ssl with the queue manager[4]. I will
>> try to understand that as well.
>>
>> That is what I have done this week. Please inform me whether my approach
>> is correct and what else I could do.
>>
>> [1]https://github.com/search?q=user%3AKirishanthy+ibm-mq
>> [2]
>> https://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.dev.doc/q026910_.htm
>> [3]
>> http://stackoverflow.com/questions/26840204/ibm-websphere-mq-triggering-issue
>> [4]
>> https://github.com/Kirishanthy/IBM-MQ-Client/blob/master/ibmmqClient/src/main/java/MQProducerSSL.java
>>
>> Thank you.
>>
>> Yours sincerely,
>> Riyafa
>>
>> On 14 February 2016 at 16:46, Riyafa Abdul Hameed <
>> riyafa...@cse.mrt.ac.lk> wrote:
>>
>>> Hi,
>>>
>>> Thank you for the reply. I shall follow the links you sent and report
>>> progress.
>>>
>>> Thanks again,
>>> Riyafa
>>>
>>> On 13 February 2016 at 20:45, Rajjaz Mohammed <raj...@wso2.com> wrote:
>>>
>>>> Hi Riyafa,
>>>> Good to hear, first learn how wso2 ESB custom inbound works[1][2]. And
>>>> there is a thread regarding IBM MQ Inbound/Connector[3] already so you can
>>>> check the issues and samples[4][5].
>>>>
>>>> [1] https://docs.wso2.com/display/ESB490/Working+with+Inbound+Endpoints
>>>> [2]
>>>> http://wso2experience.blogspot.com/2015/08/getting-started-with-simple-wso2-esb_22.html
>>>> [3]
>>>> http://wso2-oxygen-tank.10903.n7.nabble.com/IBM-MQ-Inbound-Connector-for-WSO2-ESB-td125494.html#a125507
>>>> [4] https://github.com/Kirishanthy/esb-connectors/tree/master/ibmmq
>>>> [5] https://github.com/search?q=user%3AKirishanthy+ibm-mq
>>>>
>>>> On Sat, Feb 13, 2016 at 8:22 PM, Riyafa Abdul Hameed <
>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>
>>>>> Hi Malaka,
>>>>>
>>>>> I managed to install Websphere MQ 7.5 on my windows machine and to try 
>>>>> connection
>>>>> as consumer and producer from simple java clients I created [1]. Please
>>>>> suggest what else that needs to be done to get started.
>>>>>
>>>>>
>>>>> [1] https://github.com/riyafa/websphere/tree/master/src/riyafa
>>>>>
>>>>> Thank you,
>>>>> Riyafa
>>>>>
>>>>> On 11 February 2016 at 19:32, Malaka Silva <mal...@wso2.com> wrote:
>>>>>
>>>>>> Yes sometimes there are issues when installing on linux based
>>>>>> system. Go ahead and try on Windows.
>>>>>>
>>>>>> You can call me Malaka :)
>>>>>>
>>>>>> On Thu, Feb 11, 2016 at 7:28 PM, Riyafa Abdul Hameed <
>>>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>>>
>&

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-21 Thread Riyafa Abdul Hameed

Hi,



*Reporting progress:*
This week I learned about inbound endpoints and how to use them. I did some
searching and found that two types of custom inbound endpoints are suitable
as consumer for IBM MQ:

1. Polling custom inbound endpoint
2. Event based custom inbound endpoint

As for the first one I have found that code have been written to achieve
this[1]. As for the second I think it is more appropriate to use it when "
the number of messages arriving on the queues is unpredictable. In this
case if polling is used, applications could be consuming system resources
even when there are no messages to retrieve." I have found in [2] and [3]
about triggers. I have not tried any of those yet. I will do so hopefully
in the near future.

Further I went through the code provided in [1] and found that I have
created the consumer and the producer in the same way as in the above code.
But I didn't understand how to use ssl with the queue manager[4]. I will
try to understand that as well.

That is what I have done this week. Please inform me whether my approach is
correct and what else I could do.

[1]https://github.com/search?q=user%3AKirishanthy+ibm-mq
[2]
https://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.dev.doc/q026910_.htm
[3]
http://stackoverflow.com/questions/26840204/ibm-websphere-mq-triggering-issue
[4]
https://github.com/Kirishanthy/IBM-MQ-Client/blob/master/ibmmqClient/src/main/java/MQProducerSSL.java

Thank you.

Yours sincerely,
Riyafa

On 14 February 2016 at 16:46, Riyafa Abdul Hameed <riyafa...@cse.mrt.ac.lk>
wrote:

> Hi,
>
> Thank you for the reply. I shall follow the links you sent and report
> progress.
>
> Thanks again,
> Riyafa
>
> On 13 February 2016 at 20:45, Rajjaz Mohammed <raj...@wso2.com> wrote:
>
>> Hi Riyafa,
>> Good to hear, first learn how wso2 ESB custom inbound works[1][2]. And
>> there is a thread regarding IBM MQ Inbound/Connector[3] already so you can
>> check the issues and samples[4][5].
>>
>> [1] https://docs.wso2.com/display/ESB490/Working+with+Inbound+Endpoints
>> [2]
>> http://wso2experience.blogspot.com/2015/08/getting-started-with-simple-wso2-esb_22.html
>> [3]
>> http://wso2-oxygen-tank.10903.n7.nabble.com/IBM-MQ-Inbound-Connector-for-WSO2-ESB-td125494.html#a125507
>> [4] https://github.com/Kirishanthy/esb-connectors/tree/master/ibmmq
>> [5] https://github.com/search?q=user%3AKirishanthy+ibm-mq
>>
>> On Sat, Feb 13, 2016 at 8:22 PM, Riyafa Abdul Hameed <
>> riyafa...@cse.mrt.ac.lk> wrote:
>>
>>> Hi Malaka,
>>>
>>> I managed to install Websphere MQ 7.5 on my windows machine and to try 
>>> connection
>>> as consumer and producer from simple java clients I created [1]. Please
>>> suggest what else that needs to be done to get started.
>>>
>>>
>>> [1] https://github.com/riyafa/websphere/tree/master/src/riyafa
>>>
>>> Thank you,
>>> Riyafa
>>>
>>> On 11 February 2016 at 19:32, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Yes sometimes there are issues when installing on linux based system.
>>>> Go ahead and try on Windows.
>>>>
>>>> You can call me Malaka :)
>>>>
>>>> On Thu, Feb 11, 2016 at 7:28 PM, Riyafa Abdul Hameed <
>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>
>>>>> Dear sir,
>>>>>
>>>>> I failed to install IBM MQ 7.5 on my Ubuntu machine. It seemed to be
>>>>> because of attempting to install rpm files. I will try to install it in a
>>>>> windows machine or in a redhat or fedora version of linux. Then I will try
>>>>> connection as a consumer and producer from a java client. I shall
>>>>> report progress every week.
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Yours sincerely,
>>>>> Riyafa
>>>>>
>>>>> On 11 February 2016 at 06:38, Malaka Silva <mal...@wso2.com> wrote:
>>>>>
>>>>>> Hi Riyafa,
>>>>>>
>>>>>> Please post the progress weekly or once in two weeks.
>>>>>>
>>>>>> On Wed, Feb 10, 2016 at 10:31 PM, Riyafa Abdul Hameed <
>>>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I shall do that and report once done or if I have any problem.
>>>>>>>
>>>>>>> Thank you.
>>>>>>>
>>>>>>> Yours sincerely,
>>>>>&g

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-14 Thread Riyafa Abdul Hameed

Hi,

Thank you for the reply. I shall follow the links you sent and report
progress.

Thanks again,
Riyafa

On 13 February 2016 at 20:45, Rajjaz Mohammed <raj...@wso2.com> wrote:

> Hi Riyafa,
> Good to hear, first learn how wso2 ESB custom inbound works[1][2]. And
> there is a thread regarding IBM MQ Inbound/Connector[3] already so you can
> check the issues and samples[4][5].
>
> [1] https://docs.wso2.com/display/ESB490/Working+with+Inbound+Endpoints
> [2]
> http://wso2experience.blogspot.com/2015/08/getting-started-with-simple-wso2-esb_22.html
> [3]
> http://wso2-oxygen-tank.10903.n7.nabble.com/IBM-MQ-Inbound-Connector-for-WSO2-ESB-td125494.html#a125507
> [4] https://github.com/Kirishanthy/esb-connectors/tree/master/ibmmq
> [5] https://github.com/search?q=user%3AKirishanthy+ibm-mq
>
> On Sat, Feb 13, 2016 at 8:22 PM, Riyafa Abdul Hameed <
> riyafa...@cse.mrt.ac.lk> wrote:
>
>> Hi Malaka,
>>
>> I managed to install Websphere MQ 7.5 on my windows machine and to try 
>> connection
>> as consumer and producer from simple java clients I created [1]. Please
>> suggest what else that needs to be done to get started.
>>
>>
>> [1] https://github.com/riyafa/websphere/tree/master/src/riyafa
>>
>> Thank you,
>> Riyafa
>>
>> On 11 February 2016 at 19:32, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Yes sometimes there are issues when installing on linux based system.
>>> Go ahead and try on Windows.
>>>
>>> You can call me Malaka :)
>>>
>>> On Thu, Feb 11, 2016 at 7:28 PM, Riyafa Abdul Hameed <
>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>
>>>> Dear sir,
>>>>
>>>> I failed to install IBM MQ 7.5 on my Ubuntu machine. It seemed to be
>>>> because of attempting to install rpm files. I will try to install it in a
>>>> windows machine or in a redhat or fedora version of linux. Then I will try
>>>> connection as a consumer and producer from a java client. I shall
>>>> report progress every week.
>>>>
>>>> Thank you.
>>>>
>>>> Yours sincerely,
>>>> Riyafa
>>>>
>>>> On 11 February 2016 at 06:38, Malaka Silva <mal...@wso2.com> wrote:
>>>>
>>>>> Hi Riyafa,
>>>>>
>>>>> Please post the progress weekly or once in two weeks.
>>>>>
>>>>> On Wed, Feb 10, 2016 at 10:31 PM, Riyafa Abdul Hameed <
>>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I shall do that and report once done or if I have any problem.
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> Yours sincerely,
>>>>>> Riyafa
>>>>>>
>>>>>> On 10 February 2016 at 12:38, Malaka Silva <mal...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Riyafa,
>>>>>>>
>>>>>>> First you should install IBM MQ 7.5.
>>>>>>>
>>>>>>> Then try connection as consumer and producer from a java client.
>>>>>>> Using IBM MQ client.
>>>>>>>
>>>>>>> This need to add consumer functionality to custom inbound endpoint
>>>>>>> and producer to a connector.
>>>>>>>
>>>>>>> On Wed, Feb 10, 2016 at 7:16 AM, Riyafa Abdul Hameed <
>>>>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>>>>
>>>>>>>> Dear sir,
>>>>>>>>
>>>>>>>> I am a third year Computer Science and Engineering undergraduate at
>>>>>>>> University of Moratuwa. I would like to take part in GSoC 2016 with the
>>>>>>>> open source community of WSO2.
>>>>>>>>
>>>>>>>> I am quite familiar with the ESB-Connectors of WSO2. I have
>>>>>>>> previously worked with the saleforce, google-spreadsheet and the 
>>>>>>>> peopleHR
>>>>>>>> connectors on a project that involved automating the filling of a 
>>>>>>>> google
>>>>>>>> spreadsheet with details from salesforce. I am also quite familiar 
>>>>>>>> working
>>>>>>>> with the WSO2 ESB and have prior experience of writing proxy services. 
>>>>>>>> And
>>>>>

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-13 Thread Riyafa Abdul Hameed

Hi Malaka,

I managed to install Websphere MQ 7.5 on my windows machine and to try
connection
as consumer and producer from simple java clients I created [1]. Please
suggest what else that needs to be done to get started.


[1] https://github.com/riyafa/websphere/tree/master/src/riyafa

Thank you,
Riyafa

On 11 February 2016 at 19:32, Malaka Silva <mal...@wso2.com> wrote:

> Yes sometimes there are issues when installing on linux based system. Go
> ahead and try on Windows.
>
> You can call me Malaka :)
>
> On Thu, Feb 11, 2016 at 7:28 PM, Riyafa Abdul Hameed <
> riyafa...@cse.mrt.ac.lk> wrote:
>
>> Dear sir,
>>
>> I failed to install IBM MQ 7.5 on my Ubuntu machine. It seemed to be
>> because of attempting to install rpm files. I will try to install it in a
>> windows machine or in a redhat or fedora version of linux. Then I will try
>> connection as a consumer and producer from a java client. I shall report
>> progress every week.
>>
>> Thank you.
>>
>> Yours sincerely,
>> Riyafa
>>
>> On 11 February 2016 at 06:38, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Hi Riyafa,
>>>
>>> Please post the progress weekly or once in two weeks.
>>>
>>> On Wed, Feb 10, 2016 at 10:31 PM, Riyafa Abdul Hameed <
>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>
>>>> Hi,
>>>>
>>>> I shall do that and report once done or if I have any problem.
>>>>
>>>> Thank you.
>>>>
>>>> Yours sincerely,
>>>> Riyafa
>>>>
>>>> On 10 February 2016 at 12:38, Malaka Silva <mal...@wso2.com> wrote:
>>>>
>>>>> Hi Riyafa,
>>>>>
>>>>> First you should install IBM MQ 7.5.
>>>>>
>>>>> Then try connection as consumer and producer from a java client. Using
>>>>> IBM MQ client.
>>>>>
>>>>> This need to add consumer functionality to custom inbound endpoint and
>>>>> producer to a connector.
>>>>>
>>>>> On Wed, Feb 10, 2016 at 7:16 AM, Riyafa Abdul Hameed <
>>>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>>>
>>>>>> Dear sir,
>>>>>>
>>>>>> I am a third year Computer Science and Engineering undergraduate at
>>>>>> University of Moratuwa. I would like to take part in GSoC 2016 with the
>>>>>> open source community of WSO2.
>>>>>>
>>>>>> I am quite familiar with the ESB-Connectors of WSO2. I have
>>>>>> previously worked with the saleforce, google-spreadsheet and the peopleHR
>>>>>> connectors on a project that involved automating the filling of a google
>>>>>> spreadsheet with details from salesforce. I am also quite familiar 
>>>>>> working
>>>>>> with the WSO2 ESB and have prior experience of writing proxy services. 
>>>>>> And
>>>>>> I am a quick learner.
>>>>>>
>>>>>> I have also contributed to the peopleHR connector of WSO2 [1].
>>>>>>
>>>>>> Being quite familiar with the WSO2 connector development, I consider
>>>>>> doing the project "Native inbound and connector for IBM MQ 7.5" with the
>>>>>> WSO2 community for GSoC this year.
>>>>>>
>>>>>> Please kindly make any suggestions on how I could proceed.
>>>>>>
>>>>>>
>>>>>> [1] https://github.com/wso2/esb-connectors/pull/419
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> Yours sincerely,
>>>>>> Riyafa
>>>>>>
>>>>>> --
>>>>>> Riyafa Abdul Hameed
>>>>>> Undergraduate, University of Moratuwa
>>>>>>
>>>>>> Email: riyafa...@cse.mrt.ac.lk
>>>>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>>>>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>>>>>> <http://twitter.com/Riyafa1>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Best Regards,
>>>>>
>>>>> Malaka Silva
>>>>> Senior Tech Lead
>>>>> M: +94 777 219 791
>>>>> Tel : 94 11 214 5345

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-11 Thread Riyafa Abdul Hameed

Dear sir,

I failed to install IBM MQ 7.5 on my Ubuntu machine. It seemed to be
because of attempting to install rpm files. I will try to install it in a
windows machine or in a redhat or fedora version of linux. Then I will try
connection as a consumer and producer from a java client. I shall report
progress every week.

Thank you.

Yours sincerely,
Riyafa

On 11 February 2016 at 06:38, Malaka Silva <mal...@wso2.com> wrote:

> Hi Riyafa,
>
> Please post the progress weekly or once in two weeks.
>
> On Wed, Feb 10, 2016 at 10:31 PM, Riyafa Abdul Hameed <
> riyafa...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>> I shall do that and report once done or if I have any problem.
>>
>> Thank you.
>>
>> Yours sincerely,
>> Riyafa
>>
>> On 10 February 2016 at 12:38, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Hi Riyafa,
>>>
>>> First you should install IBM MQ 7.5.
>>>
>>> Then try connection as consumer and producer from a java client. Using
>>> IBM MQ client.
>>>
>>> This need to add consumer functionality to custom inbound endpoint and
>>> producer to a connector.
>>>
>>> On Wed, Feb 10, 2016 at 7:16 AM, Riyafa Abdul Hameed <
>>> riyafa...@cse.mrt.ac.lk> wrote:
>>>
>>>> Dear sir,
>>>>
>>>> I am a third year Computer Science and Engineering undergraduate at
>>>> University of Moratuwa. I would like to take part in GSoC 2016 with the
>>>> open source community of WSO2.
>>>>
>>>> I am quite familiar with the ESB-Connectors of WSO2. I have previously
>>>> worked with the saleforce, google-spreadsheet and the peopleHR connectors
>>>> on a project that involved automating the filling of a google spreadsheet
>>>> with details from salesforce. I am also quite familiar working with the
>>>> WSO2 ESB and have prior experience of writing proxy services. And I am a
>>>> quick learner.
>>>>
>>>> I have also contributed to the peopleHR connector of WSO2 [1].
>>>>
>>>> Being quite familiar with the WSO2 connector development, I consider
>>>> doing the project "Native inbound and connector for IBM MQ 7.5" with the
>>>> WSO2 community for GSoC this year.
>>>>
>>>> Please kindly make any suggestions on how I could proceed.
>>>>
>>>>
>>>> [1] https://github.com/wso2/esb-connectors/pull/419
>>>>
>>>> Thank you.
>>>>
>>>> Yours sincerely,
>>>> Riyafa
>>>>
>>>> --
>>>> Riyafa Abdul Hameed
>>>> Undergraduate, University of Moratuwa
>>>>
>>>> Email: riyafa...@cse.mrt.ac.lk
>>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>>>> <http://twitter.com/Riyafa1>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> 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/>
>>> https://store.wso2.com/store/
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> Riyafa Abdul Hameed
>> Undergraduate, University of Moratuwa
>>
>> Email: riyafa...@cse.mrt.ac.lk
>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>> <http://twitter.com/Riyafa1>
>>
>
>
>
> --
>
> 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/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Riyafa Abdul Hameed
Undergraduate, University of Moratuwa

Email: riyafa...@cse.mrt.ac.lk
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-10 Thread Riyafa Abdul Hameed

Hi,

I shall do that and report once done or if I have any problem.

Thank you.

Yours sincerely,
Riyafa

On 10 February 2016 at 12:38, Malaka Silva <mal...@wso2.com> wrote:

> Hi Riyafa,
>
> First you should install IBM MQ 7.5.
>
> Then try connection as consumer and producer from a java client. Using IBM
> MQ client.
>
> This need to add consumer functionality to custom inbound endpoint and
> producer to a connector.
>
> On Wed, Feb 10, 2016 at 7:16 AM, Riyafa Abdul Hameed <
> riyafa...@cse.mrt.ac.lk> wrote:
>
>> Dear sir,
>>
>> I am a third year Computer Science and Engineering undergraduate at
>> University of Moratuwa. I would like to take part in GSoC 2016 with the
>> open source community of WSO2.
>>
>> I am quite familiar with the ESB-Connectors of WSO2. I have previously
>> worked with the saleforce, google-spreadsheet and the peopleHR connectors
>> on a project that involved automating the filling of a google spreadsheet
>> with details from salesforce. I am also quite familiar working with the
>> WSO2 ESB and have prior experience of writing proxy services. And I am a
>> quick learner.
>>
>> I have also contributed to the peopleHR connector of WSO2 [1].
>>
>> Being quite familiar with the WSO2 connector development, I consider
>> doing the project "Native inbound and connector for IBM MQ 7.5" with the
>> WSO2 community for GSoC this year.
>>
>> Please kindly make any suggestions on how I could proceed.
>>
>>
>> [1] https://github.com/wso2/esb-connectors/pull/419
>>
>> Thank you.
>>
>> Yours sincerely,
>> Riyafa
>>
>> --
>> Riyafa Abdul Hameed
>> Undergraduate, University of Moratuwa
>>
>> Email: riyafa...@cse.mrt.ac.lk
>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>> <http://twitter.com/Riyafa1>
>>
>
>
>
> --
>
> 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/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Riyafa Abdul Hameed
Undergraduate, University of Moratuwa

Email: riyafa...@cse.mrt.ac.lk
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Native inbound and connector for IBM MQ 7.5

2016-02-09 Thread Riyafa Abdul Hameed

Dear sir,

I am a third year Computer Science and Engineering undergraduate at
University of Moratuwa. I would like to take part in GSoC 2016 with the
open source community of WSO2.

I am quite familiar with the ESB-Connectors of WSO2. I have previously
worked with the saleforce, google-spreadsheet and the peopleHR connectors
on a project that involved automating the filling of a google spreadsheet
with details from salesforce. I am also quite familiar working with the
WSO2 ESB and have prior experience of writing proxy services. And I am a
quick learner.

I have also contributed to the peopleHR connector of WSO2 [1].

Being quite familiar with the WSO2 connector development, I consider doing
the project "Native inbound and connector for IBM MQ 7.5" with the WSO2
community for GSoC this year.

Please kindly make any suggestions on how I could proceed.


[1] https://github.com/wso2/esb-connectors/pull/419

Thank you.

Yours sincerely,
Riyafa

-- 
Riyafa Abdul Hameed
Undergraduate, University of Moratuwa

Email: riyafa...@cse.mrt.ac.lk
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][Connector] Google-spreadsheet connctor: Error while building Passthrough stream

2015-12-08 Thread Riyafa Abdul Hameed

Hi Shakila,

Thank you very much. It worked without any exceptions for 500 rows.

Thanks again,
Riyafa

On Tue, Dec 8, 2015 at 9:09 PM, Shakila Sivagnanarajah <shak...@wso2.com>
wrote:

> Hi Riyafa,
>
> This may be caused because of too many requests or due to network issue.
> Some of the rows are not updated and that calls return 429 unknown status
> code. The number of failing calls also change time to time. So try with
> thread sleep in script mediator like [1].
>
> [1]  java.lang.Thread.sleep(<INTERVAL>);
>
> Thank you
>
> On Tue, Dec 8, 2015 at 8:52 PM, Shakila Sivagnanarajah <shak...@wso2.com>
> wrote:
>
>> Hi Riyafa,
>>
>> This may be caused because of too many requests or due to network issue.
>> I attach the result here. Some of the rows are not updated and that calls
>> return 429 unknown status code. The number of failing calls also change
>> time to time. So try with thread sleep in script mediator like [1].
>>
>> [1]  java.lang.Thread.sleep(5000);
>>
>> Thank you
>>
>> On Tue, Dec 8, 2015 at 10:46 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Hi Elilmatha,
>>>
>>> It is working without any exceptions for upto 300 rows.
>>>
>>> Thanks
>>>
>>> On Tue, Dec 8, 2015 at 10:44 AM, Elilmatha Sivanesan <elilma...@wso2.com
>>> > wrote:
>>>
>>>> Hi Riyafa ,
>>>>
>>>> As per the error here you are missing an end tag.
>>>>
>>>> org.apache.axiom.om.OMException:
>>>> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'I'
>>>> (code 73) in prolog; expected '<'
>>>>
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> On Tue, Dec 8, 2015 at 10:27 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>>>> wrote:
>>>>
>>>>> [+ Thulasika]
>>>>>
>>>>> On Tue, Dec 8, 2015 at 10:26 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> To be more generic I have created a proxy which fetches a column (the
>>>>>> column shouldn't be empty) and updates the same column in an iteration.
>>>>>> The  two exceptions [1] are thrown when updating more than 500 rows. The
>>>>>> proxy service is attached with this mail.
>>>>>>
>>>>>> A sample spreadsheet is at [2] and a sample call is as given below:
>>>>>>
>>>>>> {
>>>>>>
>>>>>> "accesstoken":"ya29.RAK1F3bpXOp1TxuTg7N96CPFj5d4O1p5dyTCudfXmRTSz7UWK2OzTXmbZ2-_IBfuctb-",
>>>>>> "key":"1HI9u5PuNxURVapBPSbj_aI_eM3C5NU6p8ftTyHdHW-g",
>>>>>> "workSheetId":"1",
>>>>>> "startRowNum":"1",
>>>>>> "numRows":"500",
>>>>>> "RetrievecolNum":"1"
>>>>>> }
>>>>>>
>>>>>>
>>>>>> [1]
>>>>>> https://docs.google.com/document/d/1z37FzNjo2WHlHZHDyBoMR8zP1_w_WA_qJwz4O3AxEGk/edit
>>>>>> [2]
>>>>>> https://docs.google.com/spreadsheets/d/1HI9u5PuNxURVapBPSbj_aI_eM3C5NU6p8ftTyHdHW-g/edit#gid=0
>>>>>>
>>>>>> --
>>>>>> Riyafa Abdul Hameed
>>>>>> Software Engineering intern, WSO2
>>>>>>
>>>>>> Email: riy...@wso2.com
>>>>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>>>>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>>>>>> <http://twitter.com/Riyafa1>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Riyafa Abdul Hameed
>>>>> Software Engineering intern, WSO2
>>>>>
>>>>> Email: riy...@wso2.com
>>>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>>>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>>>>> <http://twitter.com/Riyafa1>
>>>>>
>>>>> ___
>>>>> 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.
>>>>
>>>>
>>>
>>>
>>> --
>>> Riyafa Abdul Hameed
>>> Software Engineering intern, WSO2
>>>
>>> Email: riy...@wso2.com
>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>>> <http://twitter.com/Riyafa1>
>>>
>>
>>
>>
>> --
>> Shakila Sivagnanarajah
>> Associate Software Engineer
>> Mobile :+94 (0) 768 856837
>> shak...@wso2.com
>>
>
>
>
> --
> Shakila Sivagnanarajah
> Associate Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
>



-- 
Riyafa Abdul Hameed
Software Engineering intern, WSO2

Email: riy...@wso2.com
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fwd: [ESB] Exceptions thrown when using salesforce and google-spreadsheet connectors together inside an iterator of a proxy service

2015-12-07 Thread Riyafa Abdul Hameed

Hi,

As Shakila suggested I enable wire logs and obtained the log as in [1]. And
then on going through the log I have found that html content is returned by
the google spreadsheet connector. Is it safe for me to assume that the
problem is with the connector and not my code? If I cannot how can I avoid
receiving these html content to avoid the above exceptions? Also has anyone
else tried updating more 50 cells in an iterator using the google
spreadsheet connector? I am quite new, please help me debug.

The following is the html content received which was the cause for the
exception:

*http://ssl.gstatic.com/docs/common/drive_favicon1.ico>">[0xe0][0xb6][0x85][0xe0][0xb6][0xba][0xe0][0xb7][0x90][0xe0][0xb6][0xaf][0xe0][0xb7][0x94][0xe0][0xb6][0xb8]
[0xe0][0xb6][0xb4][0xe0][0xb7][0x8a][0xe2][0x80][0x8d][0xe0][0xb6][0xbb][0xe0][0xb6][0xb8][0xe0][0xb7][0x8f][0xe0][0xb6][0xb1][0xe0][0xb6][0xba]
[0xe0][0xb7][0x80][0xe0][0xb7][0x90][0xe0][0xb6][0xa9][0xe0][0xb7][0x92][0xe0][0xb6][0xba]http://fonts.googleapis.com/css?family=Product+Sans>" rel="stylesheet"
type="text/css">/* Copyright 2015 Google Inc. All Rights Reserved.
*/[\n]" {org.apache.synapse.transport.http.wire} *

*TID: [-1] [] [2015-12-07 15:25:11,394] DEBUG
{org.apache.synapse.transport.http.wire} - >>
".goog-inline-block{position:relative;display:-moz-inline-box;display:inline-block}*
html .goog-inline-block{display:inline}*:first-child+html
.goog-inline-block{display:inline}#drive-logo{margin:18px
0;position:absolute;white-space:nowrap}.docs-drivelogo-img{background-image:url('//ssl.gstatic.com/images/branding/googlelogo/1x/googlelogo_color_116x41dp.png');background-size:116px
41px
<<a  rel="nofollow" href="http://ssl.gstatic.com/images/branding/googlelogo/1x/googlelogo_color_116x41dp.png">http://ssl.gstatic.com/images/branding/googlelogo/1x/googlelogo_color_116x41dp.png</a>');background-size:116px41px>;display:inline-block;height:41px;vertical-align:bottom;width:116px}.docs-drivelogo-text{color:#000;display:inline-block;opacity:0.54;text-decoration:none;font-family:'Product
Sans',Arial,Helvetica,sans-serif;font-size:32px;text-rendering:optimizeLegibility;position:relative;top:-6px;left:-7px;-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}@media
(-webkit-min-device-pixel-ratio:1.5),(min-resolution:144dpi){.docs-drivelogo-img{background-image:url('//ssl.gstatic.com/images/branding/googlelogo/2x/googlelogo_color_116x41dp.png')}
<<a  rel="nofollow" href="http://ssl.gstatic.com/images/branding/googlelogo/2x/googlelogo_color_116x41dp.png">http://ssl.gstatic.com/images/branding/googlelogo/2x/googlelogo_color_116x41dp.png</a>')%7D>}body {background-color: #fff; font-family:
Arial,sans-serif; font-size: 13px; margin: 0; padding: 0;}a, a:link,
a:visited {color: #112ABB;}.errorMessage
{font-size: 12pt; font-weight: bold; line-height:
150%;}Drive[0xe0][0xb6][0xb1][0xe0][0xb7][0x92][0xe0][0xb6][0xba][0xe0][0xb6][0xb8][0xe0][0xb6][0xba][0xe0][0xb7][0x92],
[0xe0][0xb6][0xb8][0xe0][0xb7][0x99][0xe0][0xb6][0xb8]
[0xe0][0xb6][0x9c][0xe0][0xb7][0x9c][0xe0][0xb6][0xb1][0xe0][0xb7][0x94][0xe0][0xb7][0x80]
[0xe0][0xb6][0x87][0xe0][0xb6][0xad][0xe0][0xb7][0x8a][0xe0][0xb6][0xad][0xe0][0xb6][0xa7][0xe0][0xb6][0xb8]
[0xe0][0xb6][0xa2][0xe0][0xb6][0xb1][0xe0][0xb6][0xb4][0xe0][0xb7][0x8a][0xe2][0x80][0x8d][0xe0][0xb6][0xbb][0xe0][0xb7][0x92][0xe0][0xb6][0xba][0xe0][0xb6][0xba][0xe0][0xb7][0x92]!
[0xe0][0xb6][0xb4][0xe0][0xb7][0x92][0xe0][0xb6][0xbb][0xe0][0xb7][0x92][0xe0][0xb7][0x83]
[0xe0][0xb6][0x89][0xe0][0xb7][0x80][0xe0][0xb6][0xad][0xe0][0xb7][0x8a]
[0xe0][0xb7][0x80][0xe0][0xb7][0x99][0xe0][0xb6][0xb1][0xe0][0xb6][0x9a][0xe0][0xb6][0xb1][0xe0][0xb7][0x8a]
[0xe0][0xb7][0x83][0xe0][0xb6][0xb8][0xe0][0xb7][0x84][0xe0][0xb6][0xbb]
[0xe0][0xb6][0xb8][0xe0][0xb7][0x99][0xe0][0xb7][0x80][0xe0][0xb6][0xbd][0xe0][0xb6][0xb8][0xe0][0xb7][0x8a]
[0xe0][0xb6][0xb1][0xe0][0xb7][0x90][0xe0][0xb6][0xad][0xe0][0xb7][0x92]
[0xe0][0xb7][0x80][0xe0][0xb7][0x92][0xe0][0xb6][0xba]
[0xe0][0xb7][0x84][0xe0][0xb7][0x90][0xe0][0xb6][0x9a]. [0xe0][0xb6][0xb1][0xe0][0xb7][0x90][0xe0][0xb7][0x80][0xe0][0xb6][0xad]
[0xe0][0xb6][0x8b][0xe0][0xb6][0xad][0xe0][0xb7][0x8a][0xe0][0xb7][0x83][0xe0][0xb7][0x8f][0xe0][0xb7][0x84]
[0xe0][0xb6][0x9a][0xe0][0xb6][0xbb][0xe0][0xb6][0xb1][0xe0][0xb7][0x8a][0xe0][0xb6][0xb1]*



[1] https://drive.google.com/open?id=0BxOnD8A85gZoOWg2NHRtbUZmLVE

Thank you.


>> On Mon, Dec 7, 2015 at 2:21 PM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> My use case is I get the column of project keys from a
>>> google-spreadsheet and iterate through the project keys. Using the project
>>> key I query the salesforce  using the salesforce connector and obtain the
>>> invoice number. Then using the invoice number I find the invoice

Re: [Dev] [ESB] Exceptions thrown when using salesforce and google-spreadsheet connectors together inside an iterator of a proxy service

2015-12-07 Thread Riyafa Abdul Hameed

tElement(StAXOMBuilder.java:570)
*

* at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
*

* at
org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:149)
*

* at
org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:133)
*

* at
org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:98)
*

* at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:400)
*

* at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
*

* at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) *

* at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
*

* at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
*

* at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
*

* at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
*

* at java.lang.Thread.run(Thread.java:745) *

*Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
character 'I' (code 73) in prolog; expected '<' *

*at [row,col {unknown-source}]: [1,1] *

* at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:639) *

* at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2052)
*

* at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1134) *

* at
org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
*

* at
org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
*

* at
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
*

* at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
*

* ... 14 more *


Thank you,
Riyafa

[1]
https://docs.google.com/spreadsheets/d/1YsXYQsaBbuOIgUzF-bflZceEPT-4_3J6PNQWp1UjYqc/edit#gid=147342676=A1

On Mon, Dec 7, 2015 at 1:15 PM, Malaka Silva <mal...@wso2.com> wrote:

> Riyafa seems like a builder error. Can you try enabling wire logs and
> analyse the response from the APIs.
>
> Also what is your use case?
>
> On Mon, Dec 7, 2015 at 12:08 PM, Riyafa Abdul Hameed <riy...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I have a proxy service which I have attached with the mail which makes
>> several one call to the salesforce api using the salesforce connector and
>> two calls to the google spreadsheet api using the google-spreadsheet
>> connector in each iteration. When the number of rows I call (or the number
>> of iterations) increase beyond 35 the proxy service starts throwing the
>> following two exceptions:
>>
>>
>> *[2015-12-07 11:22:03,785] ERROR - RelayUtils Error while building
>> Passthrough stream *
>>
>> *org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException:
>> DOCTYPE is not allowed *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:109)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:570)
>> *
>>
>> * at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:566)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:149)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:133)
>> *
>>
>> * at
>> org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:98)
>> *
>>
>> * at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:400)
>> *
>>
>> * at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>> *
>>
>> * at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) *
>>
>> * at
>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
>> *
>>
>> * at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> *
>>
>> * at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> *
>>
>> * at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> *
>>
>> * at java.lang.Thread.run(Thread.java:745) *
>>
>> *Cause

[Dev] [ESB][Connector] Google-spreadsheet connctor: Error while building Passthrough stream

2015-12-07 Thread Riyafa Abdul Hameed

Hi,

To be more generic I have created a proxy which fetches a column (the
column shouldn't be empty) and updates the same column in an iteration.
The  two exceptions [1] are thrown when updating more than 500 rows. The
proxy service is attached with this mail.

A sample spreadsheet is at [2] and a sample call is as given below:

{

"accesstoken":"ya29.RAK1F3bpXOp1TxuTg7N96CPFj5d4O1p5dyTCudfXmRTSz7UWK2OzTXmbZ2-_IBfuctb-",
"key":"1HI9u5PuNxURVapBPSbj_aI_eM3C5NU6p8ftTyHdHW-g",
"workSheetId":"1",
"startRowNum":"1",
"numRows":"500",
"RetrievecolNum":"1"
}


[1]
https://docs.google.com/document/d/1z37FzNjo2WHlHZHDyBoMR8zP1_w_WA_qJwz4O3AxEGk/edit
[2]
https://docs.google.com/spreadsheets/d/1HI9u5PuNxURVapBPSbj_aI_eM3C5NU6p8ftTyHdHW-g/edit#gid=0

-- 
Riyafa Abdul Hameed
Software Engineering intern, WSO2

Email: riy...@wso2.com
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>

http://ws.apache.org/ns/synapse;
   name="testUpdate"
   transports="http https"
   startOnLoad="true"
   trace="disable">
   
   
  
 
 
 
 
 
 
{$ctx:accesstoken1}
 
 
{$ctx:sheetKey1}
{$ctx:sheetId1}
{$ctx:rowNum1}
{$ctx:rowss1}
{$ctx:retrieveColNum1}
{$ctx:retrieveColNum1}
 
 
 http://www.w3.org/2005/Atom;
  id="iterator1"
  expression="//abc:entry"
  description="">

   http://schemas.google.com/spreadsheets/2006;
name="rowNum"
expression="//gs:cell/@row"
scope="default"
type="STRING"/>
  
  
  var cellRef=mc.getProperty("cellRef");
  	var x=cellRef.split("/");
  	var n=x.length-1;
  	cellRef=x[n]; 
  	mc.setProperty("cellVersion",cellRef)
  
  
  
  
  
  
  
  
  
  
 {$ctx:accesstoken}
  
  
 {$ctx:key}
 {$ctx:id}
 {$ctx:cellId}
 {$ctx:inputValue}
 {$ctx:row}
 {$ctx:col}
 {$ctx:cellV}
  
  
   

 
  
   
   true

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

Re: [Dev] [ESB][Connector] Google-spreadsheet connctor: Error while building Passthrough stream

2015-12-07 Thread Riyafa Abdul Hameed

[+ Thulasika]

On Tue, Dec 8, 2015 at 10:26 AM, Riyafa Abdul Hameed <riy...@wso2.com>
wrote:

> Hi,
>
> To be more generic I have created a proxy which fetches a column (the
> column shouldn't be empty) and updates the same column in an iteration.
> The  two exceptions [1] are thrown when updating more than 500 rows. The
> proxy service is attached with this mail.
>
> A sample spreadsheet is at [2] and a sample call is as given below:
>
> {
>
> "accesstoken":"ya29.RAK1F3bpXOp1TxuTg7N96CPFj5d4O1p5dyTCudfXmRTSz7UWK2OzTXmbZ2-_IBfuctb-",
> "key":"1HI9u5PuNxURVapBPSbj_aI_eM3C5NU6p8ftTyHdHW-g",
> "workSheetId":"1",
> "startRowNum":"1",
> "numRows":"500",
> "RetrievecolNum":"1"
> }
>
>
> [1]
> https://docs.google.com/document/d/1z37FzNjo2WHlHZHDyBoMR8zP1_w_WA_qJwz4O3AxEGk/edit
> [2]
> https://docs.google.com/spreadsheets/d/1HI9u5PuNxURVapBPSbj_aI_eM3C5NU6p8ftTyHdHW-g/edit#gid=0
>
> --
> Riyafa Abdul Hameed
> Software Engineering intern, WSO2
>
> Email: riy...@wso2.com
> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
> <http://twitter.com/Riyafa1>
>



-- 
Riyafa Abdul Hameed
Software Engineering intern, WSO2

Email: riy...@wso2.com
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][Connector] Google-spreadsheet connctor: Error while building Passthrough stream

2015-12-07 Thread Riyafa Abdul Hameed

Hi Elilmatha,

It is working without any exceptions for upto 300 rows.

Thanks

On Tue, Dec 8, 2015 at 10:44 AM, Elilmatha Sivanesan <elilma...@wso2.com>
wrote:

> Hi Riyafa ,
>
> As per the error here you are missing an end tag.
>
> org.apache.axiom.om.OMException:
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'I'
> (code 73) in prolog; expected '<'
>
>
> Thanks.
>
>
> On Tue, Dec 8, 2015 at 10:27 AM, Riyafa Abdul Hameed <riy...@wso2.com>
> wrote:
>
>> [+ Thulasika]
>>
>> On Tue, Dec 8, 2015 at 10:26 AM, Riyafa Abdul Hameed <riy...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> To be more generic I have created a proxy which fetches a column (the
>>> column shouldn't be empty) and updates the same column in an iteration.
>>> The  two exceptions [1] are thrown when updating more than 500 rows. The
>>> proxy service is attached with this mail.
>>>
>>> A sample spreadsheet is at [2] and a sample call is as given below:
>>>
>>> {
>>>
>>> "accesstoken":"ya29.RAK1F3bpXOp1TxuTg7N96CPFj5d4O1p5dyTCudfXmRTSz7UWK2OzTXmbZ2-_IBfuctb-",
>>> "key":"1HI9u5PuNxURVapBPSbj_aI_eM3C5NU6p8ftTyHdHW-g",
>>> "workSheetId":"1",
>>> "startRowNum":"1",
>>> "numRows":"500",
>>> "RetrievecolNum":"1"
>>> }
>>>
>>>
>>> [1]
>>> https://docs.google.com/document/d/1z37FzNjo2WHlHZHDyBoMR8zP1_w_WA_qJwz4O3AxEGk/edit
>>> [2]
>>> https://docs.google.com/spreadsheets/d/1HI9u5PuNxURVapBPSbj_aI_eM3C5NU6p8ftTyHdHW-g/edit#gid=0
>>>
>>> --
>>> Riyafa Abdul Hameed
>>> Software Engineering intern, WSO2
>>>
>>> Email: riy...@wso2.com
>>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>>> <http://twitter.com/Riyafa1>
>>>
>>
>>
>>
>> --
>> Riyafa Abdul Hameed
>> Software Engineering intern, WSO2
>>
>> Email: riy...@wso2.com
>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>> <http://twitter.com/Riyafa1>
>>
>> ___
>> 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.
>
>


-- 
Riyafa Abdul Hameed
Software Engineering intern, WSO2

Email: riy...@wso2.com
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] subscribe

2015-12-06 Thread Riyafa Abdul Hameed

-- 
Riyafa Abdul Hameed
Software Engineering intern, WSO2

Email: riy...@wso2.com
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Exceptions thrown when using salesforce and google-spreadsheet connectors together inside an iterator of a proxy service

2015-12-06 Thread Riyafa Abdul Hameed

at any problem
   because of the properties being out of context inside the proxy is resolved.
   - Increase the http.socket.timeout in the
   wso2esb-4.9.0/repository/conf/passthru-http.properties file to a quite
   large value
   - Increase the synapse.global_timeout_interval in
   wso2esb-4.9.0/repository/conf/synapse.properties to 60.
   - Run the two iterations in the proxies separately which made it
   possible to run up to 150 rows without any exceptions.

The exceptions sometimes seem to reduce when  http.socket.timeout was
increased, but still continue to appear.

What could be done to resolve this issue? Please help.


Thank you,

Riyafa

-- 
Riyafa Abdul Hameed
Software Engineering intern, WSO2

Email: riy...@wso2.com
Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
<http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
<http://twitter.com/Riyafa1>

http://ws.apache.org/ns/synapse;>
  

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
{$ctx:accesstoken1}
  
  
{$ctx:sheetKey1}
{$ctx:sheetId1}
{$ctx:rowNum1}
{$ctx:rowss1}
{$ctx:retrieveColNum1}
{$ctx:retrieveColNum1}
  
  
  http://www.w3.org/2005/Atom;>

  


http://schemas.google.com/spreadsheets/2006"/>

<![CDATA[var key = mc.getPayloadXML()..*::content.toString();
  		key=key.split("-")[0];
  		mc.setProperty("projKey",key);]]>



  1
  {$ctx:query1}


<![CDATA[var date=mc.getPayloadXML()..*::CreatedDate.toString();
  	var invoiceNumber=mc.getPayloadXML()..*::Invoice_Number__c.toString()
  	date=date.substring(0, 4);
  	date=parseInt(date, 10);
  	var invoiceVal;
  	if(date>=2015){
  		invoiceVal=invoiceNumber.substring(4, 7);
  		invoiceVal=parseInt(invoiceVal, 10);
  		if(invoiceVal<300){ //2015001 to 2015299
  			mc.setProperty("invoiceFrom", "LK");
  		}else if(invoiceVal<600){//2015300 to 2015599
  			mc.setProperty("invoiceFrom", "UK");  			
  		}else if(invoiceVal<1000){// 2015600 to ..
  			mc.setProperty("invoiceFrom", "Inc");  		
  		}else{
  			mc.setProperty("invoiceFrom", "No Invoice Number");  			
  		}
  	}else if(date<2015){
  		invoiceVal=invoiceNumber.substring(2, 4);
  		invoiceVal=parseInt(invoiceVal, 10);
  		if(invoiceNumber.length>6){
  			mc.setProperty("invoiceFrom", "Inc"); 
  		}else if(invoiceVal<30){
  			mc.setProperty("invoiceFrom", "LK");
  		}else if(invoiceVal<60){
  			mc.setProperty("invoiceFrom", "UK");  			
  		}else if(invoiceVal<100){
  			mc.setProperty("invoiceFrom", "Inc");  		
  		}else{
  			mc.setProperty("invoiceFrom", "No Invoice Number");  			
  		}
  	}else{
  		mc.setProperty("invoiceFrom", "No records found"); 
  	}]]>





  {$ctx:accesstoken}


  {$ctx:sheetKey}
  {$ctx:sheetId}
  {$ctx:updateCellId}


<![CDATA[var cellRef=mc.getProperty("cellRef");
  	var x=cellRef.split("/");
  	var n=x.length-1;
  	cellRef=x[n]; 
  	mc.setProperty("cellVersion",cellRef)]]>











  {$ctx:accesstoken}


  {$ctx:key}
  {$ctx:id}
  {$ctx:cellId}
  {$ctx:inputValue}
  {$ctx:row}
  {$ctx:col}
  {$ctx:cellV}

  

  
  
  
  <![CDATA[var x=parseInt(mc.getProperty("retrieveColNum1"),10)-1;
	mc.setProperty("retrieveColNum1",x+"");]]>
  
{$ctx:accesstoken1}
  
  
{$ctx:sheetKey1}
{$ctx:sheetId1}
{$ctx:rowNum1}
{$ctx:rowss1}
{$ctx:retrieveColNum1}
{$ctx:retrieveColNum1}
  
  
  http://www.w3.org/2005/Atom;>

  

<![CDATA[var str = mc.getPayloadXML()..*::content.toString();
var suffix="Evaluation Support";

			if(str.indexOf(suffix, str.l

[Dev] GSoC 2016

2015-10-23 Thread Riyafa Abdul Hameed

*Hi,I am a third year undergraduate at University of Moratuwa, Sri Lanka. I
am keen to participate in GSoC 2016 and am interested in Middleware related
projects. Since ideas for GSoC 2016 have not yet been posted, now I would
like to familiarize myself with the WSO2 platform. Please be kind enough to
suggest where I can start and how to proceed so that I will be quite
familiar with WSO2 products before next GSoC.I went through some of the
projects here:https://docs.wso2.com/display/GSoC/Project+Proposals+for+2015
<https://docs.wso2.com/display/GSoC/Project+Proposals+for+2015>but I am not
sure where to start.Also if I am given some tasks to complete I would be
glad to proceed.Thank you.Yours,Riyafa Abdul Hameed.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

53 matches

Mail list logo