[Dev] [GSoc-2015] Proposal 10: Google Wallet based Billing System for WSO2 Private PaaS

2015-03-05 Thread Manil Liyanage
Hi All,

My name is Manil Liyanage. I'm currently following a Masters in the field
of Information Technology at University of Colombo School of Computing.

I'm interested in doing $subject. I have previously contributed or done
projects such as WSO2 ESB connectors for soundcloud and yammer. I'm really
interested in doing projects related to web services. I also have sent a
mail in my interest to Proposal 11. I believe that will not conflict with
my interest in this proposal. I'm familiar with JAX-RS and WSO2 products.

I read the basic guild lines given to others for the proposals for
$subject. Please let me how can I can contribute more towards doing [1]. Do
I need to get starting writing a proposal for [1]?

[1]
https://docs.wso2.com/display/GSoC/Project+Proposals+for+2015#ProjectProposalsfor2015-Proposal10:GoogleWalletbasedBillingSystemforWSO2PrivatePaaS

Thank You,
Manil Liyanage
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [GSoC-2015] Proposal 11: Recommendation Solution for WSO2 Machine Learner

2015-03-04 Thread Manil Liyanage
Hi Nirmal,

Sure, I'll look in those algorithms as my first step and try working out
functionality of ML. Thanks again.

Regards,
Manil Liyanage

On Wed, Mar 4, 2015 at 7:07 PM, Nirmal Fernando  wrote:

> Yes, and for the recommendation part, you should use ML. In WSO2 ML, we
> currently do not have the support for recommendation algorithms. We use
> Apache Spark's MLLib's algorithm implementations. First step would be to
> research into the recommendation algorithms of MLLib and play with those
> and understand the nature of those algorithms.
>
> Do not hesitate to ask any questions you may run into.
>
> Good luck!
>
> On Wed, Mar 4, 2015 at 6:14 PM,  wrote:
>
>> Hi Nirmal,
>>
>> Thank you for looking into my request. I basically took a look at the
>> proposal. If we take it simply, its an extension that can be added to
>> website that would capture trends and hits and recommend it with other
>> items  to any other context. Apart from that i do not have any major
>> questions at the moment. Meanwhile I will do a in depth analysis on it.
>>
>> Thank you,
>> Manil Liyanage
>>
>> On 2015 මාර්තු 4, at ප.ව. 6.05, Nirmal Fernando  wrote:
>>
>> Hi Manil,
>>
>> Thanks for your interest on the project. Do you have any specific
>> questions that we could answer?
>>
>> PS: I'll share a slide deck done by Srinath on WSO2 Machine Learner, with
>> you.
>>
>> On Wed, Mar 4, 2015 at 5:58 PM,  wrote:
>>
>>> Hi All,
>>>
>>> My name is Manil Liyanage. I'm currently following a Masters in the
>>> field of Information Technology at University of Colombo School of
>>> Computing.
>>>
>>> I'm interested in doing $subject. i have previously contributed or done
>>> projects such as WSO2 ESB connectors for soundcloud and yammer. I'm really
>>> interested in doing projects related to web services. Im familiar with
>>> JAX-RS mostly.  please let me how can I can contribute more towards [1].
>>>
>>> Thank you,
>>> Manil Liyanage
>>>
>>>
>>> [1]
>>> https://docs.wso2.com/plugins/servlet/mobile#ProjectProposalsfor2015-Proposal11:RecommendationSolutionforWSO2MachineLearner
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 App Cloud's Repositories in the GitBilt missing

2014-09-28 Thread Manil Liyanage
Hi Amila,

The repos are there now. Thanks for the fix and the help.

Regards,
Manil

On Sun, Sep 28, 2014 at 4:44 PM, Amila Maha Arachchi 
wrote:

> Hi Manil,
>
> Can you check now. There was an issue which occurred due to a problem with
> our infrastructure provider. We fixed it.
>
> Regards,
> Amila.
>
> On Sun, Sep 28, 2014 at 4:28 PM, Amila Maha Arachchi 
> wrote:
>
>> Hi Manil,
>>
>> We'll check and get back to you.
>>
>> On Sun, Sep 28, 2014 at 3:08 PM, Manil Liyanage 
>> wrote:
>>
>>> Hi All,
>>>
>>> When I tried to clone my repository is says its not found. I tried to
>>> clone the repository few days ago, it said unauthorized access. When i
>>> checked the wso2 app cloud it was under maintenance and at that time when I
>>> logged into gitbilt my repo was there. But when I check it now my repo is
>>> not there. Is there a reason for this to happen? link of my repo is
>>> https://git.cloud.wso2.com/git/manil8056/devicemanagementser.git. All
>>> of the repositories are missing. Its like all my work is gone. Could
>>> someone help me on this?
>>>
>>> Thanks,
>>> Manil
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Amila Maharachchi*
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446
>>
>>
>
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] WSO2 App Cloud's Repositories in the GitBilt missing

2014-09-28 Thread Manil Liyanage
Hi All,

When I tried to clone my repository is says its not found. I tried to clone
the repository few days ago, it said unauthorized access. When i checked
the wso2 app cloud it was under maintenance and at that time when I logged
into gitbilt my repo was there. But when I check it now my repo is not
there. Is there a reason for this to happen? link of my repo is
https://git.cloud.wso2.com/git/manil8056/devicemanagementser.git. All of
the repositories are missing. Its like all my work is gone. Could someone
help me on this?

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


[Dev] ESB Connector Soundcloud | Upload a soundfile from a proxy- API cannot recognize as a file

2014-07-02 Thread Manil Liyanage
Hi All,

I'm trying to upload a song file to the soundcloud using its API. When i
upload it using curl [1] , i was able to upload it. But when I upload it
using a proxy sequence[2], it sends a error message from the API saying
cannot recognize is its as a soundfile[3].  Please let me know a solution
for this.

[1]

curl -X POST "https://api.soundcloud.com/tracks.json"; \
-F 'oauth_token=mytoken' \
-F 'track[asset_data]=@ola.mp3' \
-F 'track[title]=title' \
-F 'track[sharing]=public'



[2] - I have disable chunking because it gives a error message 411, as a
solution for it only i have used it.

http://ws.apache.org/ns/synapse";
   name="uploadtest"
   transports="https,http"
   statistics="disable"
   trace="disable"
   startOnLoad="true">
   
  
 
 

   https://api.soundcloud.com/tracks.json?oauth_token=mytoken&track[title]=testsong&track[asset_data]=/home/manil/ola.mp3"/>

 
  
   
   



[3]

{"errors":[{"error_message":"Couldn't upload that
sound."},{"error_message":"Couldn't upload that file, sure they're
valid soundfiles?"}]}



Thank You,
Manil Liyanage
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] ESB Proxy | DOCTYPE Return not allowed

2014-06-20 Thread Manil Liyanage
Hi Vijayaratha,

Using a endpoint as you mentioned solved the issue. Really appreciate and
thanks your help. +1



On Fri, Jun 20, 2014 at 3:12 PM, Vijayaratha Vijayasingam 
wrote:

> You can try with RESTAPI ..i believe you try to POST a message..
>
>
> On 20 June 2014 02:36, Manil Liyanage  wrote:
>
>> Hi,
>>
>> In soundcloud, I'm trying to add a connection(twitter service) to my
>> account, the URL is given below[1] and the message are passed from the url.
>> There is no body been sent. Basically the below link works when invoked
>> through the rest client extension in firefox. It will send me back the
>> authorized url in a xml body[2]
>>
>> POST
>> [1]
>>
>> https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud
>>  
>> <https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud>
>>
>>
>>
>> [2]
>>
>> 
>> 
>>
>> https://soundcloud.com/connect/twitter/new?external_identity%5Bpost_favorites%5D=false&external_identity%5Bpost_tracks%5D=true&external_identity%5Buser_id%5D=99675972&redirect_uri=https%3A%2F%2Fwww.example.com%2Fsoundcloud&signature=3046ec675f5a430c8ff7c617ac6a38e8
>> 
>> 
>>
>>
>> On Fri, Jun 20, 2014 at 2:53 PM, Vijayaratha Vijayasingam <
>> rat...@wso2.com> wrote:
>>
>>> Are you posing empty message?
>>> What is the endpoint uRL you try to call?
>>> Do you want to send back the empty message to client?
>>> What is the scenario you are trying?
>>>
>>>
>>> On 19 June 2014 05:41, Manil Liyanage  wrote:
>>>
>>>> Hi All,
>>>>
>>>> I Use the following code to send a post request to soundcloud API. In
>>>> rest client widget in firefox above url works. But when I do this from the
>>>> ESB proxy I get an error which I have shown at last.
>>>>
>>>> I tried adding  after the  tag and I tried
>>>> adding >>> name="ApplicationXMLBuilder.allowDTD">true after the
>>>>  tag.
>>>>
>>>> It still gives me the same error. Please let me know a solution for
>>>> this. Thanks in Advance.
>>>>
>>>> Regards,
>>>> Manil Liyanage
>>>>
>>>> http://ws.apache.org/ns/synapse";
>>>>
>>>>
>>>>
>>>>
>>>>name="soundcloud"
>>>>transports="https,http"
>>>>statistics="disable"
>>>>trace="disable"
>>>>startOnLoad="true">
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>   
>>>>  >>> action="remove"/>
>>>>  
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>>>>   
>>>>
>>>>
>>>>
>>>>   
>>>>
>>>>
>>>> 
>>>> 
>>>>  
>>>>  
>>>> 
>>>>>>>
>>>>
>>>>
>>>>
>>>>  
>>>> uri-template="https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud
>>>>  
>>>> <https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud>"/>
>>>>
>>>>
>>>>
>>>>
>>>> 
>>>>  
>>>>  >>> scope="axis2"/>
>>>>  
>>>>   
>>>>
>>>>
>>>>
>>>>
>>>>   
>>>>   
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>> ERROR MESSAGE IN ESB CONSOLE
>>>>
>>>> [2014-06-19 18:09:43,354] ERROR - RelayUtils Error while building 
>>>> Passthrough stream
>>>>
>>>>
>>>>

Re: [Dev] ESB Proxy | DOCTYPE Return not allowed

2014-06-20 Thread Manil Liyanage
Hi,

In soundcloud, I'm trying to add a connection(twitter service) to my
account, the URL is given below[1] and the message are passed from the url.
There is no body been sent. Basically the below link works when invoked
through the rest client extension in firefox. It will send me back the
authorized url in a xml body[2]

POST
[1]

https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud
<https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud>



[2]



https://soundcloud.com/connect/twitter/new?external_identity%5Bpost_favorites%5D=false&external_identity%5Bpost_tracks%5D=true&external_identity%5Buser_id%5D=99675972&redirect_uri=https%3A%2F%2Fwww.example.com%2Fsoundcloud&signature=3046ec675f5a430c8ff7c617ac6a38e8




On Fri, Jun 20, 2014 at 2:53 PM, Vijayaratha Vijayasingam 
wrote:

> Are you posing empty message?
> What is the endpoint uRL you try to call?
> Do you want to send back the empty message to client?
> What is the scenario you are trying?
>
>
> On 19 June 2014 05:41, Manil Liyanage  wrote:
>
>> Hi All,
>>
>> I Use the following code to send a post request to soundcloud API. In
>> rest client widget in firefox above url works. But when I do this from the
>> ESB proxy I get an error which I have shown at last.
>>
>> I tried adding  after the  tag and I tried
>> adding true 
>> after
>> the  tag.
>>
>> It still gives me the same error. Please let me know a solution for
>> this. Thanks in Advance.
>>
>> Regards,
>> Manil Liyanage
>>
>> http://ws.apache.org/ns/synapse";
>>
>>
>>name="soundcloud"
>>transports="https,http"
>>statistics="disable"
>>trace="disable"
>>startOnLoad="true">
>>
>>
>>
>>   
>>  
>>  
>> 
>>
>>
>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>>   
>>
>>   
>>
>>
>> 
>> 
>>  
>>  
>> 
>>>
>>
>>  
>> uri-template="https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud
>>  
>> <https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud>"/>
>>
>>
>> 
>>  
>>  
>>  
>>   
>>
>>
>>   
>>   
>>
>>
>> 
>>
>>
>> ERROR MESSAGE IN ESB CONSOLE
>>
>> [2014-06-19 18:09:43,354] ERROR - RelayUtils Error while building 
>> Passthrough stream
>>
>>
>> org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: 
>> ParseError at [row,col]:[3,68]
>> Message: DOCTYPE is not allowed
>>  at 
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
>>
>>
>>  at 
>> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:204)
>>  at 
>> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:154)
>>  at 
>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXSOAPModelBuilder(AbstractOMMetaFactory.java:73)
>>
>>
>>  at 
>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createSOAPModelBuilder(AbstractOMMetaFactory.java:79)
>>  at 
>> org.apache.axiom.om.OMXMLBuilderFactory.createSOAPModelBuilder(OMXMLBuilderFactory.java:196)
>>  at 
>> org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:55)
>>
>>
>>  at 
>> org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:138)
>>  at 
>> org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:107)
>>  at 
>> org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:82)
>>
>>
>>  at 
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:68)
>>  at 
>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:239)
>>  

Re: [Dev] ESB Proxy | DOCTYPE Return not allowed

2014-06-20 Thread Manil Liyanage
Hi All,

The root cause error for this was Transport error: 411 Error: Length , so
as a solution I added the property . When i add this property, There was another
error to this as following.

[2014-06-20 14:23:03,414] ERROR - TargetHandler Unexpected error: The
parser is already consumed!
java.lang.UnsupportedOperationException: The parser is already consumed!
at 
org.apache.axiom.om.impl.llom.OMContainerHelper.getXMLStreamReader(OMContainerHelper.java:58)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.getXMLStreamReader(OMElementImpl.java:736)
at 
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:547)
at 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:249)
at 
org.apache.axiom.om.impl.llom.OMSerializableImpl.serializeAndConsume(OMSerializableImpl.java:193)
at 
org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:74)
at 
org.apache.synapse.transport.passthru.TargetRequest.processChunking(TargetRequest.java:331)
at 
org.apache.synapse.transport.passthru.TargetRequest.start(TargetRequest.java:267)
at 
org.apache.synapse.transport.passthru.TargetHandler.requestReady(TargetHandler.java:141)
at 
org.apache.http.impl.nio.DefaultNHttpClientConnection.produceOutput(DefaultNHttpClientConnection.java:244)
at 
org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection.produceOutput(LoggingNHttpClientConnection.java:114)
at 
org.apache.synapse.transport.passthru.ClientIODispatch.onOutputReady(ClientIODispatch.java:88)
at 
org.apache.synapse.transport.passthru.ClientIODispatch.onOutputReady(ClientIODispatch.java:41)
at 
org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:148)
at 
org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:181)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:346)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
at 
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
at 
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
at java.lang.Thread.run(Thread.java:744)
[2014-06-20 14:23:03,417]  WARN - PassThroughHttpSSLSender System may
be unstable: HTTPS ConnectingIOReactor encountered a runtime exception
: null
java.lang.NullPointerException
at 
org.apache.synapse.transport.passthru.TargetHandler.logIOException(TargetHandler.java:426)
at 
org.apache.synapse.transport.passthru.TargetHandler.exception(TargetHandler.java:569)
at 
org.apache.synapse.transport.passthru.ClientIODispatch.onException(ClientIODispatch.java:78)
at 
org.apache.synapse.transport.passthru.ClientIODispatch.onException(ClientIODispatch.java:41)
at 
org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:152)
at 
org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:181)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:346)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
at 
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
at 
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
at java.lang.Thread.run(Thread.java:744)




On Thu, Jun 19, 2014 at 6:11 PM, Manil Liyanage 
wrote:

> Hi All,
>
> I Use the following code to send a post request to soundcloud API. In rest
> client widget in firefox above url works. But when I do this from the ESB
> proxy I get an error which I have shown at last.
>
> I tried adding  after the  tag and I tried
> adding true after
> the  tag.
>
> It still gives me the same error. Please let me know a solution for this.
> Thanks in Advance.
>
> Regards,
> Manil Liyanage
>
> http://ws.apache.org/ns/synapse";
>
>name="soundcloud"
>transports="https,http"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>
>   
>  
>  
> 
>
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
>   
>
>
> 
> 
>  

[Dev] ESB Proxy | DOCTYPE Return not allowed

2014-06-19 Thread Manil Liyanage
Hi All,

I Use the following code to send a post request to soundcloud API. In rest
client widget in firefox above url works. But when I do this from the ESB
proxy I get an error which I have shown at last.

I tried adding  after the  tag and I tried
adding true after the 
tag.

It still gives me the same error. Please let me know a solution for this.
Thanks in Advance.

Regards,
Manil Liyanage

http://ws.apache.org/ns/synapse";
   name="soundcloud"
   transports="https,http"
   statistics="disable"
   trace="disable"
   startOnLoad="true">
   
  
 
 

   http://schemas.xmlsoap.org/soap/envelope/";>
  
  
   


 
 

   https://api.soundcloud.com/me/connections.xml?oauth_token=MYTOKEN&service=twitter&redirect_uri=https://www.example.com/soundcloud"/>

 
 
 
  
  
  
   
   



ERROR MESSAGE IN ESB CONSOLE

[2014-06-19 18:09:43,354] ERROR - RelayUtils Error while building
Passthrough stream
org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException:
ParseError at [row,col]:[3,68]
Message: DOCTYPE is not allowed
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:204)
at 
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:154)
at 
org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXSOAPModelBuilder(AbstractOMMetaFactory.java:73)
at 
org.apache.axiom.om.impl.AbstractOMMetaFactory.createSOAPModelBuilder(AbstractOMMetaFactory.java:79)
at 
org.apache.axiom.om.OMXMLBuilderFactory.createSOAPModelBuilder(OMXMLBuilderFactory.java:196)
at 
org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:55)
at 
org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:138)
at 
org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:107)
at 
org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:82)
at 
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:68)
at 
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:239)
at 
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:556)
at 
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:198)
at 
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:488)
at 
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:170)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at 
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:225)
at 
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,68]
Message: DOCTYPE is not allowed
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] ESB Connector | Synapse configuration for REST API

2014-06-13 Thread Manil Liyanage
Hi All,


I got this fixed. Thanks


On Fri, Jun 13, 2014 at 3:19 PM, Manil Liyanage 
wrote:

> Hi All,
>
> I'm currently writing a synapse configuration for a connector and its a
> REST base api which send responses in json format as in the attachment.
>
> My question is that how to put the response recieved on json to the
> payload body. code of the configuration is shown below. I have hardcoded
> for the request url for testing purpose. Please help me on this.
>
> http://ws.apache.org/ns/synapse"; name="getUser">
> 
>  
> **
> * *
> *  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> <http://schemas.xmlsoap.org/soap/envelope/>">*
> * *
> * *
> * *
> * *
> * *
> * *
>  
> 
>  **
> *  *
> uri-template="http://api.soundcloud.com/users/3207.json?client_id=21fded24c32c2d9b0316971643d2f75f
> <http://api.soundcloud.com/users/3207.json?client_id=21fded24c32c2d9b0316971643d2f75f>"
> />*
> * *
> 
> 
> 
>
>
> Thanks,
> Manil Liyanage
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] ESB Connector | Synapse configuration for REST API

2014-06-13 Thread Manil Liyanage
Hi All,

I'm currently writing a synapse configuration for a connector and its a
REST base api which send responses in json format as in the attachment.

My question is that how to put the response recieved on json to the payload
body. code of the configuration is shown below. I have hardcoded for the
request url for testing purpose. Please help me on this.

http://ws.apache.org/ns/synapse"; name="getUser">


**
* *
* http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/>">*
* *
* *
* *
* *
* *
* *


**
* http://api.soundcloud.com/users/3207.json?client_id=21fded24c32c2d9b0316971643d2f75f
<http://api.soundcloud.com/users/3207.json?client_id=21fded24c32c2d9b0316971643d2f75f>"
/>*
* *





Thanks,
Manil Liyanage


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