date:20171111

Re: [Dev] Exception with header

2017-11-11 Thread Bhathiya Jayasekara

Looks like the backend is expecting at least a dummy header. So it's ok to
send one/

Thanks.
Bhathiya

On Sun, Nov 12, 2017 at 12:35 PM, Dilusha Alphonso  wrote:

> It is deployed on the app server. We have only given the back-end URL with
> username, password.Within the wso2 environment, we can access the backend.
>
> Thanks
> Dilusha.
>
> On Sun, Nov 12, 2017 at 11:55 AM, Bhathiya Jayasekara 
> wrote:
>
>>
>> On Sun, Nov 12, 2017 at 10:45 AM, Dilusha Alphonso 
>> wrote:
>>
>>> I got the back-end[1] for my task.
>>>
>>
>> I don't think I can access this. Please post the code of your backend.
>>
>>
>>> When I invoke [1] through SOAP UI with empty soap header it works and
>>> gives 200 ok. But when I remove empty header the backend gives 500 error.
>>>
>>
>> Do you see any errors in the log?
>>
>> Thanks,
>> Bhathiya
>>
>>
>>>
>>> Is this valid behavior or a bug in the back-end?
>>>
>>> If it is a valid behavior how to send empty soap header when creating
>>> soap payload using payload factory. Currently, as a temporary solution, I
>>> am adding dummy header like below.
>>>
>>>
>>>  
>>> 
>>>http://schemas.
>>> xmlsoap.org/soap/envelope/">
>>> *   *
>>> * 12*
>>> *  *
>>> 
>>>  http://service.samp
>>> le.durdans.com">
>>> 500
>>>  
>>>   
>>>
>>> 
>>> 
>>>
>>> 
>>>  
>>>
>>> [1]. https://192.168.55.160:9443/services/
>>> 
>>> DurdansPatientService
>>> .
>>>
>>> Thanks
>>> Dilusha
>>>
>>>
>>> On Sun, Nov 12, 2017 at 1:23 AM, Bhathiya Jayasekara 
>>> wrote:
>>>
 As per the log, your backend is sending the 500. What is your backend?
 Check that.

 Thanks,
 Bhathiya

 On Sun, Nov 12, 2017 at 12:16 AM, Dilusha Alphonso 
 wrote:

> Hi All,
>
> I am using a wum pack of ESB 5.0.0(wso2esb-5.0.0.1510144891829).I
> have created API in ESB. Below is the payload of my API configuration.
>
>  
> 
>http://schemas.
> xmlsoap.org/soap/envelope/">
>   
> 
>  http://service.samp
> le.durdans.com">
> 500
>  
>   
>
> 
> 
>
> 
>  
>
> I find fault string exception logged in the console for this payload.
> But when I add a dummy header in the request payload, I was able to get
> the 200 OK response. getting.
> Please let me know whether this is a best practice.
>
> I have attached the screenshot of the wire log.
>
> Please provide the suggestion.
>
> Thanks
> Dilusha
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Bhathiya Jayasekara*
 *Associate Technical Lead,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <+94%2071%20547%208185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

>>>
>>>
>>>
>>> --
>>>
>>>
>>> *Best Regards,Dilusha Alphonso*
>>>
>>> *Software Engineer - Support Team*
>>>
>>>
>>> *WSO2*
>>> *Mobile : *
>>>
>>> *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
>>> *
>>>
>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <+94%2071%20547%208185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
> *
>



-- 
*Bhathiya

Re: [Dev] API gives "SOAP Envelope can not have children other than SOAP Header and Body" Exception

2017-11-11 Thread Bhathiya Jayasekara

Looks like you're facing the same error mentioned here[1]. It seems the
backend is expecting at least a dummy header. Try that.

[1] "[Dev] Exception with header"

Thanks,
Bhathiya

On Sun, Nov 12, 2017 at 12:34 PM, Buddhimala Ranasinghe  wrote:

> Hi All,
>
> I have create an API in ESB 5.0.0 for accessing a secured  SOAP BE
> service. Attached is the sysnapse configuraion for my API.
>
> http://ws.apache.org/ns/synapse; name="NawalokaPatientAPI"
> context="/nawaloka">
>
>   
>  
>  
> 
>http://service.sample.nawaloka.com;>
>   123
>
> 
> 
>
> 
>  
>  
>  
>  
>  
>  
> 
>https://192.168.55.160:9443/services/
> NawalokaPatientService" format="soap11"/>
> 
>  
>   
>   
>   scope="axis2"/>
>  
>   
>
> 
>
> The WSDL for my BE service can be found in following URL location.
>
> http://192.168.55.160:9763/services/NawalokaPatientService?wsdl
>
>
> My problem is, when I tried to invoke the API using SOAPUI, the following
> error message prompt with 500 error code.
>
> {"Exception": "SOAP Envelope can not have children other than SOAP Header
> and Body"}
>
> Attached what is logged in ESB, enabled wirelogs and debug logs.
>
> How can I resolve this issue? Appreciate your support.
> --
>
>
> *Buddhimala Ranasinghe*
> Software Engineer-Support Team | WSO2
> Emil: buddhim...@wso2.com
> Mobile:+94771563138 <077%20156%203138>
> Web:http://wso2.com
> [image: https://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception with header

2017-11-11 Thread Dilusha Alphonso

It is deployed on the app server. We have only given the back-end URL with
username, password.Within the wso2 environment, we can access the backend.

Thanks
Dilusha.

On Sun, Nov 12, 2017 at 11:55 AM, Bhathiya Jayasekara 
wrote:

>
> On Sun, Nov 12, 2017 at 10:45 AM, Dilusha Alphonso 
> wrote:
>
>> I got the back-end[1] for my task.
>>
>
> I don't think I can access this. Please post the code of your backend.
>
>
>> When I invoke [1] through SOAP UI with empty soap header it works and
>> gives 200 ok. But when I remove empty header the backend gives 500 error.
>>
>
> Do you see any errors in the log?
>
> Thanks,
> Bhathiya
>
>
>>
>> Is this valid behavior or a bug in the back-end?
>>
>> If it is a valid behavior how to send empty soap header when creating
>> soap payload using payload factory. Currently, as a temporary solution, I
>> am adding dummy header like below.
>>
>>
>>  
>> 
>>http://schemas.
>> xmlsoap.org/soap/envelope/">
>> *   *
>> * 12*
>> *  *
>> 
>>  http://service.samp
>> le.durdans.com">
>> 500
>>  
>>   
>>
>> 
>> 
>>
>> 
>>  
>>
>> [1]. https://192.168.55.160:9443/services/
>> 
>> DurdansPatientService
>> .
>>
>> Thanks
>> Dilusha
>>
>>
>> On Sun, Nov 12, 2017 at 1:23 AM, Bhathiya Jayasekara 
>> wrote:
>>
>>> As per the log, your backend is sending the 500. What is your backend?
>>> Check that.
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>> On Sun, Nov 12, 2017 at 12:16 AM, Dilusha Alphonso 
>>> wrote:
>>>
 Hi All,

 I am using a wum pack of ESB 5.0.0(wso2esb-5.0.0.1510144891829).I have
 created API in ESB. Below is the payload of my API configuration.

  
 
http://schemas.
 xmlsoap.org/soap/envelope/">
   
 
  http://service.samp
 le.durdans.com">
 500
  
   

 
 

 
  

 I find fault string exception logged in the console for this payload.
 But when I add a dummy header in the request payload, I was able to get
 the 200 OK response. getting.
 Please let me know whether this is a best practice.

 I have attached the screenshot of the wire log.

 Please provide the suggestion.

 Thanks
 Dilusha


 --


 *Best Regards,Dilusha Alphonso*

 *Software Engineer - Support Team*


 *WSO2*
 *Mobile : *

 *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
 *

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


>>>
>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Associate Technical Lead,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185 <+94%2071%20547%208185>*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>>
>>
>> *Best Regards,Dilusha Alphonso*
>>
>> *Software Engineer - Support Team*
>>
>>
>> *WSO2*
>> *Mobile : *
>>
>> *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
>> *
>>
>
>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <+94%2071%20547%208185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>



-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

*+94766837098[image: http://wso2.com/signature] *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] API gives "SOAP Envelope can not have children other than SOAP Header and Body" Exception

2017-11-11 Thread Buddhimala Ranasinghe

Hi All,

I have create an API in ESB 5.0.0 for accessing a secured  SOAP BE service.
Attached is the sysnapse configuraion for my API.

http://ws.apache.org/ns/synapse; name="NawalokaPatientAPI"
context="/nawaloka">
   
  
 
 

   http://service.sample.nawaloka.com;>
  123
   


   

 
 
 
 
 
 

   https://192.168.55.160:9443/services/NawalokaPatientService;
format="soap11"/>

 
  
  
 
 
  
   


The WSDL for my BE service can be found in following URL location.

http://192.168.55.160:9763/services/NawalokaPatientService?wsdl


My problem is, when I tried to invoke the API using SOAPUI, the following
error message prompt with 500 error code.

{"Exception": "SOAP Envelope can not have children other than SOAP Header
and Body"}

Attached what is logged in ESB, enabled wirelogs and debug logs.

How can I resolve this issue? Appreciate your support.
-- 


*Buddhimala Ranasinghe*
Software Engineer-Support Team | WSO2
Emil: buddhim...@wso2.com
Mobile:+94771563138
Web:http://wso2.com
[image: https://wso2.com/signature] 


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

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

2017-11-11 Thread Piriya Sivalingam

I am attaching the WSDL of my deployed backend service.



On Sun, Nov 12, 2017 at 11:47 AM, Piriya Sivalingam  wrote:

> I am attaching the WSDL of my proxy service.
>
>
>
> On Sun, Nov 12, 2017 at 11:44 AM, Mushthaq Rumy  wrote:
>
>> Hi Piriya,
>>
>> Can you attach the proxy WSDL file?
>>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Sun, Nov 12, 2017 at 10:53 AM, Piriya Sivalingam 
>> wrote:
>>
>>> Hi Mushthaq,
>>>
>>> I tried the same operation in SOAPUI and it works fine. "readNinewells"
>>> is a correct operation.
>>>
>>> Thanks.
>>>
>>> On Sun, Nov 12, 2017 at 12:55 AM, Mushthaq Rumy 
>>> wrote:
>>>
 Hi Pririya,

 Seems like the operation you use is an incorrect operation. Was this
 working fine in SOAPUI? Could you please check if *"readNinewells" *is
 the correct operation?

 Thanks & Regards,
 Mushthaq

 On Sat, Nov 11, 2017 at 11:59 PM, Piriya Sivalingam 
 wrote:

> Hi,
>
> I am creating an API in ESB 5.0.0 for GET Resource, where I have a
> secured SOAP backend service. Below is my synapse configuration of the 
> API.
> I find some error logged in the console.
>
> 
> http://ws.apache.org/ns/synapse;
>  name="PatientAPI"
>  context="/patientapi">
>
>   
>    scope="transport"
>  value="Basic cGlyaXlhOnBpcml5YTEyMw=="/>
>  
> 
>http://schemas.
> xmlsoap.org/soap/envelope/"
>  xmlns:ser="http://service.sam
> ple.ninewells.com">
>   
>   
>  
> 
>  
>   
>
> 
> 
>
> 
>  
>  
>   scope="transport"/>
>  value="application/soap+xml"
>scope="axis2"
>type="STRING"/>
>  
> 
>https://.xx.xx.xx:xxx
> 3/services/NinewellsPatientService"
> format="soap11"/>
> 
>  
>   
>   
>  value="application/json"
>scope="axis2"
>type="STRING"/>
>  
>   
>
> 
>
> There is a 500 Internal Server Error logged in the console.
>
> Below is the exception found.
> {"faultstring":"The endpoint reference (EPR) for the Operation not
> found is /services/DurdansPatientService and the WSA Action = null.
> If this EPR was previously reachable, please contact the server
> administrator."}
>
> Highly appreciate your advice on this.
>
> Thanks.
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Mushthaq Rumy
 *Software Engineer*
 Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
 Email : musht...@wso2.com
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middleware.

 

>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> *Piriya Sivalingam*
>>>
>>> *Software Engineer - Support Team*
>>>
>>> *WSO2*
>>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>>
>>
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> 
>>
>
>
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
>


-- 
Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

[image: http://wso2.com/signature] 
http://schemas.xmlsoap.org/wsdl/; xmlns:ax215="http://dto.service.sample.ninewells.com/xsd; xmlns:ns1="http://org.apache.axis2/xsd; xmlns:ns="http://service.sample.ninewells.com; xmlns:ax213="http://service.sample.ninewells.com/xsd; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/;

Re: [Dev] Exception with header

2017-11-11 Thread Bhathiya Jayasekara

On Sun, Nov 12, 2017 at 10:45 AM, Dilusha Alphonso  wrote:

> I got the back-end[1] for my task.
>

I don't think I can access this. Please post the code of your backend.


> When I invoke [1] through SOAP UI with empty soap header it works and
> gives 200 ok. But when I remove empty header the backend gives 500 error.
>

Do you see any errors in the log?

Thanks,
Bhathiya


>
> Is this valid behavior or a bug in the back-end?
>
> If it is a valid behavior how to send empty soap header when creating soap
> payload using payload factory. Currently, as a temporary solution, I am
> adding dummy header like below.
>
>
>  
> 
>http://schemas.
> xmlsoap.org/soap/envelope/">
> *   *
> * 12*
> *  *
> 
>  http://service.samp
> le.durdans.com">
> 500
>  
>   
>
> 
> 
>
> 
>  
>
> [1]. https://192.168.55.160:9443/services/
> 
> DurdansPatientService
> .
>
> Thanks
> Dilusha
>
>
> On Sun, Nov 12, 2017 at 1:23 AM, Bhathiya Jayasekara 
> wrote:
>
>> As per the log, your backend is sending the 500. What is your backend?
>> Check that.
>>
>> Thanks,
>> Bhathiya
>>
>> On Sun, Nov 12, 2017 at 12:16 AM, Dilusha Alphonso 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am using a wum pack of ESB 5.0.0(wso2esb-5.0.0.1510144891829).I have
>>> created API in ESB. Below is the payload of my API configuration.
>>>
>>>  
>>> 
>>>http://schemas.
>>> xmlsoap.org/soap/envelope/">
>>>   
>>> 
>>>  http://service.samp
>>> le.durdans.com">
>>> 500
>>>  
>>>   
>>>
>>> 
>>> 
>>>
>>> 
>>>  
>>>
>>> I find fault string exception logged in the console for this payload.
>>> But when I add a dummy header in the request payload, I was able to get
>>> the 200 OK response. getting.
>>> Please let me know whether this is a best practice.
>>>
>>> I have attached the screenshot of the wire log.
>>>
>>> Please provide the suggestion.
>>>
>>> Thanks
>>> Dilusha
>>>
>>>
>>> --
>>>
>>>
>>> *Best Regards,Dilusha Alphonso*
>>>
>>> *Software Engineer - Support Team*
>>>
>>>
>>> *WSO2*
>>> *Mobile : *
>>>
>>> *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <+94%2071%20547%208185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
> *
>



-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

2017-11-11 Thread Piriya Sivalingam

I am attaching the WSDL of my proxy service.



On Sun, Nov 12, 2017 at 11:44 AM, Mushthaq Rumy  wrote:

> Hi Piriya,
>
> Can you attach the proxy WSDL file?
>
> Thanks & Regards,
> Mushthaq
>
> On Sun, Nov 12, 2017 at 10:53 AM, Piriya Sivalingam 
> wrote:
>
>> Hi Mushthaq,
>>
>> I tried the same operation in SOAPUI and it works fine. "readNinewells"
>> is a correct operation.
>>
>> Thanks.
>>
>> On Sun, Nov 12, 2017 at 12:55 AM, Mushthaq Rumy 
>> wrote:
>>
>>> Hi Pririya,
>>>
>>> Seems like the operation you use is an incorrect operation. Was this
>>> working fine in SOAPUI? Could you please check if *"readNinewells" *is
>>> the correct operation?
>>>
>>> Thanks & Regards,
>>> Mushthaq
>>>
>>> On Sat, Nov 11, 2017 at 11:59 PM, Piriya Sivalingam 
>>> wrote:
>>>
 Hi,

 I am creating an API in ESB 5.0.0 for GET Resource, where I have a
 secured SOAP backend service. Below is my synapse configuration of the API.
 I find some error logged in the console.

 
 http://ws.apache.org/ns/synapse;
  name="PatientAPI"
  context="/patientapi">

   
  >>>  scope="transport"
  value="Basic cGlyaXlhOnBpcml5YTEyMw=="/>
  
 
http://schemas.
 xmlsoap.org/soap/envelope/"
  xmlns:ser="http://service.sam
 ple.ninewells.com">
   
   
  
 
  
   

 
 

 
  
  
  >>> scope="transport"/>
  >>>value="application/soap+xml"
scope="axis2"
type="STRING"/>
  
 
https://.xx.xx.xx:xxx
 3/services/NinewellsPatientService"
 format="soap11"/>
 
  
   
   
  >>>value="application/json"
scope="axis2"
type="STRING"/>
  
   

 

 There is a 500 Internal Server Error logged in the console.

 Below is the exception found.
 {"faultstring":"The endpoint reference (EPR) for the Operation not
 found is /services/DurdansPatientService and the WSA Action = null. If
 this EPR was previously reachable, please contact the server
 administrator."}

 Highly appreciate your advice on this.

 Thanks.

 --
 Regards,

 *Piriya Sivalingam*

 *Software Engineer - Support Team*

 *WSO2*
 *Mobile : +94 77 8462039 <+94%2077%20846%202039>*

 [image: http://wso2.com/signature] 


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


>>>
>>>
>>> --
>>> Mushthaq Rumy
>>> *Software Engineer*
>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>> Email : musht...@wso2.com
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middleware.
>>>
>>> 
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> *Piriya Sivalingam*
>>
>> *Software Engineer - Support Team*
>>
>> *WSO2*
>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>
>> [image: http://wso2.com/signature] 
>>
>>
>
>
> --
> Mushthaq Rumy
> *Software Engineer*
> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
> Email : musht...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
> 
>



-- 
Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

[image: http://wso2.com/signature] 
http://schemas.xmlsoap.org/wsdl/; xmlns:ns="http://service.sample.ninewells.com; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:ns1="http://org.apache.axis2/xsd; xmlns:ax215="http://dto.service.sample.ninewells.com/xsd; xmlns:ax213="http://service.sample.ninewells.com/xsd; xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/; xmlns:xs="http://www.w3.org/2001/XMLSchema; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/; targetNamespace="http://service.sample.ninewells.com;>
   NinewellsPatientService
   
  http://dto.service.sample.ninewells.com/xsd;>

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

2017-11-11 Thread Mushthaq Rumy

Hi Piriya,

Can you attach the proxy WSDL file?

Thanks & Regards,
Mushthaq

On Sun, Nov 12, 2017 at 10:53 AM, Piriya Sivalingam  wrote:

> Hi Mushthaq,
>
> I tried the same operation in SOAPUI and it works fine. "readNinewells" is
> a correct operation.
>
> Thanks.
>
> On Sun, Nov 12, 2017 at 12:55 AM, Mushthaq Rumy  wrote:
>
>> Hi Pririya,
>>
>> Seems like the operation you use is an incorrect operation. Was this
>> working fine in SOAPUI? Could you please check if *"readNinewells" *is
>> the correct operation?
>>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Sat, Nov 11, 2017 at 11:59 PM, Piriya Sivalingam 
>> wrote:
>>
>>> Hi,
>>>
>>> I am creating an API in ESB 5.0.0 for GET Resource, where I have a
>>> secured SOAP backend service. Below is my synapse configuration of the API.
>>> I find some error logged in the console.
>>>
>>> 
>>> http://ws.apache.org/ns/synapse;
>>>  name="PatientAPI"
>>>  context="/patientapi">
>>>
>>>   
>>>  >>  scope="transport"
>>>  value="Basic cGlyaXlhOnBpcml5YTEyMw=="/>
>>>  
>>> 
>>>http://schemas.
>>> xmlsoap.org/soap/envelope/"
>>>  xmlns:ser="http://service.sam
>>> ple.ninewells.com">
>>>   
>>>   
>>>  
>>> 
>>>  
>>>   
>>>
>>> 
>>> 
>>>
>>> 
>>>  
>>>  
>>>  >> scope="transport"/>
>>>  >>value="application/soap+xml"
>>>scope="axis2"
>>>type="STRING"/>
>>>  
>>> 
>>>https://.xx.xx.xx:xxx
>>> 3/services/NinewellsPatientService"
>>> format="soap11"/>
>>> 
>>>  
>>>   
>>>   
>>>  >>value="application/json"
>>>scope="axis2"
>>>type="STRING"/>
>>>  
>>>   
>>>
>>> 
>>>
>>> There is a 500 Internal Server Error logged in the console.
>>>
>>> Below is the exception found.
>>> {"faultstring":"The endpoint reference (EPR) for the Operation not found
>>> is /services/DurdansPatientService and the WSA Action = null. If this
>>> EPR was previously reachable, please contact the server administrator."}
>>>
>>> Highly appreciate your advice on this.
>>>
>>> Thanks.
>>>
>>> --
>>> Regards,
>>>
>>> *Piriya Sivalingam*
>>>
>>> *Software Engineer - Support Team*
>>>
>>> *WSO2*
>>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> 
>>
>
>
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.


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

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

2017-11-11 Thread Piriya Sivalingam

Hi Mushthaq,

I tried the same operation in SOAPUI and it works fine. "readNinewells" is
a correct operation.

Thanks.

On Sun, Nov 12, 2017 at 12:55 AM, Mushthaq Rumy  wrote:

> Hi Pririya,
>
> Seems like the operation you use is an incorrect operation. Was this
> working fine in SOAPUI? Could you please check if *"readNinewells" *is
> the correct operation?
>
> Thanks & Regards,
> Mushthaq
>
> On Sat, Nov 11, 2017 at 11:59 PM, Piriya Sivalingam 
> wrote:
>
>> Hi,
>>
>> I am creating an API in ESB 5.0.0 for GET Resource, where I have a
>> secured SOAP backend service. Below is my synapse configuration of the API.
>> I find some error logged in the console.
>>
>> 
>> http://ws.apache.org/ns/synapse;
>>  name="PatientAPI"
>>  context="/patientapi">
>>
>>   
>>  >  scope="transport"
>>  value="Basic cGlyaXlhOnBpcml5YTEyMw=="/>
>>  
>> 
>>http://schemas.
>> xmlsoap.org/soap/envelope/"
>>  xmlns:ser="http://service.sam
>> ple.ninewells.com">
>>   
>>   
>>  
>> 
>>  
>>   
>>
>> 
>> 
>>
>> 
>>  
>>  
>>  > scope="transport"/>
>>  >value="application/soap+xml"
>>scope="axis2"
>>type="STRING"/>
>>  
>> 
>>https://.xx.xx.xx:xxx
>> 3/services/NinewellsPatientService"
>> format="soap11"/>
>> 
>>  
>>   
>>   
>>  >value="application/json"
>>scope="axis2"
>>type="STRING"/>
>>  
>>   
>>
>> 
>>
>> There is a 500 Internal Server Error logged in the console.
>>
>> Below is the exception found.
>> {"faultstring":"The endpoint reference (EPR) for the Operation not found
>> is /services/DurdansPatientService and the WSA Action = null. If this
>> EPR was previously reachable, please contact the server administrator."}
>>
>> Highly appreciate your advice on this.
>>
>> Thanks.
>>
>> --
>> Regards,
>>
>> *Piriya Sivalingam*
>>
>> *Software Engineer - Support Team*
>>
>> *WSO2*
>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>
>> [image: http://wso2.com/signature] 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Mushthaq Rumy
> *Software Engineer*
> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
> Email : musht...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
> 
>



-- 
Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception with header

2017-11-11 Thread Dilusha Alphonso

I got the back-end[1] for my task. When I invoke [1] through SOAP UI with
empty soap header it works and gives 200 ok. But when I remove empty header
the backend gives 500 error.

Is this valid behavior or a bug in the back-end?

If it is a valid behavior how to send empty soap header when creating soap
payload using payload factory. Currently, as a temporary solution, I am
adding dummy header like below.


 

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

 http://service.
sample.durdans.com">
500
 
  
   


   

 

[1]. https://192.168.55.160:9443/services/

DurdansPatientService
.

Thanks
Dilusha


On Sun, Nov 12, 2017 at 1:23 AM, Bhathiya Jayasekara 
wrote:

> As per the log, your backend is sending the 500. What is your backend?
> Check that.
>
> Thanks,
> Bhathiya
>
> On Sun, Nov 12, 2017 at 12:16 AM, Dilusha Alphonso 
> wrote:
>
>> Hi All,
>>
>> I am using a wum pack of ESB 5.0.0(wso2esb-5.0.0.1510144891829).I have
>> created API in ESB. Below is the payload of my API configuration.
>>
>>  
>> 
>>http://schemas.
>> xmlsoap.org/soap/envelope/">
>>   
>> 
>>  http://service.samp
>> le.durdans.com">
>> 500
>>  
>>   
>>
>> 
>> 
>>
>> 
>>  
>>
>> I find fault string exception logged in the console for this payload. But
>> when I add a dummy header in the request payload, I was able to get the 200
>> OK response. getting.
>> Please let me know whether this is a best practice.
>>
>> I have attached the screenshot of the wire log.
>>
>> Please provide the suggestion.
>>
>> Thanks
>> Dilusha
>>
>>
>> --
>>
>>
>> *Best Regards,Dilusha Alphonso*
>>
>> *Software Engineer - Support Team*
>>
>>
>> *WSO2*
>> *Mobile : *
>>
>> *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <+94%2071%20547%208185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>



-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

*+94766837098[image: http://wso2.com/signature] *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] Multiple stubs version in 5.4.0 pack

2017-11-11 Thread Ruwan Abeykoon

Hi All,
We need to work on removing previous version.

On Sat, Nov 11, 2017 at 12:01 PM, Harsha Thirimanna 
wrote:

> Hi Devs,
>
> We have zipped two stub versions in IS 5.4.0 pack OOB. Any special reason
> for that ?
>
> org.wso2.carbon.identity.sso.saml.stub_5.1.3.jar
> org.wso2.carbon.identity.sso.saml.stub_5.3.34.jar
>
>
> thanks
>
> *Harsha Thirimanna*
> *Associate Tech Lead | WSO2*
>
> Email: hars...@wso2.com
> Mob: +94715186770 <+94%2071%20518%206770>
> Blog: http://harshathirimanna.blogspot.com/
> Twitter: http://twitter.com/harshathirimann
> Linked-In: linked-in: http://www.linkedin.com/pub/
> harsha-thirimanna/10/ab8/122
> 
>

-- 

*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception with header

2017-11-11 Thread Bhathiya Jayasekara

As per the log, your backend is sending the 500. What is your backend?
Check that.

Thanks,
Bhathiya

On Sun, Nov 12, 2017 at 12:16 AM, Dilusha Alphonso  wrote:

> Hi All,
>
> I am using a wum pack of ESB 5.0.0(wso2esb-5.0.0.1510144891829).I have
> created API in ESB. Below is the payload of my API configuration.
>
>  
> 
>http://schemas.
> xmlsoap.org/soap/envelope/">
>   
> 
>  http://service.
> sample.durdans.com">
> 500
>  
>   
>
> 
> 
>
> 
>  
>
> I find fault string exception logged in the console for this payload. But
> when I add a dummy header in the request payload, I was able to get the 200
> OK response. getting.
> Please let me know whether this is a best practice.
>
> I have attached the screenshot of the wire log.
>
> Please provide the suggestion.
>
> Thanks
> Dilusha
>
>
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <076%20683%207098>[image: http://wso2.com/signature]
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

2017-11-11 Thread Mushthaq Rumy

Hi Pririya,

Seems like the operation you use is an incorrect operation. Was this
working fine in SOAPUI? Could you please check if *"readNinewells" *is the
correct operation?

Thanks & Regards,
Mushthaq

On Sat, Nov 11, 2017 at 11:59 PM, Piriya Sivalingam  wrote:

> Hi,
>
> I am creating an API in ESB 5.0.0 for GET Resource, where I have a secured
> SOAP backend service. Below is my synapse configuration of the API. I find
> some error logged in the console.
>
> 
> http://ws.apache.org/ns/synapse;
>  name="PatientAPI"
>  context="/patientapi">
>
>   
>scope="transport"
>  value="Basic cGlyaXlhOnBpcml5YTEyMw=="/>
>  
> 
>http://schemas.
> xmlsoap.org/soap/envelope/"
>  xmlns:ser="http://service.
> sample.ninewells.com">
>   
>   
>  
> 
>  
>   
>
> 
> 
>
> 
>  
>  
>   scope="transport"/>
>  value="application/soap+xml"
>scope="axis2"
>type="STRING"/>
>  
> 
>https://.xx.xx.xx:xxx3/services/
> NinewellsPatientService"
> format="soap11"/>
> 
>  
>   
>   
>  value="application/json"
>scope="axis2"
>type="STRING"/>
>  
>   
>
> 
>
> There is a 500 Internal Server Error logged in the console.
>
> Below is the exception found.
> {"faultstring":"The endpoint reference (EPR) for the Operation not found
> is /services/DurdansPatientService and the WSA Action = null. If this EPR
> was previously reachable, please contact the server administrator."}
>
> Highly appreciate your advice on this.
>
> Thanks.
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.


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

[Dev] Exception in ESB 5.0.0 while creating an API.

2017-11-11 Thread Piriya Sivalingam

Hi,

I am creating an API in ESB 5.0.0 for GET Resource, where I have a secured
SOAP backend service. Below is my synapse configuration of the API. I find
some error logged in the console.


http://ws.apache.org/ns/synapse;
 name="PatientAPI"
 context="/patientapi">
   
  
 
 

   http://schemas.xmlsoap.org/soap/envelope/;
 xmlns:ser="
http://service.sample.ninewells.com;>
  
  
 

 
  
   


   

 
 
 
 
 

   https://.xx.xx.xx:xxx3
/services/NinewellsPatientService"
format="soap11"/>

 
  
  
 
 
  
   


There is a 500 Internal Server Error logged in the console.

Below is the exception found.
{"faultstring":"The endpoint reference (EPR) for the Operation not found is
/services/DurdansPatientService and the WSA Action = null. If this EPR was
previously reachable, please contact the server administrator."}

Highly appreciate your advice on this.

Thanks.

-- 
Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CSRF token error in working with EI Management Console with Java 1.8.0_151

2017-11-11 Thread Sudharma Subasinghe

Hi Prakash,

As you mentioned I tried again with jdk1.8.0_144. It does not work for EI
6.1.1-update 8 with JDK 1.8.0_144 or JDK 1.8.0_45.

On Tue, Nov 7, 2017 at 9:14 PM, Sudharma Subasinghe 
wrote:

>
>
> On Tue, Nov 7, 2017 at 7:01 PM, Arunan Sugunakumar 
> wrote:
>
>> Hi,
>>
>> I seem to be getting this issue in wso2das-3.1.0 and wso2esb5.0.0 as
>> well. Is there any temporary fix for this problem?
>>
>
> Did you get the issue for wso2esb 5.0.0 with JDK 1.8.0_144? Try with JDK
> 1.8.0_45 for wso2 esb 5.0.0 which works for me.
>
>>
>> Thanks
>>
>> On Mon, Nov 6, 2017 at 9:04 PM, Sudharma Subasinghe 
>> wrote:
>>
>>> Hi Prakash,
>>>
>>> Still with jdk1.8.0_144, same issue happens with EI 6.1.1-update 8 pack
>>>
>>> On Mon, Nov 6, 2017 at 8:06 PM, Sudharma Subasinghe 
>>> wrote:
>>>
 Same thing is happening with EI 6.1.1-update 8 with JDK 1.8.0_45.


 On Wed, Nov 1, 2017 at 7:14 AM, Prakhash Sivakumar 
 wrote:

>
>
> On Tue, Oct 31, 2017 at 3:20 PM, Thejan Rupasinghe 
> wrote:
>
>> Hi Chaminda,
>>
>> Seems it is an issue in the Tomcat server with that jdk update.
>>
> Yes. This is happining due to a gzip decoding issue with JDK 1.8.0_151,
> which is reported in [1] .
>
> [1] https://bugs.openjdk.java.net/browse/JDK-8189789
>
>
>> Thanks for informing.
>>
>> Regards,
>> Thejan
>>
>> On Tue, Oct 31, 2017 at 2:54 PM, Chaminda Jayawardena <
>> chami...@wso2.com> wrote:
>>
>>>
>>> seems a known issue and the ESB document has been updated with the
>>> info.
>>>
>>> [1] https://docs.wso2.com/display/ESB500/Installation+Prerequisites
>>>
>>> Thanks
>>> Chaminda
>>>
>>> On Tue, Oct 31, 2017 at 10:21 AM, Thejan Rupasinghe >> > wrote:
>>>
 Hi all,

 When I'm working with EI Management Console with the latest Java 8
 version, 1.8.0_151 [1], following error occurred.

 [2017-10-30 19:14:54,210] [EI-Core]  WARN - JavaLogger potential
 cross-site request forgery (CSRF) attack thwarted (user:,
 ip:10.100.4.201, method:POST, 
 uri:/carbon/admin/jsp/WSRequestXSSproxy_ajaxprocessor.jsp,
 error:required token is missing from the request)

 I could not submit any form data through Management Console.

 I tested with EI 6.1.1 and current update, EI 6.1.1-update 7, but
 the same error occurred.

 When I use Java 1.8.0_144, everything works fine.

 Can anyone explain why does this happen?

 [1] https://java.com/en/download/

 Thanks,
 Regards,
 Thejan
 --

 *Thejan Rupasinghe*

 *Intern - Software EngineeringWSO2*

 *Mobile : +94 77-9020962 <+94%2077%20902%200962>*
 

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


>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> *Chaminda Jayawardena*
>>> Associate Technical Lead - QA
>>> WSO2 Inc. - http://wso2.com
>>> +94-77-7725234 <+94%2077%20772%205234>
>>>
>>
>>
>>
>> --
>>
>> *Thejan Rupasinghe*
>>
>> *Intern - Software EngineeringWSO2*
>>
>> *Mobile : +94 77-9020962 <+94%2077%20902%200962>*
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Prakhash Sivakumar
> Software Engineer | WSO2 Inc
> Platform Security Team
> Mobile : +94771510080 <+94%2077%20151%200080>
> Blog : https://medium.com/@PrakhashS
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Sudharma Subasinghe,
 Software Engineer,
 WSO2 Inc.
 Email: sudhar...@wso2.com 
 Mobile : +94 710 565 157 <%2B94%20718%20210%20200>

>>>
>>>
>>>
>>> --
>>> Sudharma Subasinghe,
>>> Software Engineer,
>>> WSO2 Inc.
>>> Email: sudhar...@wso2.com 
>>> Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Sugunakumar Arunan*
>> Sofware Engineering - Intern | WSO2
>>
>> Email : aru...@wso2.com
>> Mobile : 0766016272
>> Web : http://wso2.com
>> 
>>
>
>
>
> --
> Sudharma Subasinghe,
>

Re: [Dev] Exception when Publishing API in API Manager 2.1.0

2017-11-11 Thread Rukshan Premathunga

Hi Priya,

In the screenshot you have attached, it says to select a GW environment to
be publish. Can you expand the gateway environment section and select a
option first.

Thanks and Regards

On Sat, Nov 11, 2017 at 11:47 AM, Piriya Sivalingam  wrote:

> Thank you Mushthaq for your prompt response.
>
> But I couldn't find any errors logged in the console. I am attaching the
> wso2carbon.log file.
>
> On Fri, Nov 10, 2017 at 7:23 PM, Mushthaq Rumy  wrote:
>
>> Hi Piriya,
>>
>> Was there any error logged in the console. If so could you please attach
>> the error log?
>>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Fri, Nov 10, 2017 at 5:27 PM, Piriya Sivalingam 
>> wrote:
>>
>>> Hi,
>>>
>>> I am working on a task where I have followed the below steps:
>>>
>>>
>>>- There is a SOAP backend which is hosted on Application Server and
>>>secured UT over Transport.
>>>- I have created a proxy service in ESB 5.0.0 having the SOAP
>>>backend as the endpoint of the proxy.
>>>- Then I followed this [1] blog to create an API in API Manager
>>>2.1.0 having the created ESB as the endpoint of the API.
>>>- According to the blog when I create the API, I couldn't publish
>>>this API. I could notice some exception in the Publisher UI.
>>>
>>> I am attaching a screenshot of the Publisher when it gives the exception.
>>> Could you please suggest me the reason for this exception and whether I
>>> have done something wrong here and how can I solve this issue?
>>>
>>> [1] https://medium.com/@shenavi21/exposing-a-soap-service-as
>>> -a-managed-rest-api-288676e06418
>>>
>>> Highly appreciate your suggestion on this.
>>>
>>> Thanks.
>>> --
>>> Regards,
>>>
>>> *Piriya Sivalingam*
>>>
>>> *Software Engineer - Support Team*
>>>
>>> *WSO2*
>>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> 
>>
>
>
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
+94711822074
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception while invoking proxy service in ESB 5.0.0

2017-11-11 Thread Dilusha Alphonso

I have attached the diagram of task.
[image: Inline image 1]

In ESB 5.0.0 I created the proxy service. Those configurations attached
below.


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

   https://192.168.55.160:9443/services/DurdansPatientService"/>

 
  
  
 
  
   
   http://192.168.55.160:9763/services/DurdansPatientService?wsdl"/>
   


When I invoke the proxy service using SOAPUI. I got the above exception.

Thanks
Dilusha




On Sat, Nov 11, 2017 at 12:38 AM, Vijitha Ekanayake 
wrote:

> Hi Dilusha,
>
> Can you provide more context about the scenario and share the complete
> configurations to provide you a solution.
>
> Thanks.
>
> On Fri, Nov 10, 2017 at 5:29 PM, Dilusha Alphonso 
> wrote:
>
>> Hi All,
>>
>> I am working on the scenario. where I have to create a proxy service in
>> ESB 5.0.0 using a WSDL of a SOAP backend service. When I invoke the proxy
>> service using SOAPUI I am getting some error.
>>
>>  When I invoke the service with the GET method I get the proper response,
>> but for POST method I could get 202 Accepted response with some exception
>> in the log.
>>
>> java.lang.UnsupportedOperationException: An access occurred that
>> is not valid.
>> at org.apache.axis2.description.InOnlyAxisOperation.getMessage(
>> InOnlyAxisOperation.java:117)
>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handle
>> Message(SynapseCallbackReceiver.java:324)
>> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receiv
>> e(SynapseCallbackReceiver.java:188)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.synapse.transport.passthru.ClientWorker.run(Clien
>> tWorker.java:261)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.r
>> un(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>>
>> Could you please advice on this?
>>
>> Thanks
>> Dilusha
>> --
>>
>>
>> *Best Regards,Dilusha Alphonso*
>>
>> *Software Engineer - Support Team*
>>
>>
>> *WSO2*
>> *Mobile : *
>>
>> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vijitha Ekanayake
> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>



-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

*+94766837098[image: http://wso2.com/signature] *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Enabling REST to SOAP sample gives an error

2017-11-11 Thread Vijitha Ekanayake

[+ dev@wso2.org]

On Fri, Nov 10, 2017 at 5:04 PM, Vijitha Ekanayake 
wrote:

> Hi Buddhimala,
>
> The reason for the issue seems to be, ESB is preserving the Content-Type
> header as the default behavior. Since GET request doesn't have a
> Content-Type, ESB sends application/x-www-form-urlencoded as the
> Content-Type to the backend which is the reason for this failure. To
> overcome this issue you can comment out the following parameter in the
> passthru-http.properties.
>
> http.headers.preserve=Content-Type
>
> Thanks,
> Vijitha.
>
>
> On Fri, Nov 10, 2017 at 4:29 PM, Buddhimala Ranasinghe <
> buddhim...@wso2.com> wrote:
>
>> Hi All,
>>
>> Today I tried out "Enabling REST to SOAP" sample in ESB as per the
>> following wso2 document.
>>
>> https://docs.wso2.com/display/ESB500/Configuring+Specific+Us
>> e+Cases#ConfiguringSpecificUseCases-EnablingRESTtoSOAP
>>
>> But when I tried to invoke the API using the curl command, I got
>> following error.
>>
>> The endpoint reference (EPR) for the Operation not found is
>> /services/SimpleStockQuoteService and the WSA Action = null. If this EPR
>> was previously reachable, please contact the server
>> administrator.
>>
>> And the axis2 server side it gave the following error.
>>
>> [2017-11-10 16:25:33,268] ERROR {org.apache.axis2.engine.AxisEngine} -
>> The endpoint reference (EPR) for the Operation not found is
>> /services/SimpleStockQuoteService and the WSA Action = null. If this EPR
>> was previously reachable, please contact the server administrator.
>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>> Operation not found is /services/SimpleStockQuoteService and the WSA
>> Action = null. If this EPR was previously reachable, please contact the
>> server administrator.
>> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(Di
>> spatchPhase.java:102)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngi
>> ne(RESTUtil.java:144)
>> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequ
>> est(RESTUtil.java:89)
>> at org.apache.synapse.transport.nhttp.util.RESTUtil.processPOST
>> Request(RESTUtil.java:213)
>> at org.apache.synapse.transport.nhttp.ServerWorker.processEntit
>> yEnclosingMethod(ServerWorker.java:468)
>> at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWo
>> rker.java:291)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>> [2017-11-10 16:25:33,270] ERROR 
>> {org.apache.synapse.transport.nhttp.ServerWorker}
>> -  Error processing POST request
>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>> Operation not found is /services/SimpleStockQuoteService and the WSA
>> Action = null. If this EPR was previously reachable, please contact the
>> server administrator.
>> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(Di
>> spatchPhase.java:102)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngi
>> ne(RESTUtil.java:144)
>> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequ
>> est(RESTUtil.java:89)
>> at org.apache.synapse.transport.nhttp.util.RESTUtil.processPOST
>> Request(RESTUtil.java:213)
>> at org.apache.synapse.transport.nhttp.ServerWorker.processEntit
>> yEnclosingMethod(ServerWorker.java:468)
>> at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWo
>> rker.java:291)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>>
>> Please help to resolve.
>>
>> Regards,
>> Buddhimala
>> --
>>
>>
>> *Buddhimala Ranasinghe*
>> Software Engineer-Support Team | WSO2
>> Emil: buddhim...@wso2.com
>> Mobile:+94771563138 <+94%2077%20156%203138>
>> Web:http://wso2.com
>> [image: https://wso2.com/signature] 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vijitha Ekanayake
> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39

Re: [Dev] Exception with header

Re: [Dev] API gives "SOAP Envelope can not have children other than SOAP Header and Body" Exception

Re: [Dev] Exception with header

[Dev] API gives "SOAP Envelope can not have children other than SOAP Header and Body" Exception

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

Re: [Dev] Exception with header

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

Re: [Dev] Exception with header

Re: [Dev] [IS] Multiple stubs version in 5.4.0 pack

Re: [Dev] Exception with header

Re: [Dev] Exception in ESB 5.0.0 while creating an API.

[Dev] Exception in ESB 5.0.0 while creating an API.

Re: [Dev] CSRF token error in working with EI Management Console with Java 1.8.0_151

Re: [Dev] Exception when Publishing API in API Manager 2.1.0

Re: [Dev] Exception while invoking proxy service in ESB 5.0.0

Re: [Dev] Enabling REST to SOAP sample gives an error

18 matches

Site Navigation

Mail list logo

Footer information