Re: [Dev] [DEV] How to generate an invoice based on the usage of commercial APIs

[Rukshan Premathunga]

Hi Sashika,

Can you please check on private browser? And also please check das rest api
configurations in the billing engine.

Thanks and Regards

On 1 Dec 2017 11:10 am, "Sashika Wijesinghe"  wrote:

> Hi All,
>
> I have tried this sample several times by following the steps in the
> documentation. (Deployed the war as a web application in APIM server itself
> as well) but invoice generation failed with the same error 
> (*java.lang.**IllegalArgumentException:
> attempt to create create event with null entity*).
>
> Any suggestion to solve this issue is highly appreciated.
>
> Regards,
> Sashika
>
> On Wed, Nov 29, 2017 at 10:44 PM, Irham Iqbal  wrote:
>
>> Hi Sashika,
>>
>> I recently tried the billing engine war by deploying it on APIM 2.1.0 it
>> self, it worked for me without any issue.
>>
>> Thanks,
>> Iqbal
>>
>> On Wed, Nov 29, 2017 at 5:08 PM, Sashika Wijesinghe 
>> wrote:
>>
>>> Hi Rukshan,
>>>
>>> Thanks for the quick response. I have used the billing engine version
>>> linked in the APIM documentation (1.2.0).
>>>
>>> Further, I have tried with the artefacts you shared in [1] but still
>>> getting the same issue even after manually executing all the available
>>> analytics scripts.
>>>
>>> Attached the tomcat logs and application logs.
>>>
>>> Thanks
>>> Sashika
>>>
>>>
>>> [1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0
>>>
>>> On Wed, Nov 29, 2017 at 2:39 PM, Rukshan Premathunga 
>>> wrote:
>>>
 Hi Sashika,

 Which billing engine version did you check? Can you check on the
 following[1] if not already. *invoice* table is empty because invoice
 generation is failed. Also in the billing capp, it take time to generate
 summary tables and please wait bit longer or execute the script manually to
 generate data. If you observed this again, can you please attached the full
 log as well?

 [1] https://github.com/ruks/wso2-am-billing-engine/releases/
 tag/am-2.1.0

 Thanks and Regards

 On Wed, Nov 29, 2017 at 2:14 PM, Sashika Wijesinghe 
 wrote:

> Hi All,
>
> I have tried to generate an invoice for the monetized APIs as
> documented in [1].
>
> When I select the 'invoice' tab in the sample billing engine to
> generate the invoices observed the following error from the billing engine
> deployed in tomcat server.
>
> *HTTP Status 500 - Request processing failed; nested exception is
> org.springframework.webflow.execution.ActionExecutionException: Exception
> thrown executing [AnnotatedAction@3fa06082 targetAction =
> [EvaluateAction@274d6a91 expression = invoiceService.createInvoice(user),
> resultExpression = viewScope.invoice], attributes = map[[empty]]] in state
> 'invoiceHome' of flow 'account' -- action execution attributes were
> 'map[[empty]]'*
>
> After verifying the 'billing' database observed that there are
> no records in the "*invoice*" table.  However, as per the API
> statistics, there are 20 API calls for that particular API.
>
> May I know how to solve this issue?
>
>
> [1] https://docs.wso2.com/display/AM210/Enabling+Monetization+of+APIs
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>



 --
 Rukshan Chathuranga.
 Software Engineer.
 WSO2, Inc.
 +94711822074 <+94%2071%20182%202074>

>>>
>>>
>>>
>>> --
>>>
>>> *Sashika WijesingheSoftware Engineer - QA Team*
>>> Mobile : +94 (0) 774537487
>>> sash...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Irham Iqbal
>> Software Engineer
>> WSO2
>> phone: +94 777888452
>> 
>>
>>
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] How to generate an invoice based on the usage of commercial APIs

[Sashika Wijesinghe]

Hi All,

I have tried this sample several times by following the steps in the
documentation. (Deployed the war as a web application in APIM server itself
as well) but invoice generation failed with the same error
(*java.lang.**IllegalArgumentException:
attempt to create create event with null entity*).

Any suggestion to solve this issue is highly appreciated.

Regards,
Sashika

On Wed, Nov 29, 2017 at 10:44 PM, Irham Iqbal  wrote:

> Hi Sashika,
>
> I recently tried the billing engine war by deploying it on APIM 2.1.0 it
> self, it worked for me without any issue.
>
> Thanks,
> Iqbal
>
> On Wed, Nov 29, 2017 at 5:08 PM, Sashika Wijesinghe 
> wrote:
>
>> Hi Rukshan,
>>
>> Thanks for the quick response. I have used the billing engine version
>> linked in the APIM documentation (1.2.0).
>>
>> Further, I have tried with the artefacts you shared in [1] but still
>> getting the same issue even after manually executing all the available
>> analytics scripts.
>>
>> Attached the tomcat logs and application logs.
>>
>> Thanks
>> Sashika
>>
>>
>> [1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0
>>
>> On Wed, Nov 29, 2017 at 2:39 PM, Rukshan Premathunga 
>> wrote:
>>
>>> Hi Sashika,
>>>
>>> Which billing engine version did you check? Can you check on the
>>> following[1] if not already. *invoice* table is empty because invoice
>>> generation is failed. Also in the billing capp, it take time to generate
>>> summary tables and please wait bit longer or execute the script manually to
>>> generate data. If you observed this again, can you please attached the full
>>> log as well?
>>>
>>> [1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0
>>>
>>> Thanks and Regards
>>>
>>> On Wed, Nov 29, 2017 at 2:14 PM, Sashika Wijesinghe 
>>> wrote:
>>>
 Hi All,

 I have tried to generate an invoice for the monetized APIs as
 documented in [1].

 When I select the 'invoice' tab in the sample billing engine to
 generate the invoices observed the following error from the billing engine
 deployed in tomcat server.

 *HTTP Status 500 - Request processing failed; nested exception is
 org.springframework.webflow.execution.ActionExecutionException: Exception
 thrown executing [AnnotatedAction@3fa06082 targetAction =
 [EvaluateAction@274d6a91 expression = invoiceService.createInvoice(user),
 resultExpression = viewScope.invoice], attributes = map[[empty]]] in state
 'invoiceHome' of flow 'account' -- action execution attributes were
 'map[[empty]]'*

 After verifying the 'billing' database observed that there are
 no records in the "*invoice*" table.  However, as per the API
 statistics, there are 20 API calls for that particular API.

 May I know how to solve this issue?


 [1] https://docs.wso2.com/display/AM210/Enabling+Monetization+of+APIs


 --

 *Sashika WijesingheSoftware Engineer - QA Team*
 Mobile : +94 (0) 774537487
 sash...@wso2.com

>>>
>>>
>>>
>>> --
>>> Rukshan Chathuranga.
>>> Software Engineer.
>>> WSO2, Inc.
>>> +94711822074 <+94%2071%20182%202074>
>>>
>>
>>
>>
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Irham Iqbal
> Software Engineer
> WSO2
> phone: +94 777888452
> 
>
>


-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Stream Processor 4.0.0-beta2 Released!

[Ramindu De Silva]

Hi All,

The WSO2 Analytics team is pleased to announce the release of *WSO2 Stream
Processor Version 4.0.0 Beta2*.

WSO2 Analytics let digital business creating real-time, intelligent,
actionable business insights, and data products which are achieved by WSO2
Stream Processor's real-time, incremental & intelligent data processing
capabilities.

*WSO2 Stream Processor can*:

   - Receive events from various data sources
   - Process & correlate them in real-time with the state-of-the-art
   high-performance real-time Siddhi Complex Event Processing Engine that
   works with easy to learn the SQL-Like query language.
   - Conduct analysis that spans for longer time duration with its
   incremental processing capability by achieving high performance with low
   infrastructure cost.
   - Use Machine Learning to drive intelligent insights from the data
   - Notify interesting event occurrences as alerts via multiple types of
   transports & let users visualize the results via customizable dashboards.


WSO2 SP is released under Apache Software License Version 2.0, one of the
most business-friendly licenses available today.

   - You can find the product at
   
https://github.com/wso2/product-sp/releases/download/v4.0.0-beta2/wso2sp-4.0.0-beta2.zip
   - Documentation at https://docs.wso2.com/display/
   SP400/Introducing+the+Stream+Processor
   
   - Source code at https://github.com/wso2/product-sp

*WSO2 SP 4.0.0 Beta2 includes the following*

*Improvements*

   - Permission Model for Dashboard
   - Adding Error Pages for Dashboard
   - Localize error messages for Dashboard
   - Admin role identification improvement
   - Support for limit and order by.


*Bug fixes*

   - IdP bug fixes
   - Simulator bug fixes
   - RDBMS and incremental processor fixes
   - Bug fixes for status dashboard



*Reporting Issues *
Issues can be reported using the GitHub issue tracker available at
https://github.com/wso2/product-sp

*Contact us *

WSO2 Stream Processor developers can be contacted via the mailing lists:
Developer List: dev@wso2.org | Subscribe  | Mailing
List 

Alternatively, questions can also be raised in the Stackoverflow:
Forum http://stackoverflow.com/questwso2/

*Support*

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support.

For more information on WSO2 Smart Analytics and Smart Analytics Solutions,
visit the WSO2 Smart Analytics Page .

~ *The WSO2 Analytics Team* ~

Best Regards,
-- 
*Ramindu De Silva*
Software Engineer
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

email: ramin...@wso2.com 
mob: +94 719678895
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 IoT Server 3.1.0 UPDATE 8 released!

[Ruwan Yatawara]

WSO2 IoT Server 3.1.0 UPDATE 8

We are pleased to announce the latest update to WSO2 IoT Server 3.1.0

WSO2 IoT Server is one of the most adaptive Apache licensed open source IoT
platforms available today. It provides best of breed technologies for
device manufacturers to develop connected products as well as rich
integration and smart analytics capabilities for system integrators to
adopt devices into systems they build.

These capabilities involve device management, smart analytics, API and app
management for devices, transport extensions for MQTT, XMPP and many more.
What's new in WSO2 IoTS 3.1.0 Update 8

New Features & Bug Fixes: A list of new features and bug fixes shipped with
this release can be found here

Download

You can download WSO2 IoT Server 3.1.0-UPDATE8 from here

.
Documentation

Documentations: WSO2 IoT Server Documentation

Known Issues

The known set of issues in this version can be found here

Engaging with CommunityMailing Lists

Join our mailing list and correspondence with the developers directly.

Developer list: dev@wso2.org | Subscribe
 | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 IoT Server through WSO2 IoT GIT Issues
.
Discussion Forums

We encourage you to use stackoverflow

to
engage with developers as well as other users.

For more information about WSO2 IoT Server, please see
http://wso2.com/products/iot-server or visit the WSO2 Oxygen Tank
 developer portal for additional resources.

Thank you for your interest in WSO2 IoT Server.


*The WSO2 IoT Server Team*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Issue with Salesforce REST connector

[Lahiru Cooray]

Hi Rajith,
Thank you for the reply but I'm using 'init for username password flow'
mentioned in [1]


[1]
https://docs.wso2.com/display/ESBCONNECTORS/Configuring+Salesforce+Operations

On Fri, Dec 1, 2017 at 8:31 AM, Rajith Siriwardena  wrote:

>
> Hi Lahiru,
>
> Aren't you missing following init properties.
>
>- ​​
>intervalTime: The Interval time in milliseconds to check the access
>token validity.
>- registryPath: Registry path of the connector where the values are
>stored. You must give the value as : connectors/
>​.​
>​
>For example: registryPath = "connectors/salesforcerest".
>
>
> ​Thanks,
> Rajith​
>
>
> [1] https://docs.wso2.com/display/ESBCONNECTORS/Configuring+
> Salesforce+Operations
>
> On Thu, Nov 30, 2017 at 12:56 PM, Lahiru Cooray 
> wrote:
>
>> Hi team,
>> Im using ESB Salesforce REST connector to performce some operations in SF.
>>
>> http://ws.apache.org/ns/synapse"; name="sendOrder"
>> context="/sendOrder">
>>
>>   
>>  
>> https://ap5.salesforce.com/
>> XXX
>> XXX
>> https://login.salesforce.com
>> XXX
>> X
>> XX
>>  
>>  
>>  
>> 5
>>  
>>  
>>  
>>   
>>   
>>  
>>   
>>
>> 
>>
>> Init get succeeded but the subsequent API calls get failed saying that
>> the session is invalid.
>>{
>> "message": "Session expired or invalid",
>> "errorCode": "INVALID_SESSION_ID"
>> }
>>
>> I tried to revoke the access token and generating a new one but still I
>> face the same issue. highly appreciate your suggestions on this.
>>
>>
>>
>> 7-12-01 00:14:47,172]  INFO - LogMediator To:
>> http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction:
>> , MessageID: urn:uuid:076481b3-c1f0-4663-a19f-511f2ecd0eee, Direction:
>> request, Payload: {"access_token":"XXX!XX","instance_url":"
>> https://cs58.salesforce.com","id":"https://te
>> st.salesforce.com/id/00D0l0340CrhxEAC/005546F05kaBGQAY
>> ","token_type":"Bearer","issued_at":"XXX","signature":"
>> X+z6HbpWvod+4DUI="}
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "GET //services/data/v40.0/theme HTTP/1.1[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Authorization: Bearer  !XX[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Strict-Transport-Security: max-age=31536000; includeSubDomains[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "X-ReadOnlyMode: false[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Cache-Control: no-cache,must-revalidate,max-a
>> ge=0,no-store,private[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "X-Content-Type-Options: nosniff[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Content-Security-Policy: upgrade-insecure-requests[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Set-Cookie: BrowserId=9efBu0mDTIWX7as_4T0ihA;Path=/;Domain=.salesforce.
>> com;Expires=Mon, 29-Jan-2018 18:44:46 GMT;Max-Age=5184000[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Vary: Accept-Encoding[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Expires: Thu, 01 Jan 1970 00:00:00 GMT[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "X-XSS-Protection: 1; mode=block[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Content-Type: application/json;charset=UTF-8[\r][\n]"
>> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Host: ap5.salesforce.com[\r][\n]"
>> [2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "Connection: Keep-Alive[\r][\n]"
>> [2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
>> [2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
>> "[\r][\n]"
>> [2017-12-01 00:14:47,560] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
>> "HTTP/1.1 401 Unauthorized[\r][\n]"
>> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
>> "Date: Thu, 30 Nov 2017 18:44:47 GMT[\r][\n]"
>> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
>> "Strict-Transport-Security: max-age=31536000; includeSubDomains[\r][\n]"
>> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
>> "X-Content-Type-Options: nosniff[\r][\n]"
>> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
>> "X-XSS-Protection: 1; mode=block[\r][\n]"
>> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
>> "Content-Security

Re: [Dev] [MSF4J] Swagger annotation support in MSF4J 2.4.2

[Pubudu D.P]

Thanks, Azeez,

Got it working on the new version now.

Cheers,
Pubudu.

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

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


On Thu, Nov 30, 2017 at 10:58 PM, Afkham Azeez  wrote:

> msf4j-swagger has been separated to make the size smaller so you have to
> now import that. Take a look at the StockQuote sample.
>
> On Thu, Nov 30, 2017 at 7:41 PM, Pubudu D.P  wrote:
>
>> Hi all,
>>
>> Earlier I developed a microservice using MSF4J with Swagger annotations
>> to add API documentation using msf4j 2.0.0. I have now upgraded the version
>> to 2.4.2 and I am getting the following error when I am trying to build the
>> project. I have imported all the dependencies etc.
>>
>>
>> -
>> Error:
>>
>>   cannot find symbol
>> [ERROR] symbol: class SwaggerDefinition
>>  cannot find symbol
>> [ERROR] symbol: class Api
>>  cannot find symbol
>> [ERROR] symbol:   class ApiOperation
>>
>> -
>>
>> Is there anything we should do to get this working with msf4j 2.4.2?
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547 <077%20546%204547>
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>
>
> --
> *Afkham Azeez*
> Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <+94%2077%20332%200919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Issue with Salesforce REST connector

[Rajith Siriwardena]

Hi Lahiru,

Aren't you missing following init properties.

   - ​​
   intervalTime: The Interval time in milliseconds to check the access
   token validity.
   - registryPath: Registry path of the connector where the values are
   stored. You must give the value as : connectors/
   ​.​
   ​
   For example: registryPath = "connectors/salesforcerest".


​Thanks,
Rajith​


[1] https://docs.wso2.com/display/ESBCONNECTORS/Configuring+Salesforce+
Operations

On Thu, Nov 30, 2017 at 12:56 PM, Lahiru Cooray 
wrote:

> Hi team,
> Im using ESB Salesforce REST connector to performce some operations in SF.
>
> http://ws.apache.org/ns/synapse"; name="sendOrder"
> context="/sendOrder">
>
>   
>  
> https://ap5.salesforce.com/
> XXX
> XXX
> https://login.salesforce.com
> XXX
> X
> XX
>  
>  
>  
> 5
>  
>  
>  
>   
>   
>  
>   
>
> 
>
> Init get succeeded but the subsequent API calls get failed saying that the
> session is invalid.
>{
> "message": "Session expired or invalid",
> "errorCode": "INVALID_SESSION_ID"
> }
>
> I tried to revoke the access token and generating a new one but still I
> face the same issue. highly appreciate your suggestions on this.
>
>
>
> 7-12-01 00:14:47,172]  INFO - LogMediator To: http://www.w3.org/2005/08/
> addressing/anonymous, WSAction: , SOAPAction: , MessageID:
> urn:uuid:076481b3-c1f0-4663-a19f-511f2ecd0eee, Direction: request,
> Payload: {"access_token":"XXX!XX","instance_url":"https://cs58.
> salesforce.com","id":"https://test.salesforce.com/id/00D0l0340CrhxEAC/
> 005546F05kaBGQAY","token_type":"Bearer","issued_at":"
> XXX","signature":"X+z6HbpWvod+4DUI="}
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "GET //services/data/v40.0/theme HTTP/1.1[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Authorization: Bearer  !XX[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Strict-Transport-Security: max-age=31536000; includeSubDomains[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "X-ReadOnlyMode: false[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Cache-Control: no-cache,must-revalidate,max-
> age=0,no-store,private[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "X-Content-Type-Options: nosniff[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Content-Security-Policy: upgrade-insecure-requests[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Set-Cookie: BrowserId=9efBu0mDTIWX7as_4T0ihA;Path=/;Domain=.salesfor
> ce.com;Expires=Mon, 29-Jan-2018 18:44:46 GMT;Max-Age=5184000[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Vary: Accept-Encoding[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Expires: Thu, 01 Jan 1970 00:00:00 GMT[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "X-XSS-Protection: 1; mode=block[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Content-Type: application/json;charset=UTF-8[\r][\n]"
> [2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Host: ap5.salesforce.com[\r][\n]"
> [2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "Connection: Keep-Alive[\r][\n]"
> [2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
> [2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
> "[\r][\n]"
> [2017-12-01 00:14:47,560] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
> "HTTP/1.1 401 Unauthorized[\r][\n]"
> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
> "Date: Thu, 30 Nov 2017 18:44:47 GMT[\r][\n]"
> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
> "Strict-Transport-Security: max-age=31536000; includeSubDomains[\r][\n]"
> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
> "X-Content-Type-Options: nosniff[\r][\n]"
> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
> "X-XSS-Protection: 1; mode=block[\r][\n]"
> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
> "Content-Security-Policy: upgrade-insecure-requests [\r][\n]"
> [2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
> "Cache-Control: no-cache,must-revalidate,max-
> age=0,no-store,private[\r][\n]"
> [2017-12-01 00:14:47,562] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
> "Set-Cookie: BrowserId=nrfXAmi3RPidZl2vKAAAiA;Path=/;Domain=.
> salesforce.com;Expires=Mon, 29-Jan-2018 18:

[Dev] [IS 5.3.0] Secondary LDAP User Store Properties - DNSUrl and DnsDomain

[Vazquez-Hidalgo, Javier]

Hello,

When configuring a secondary LDAP user store I see (in the carbon kernel source 
code)  that there are two properties named "URLOfDNS" and "DNSDomainName", can 
someone explain how they work together and under which circumstances is 
recommended to set these properties.

https://svn.wso2.org/repos/wso2/carbon/kernel/tags/4.2.0/core/org.wso2.carbon.user.core/4.2.0/src/main/java/org/wso2/carbon/user/core/ldap/LDAPConnectionContext.java


Thanks,
Javier Vazquez


If you wish to unsubscribe from receiving commercial electronic messages from 
TD Bank Group, please click here or go to the following web address: 
www.td.com/tdoptout
Si vous souhaitez vous désabonner des messages électroniques de nature 
commerciale envoyés par Groupe Banque TD veuillez cliquer ici ou vous rendre à 
l'adresse www.td.com/tddesab

NOTICE: Confidential message which may be privileged. Unauthorized 
use/disclosure prohibited. If received in error, please go to www.td.com/legal 
for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié. 
Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière 
d'aller au www.td.com/francais/avis_juridique pour des instructions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Issue with Salesforce REST connector

[Lahiru Cooray]

Hi team,
Im using ESB Salesforce REST connector to performce some operations in SF.

http://ws.apache.org/ns/synapse"; name="sendOrder"
context="/sendOrder">
   
  
 
https://ap5.salesforce.com/
XXX
XXX
https://login.salesforce.com
XXX
X
XX
 
 
 
5
 
 
 
  
  
 
  
   


Init get succeeded but the subsequent API calls get failed saying that the
session is invalid.
   {
"message": "Session expired or invalid",
"errorCode": "INVALID_SESSION_ID"
}

I tried to revoke the access token and generating a new one but still I
face the same issue. highly appreciate your suggestions on this.



7-12-01 00:14:47,172]  INFO - LogMediator To:
http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: ,
MessageID: urn:uuid:076481b3-c1f0-4663-a19f-511f2ecd0eee, Direction:
request, Payload: {"access_token":"XXX!XX","instance_url":"
https://cs58.salesforce.com","id":";
https://test.salesforce.com/id/00D0l0340CrhxEAC/005546F05kaBGQAY
","token_type":"Bearer","issued_at":"XXX","signature":"X+z6HbpWvod+4DUI="}
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"GET //services/data/v40.0/theme HTTP/1.1[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Authorization: Bearer  !XX[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Strict-Transport-Security: max-age=31536000; includeSubDomains[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"X-ReadOnlyMode: false[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Cache-Control: no-cache,must-revalidate,max-age=0,no-store,private[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"X-Content-Type-Options: nosniff[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Content-Security-Policy: upgrade-insecure-requests[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Set-Cookie: 
BrowserId=9efBu0mDTIWX7as_4T0ihA;Path=/;Domain=.salesforce.com;Expires=Mon,
29-Jan-2018 18:44:46 GMT;Max-Age=5184000[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Vary: Accept-Encoding[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Expires: Thu, 01 Jan 1970 00:00:00 GMT[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"X-XSS-Protection: 1; mode=block[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Content-Type: application/json;charset=UTF-8[\r][\n]"
[2017-12-01 00:14:47,174] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Host: ap5.salesforce.com[\r][\n]"
[2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"Connection: Keep-Alive[\r][\n]"
[2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2017-12-01 00:14:47,175] DEBUG - wire HTTPS-Sender I/O dispatcher-2 <<
"[\r][\n]"
[2017-12-01 00:14:47,560] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"HTTP/1.1 401 Unauthorized[\r][\n]"
[2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Date: Thu, 30 Nov 2017 18:44:47 GMT[\r][\n]"
[2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Strict-Transport-Security: max-age=31536000; includeSubDomains[\r][\n]"
[2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"X-Content-Type-Options: nosniff[\r][\n]"
[2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"X-XSS-Protection: 1; mode=block[\r][\n]"
[2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Content-Security-Policy: upgrade-insecure-requests [\r][\n]"
[2017-12-01 00:14:47,561] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Cache-Control: no-cache,must-revalidate,max-age=0,no-store,private[\r][\n]"
[2017-12-01 00:14:47,562] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Set-Cookie: 
BrowserId=nrfXAmi3RPidZl2vKAAAiA;Path=/;Domain=.salesforce.com;Expires=Mon,
29-Jan-2018 18:44:47 GMT;Max-Age=5184000[\r][\n]"
[2017-12-01 00:14:47,562] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Expires: Thu, 01 Jan 1970 00:00:00 GMT[\r][\n]"
[2017-12-01 00:14:47,562] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"WWW-Authenticate: Token[\r][\n]"
[2017-12-01 00:14:47,562] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Content-Type: application/json;charset=UTF-8[\r][\n]"
[2017-12-01 00:14:47,562] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"Transfer-Encoding: chunked[\r][\n]"
[2017-12-01 00:14:47,562] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"[\r][\n]"
[2017-12-01 00:14:47,562] DEBUG - wire HTTPS-Sender I/O dispatcher-2 >>
"4B[\r][\n]"
[2017-12-01 00:14:47,563] DEBUG - wire HTTPS

Re: [Dev] [MSF4J] Swagger annotation support in MSF4J 2.4.2

[Afkham Azeez]

msf4j-swagger has been separated to make the size smaller so you have to
now import that. Take a look at the StockQuote sample.

On Thu, Nov 30, 2017 at 7:41 PM, Pubudu D.P  wrote:

> Hi all,
>
> Earlier I developed a microservice using MSF4J with Swagger annotations to
> add API documentation using msf4j 2.0.0. I have now upgraded the version to
> 2.4.2 and I am getting the following error when I am trying to build the
> project. I have imported all the dependencies etc.
>
>
> -
> Error:
>
>   cannot find symbol
> [ERROR] symbol: class SwaggerDefinition
>  cannot find symbol
> [ERROR] symbol: class Api
>  cannot find symbol
> [ERROR] symbol:   class ApiOperation
>
> -
>
> Is there anything we should do to get this working with msf4j 2.4.2?
>
> Cheers,
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547 <077%20546%204547>
>
> Linkedin: https://uk.linkedin.com/in/pubududp
> Medium: https://medium.com/@pubududp
>
>


-- 
*Afkham Azeez*
Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

[Dev] WSO2 API Manager 3.0.0-M8 Released!

[Tharindu Dharmarathna]

The WSO2 API Manager team is pleased to announce the release of API Manager
3.0.0-M8. It's now available to download.
Distribution

   -
   
https://github.com/wso2/product-apim/releases/download/v3.0.0-m8/wso2apim-3.0.0-m8.zip
   -
   
https://github.com/wso2/product-apim/releases/download/v3.0.0-m8/wso2apim-gateway-3.0.0-m8.zip
   -
   
https://github.com/wso2/product-apim/releases/download/v3.0.0-m8/wso2apim-das-3.0.0-m8.zip

Documentation

   - https://docs.wso2.com/display/AM300/

Following list contains all the features, improvements and bug fixes
available with this milestone.
New Feature

   -


   
https://github.com/wso2/product-apim/issues?q=label%3A3.0.0+milestone%3A3.0.0-m8+is%3Aclosed+label%3A%22Type%2FNew+Feature%22

Tasks/Bug Fixes and Improvements

   -


   
https://github.com/wso2/product-apim/issues?q=label%3A3.0.0+milestone%3A3.0.0-m8+is%3Aclosed+label%3AType%2FBug

List of Open Issues

   - https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%
   3Aissue+label%3A3.0.0+label%3AType%2FBug
   

   - https://github.com/wso2/carbon-apimgt/issues?q=is%3Aopen+is%
   3Aissue+label%3A3.0.0
   


How To Contribute

Your feedback is most welcome!
Mailing Lists

   - Join our mailing list and correspond with the developers directly.

Developer List : dev@wso2.org | Subscribe | Mail Archive


   - User Forum : StackOverflow
   

Reporting Issues

We encourage you to report issues, improvements and feature requests
regarding WSO2 API Manager through WSO2 API Manager GIT Issues
.

~ WSO2 API Manager Team ~

Thanks

*Tharindu Dharmarathna*Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [DEV] How to generate an invoice based on the usage of commercial APIs

[Jorge]

Hi Sashika.
I found several issues related with the sample billing in WSO2 AM 2.1.0,
checkout this issue [1]

Try with the tag am-2.1.0 suggested by Rukshan.

In my scenario it work for users previous created in the billing systema.
For the new users I need to re subscribe to the application inside the
store.

Regards,
Jorge.

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




2017-11-29 6:38 GMT-05:00 Sashika Wijesinghe :

> Hi Rukshan,
>
> Thanks for the quick response. I have used the billing engine version
> linked in the APIM documentation (1.2.0).
>
> Further, I have tried with the artefacts you shared in [1] but still
> getting the same issue even after manually executing all the available
> analytics scripts.
>
> Attached the tomcat logs and application logs.
>
> Thanks
> Sashika
>
>
> [1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0
>
> On Wed, Nov 29, 2017 at 2:39 PM, Rukshan Premathunga 
> wrote:
>
>> Hi Sashika,
>>
>> Which billing engine version did you check? Can you check on the
>> following[1] if not already. *invoice* table is empty because invoice
>> generation is failed. Also in the billing capp, it take time to generate
>> summary tables and please wait bit longer or execute the script manually to
>> generate data. If you observed this again, can you please attached the full
>> log as well?
>>
>> [1] https://github.com/ruks/wso2-am-billing-engine/releases/tag/am-2.1.0
>>
>> Thanks and Regards
>>
>> On Wed, Nov 29, 2017 at 2:14 PM, Sashika Wijesinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tried to generate an invoice for the monetized APIs as documented
>>> in [1].
>>>
>>> When I select the 'invoice' tab in the sample billing engine to generate
>>> the invoices observed the following error from the billing engine deployed
>>> in tomcat server.
>>>
>>> *HTTP Status 500 - Request processing failed; nested exception is
>>> org.springframework.webflow.execution.ActionExecutionException: Exception
>>> thrown executing [AnnotatedAction@3fa06082 targetAction =
>>> [EvaluateAction@274d6a91 expression = invoiceService.createInvoice(user),
>>> resultExpression = viewScope.invoice], attributes = map[[empty]]] in state
>>> 'invoiceHome' of flow 'account' -- action execution attributes were
>>> 'map[[empty]]'*
>>>
>>> After verifying the 'billing' database observed that there are
>>> no records in the "*invoice*" table.  However, as per the API
>>> statistics, there are 20 API calls for that particular API.
>>>
>>> May I know how to solve this issue?
>>>
>>>
>>> [1] https://docs.wso2.com/display/AM210/Enabling+Monetization+of+APIs
>>>
>>>
>>> --
>>>
>>> *Sashika WijesingheSoftware Engineer - QA Team*
>>> Mobile : +94 (0) 774537487
>>> sash...@wso2.com
>>>
>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>> +94711822074 <+94%2071%20182%202074>
>>
>
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [MSF4J] Swagger annotation support in MSF4J 2.4.2

[Pubudu D.P]

Hi all,

Earlier I developed a microservice using MSF4J with Swagger annotations to
add API documentation using msf4j 2.0.0. I have now upgraded the version to
2.4.2 and I am getting the following error when I am trying to build the
project. I have imported all the dependencies etc.


-
Error:

  cannot find symbol
[ERROR] symbol: class SwaggerDefinition
 cannot find symbol
[ERROR] symbol: class Api
 cannot find symbol
[ERROR] symbol:   class ApiOperation

-

Is there anything we should do to get this working with msf4j 2.4.2?

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

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Gateway worker node gives org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.jms.JMSSender cannot be found by axis2_1.6.1.wso2v20

[Maneesha Wijesekara]

Hi Dushantha,

Can you try by commenting below line in axis2_blocking_client.xml inside
/repository/conf/axis2 folder ?



Regards
Maneesha

On Thu, Nov 30, 2017 at 3:21 PM, Dushantha Batuwita 
wrote:

> Hi Rukshan
>
> I checked the configuration again and yes I have disabled the 
> *JMSEventPublisherParameters
> *in Gateway Nodes.
>
> Stille the error mentioned above comes when GW worker is attempting to run.
>
> Regards
>
> On Thu, Nov 30, 2017 at 3:06 PM, Rukshan Premathunga 
> wrote:
>
>> Hi Dushantha,
>>
>> Did you disable the *JMSEventPublisherParameters* configuration from the
>> api-manager.xml?
>>
>> Thanks and Regards
>>
>> On Thu, Nov 30, 2017 at 2:59 PM, Dushantha Batuwita 
>> wrote:
>>
>>> Hi  Dev
>>>
>>> I'm involved in developing a Gateway cluster and the particulars  are as
>>> follows
>>>
>>>
>>>- Cluster is developed in the local machine
>>>- consists of two Gateway Nodes
>>>- One is a* Gateway worker offset by 3*
>>>- Other is a *Gateway worker and Manager* *offset by 2*
>>>- Those nodes are fronted by LB
>>>
>>>
>>>I have started the IS as *KM, PubstoreTraficManager,
>>>GatewayWorkerManager* nodes without an error
>>>But when try starting the* Gateway Worker *node I receive an error
>>>similar to one bellow.
>>>
>>>
>>>  ERROR - BasicAuthEntitlementServiceClient Error initializing Axis2
>>> configuration context
>>> org.apache.axis2.deployment.DeploymentException:
>>> org.apache.axis2.transport.jms.JMSSender cannot be found by
>>> axis2_1.6.1.wso2v20
>>> 
>>> 
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.apache.axis2.transport.jms.JMSSender cannot be found by
>>> axis2_1.6.1.wso2v20
>>>
>>> If you have any advice to avoid this error, I would be much grateful.
>>>
>>> Regards
>>> --
>>> *Dushantha Nayanajith Chandima Batuwita*
>>> Software Engineer Support | WSO2
>>> dushan...@wso2.com
>>> mobile : 0094777453010
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>> +94711822074 <+94%2071%20182%202074>
>>
>
>
>
> --
> *Dushantha Nayanajith Chandima Batuwita*
> Software Engineer Support | WSO2
> dushan...@wso2.com
> mobile : 0094777453010
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Maneesha Wijesekara
Software Engineer - QA Team
WSO2 Inc.

Email: manee...@wso2.com
Linkedin: http://linkedin.com/in/maneeshawijesekara
Mobile: +94712443119
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Gateway worker node gives org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.jms.JMSSender cannot be found by axis2_1.6.1.wso2v20

[Dushantha Batuwita]

Hi Rukshan

I checked the configuration again and yes I have disabled the
*JMSEventPublisherParameters
*in Gateway Nodes.

Stille the error mentioned above comes when GW worker is attempting to run.

Regards

On Thu, Nov 30, 2017 at 3:06 PM, Rukshan Premathunga 
wrote:

> Hi Dushantha,
>
> Did you disable the *JMSEventPublisherParameters* configuration from the
> api-manager.xml?
>
> Thanks and Regards
>
> On Thu, Nov 30, 2017 at 2:59 PM, Dushantha Batuwita 
> wrote:
>
>> Hi  Dev
>>
>> I'm involved in developing a Gateway cluster and the particulars  are as
>> follows
>>
>>
>>- Cluster is developed in the local machine
>>- consists of two Gateway Nodes
>>- One is a* Gateway worker offset by 3*
>>- Other is a *Gateway worker and Manager* *offset by 2*
>>- Those nodes are fronted by LB
>>
>>
>>I have started the IS as *KM, PubstoreTraficManager,
>>GatewayWorkerManager* nodes without an error
>>But when try starting the* Gateway Worker *node I receive an error
>>similar to one bellow.
>>
>>
>>  ERROR - BasicAuthEntitlementServiceClient Error initializing Axis2
>> configuration context
>> org.apache.axis2.deployment.DeploymentException:
>> org.apache.axis2.transport.jms.JMSSender cannot be found by
>> axis2_1.6.1.wso2v20
>> 
>> 
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.axis2.transport.jms.JMSSender cannot be found by
>> axis2_1.6.1.wso2v20
>>
>> If you have any advice to avoid this error, I would be much grateful.
>>
>> Regards
>> --
>> *Dushantha Nayanajith Chandima Batuwita*
>> Software Engineer Support | WSO2
>> dushan...@wso2.com
>> mobile : 0094777453010
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
> +94711822074 <+94%2071%20182%202074>
>



-- 
*Dushantha Nayanajith Chandima Batuwita*
Software Engineer Support | WSO2
dushan...@wso2.com
mobile : 0094777453010
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Gateway worker node gives org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.jms.JMSSender cannot be found by axis2_1.6.1.wso2v20

[Rukshan Premathunga]

Hi Dushantha,

Did you disable the *JMSEventPublisherParameters* configuration from the
api-manager.xml?

Thanks and Regards

On Thu, Nov 30, 2017 at 2:59 PM, Dushantha Batuwita 
wrote:

> Hi  Dev
>
> I'm involved in developing a Gateway cluster and the particulars  are as
> follows
>
>
>- Cluster is developed in the local machine
>- consists of two Gateway Nodes
>- One is a* Gateway worker offset by 3*
>- Other is a *Gateway worker and Manager* *offset by 2*
>- Those nodes are fronted by LB
>
>
>I have started the IS as *KM, PubstoreTraficManager,
>GatewayWorkerManager* nodes without an error
>But when try starting the* Gateway Worker *node I receive an error
>similar to one bellow.
>
>
>  ERROR - BasicAuthEntitlementServiceClient Error initializing Axis2
> configuration context
> org.apache.axis2.deployment.DeploymentException:
> org.apache.axis2.transport.jms.JMSSender cannot be found by
> axis2_1.6.1.wso2v20
> 
> 
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.axis2.transport.jms.JMSSender
> cannot be found by axis2_1.6.1.wso2v20
>
> If you have any advice to avoid this error, I would be much grateful.
>
> Regards
> --
> *Dushantha Nayanajith Chandima Batuwita*
> Software Engineer Support | WSO2
> dushan...@wso2.com
> mobile : 0094777453010
>
> ___
> 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

[Dev] Gateway worker node gives org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.jms.JMSSender cannot be found by axis2_1.6.1.wso2v20

[Dushantha Batuwita]

Hi  Dev

I'm involved in developing a Gateway cluster and the particulars  are as
follows


   - Cluster is developed in the local machine
   - consists of two Gateway Nodes
   - One is a* Gateway worker offset by 3*
   - Other is a *Gateway worker and Manager* *offset by 2*
   - Those nodes are fronted by LB


   I have started the IS as *KM, PubstoreTraficManager,
   GatewayWorkerManager* nodes without an error
   But when try starting the* Gateway Worker *node I receive an error
   similar to one bellow.


 ERROR - BasicAuthEntitlementServiceClient Error initializing Axis2
configuration context
org.apache.axis2.deployment.DeploymentException:
org.apache.axis2.transport.jms.JMSSender cannot be found by
axis2_1.6.1.wso2v20


Caused by: java.lang.ClassNotFoundException:
org.apache.axis2.transport.jms.JMSSender cannot be found by
axis2_1.6.1.wso2v20

If you have any advice to avoid this error, I would be much grateful.

Regards
-- 
*Dushantha Nayanajith Chandima Batuwita*
Software Engineer Support | WSO2
dushan...@wso2.com
mobile : 0094777453010
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shouldnt we validate issuer id among users in service providers?

[Ishara Karunarathna]

On Thu, Nov 30, 2017 at 1:50 PM, Ushani Balasooriya  wrote:

> Wum updated pack*
>

Can you please re try this.
I just checked the WUM updated pack and didn't see that issue and recently
we didn't change anything in that areas so it should not break in 27 wum as
well.

-Ishara

>
> On 30 Nov 2017 1:31 pm, "Ushani Balasooriya"  wrote:
>
>> Hi Ishara,
>>
>> 27th Nov win updated pack allowed to add sp with same issuer id.
>>
>> On 30 Nov 2017 10:36 am, "Ishara Karunarathna"  wrote:
>>
>>> Hi Ushani,
>>>
>>> How did you test this scenarios. It does not allow to register two SPs
>>> with same issuer id.
>>>
>>> -Ishara
>>>
>>> On Thu, Nov 30, 2017 at 8:22 AM, Ushani Balasooriya 
>>> wrote:
>>>
 Hi IAM team,

 Please consider the below scenario.

 When I think of a system as an admin and developer personas in a same
 tenant,

 1. Admin registers a service provider as *travelocity* with issuer id
 as *travelocity.com * and assertion consumer
 url as http://localhost:8080/travelocity.com/home.jsp and configure
 Federated IDP as Google

 2. Then developer persona registers a service provider as *travelocity.com
 *  with same issuer id as *travelocity.com
 * and assertion consumer url as
 http://localhost:8080/travelocity.com/home.jsp since it does not
 validate issuer id and configure federated IDP as facebook.

 In this scenario, only the *service provider name* will be *validated*
 and *issuer id* will *not be validated.*

 Therefore when we try to access service provider, it will federate only
 through google.

 This is a very rare negative use case, but when you think of different
 personas, I think this should be considered.

 Please correct me if I am wrong.

 Thanks,
 --
 *Ushani Balasooriya*
 Associate Technical Lead - EE;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; +94772636796


>>>
>>>
>>> --
>>> Ishara Karunarathna
>>> Technical Lead
>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>
>>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>>> +94717996791 <+94%2071%20799%206791>
>>>
>>>
>>>


-- 
Ishara Karunarathna
Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [SP][Windows] Error during startup

[Danesh Kuruppu]

Thanks Gokul and Vidura for reviewing the PR.

We merged the fix and released carbon-config 4.1.5. Please check.

Regards
Danesh

On Wed, Nov 29, 2017 at 11:00 AM, Gokul Balakrishnan  wrote:

> Hi all,
>
> I was able to verify that the SP4 Beta pack starts up in Windows 7 without
> any issues with the fix applied. Thanks a lot Danesh for the quick
> resolution!
>
> Best,
>
> On 29 November 2017 at 09:41, Danesh Kuruppu  wrote:
>
>> Hi Gokul,
>>
>> Just checking whether you are able to test this fix in SP. If the fix is
>> ok, we can release new version with this fix.
>>
>> Thanks
>> Danesh
>>
>> On Fri, Nov 24, 2017 at 7:57 PM, Sriskandarajah Suhothayan > > wrote:
>>
>>> @Gokul also please test and verity whether it fixes in SP.
>>>
>>> On Fri, Nov 24, 2017 at 7:54 PM, Danesh Kuruppu  wrote:
>>>
 Hi Gokul,

 This Issue is fixed with PR[1]. Can you please test with new changes.
 @Kishanthan/Nira/Jayanga, please review and merge

 1. https://github.com/wso2/carbon-config/pull/62

 Thanks
 Danesh

 On Fri, Nov 24, 2017 at 5:19 AM, Gokul Balakrishnan 
 wrote:

> Hi,
>
> We're seeing the following error while starting up Stream Processor
> Alpha2/3 in Windows. The main reason appears to be the server failing to
> resolve the ${sys:carbon.home} properties in deployment.yaml:
>
> Bad pathname"; "E:wso2sp-4.0.0-Alpha3-SNAPSHO
> Tbin../wso2/editor/database/WSO2_CARBON_DB.mv.db"
>
> As you can see, the path delimiter ("\") is missing between the drive
> and the initial path elements.
>
> Opened [1] to track this issue. Could you please take a look since
> this is critical for us?
>
> [1] https://github.com/wso2/carbon-kernel/issues/1615
>
> Thanks,
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> M +94 77 5935 789 | +44 7563 570502 <+44%207563%20570502>
>
>


 --

 *Danesh Kuruppu*
 Senior Software Engineer | WSO2

 Email: dan...@wso2.com
 Mobile: +94 (77) 1690552 <077%20169%200552>
 Web: WSO2 Inc 


>>>
>>>
>>> --
>>>
>>> *S. Suhothayan*
>>> Associate Director / Architect
>>> *WSO2 Inc. *http://wso2.com
>>> * *
>>> lean . enterprise . middleware
>>>
>>>
>>> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
>>> http://suhothayan.blogspot.com/ twitter:
>>> http://twitter.com/suhothayan  | linked-in:
>>> http://lk.linkedin.com/in/suhothayan *
>>>
>>
>>
>>
>> --
>>
>> *Danesh Kuruppu*
>> Senior Software Engineer | WSO2
>>
>> Email: dan...@wso2.com
>> Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
>> Web: WSO2 Inc 
>>
>>
>
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> M +94 77 5935 789 | +44 7563 570502 <+44%207563%20570502>
>
>


-- 

*Danesh Kuruppu*
Senior Software Engineer | WSO2

Email: dan...@wso2.com
Mobile: +94 (77) 1690552
Web: WSO2 Inc 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shouldnt we validate issuer id among users in service providers?

[Ushani Balasooriya]

Wum updated pack*

On 30 Nov 2017 1:31 pm, "Ushani Balasooriya"  wrote:

> Hi Ishara,
>
> 27th Nov win updated pack allowed to add sp with same issuer id.
>
> On 30 Nov 2017 10:36 am, "Ishara Karunarathna"  wrote:
>
>> Hi Ushani,
>>
>> How did you test this scenarios. It does not allow to register two SPs
>> with same issuer id.
>>
>> -Ishara
>>
>> On Thu, Nov 30, 2017 at 8:22 AM, Ushani Balasooriya 
>> wrote:
>>
>>> Hi IAM team,
>>>
>>> Please consider the below scenario.
>>>
>>> When I think of a system as an admin and developer personas in a same
>>> tenant,
>>>
>>> 1. Admin registers a service provider as *travelocity* with issuer id
>>> as *travelocity.com * and assertion consumer
>>> url as http://localhost:8080/travelocity.com/home.jsp and configure
>>> Federated IDP as Google
>>>
>>> 2. Then developer persona registers a service provider as *travelocity.com
>>> *  with same issuer id as *travelocity.com
>>> * and assertion consumer url as
>>> http://localhost:8080/travelocity.com/home.jsp since it does not
>>> validate issuer id and configure federated IDP as facebook.
>>>
>>> In this scenario, only the *service provider name* will be *validated*
>>> and *issuer id* will *not be validated.*
>>>
>>> Therefore when we try to access service provider, it will federate only
>>> through google.
>>>
>>> This is a very rare negative use case, but when you think of different
>>> personas, I think this should be considered.
>>>
>>> Please correct me if I am wrong.
>>>
>>> Thanks,
>>> --
>>> *Ushani Balasooriya*
>>> Associate Technical Lead - EE;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; +94772636796
>>>
>>>
>>
>>
>> --
>> Ishara Karunarathna
>> Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791 <+94%2071%20799%206791>
>>
>>
>>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shouldnt we validate issuer id among users in service providers?

[Ushani Balasooriya]

Hi Ishara,

27th Nov win updated pack allowed to add sp with same issuer id.

On 30 Nov 2017 10:36 am, "Ishara Karunarathna"  wrote:

> Hi Ushani,
>
> How did you test this scenarios. It does not allow to register two SPs
> with same issuer id.
>
> -Ishara
>
> On Thu, Nov 30, 2017 at 8:22 AM, Ushani Balasooriya 
> wrote:
>
>> Hi IAM team,
>>
>> Please consider the below scenario.
>>
>> When I think of a system as an admin and developer personas in a same
>> tenant,
>>
>> 1. Admin registers a service provider as *travelocity* with issuer id as 
>> *travelocity.com
>> * and assertion consumer url as
>> http://localhost:8080/travelocity.com/home.jsp and configure Federated
>> IDP as Google
>>
>> 2. Then developer persona registers a service provider as *travelocity.com
>> *  with same issuer id as *travelocity.com
>> * and assertion consumer url as
>> http://localhost:8080/travelocity.com/home.jsp since it does not
>> validate issuer id and configure federated IDP as facebook.
>>
>> In this scenario, only the *service provider name* will be *validated*
>> and *issuer id* will *not be validated.*
>>
>> Therefore when we try to access service provider, it will federate only
>> through google.
>>
>> This is a very rare negative use case, but when you think of different
>> personas, I think this should be considered.
>>
>> Please correct me if I am wrong.
>>
>> Thanks,
>> --
>> *Ushani Balasooriya*
>> Associate Technical Lead - EE;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; +94772636796
>>
>>
>
>
> --
> Ishara Karunarathna
> Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <+94%2071%20799%206791>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev