Re: [Dev] Please update the attached file in developer studio kernel P2

[Awanthika Senarath]

thanks !

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Fri, Apr 1, 2016 at 8:52 PM, Thimuth Amarakoon  wrote:

> This is uploaded.
>
> Regards,
> Thimuth
>
> On Thu, Mar 31, 2016 at 9:54 AM, Awanthika Senarath 
> wrote:
>
>> Hi Thimuth,
>>
>> Please upload the attached file in the root level at  [1]
>>
>> [1] http://product-dist.wso2.com/p2/developer-studio-kernel/4.0.0/updates
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>
>
> --
>
> *Thimuth Amarakoon*
>
> *Associate Technical Lead*
>
>
> *WSO2 Inc. http://wso2.com lean.enterprise.middleware*
>
>
> *mobile : +94718340414 <%2B94718340414>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] REST-API: Fine Grained resources vs Coarse Grained resources

[Thamali Wijewardhana]

Thank you very much Frank. I am preparing a report including the changes
that could be done to the ML API according to the things we discussed. Once
I finished it, I will send you to be reviewed.

Thanks
Thamali

On Thu, Mar 31, 2016 at 5:12 PM, Frank Leymann  wrote:

> Yes, Thamali!
>
> Please let me know if I can be of any help. For example, we may schedule a
> call to discuss some of the APIs whenever you think that's appropriate :-)
>
>
> Best regards,
> Frank
>
> 2016-03-31 7:10 GMT+02:00 Thamali Wijewardhana :
>
>> Thank you very much  Frank for your comments.
>> I am now clear that deciding whether to use fine grained resources or
>> coarse grained resource does not depend on the size of the object. We have
>> to consider what objects change and how often they are changed when
>> defining resources. And also the number of requests does not depend on the
>> number of resources defined.  I am trying to use this knowledge and the
>> above three options.
>>
>> Best regards
>> Thamali
>>
>> On Wed, Mar 30, 2016 at 11:35 PM, Frank Leymann  wrote:
>>
>>> Hi all,
>>>
>>> first of all, I fully support Jo's comment on the importance of the
>>> intuitiveness of an API.
>>>
>>> Next, I have a few questions and comments.
>>>
>>> @Thamali:
>>>
>>>1. If you need to update more than one "fine grained resources"
>>>atomically in order to maintain consistency, you can use a Controller
>>>Resource (see section 4.4 of the Guideline document). You pass the set of
>>>fine grained resources in a single invocation of the Controller and the
>>>Controller ensures atomicity (typically by using transactions 
>>> internally).
>>>2. To reduce data exchange, REST recommends caching - for example at
>>>the client side. A resource always comes with "validators" like
>>>Last-Modified header or the ETag header. Clients store these validators 
>>> and
>>>when requesting the resource again, the request is a conditional GET
>>>passing the validators with the request to the server; a server won't
>>>return the resource if the validators did not change (see section 10.4).
>>>This will reduce data transfer but admittedly not (!) the number of
>>>requests to servers.
>>>   - If you don't expect the number of requests be orders of
>>>   magnitudes higher based on fine grained resources, I would rely on 
>>> load
>>>   balancing capabilities - unless practice proves that we run into 
>>> problems...
>>>3. What does actually change and how often?
>>>   - A client requesting a config doesn't want to retrieve the
>>>   encompassing analysis resource in case only the config changed. It add
>>>   parsing burden to the client etc.
>>>   - In your question before you wanted to avoid frequent config
>>>   retrieval, but how does including configs in the analysis resource 
>>> reduce
>>>   the numbers of requests at all? Clients now will retrieve large 
>>> analysis
>>>   results as often as they will retrieve small configs - sounds worse.
>>>   - If configs don't change often, but analysis resources do,
>>>   client's wont be happy to retrieve valid configs with each modified 
>>> analysis
>>>  - Jo's option (1) gives a solution for that problem in case
>>>  coarse-grained resources are used.
>>>   4. When designing resources, considering retrieval only is wrong.
>>>We must understand, e.g. the creation of resources. Is a config always
>>>created together with an analysis resource and vice versa? Or are 
>>> analysis
>>>resources and configs perceived as independent (but related) entities? 
>>> The
>>>latter case indicates that you have to have two separate resources, the
>>>former indicates that you should (not must!) have a single resource.
>>>   - Independent resources that are often manipulate as a whole are
>>>   covered by Composite Resources (section 4.3). I.e. APIs that allow you
>>>   manipulated groups of related resources as a whole when needed, but 
>>> still
>>>   to manipulate the individual resources because the regular GET/PUT/...
>>>   methods on these fine grained resources are available too.
>>>  - This is a generalization of Jo's option (1).
>>>   5. Retrieving pieces of a resource should be done by supporting
>>>filters (as you say yourself). E.g. retrieving the name of an algorithm 
>>> is
>>>done via the API for retrieving the algorithm an adding a corresponding
>>>filter condition as query string (see the notion of "projection" in 
>>> section
>>>10.2.).
>>>   - This is Jo's option (2).
>>>
>>> Please get back with further questions if this didn't help - I am happy
>>> to continue the discussion :-)
>>>
>>>
>>> Best regards,
>>> Frank
>>>
>>> 2016-03-29 12:47 GMT+02:00 Joseph Fonseka :
>>>
 Hi

 Having different ways to retrieve the configs of the resource 

Re: [Dev] US Election Analytics - Data won't persist in DAS

[Niranda Perera]

Hi Chehara,

It's highly unlikely that a stream persistence configuration to get
disabled automatically. Looks like someone have mistakenly disabled it from
the UI. As per the current persistence UI, there is a possibility that such
an incident may occur.


On Fri, Apr 1, 2016 at 8:43 PM, Chehara Pathmabandu 
wrote:

> Hi,
>
> Solved. event persistent had been disabled automatically.
>
> On Fri, Apr 1, 2016 at 8:16 PM, Niranda Perera  wrote:
>
>> Hi Yasara,
>>
>> We need to find where exactly the data stopped persisting. can you find
>> the final entry? Are there any error in the logs?
>>
>> also, we need to check the mysql connections. Check if it has grown out
>> of proportion as previously.
>> And the CPU and memory usage of the node.
>>
>> On Fri, Apr 1, 2016 at 7:37 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> [Adding Dev mail thread]
>>>
>>> @Niranda, can you please dig on this issue and find the root cause..
>>>
>>>
>>>
>>> On Fri, Apr 1, 2016 at 7:26 PM, Yasara Dissanayake 
>>> wrote:
>>>
 Hi,

 As you can see from the image attached here[1]:
 Current status is growing as the data receive and we use this same
 stream to persist. But from a particular date data had not been persisted.

 regards,
 yasara




















>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Senior Software Engineer,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>>
>> --
>> *Niranda Perera*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-71-554-8430
>> Twitter: @n1r44 
>> https://pythagoreanscript.wordpress.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Chehara Pathmabandu
> *Software Engineer - Intern*
> Mobile : +94711976407
> cheh...@wso2.com
>



-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please update the attached file in developer studio kernel P2

[Thimuth Amarakoon]

This is uploaded.

Regards,
Thimuth

On Thu, Mar 31, 2016 at 9:54 AM, Awanthika Senarath 
wrote:

> Hi Thimuth,
>
> Please upload the attached file in the root level at  [1]
>
> [1] http://product-dist.wso2.com/p2/developer-studio-kernel/4.0.0/updates
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>


-- 

*Thimuth Amarakoon*

*Associate Technical Lead*


*WSO2 Inc. http://wso2.com lean.enterprise.middleware*


*mobile : +94718340414 <%2B94718340414>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] US Election Analytics - Data won't persist in DAS

[Mohanadarshan Vivekanandalingam]

Hi Niranda,

Thanks for quick hint.. Now it is working fine.. It seems, event stream is
not persisted properly.. That is the root cause for the issue..

Regards,
Mohan


On Fri, Apr 1, 2016 at 8:16 PM, Niranda Perera  wrote:

> Hi Yasara,
>
> We need to find where exactly the data stopped persisting. can you find
> the final entry? Are there any error in the logs?
>
> also, we need to check the mysql connections. Check if it has grown out of
> proportion as previously.
> And the CPU and memory usage of the node.
>
> On Fri, Apr 1, 2016 at 7:37 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> [Adding Dev mail thread]
>>
>> @Niranda, can you please dig on this issue and find the root cause..
>>
>>
>>
>> On Fri, Apr 1, 2016 at 7:26 PM, Yasara Dissanayake 
>> wrote:
>>
>>> Hi,
>>>
>>> As you can see from the image attached here[1]:
>>> Current status is growing as the data receive and we use this same
>>> stream to persist. But from a particular date data had not been persisted.
>>>
>>> regards,
>>> yasara
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Senior Software Engineer,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>



-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] US Election Analytics - Data won't persist in DAS

[Chehara Pathmabandu]

Hi,

Solved. event persistent had been disabled automatically.

On Fri, Apr 1, 2016 at 8:16 PM, Niranda Perera  wrote:

> Hi Yasara,
>
> We need to find where exactly the data stopped persisting. can you find
> the final entry? Are there any error in the logs?
>
> also, we need to check the mysql connections. Check if it has grown out of
> proportion as previously.
> And the CPU and memory usage of the node.
>
> On Fri, Apr 1, 2016 at 7:37 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> [Adding Dev mail thread]
>>
>> @Niranda, can you please dig on this issue and find the root cause..
>>
>>
>>
>> On Fri, Apr 1, 2016 at 7:26 PM, Yasara Dissanayake 
>> wrote:
>>
>>> Hi,
>>>
>>> As you can see from the image attached here[1]:
>>> Current status is growing as the data receive and we use this same
>>> stream to persist. But from a particular date data had not been persisted.
>>>
>>> regards,
>>> yasara
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Senior Software Engineer,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chehara Pathmabandu
*Software Engineer - Intern*
Mobile : +94711976407
cheh...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] US Election Analytics - Data won't persist in DAS

[Niranda Perera]

Hi Yasara,

We need to find where exactly the data stopped persisting. can you find the
final entry? Are there any error in the logs?

also, we need to check the mysql connections. Check if it has grown out of
proportion as previously.
And the CPU and memory usage of the node.

On Fri, Apr 1, 2016 at 7:37 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> [Adding Dev mail thread]
>
> @Niranda, can you please dig on this issue and find the root cause..
>
>
>
> On Fri, Apr 1, 2016 at 7:26 PM, Yasara Dissanayake 
> wrote:
>
>> Hi,
>>
>> As you can see from the image attached here[1]:
>> Current status is growing as the data receive and we use this same stream
>> to persist. But from a particular date data had not been persisted.
>>
>> regards,
>> yasara
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] US Election Analytics - Data won't persist in DAS

[Mohanadarshan Vivekanandalingam]

[Adding Dev mail thread]

@Niranda, can you please dig on this issue and find the root cause..



On Fri, Apr 1, 2016 at 7:26 PM, Yasara Dissanayake  wrote:

> Hi,
>
> As you can see from the image attached here[1]:
> Current status is growing as the data receive and we use this same stream
> to persist. But from a particular date data had not been persisted.
>
> regards,
> yasara
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>


-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [IS] Change the nameid-format in SAML Response

[Waruna Jayaweera]

Hi gvalencia,
Thanks for the suggestion. It worked as well.

Thanks,
Waruna

On Wed, Mar 30, 2016 at 8:51 PM, gvalen...@heritas.es 
wrote:

> Hi, an alternative solution is to unset the “Use tenant domain in local
> subject identifier” option, within the “Local & Outbound Authentication
> Configuration” of your Service Provider.
>
> Regards,
> Gonzalo
>
> El 30 mar 2016, a las 10:15, Waruna Jayaweera  escribió:
>
> Hi Tharindu,
> Thanks for the solution.My Service Provide is SAAS enabled,but still I got
> the name id with domain. BTW I have set the Subject Claim URI to "
> http://wso2.org/claims.givenname; and it worked as I got the nameid
> without domain.
>
> Thanks,
> Waruna
>
> On Tue, Mar 29, 2016 at 6:22 PM, Tharindu Edirisinghe 
>  wrote:
>
>> Hi Waruna,
>>
>> One thing you can try out is setting the "Subject Claim URI" in Claim
>> Configuration of Service Provider. For example if you set the Subject Claim
>> URI to "http://wso2.org/claims.givenname;, then in the SAML response you
>> will not receive the tenant for the username.
>>
>> > Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">*admin*
>> 
>>
>> However if the Service Provider is SAAS enabled, you won't receive the
>> tenant domain of the logged in user.
>>
>> Regards,
>> TharinduE
>>
>> On Tue, Mar 29, 2016 at 4:42 PM, Waruna Jayaweera 
>> wrote:
>>
>>> Hi,
>>> I have configured SAML SSO for API manager store ( 1.10.0) with IS
>>> 5.1.0. It seems SAML response nameid  contains the full username for super
>>> tenant users as [1]. Is there any way to configure Identity server to send
>>> the SAML response name ID without carbon.super domain [2].
>>>
>>> [1]>> Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">
>>> admin@carbon.super
>>> [2] >> Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">admin>>
>>> Thanks,
>>> Waruna
>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Waruna Lakshitha Jayaweera
>>> Software Engineer
>>> WSO2 Inc; http://wso2.com
>>> phone: +94713255198
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Tharindu Edirisinghe
>> Software Engineer | WSO2 Inc
>> Platform Security Team
>> Blog : tharindue.blogspot.com
>> mobile : +94 775181586
>>
>
>
>
> --
> Regards,
>
> Waruna Lakshitha Jayaweera
> Software Engineer
> WSO2 Inc; http://wso2.com
> phone: +94713255198
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>


-- 
Regards,

Waruna Lakshitha Jayaweera
Software Engineer
WSO2 Inc; http://wso2.com
phone: +94713255198
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Governance Registry 5.2.0 Beta Released

[Thushara Ranawaka]

WSO2 Governance Registry team is pleased to announce the Beta release of
WSO2 Governance Registry 5.2.0.

Please download WSO2 Governance Registry 5.2.0 Beta from this
location[1][2]. Kindly find the official documentation from here[5].This
release includes following features, improvements and bug fixes. To see the
full list please visit jira release note[3]
Improvement

   - [REGISTRY-3455 ] -
   [STORE][PUBLISHER] Add a header and footer to the Swagger UI
   - [REGISTRY-3465 ] -
   [STORE][PUBLISHER] Add a hover tip over the asset type icon indicating the
   type
   - [REGISTRY-3474 ] - Support
   operations for content type artifacts in governance rest api
   - [REGISTRY-3493 ] - Need to
   have association type icons

Bug

   - [REGISTRY-3246 ] -
   Exception occurred when login to the store in windows
   - [REGISTRY-3335 ] -
   Unnecessary warning message once service promoted to "published to API
   store' state.
   - [REGISTRY-3337 ] -
   Production endpoint is set to null for APIs which are published from rest
   services.
   - [REGISTRY-3362 ] -
   Incorrect message, if we add a duplicate rxt file
   - [REGISTRY-3376 ] - In
   tenant anonymous view for REST services swagger IU and swagger down load
   links are not shown
   - [REGISTRY-3402 ] -
   UserStoreException during tenant log in
   - [REGISTRY-3412 ] - Asset
   Menu issue after deleting an asset
   - [REGISTRY-3441 ] - About
   page displaying incorrect product version
   - [REGISTRY-3452 ] -
   [PUBLISHER] The Show Dependency button is stickies to the details table of
   content type RXTs
   - [REGISTRY-3454 ] -
   [PUBLISHER] After selecting an asset from association list - part of drop
   down is remain below to selection menu
   - [REGISTRY-3456 ] - [STORE]
   The OPTIONs label should remain fixed when scrolling down
   - [REGISTRY-3457 ] -
   [STORE][PUBLISHER] The code view of assets should have a consistent color
   scheme across both applications
   - [REGISTRY-3459 ] - [STORE]
   Add missing class to the details page (md,sm and xs)
   - [REGISTRY-3461 ] -
   [PUBLISHER][STORE] The loading assets message should have three dots
   - [REGISTRY-3471 ] -
   [PUBLISHER] Error indicates that the user has not provided a username with
   insufficient privileges error
   - [REGISTRY-3485 ] -
   Publisher/Store login once changing the keystore is not working
   - [REGISTRY-3486 ] - Only
   'policy' is shown under 9 square button in delete page
   - [REGISTRY-3487 ] -
   [Store][All List view] Bookmark feature is still viewable for wadl and wsdl
   - [REGISTRY-3488 ] -
   [STORE][PUBLISHER] Information update notifications do not appear in the
   notification view
   - [REGISTRY-3489 ] -
   [STORE][PUBLISHER] All AJAX calls in IE browser are cached
   - [REGISTRY-3490 ] -
   [Publisher] Life cycle Load history icon continuously Processing in IE 11.
   - [REGISTRY-3491 ] - [IE
   11][publisher]Empty White message is populating when adding a note
   - [REGISTRY-3492 ] -
   Confirmation pop up does not appear when editting life cycles
   - [REGISTRY-3494 ] - Report
   generation is not working in clustered setup.
   - [REGISTRY-3495 ] - [STORE]
   The dependency view error messages reference "publisher" name even in the
   Store
   - [REGISTRY-3496 ] - Created
   Date is truncated in search reports
   - [REGISTRY-3497 ] - tenant
   anonymous download link is not working
   - [REGISTRY-3498 ] -
   [Publisher] Endpoint list & overview pages are not rendered properly
   - [REGISTRY-3500 ] -
   Significant delay in syncing 

Re: [Dev] [Automation Framework]

[Rajjaz Mohammed]

Hi Yashothara,

When your running the integration test ESB will start with axis2 service to
test the synapse samples[1] in port 9000 because these samples[1] are
written to test the service running on port 9000. so if you want to remove
it you need to edit org.wso2.carbon.esbESBIntegrationTest.

test/resources/artifacts/ESB/samples/synapse_sample_xx.xml

On Fri, Apr 1, 2016 at 4:29 PM, Yashothara Shanmugarajah <
yashoth...@wso2.com> wrote:

> Hi,
>
> Shall I know the purpose of having "test_axis2_server_9000.xml" when we
> are doing automation test? It is calling in
> "org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server"
>
>
> When I delete this file for running automation test in connector, it is
> give giving error like below.
>
> ERROR
> {org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server}
> -  Error while initializing the configuration context
> java.io.FileNotFoundException:
> /home/yasho/Videos/servicenow/servicenow-connector/servicenow-connect-1.0.0/org.wso2.carbon.connector/src/test/resources/artifacts/AXIS2/config/test_axis2_server_9000.xml
> (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.(FileInputStream.java:146)
> at java.io.FileInputStream.(FileInputStream.java:101)
> at
> org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server.copyResourceToFileSystem(SampleAxis2Server.java:152)
> at
> org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server.(SampleAxis2Server.java:69)
> at
> org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server.(SampleAxis2Server.java:57)
> at
> org.wso2.carbon.automation.core.PlatformExecutionManager.startSimpleAxis2Server(PlatformExecutionManager.java:227)
> at
> org.wso2.carbon.automation.core.PlatformExecutionManager.startSevers(PlatformExecutionManager.java:190)
> at
> org.wso2.carbon.automation.core.PlatformExecutionManager.onExecutionStart(PlatformExecutionManager.java:76)
> at org.testng.TestNG.runExecutionListeners(TestNG.java:1032)
> at org.testng.TestNG.run(TestNG.java:983)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> [2016-04-01 16:25:35,905]  INFO
> {org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server}
> -  Starting sample Axis2 server
> org.apache.maven.surefire.util.SurefireReflectionException:
> java.lang.reflect.InvocationTargetException; nested exception is
> java.lang.reflect.InvocationTargetException: null
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.NullPointerException
> at
> org.apache.axis2.engine.ListenerManager.init(ListenerManager.java:74)
> at
> org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server.start(SampleAxis2Server.java:85)
> at
> org.wso2.carbon.automation.core.PlatformExecutionManager.startSimpleAxis2Server(PlatformExecutionManager.java:228)
> at
> org.wso2.carbon.automation.core.PlatformExecutionManager.startSevers(PlatformExecutionManager.java:190)
> at
> 

Re: [Dev] WSO2 DAS: Event streaming not working

[Damith Wickramasinghe]

Hi Samudra,

Yes since the delimiter is comma in event simulator, and if your attributes
contains commas as well then it will split those as too.

Regards,
Damith.

On Fri, Apr 1, 2016 at 4:52 PM, Samudra Weerasinghe 
wrote:

> Hi Damith,
>
> I'm sending a list of tweets. Was wondering, if one of the fields has
> commas in it then will DAS recognize those as delimiters too?
>
> Thanks,
> Sam
>
> On Thu, Mar 31, 2016 at 1:50 PM, Samudra Weerasinghe 
> wrote:
>
>> Thanks Damith. Will check on this!
>>
>>
>>
>> On Wed, Mar 30, 2016 at 8:59 PM, Damith Wickramasinghe 
>> wrote:
>>
>>> Hi Samudra,
>>>
>>> This can occur if the csv data is not according to the event stream
>>> definition parameters. Please check whether your sending data according to
>>> the the stream definition attribute order.
>>>
>>> Regards,
>>> Damith.
>>>
>>> On Wed, Mar 30, 2016 at 7:26 PM, Srinath Perera 
>>> wrote:
>>>
 Samudra, I think problem may be csv file somehow does not fit the
 expected format. It may be something to do with how header files specified
 ( please check that against sample given in userguide if there is any)

 Dunith, Gihan, could someone help.

 --Srinath

 On Wed, Mar 30, 2016 at 5:11 PM, Samudra Weerasinghe 
 wrote:

> Hi,
>
> I have created an event stream and persisted it. When I upload a csv
> file to the event simulator and try to play it the "Events sending
> using file is started ..."  message comes but the table in the
> data explorer doesn't get populated.
>
> The error in the log is:
>
> TID: [-1234] [] [2016-03-30 11:41:44,588] ERROR
> {org.wso2.carbon.event.simulator.core.internal.CarbonEventSimulator} -
>  Error in row 36530-failed to create an event org.apache.axis2.AxisFault:
> Failed configuration of event stream in this file or file is corrupted
>  {org.wso2.carbon.event.simulator.core.internal.CarbonEventSimulator}
>
> Hope someone can help.
>
> Thanks,
> Sam
>
> --
> *Samudra Weerasinghe*
> *Trainee Marketing Officer*
> WSO2 Inc.
> Mobile: +94774658752
> Website: wso2.com
>
>


 --
 
 Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
 Site: http://home.apache.org/~hemapani/
 Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902

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


>>>
>>>
>>> --
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> 
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94728671315 <%2B94728671315>*
>>>
>>>
>>
>>
>> --
>> *Samudra Weerasinghe*
>> *Trainee Marketing Officer*
>> WSO2 Inc.
>> Mobile: +94774658752
>> Website: wso2.com
>>
>>
>
>
> --
> *Samudra Weerasinghe*
> *Trainee Marketing Officer*
> WSO2 Inc.
> Mobile: +94774658752
> Website: wso2.com
>
>


-- 
Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

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

Re: [Dev] Kubernetes (and Openshift) modules

[Imesh Gunaratne]

Hi Ramon,

On Thu, Mar 31, 2016 at 9:42 PM, Ramon Gordillo 
wrote:

> Hi.
>
> After doing some research and test on the puppet modules and dockerfiles
> with WSO2 API Management, I have some thoughts to share on this list.
>
> Great! It's really nice to hear you thoughts on $subject.

>
> Some particular information, for example the DNS domain name for the
> cluster, the namespace, etc, is a runtime configuration. That is, if we
> want, for example, to deploy an instance of api management per project (aka
> namespace), with the current approach it will require to build a set of
> docker containers per project. Currently, we have 10 teams working in their
> own projects, so you can figure out the maintainability of 10 different
> sets.
>
> It's not a must create a container image with all the required
configuration. It's just a best practice. If the startup time of the server
is not a problem, running an orchestration tool at the startup should be
fine. We followed the same pattern few months back with Stratos + K8S.

However I personally prefer fully configured container images approach as
they are less error prone and may not depend on any dynamic parameters. It
would be much similar to a product archive which includes all
configurations, the person who deploys the product just need to extract and
run. If there are any security concerns on the credentials and keys
packaged, we might need to use a tool like secure wallet.


> Apart from it, there are some configuration information that can be
> obtained from the kubernetes master instead of hardcoding it in the
> container. Even the kubernetes master information is injected in the
> containers in environment variables (
> http://kubernetes.io/docs/user-guide/environment-guide/, see
> KUBERNETES_SERVICE_HOST, KUBERNETES_SERVICE_PORT).
>
> With those considerations, I propose to use puppet also at runtime when
> starting the container, for configuring it using template environment
> variables (which are instanced at runtime), and getting as much information
> as we could automatically instead of forcing the user to provide it.
>

Yes, as I mentioned above, it's a compromise between optimizing the startup
time against the number of container images we need to maintain.

>
> Other than that, I also propose to have one script at startup per PaaS
> solution. It will customize the peculiarities of this PaaS, and adapt it to
> the agnostic configuration. For example, in kubernetes, some environment
> variables are injected by default in the container, but in CloudFoundry,
> for example, other variables with other structure is used. With this
> approach, the container can be used for both of them (even with standalone
> docker-compose for example) just having a simple and reusable script for
> any PaaS solution.
>

AFAIU this would be only needed if we are to do configurations at the
startup. If the container image contains all configurations needed we may
not need a PaaS specific startup script.

Thanks


> What do you think?
>
> Thanks.
>
> Regards.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.io
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Pulasthi Mahawithana]

Yes, we no longer use the wso2/carbon-identity repo for development. We use
the repos in 'wso2-extensions'. However the group ids, artifact ids and
versions follow the same from carbon-identity.

On Fri, Apr 1, 2016 at 3:56 PM, Rushmin Fernando  wrote:

> Thanks Supun !
>
> So is [1] obsolete now since the connector code resides in
> 'wso2-extensions' account now ?
>
>
> Thanks
> Rushmin
>
> [1] -
> https://github.com/wso2/carbon-identity/blob/master/features/provisioning/org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature
>
> On Fri, Apr 1, 2016 at 3:47 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi Rushmin,
>>
>> This issue was due to that component being moved from carbon-commons to
>> analytic commons. Isura fixed that issue with [1] and [2]. Can you please
>> try now?
>>
>> [1] https://github.com/wso2-extensions/identity-extension-parent/pull/6
>> [2]
>> https://github.com/wso2-extensions/identity-outbound-provisioning-salesforce/pull/6
>>
>> On Fri, Apr 1, 2016 at 12:21 PM, Rushmin Fernando 
>> wrote:
>>
>>>
>>> Hi Devs,
>>>
>>> We are in the process of upgrading the Carbon Kernel version to 4.4.5
>>>
>>> During this upgrade we found out that
>>> "org.wso2.carbon.identity.provisioning.connector.salesforce.server" feature
>>> is dependenct on a non-existing feature version of
>>> "org.wso2.carbon.databridge.commons.server"
>>>
>>> I opened a Jira to track this. [1]
>>>
>>> Had a chat with Pulasthi and this will be fixed with IS 5.2.0 release
>>> which will happen in the next week.
>>>
>>> Until this is fixed, I'm proceeding with the identity 5.0.9-SNAPSHOT
>>> having the issue fixed locally.
>>>
>>> Thanks
>>> Rushmin
>>>
>>> [1] - https://wso2.org/jira/browse/IDENTITY-4465
>>>
>>> --
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> email : rush...@wso2.com
>>> mobile : +94772310855
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pulasthi Mahawithana*
>> Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022
>> Blog: http://blog.pulasthi.org
>>
>
>
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>


-- 
*Pulasthi Mahawithana*
Software Engineer
WSO2 Inc., http://wso2.com/
Mobile: +94-71-5179022
Blog: http://blog.pulasthi.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Automation Framework]

[Yashothara Shanmugarajah]

Hi,

Shall I know the purpose of having "test_axis2_server_9000.xml" when we are
doing automation test? It is calling in
"org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server"


When I delete this file for running automation test in connector, it is
give giving error like below.

ERROR
{org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server}
-  Error while initializing the configuration context
java.io.FileNotFoundException:
/home/yasho/Videos/servicenow/servicenow-connector/servicenow-connect-1.0.0/org.wso2.carbon.connector/src/test/resources/artifacts/AXIS2/config/test_axis2_server_9000.xml
(No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:146)
at java.io.FileInputStream.(FileInputStream.java:101)
at
org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server.copyResourceToFileSystem(SampleAxis2Server.java:152)
at
org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server.(SampleAxis2Server.java:69)
at
org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server.(SampleAxis2Server.java:57)
at
org.wso2.carbon.automation.core.PlatformExecutionManager.startSimpleAxis2Server(PlatformExecutionManager.java:227)
at
org.wso2.carbon.automation.core.PlatformExecutionManager.startSevers(PlatformExecutionManager.java:190)
at
org.wso2.carbon.automation.core.PlatformExecutionManager.onExecutionStart(PlatformExecutionManager.java:76)
at org.testng.TestNG.runExecutionListeners(TestNG.java:1032)
at org.testng.TestNG.run(TestNG.java:983)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
[2016-04-01 16:25:35,905]  INFO
{org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server}
-  Starting sample Axis2 server
org.apache.maven.surefire.util.SurefireReflectionException:
java.lang.reflect.InvocationTargetException; nested exception is
java.lang.reflect.InvocationTargetException: null
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: java.lang.NullPointerException
at org.apache.axis2.engine.ListenerManager.init(ListenerManager.java:74)
at
org.wso2.carbon.automation.core.utils.axis2serverutils.SampleAxis2Server.start(SampleAxis2Server.java:85)
at
org.wso2.carbon.automation.core.PlatformExecutionManager.startSimpleAxis2Server(PlatformExecutionManager.java:228)
at
org.wso2.carbon.automation.core.PlatformExecutionManager.startSevers(PlatformExecutionManager.java:190)
at
org.wso2.carbon.automation.core.PlatformExecutionManager.onExecutionStart(PlatformExecutionManager.java:76)
at org.testng.TestNG.runExecutionListeners(TestNG.java:1032)
at org.testng.TestNG.run(TestNG.java:983)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)



Shall I know what is the purpose of this file?

Thanks.

Best Regards,
Yashothara.S

Software Engineer
WSO2
___
Dev mailing list
Dev@wso2.org

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Rushmin Fernando]

Thanks Supun !

So is [1] obsolete now since the connector code resides in
'wso2-extensions' account now ?


Thanks
Rushmin

[1] -
https://github.com/wso2/carbon-identity/blob/master/features/provisioning/org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature

On Fri, Apr 1, 2016 at 3:47 PM, Pulasthi Mahawithana 
wrote:

> Hi Rushmin,
>
> This issue was due to that component being moved from carbon-commons to
> analytic commons. Isura fixed that issue with [1] and [2]. Can you please
> try now?
>
> [1] https://github.com/wso2-extensions/identity-extension-parent/pull/6
> [2]
> https://github.com/wso2-extensions/identity-outbound-provisioning-salesforce/pull/6
>
> On Fri, Apr 1, 2016 at 12:21 PM, Rushmin Fernando 
> wrote:
>
>>
>> Hi Devs,
>>
>> We are in the process of upgrading the Carbon Kernel version to 4.4.5
>>
>> During this upgrade we found out that
>> "org.wso2.carbon.identity.provisioning.connector.salesforce.server" feature
>> is dependenct on a non-existing feature version of
>> "org.wso2.carbon.databridge.commons.server"
>>
>> I opened a Jira to track this. [1]
>>
>> Had a chat with Pulasthi and this will be fixed with IS 5.2.0 release
>> which will happen in the next week.
>>
>> Until this is fixed, I'm proceeding with the identity 5.0.9-SNAPSHOT
>> having the issue fixed locally.
>>
>> Thanks
>> Rushmin
>>
>> [1] - https://wso2.org/jira/browse/IDENTITY-4465
>>
>> --
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> email : rush...@wso2.com
>> mobile : +94772310855
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pulasthi Mahawithana*
> Software Engineer
> WSO2 Inc., http://wso2.com/
> Mobile: +94-71-5179022
> Blog: http://blog.pulasthi.org
>



-- 
*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

email : rush...@wso2.com
mobile : +94772310855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Dockerfiles 1.0.0 RC3

[Isuru Haththotuwa]

This is the third release candidate (RC3) of WSO2 Dockerfiles 1.0.0
release.

*Tag to be voted upon:*
https://github.com/wso2/dockerfiles/tree/v1.0.0-rc3

*Source and distribution packages:*
https://github.com/wso2/dockerfiles/releases/tag/v1.0.0-rc3

Please download, test, and vote. The README file under each product
directory contains instructions on how to try it out locally.

[ ] Broken - Do not release (explain why)
[ ] Stable - Go ahead and release

This vote will be open for 72 hours or as needed.

-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Pulasthi Mahawithana]

Hi Rushmin,

This issue was due to that component being moved from carbon-commons to
analytic commons. Isura fixed that issue with [1] and [2]. Can you please
try now?

[1] https://github.com/wso2-extensions/identity-extension-parent/pull/6
[2]
https://github.com/wso2-extensions/identity-outbound-provisioning-salesforce/pull/6

On Fri, Apr 1, 2016 at 12:21 PM, Rushmin Fernando  wrote:

>
> Hi Devs,
>
> We are in the process of upgrading the Carbon Kernel version to 4.4.5
>
> During this upgrade we found out that
> "org.wso2.carbon.identity.provisioning.connector.salesforce.server" feature
> is dependenct on a non-existing feature version of
> "org.wso2.carbon.databridge.commons.server"
>
> I opened a Jira to track this. [1]
>
> Had a chat with Pulasthi and this will be fixed with IS 5.2.0 release
> which will happen in the next week.
>
> Until this is fixed, I'm proceeding with the identity 5.0.9-SNAPSHOT
> having the issue fixed locally.
>
> Thanks
> Rushmin
>
> [1] - https://wso2.org/jira/browse/IDENTITY-4465
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pulasthi Mahawithana*
Software Engineer
WSO2 Inc., http://wso2.com/
Mobile: +94-71-5179022
Blog: http://blog.pulasthi.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][APIM]OSGI bundle doesn't import the correct package version.

[Randika Navagamuwa]

Hi all,
  I'm using two 3rd party libraries(Swagger-codegen and swagger-parser)
which are not OSGI bundles. I have managed to create OSGI bundles and I'm
having this problem now.

Swagger-codegen should import *io.swagger.models:version="1.5.6"
*and Swagger-parser should import *io.swagger.models:version="1.5.8" * so I
have added those two versions of *swagger-models(Already a bundle) *to the
project. But both swagger-codegen and parser import
*io.swagger.models:version="1.5.8".
 *Swagge-codegen won't work without *swagger-models:version="1.5.6"*

pom files of those two bundles can be found here[1][2]

[1]
https://github.com/rnavagamuwa/orbit/blob/master/swagger-codegen/2.1.5.wso2v1/pom.xml
[2]
https://github.com/rnavagamuwa/orbit/blob/master/swagger-parser/1.0.17.wso2v1/pom.xml

Thanks and regards,
-- 
*Randika Navagamuwa*
*Intern - Software Engineering*
*Mobile : +94711853466*
*Twitter : twitter.com/rnavagamuwa *
*Facebook : facebook.com/rnavagamuwa *
*Linkedin : lk.linkedin.com/in/rnavagamuwa
*
*Blog : rnavagamuwa.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Include carbon.yml and other config files in Carbon Core feature

[Niranjan Karunanandham]

Hi Devs,

In Carbon 5, the carbon.yml, log4j2.xml and etc., are in the distribution
folder and copied to the distribution pack via bin.xml. Why don't we add
these configuration files to Carbon Server Feature
(org.wso2.carbon.core.server.feature) which are copied to the packed when
the feature is installed. WDYT?

Regards,
Nira

-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB]Blocking option of Call mediator

[Dilshani Subasinghe]

Hi Malintha and Senduran,

Thank you for your clarifications and I understood the real process through
that. It was really helpful.

Regards,
Dilshani

On Fri, Apr 1, 2016 at 12:25 PM, Malintha Amarasinghe 
wrote:

> Sorry.. resending with some of the typos corrected :)
>
> --
>
> I and Prabath (from ESB team) had a similar discussion about this before. 
> Blocking
> false in a call mediator is intended for a different behavior and it is not
> same as send mediator.
>
> AFAIU a call mediator with call-blocking=false is not same as
> blocking=true although it seems to be same at first glance. This is
> executed differently in thread level.
>
> Say you have a config like below.
>
> 
> 
> 
> ..
>
> In thread level this will be executed like below when there's a call
> mediator with blocking false.
>
>  ---  executed by thread T1 and it
> will end after registering a call back to process the response.
>--- response is received by a different thread  T2 via
> callback. After that T2 takes care of executing mediators after that.
>  --- executed by T2
>
> With blocking true :
>
>  ---  executed by thread T1 and the
> same thread will wait till it get the response.
>--- response is received and same thread T1 takes care
> of executing mediators after that.
>  --- executed by T1
>
> Hope this helps you to understand the difference.
>
> When blocking false, there are no waiting threads till receiving responses
> that consumes resources like blocking true.
>
> Prabath, can you please correct if anything need to be changed.
>
> -
>
> Thanks!
>
> On Fri, Apr 1, 2016 at 12:17 PM, Malintha Amarasinghe 
> wrote:
>
>> Hi Dilshani,
>>
>> I and Prabath (from ESB team) had a similar discussion about this before.
>> AFAIU a call mediator without call-blocking=true (which is default) is not
>> same as send mediator. This is executed differently in thread level.
>>
>> Say you have a config like below.
>>
>> 
>> 
>> 
>> ..
>>
>> In thread level this will be executed like below when there's a call
>> mediator with blocking true.
>>
>>  ---  executed by thread T1 and it
>> will end after registering a call back to process the response.
>>--- response is received by a different thread  T2 via
>> callback. After that T2 takes care of executing mediators after that.
>>  --- executed by T2
>>
>> With blocking false :
>>
>>  ---  executed by thread T1 and the
>> same thread will wait till it get the response.
>>--- response is received and same thread T1 takes care
>> of executing mediators after that.
>>  --- executed by T1
>>
>> Hope this helps you to understand the difference.
>>
>> When blocking false, there are no waiting threads till receiving
>> responses that consumes resources like blocking true.
>>
>> Prabath, can you please correct if anything need to be changed.
>>
>> Thanks,
>> Malintha
>>
>> On Fri, Apr 1, 2016 at 11:53 AM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi Kathees,
>>>
>>> Thank you for the response.
>>>
>>> If it is, When blocking disabled call mediator should work as just like
>>> send mediator. Right ? (Correct me If I am wrong) Because call mediator
>>> will send message to endpoint and do not wait for response.
>>>
>>> But it doesn't work in that manner. Any clarification ?
>>>
>>> Regards,
>>> Dilshani
>>>
>>>
>>> On Fri, Apr 1, 2016 at 11:47 AM, Kathees Rajendram 
>>> wrote:
>>>
 Hi Dilshani,

 Call mediator blocking functionality [1] is similar to the Callout
 mediator.

 When invoked in a asynchronous manner, the Call mediator performs a
 blocking external service invocation during mediation. So when you send the
 call to backend with blocking functionality (blocking=true), It will wait
 for the response. When you send the call with non blocking, It will work in
 a synchronous manner without waiting for the response.

 [1] - https://docs.wso2.com/display/ESB490/Call+Mediator


 Thanks,
 Kathees

 On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe  wrote:

> Hi ESB team,
>
> In call mediator, there is a separate option called "Blocking". AFAIK
> call mediator having default functionality of blocking mediation.
>
> What will be the different behavior can have through Enabling Blocking
> rather than in-built blocking feature ? Even though Blocking disabled, it
> may not act as send mediator.
>
> Can someone help to figure out this ?
>
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
>
> Mobile: +94773375185
>
> ___
> Dev mailing list
> Dev@wso2.org
> 

Re: [Dev] [ESB]Blocking option of Call mediator

[Malintha Amarasinghe]

Sorry.. resending with some of the typos corrected :)

--

I and Prabath (from ESB team) had a similar discussion about this
before. Blocking
false in a call mediator is intended for a different behavior and it is not
same as send mediator.

AFAIU a call mediator with call-blocking=false is not same as blocking=true
although it seems to be same at first glance. This is executed differently
in thread level.

Say you have a config like below.




..

In thread level this will be executed like below when there's a call
mediator with blocking false.

 ---  executed by thread T1 and it will
end after registering a call back to process the response.
   --- response is received by a different thread  T2 via
callback. After that T2 takes care of executing mediators after that.
 --- executed by T2

With blocking true :

 ---  executed by thread T1 and the same
thread will wait till it get the response.
   --- response is received and same thread T1 takes care
of executing mediators after that.
 --- executed by T1

Hope this helps you to understand the difference.

When blocking false, there are no waiting threads till receiving responses
that consumes resources like blocking true.

Prabath, can you please correct if anything need to be changed.

-

Thanks!

On Fri, Apr 1, 2016 at 12:17 PM, Malintha Amarasinghe 
wrote:

> Hi Dilshani,
>
> I and Prabath (from ESB team) had a similar discussion about this before.
> AFAIU a call mediator without call-blocking=true (which is default) is not
> same as send mediator. This is executed differently in thread level.
>
> Say you have a config like below.
>
> 
> 
> 
> ..
>
> In thread level this will be executed like below when there's a call
> mediator with blocking true.
>
>  ---  executed by thread T1 and it will
> end after registering a call back to process the response.
>--- response is received by a different thread  T2 via
> callback. After that T2 takes care of executing mediators after that.
>  --- executed by T2
>
> With blocking false :
>
>  ---  executed by thread T1 and the
> same thread will wait till it get the response.
>--- response is received and same thread T1 takes care
> of executing mediators after that.
>  --- executed by T1
>
> Hope this helps you to understand the difference.
>
> When blocking false, there are no waiting threads till receiving responses
> that consumes resources like blocking true.
>
> Prabath, can you please correct if anything need to be changed.
>
> Thanks,
> Malintha
>
> On Fri, Apr 1, 2016 at 11:53 AM, Dilshani Subasinghe 
> wrote:
>
>> Hi Kathees,
>>
>> Thank you for the response.
>>
>> If it is, When blocking disabled call mediator should work as just like
>> send mediator. Right ? (Correct me If I am wrong) Because call mediator
>> will send message to endpoint and do not wait for response.
>>
>> But it doesn't work in that manner. Any clarification ?
>>
>> Regards,
>> Dilshani
>>
>>
>> On Fri, Apr 1, 2016 at 11:47 AM, Kathees Rajendram 
>> wrote:
>>
>>> Hi Dilshani,
>>>
>>> Call mediator blocking functionality [1] is similar to the Callout
>>> mediator.
>>>
>>> When invoked in a asynchronous manner, the Call mediator performs a
>>> blocking external service invocation during mediation. So when you send the
>>> call to backend with blocking functionality (blocking=true), It will wait
>>> for the response. When you send the call with non blocking, It will work in
>>> a synchronous manner without waiting for the response.
>>>
>>> [1] - https://docs.wso2.com/display/ESB490/Call+Mediator
>>>
>>>
>>> Thanks,
>>> Kathees
>>>
>>> On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe 
>>> wrote:
>>>
 Hi ESB team,

 In call mediator, there is a separate option called "Blocking". AFAIK
 call mediator having default functionality of blocking mediation.

 What will be the different behavior can have through Enabling Blocking
 rather than in-built blocking feature ? Even though Blocking disabled, it
 may not act as send mediator.

 Can someone help to figure out this ?

 Thank you.

 --
 Best Regards,

 Dilshani Subasinghe
 Software Engineer - QA
 WSO2, Inc.;http://wso2.com/
 
 lean.enterprise.middleware

 Mobile: +94773375185

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


>>>
>>>
>>> --
>>> Kathees
>>> Software Engineer,
>>> email: kath...@wso2.com
>>> mobile: +94772596173
>>>
>>
>>
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> 
>> lean.enterprise.middleware
>>
>> Mobile: +94773375185
>>
>> 

[Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Rushmin Fernando]

Hi Devs,

We are in the process of upgrading the Carbon Kernel version to 4.4.5

During this upgrade we found out that
"org.wso2.carbon.identity.provisioning.connector.salesforce.server" feature
is dependenct on a non-existing feature version of
"org.wso2.carbon.databridge.commons.server"

I opened a Jira to track this. [1]

Had a chat with Pulasthi and this will be fixed with IS 5.2.0 release which
will happen in the next week.

Until this is fixed, I'm proceeding with the identity 5.0.9-SNAPSHOT having
the issue fixed locally.

Thanks
Rushmin

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

-- 
*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

email : rush...@wso2.com
mobile : +94772310855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB]Blocking option of Call mediator

[Senduran Balasubramaniyam]

Hi Dilshani,

Both call mediator and call out mediator will wait for the response. But
the difference is, in call mediator the thread which send the request will
return and a new thread will process the response, where as in callout
mediator (or call mediator will blocking enabled) same thread will process
the response.

Regards
Senduran

On Fri, Apr 1, 2016 at 11:53 AM, Dilshani Subasinghe 
wrote:

> Hi Kathees,
>
> Thank you for the response.
>
> If it is, When blocking disabled call mediator should work as just like
> send mediator. Right ? (Correct me If I am wrong) Because call mediator
> will send message to endpoint and do not wait for response.
>
> But it doesn't work in that manner. Any clarification ?
>
> Regards,
> Dilshani
>
>
> On Fri, Apr 1, 2016 at 11:47 AM, Kathees Rajendram 
> wrote:
>
>> Hi Dilshani,
>>
>> Call mediator blocking functionality [1] is similar to the Callout
>> mediator.
>>
>> When invoked in a asynchronous manner, the Call mediator performs a
>> blocking external service invocation during mediation. So when you send the
>> call to backend with blocking functionality (blocking=true), It will wait
>> for the response. When you send the call with non blocking, It will work in
>> a synchronous manner without waiting for the response.
>>
>> [1] - https://docs.wso2.com/display/ESB490/Call+Mediator
>>
>>
>> Thanks,
>> Kathees
>>
>> On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi ESB team,
>>>
>>> In call mediator, there is a separate option called "Blocking". AFAIK
>>> call mediator having default functionality of blocking mediation.
>>>
>>> What will be the different behavior can have through Enabling Blocking
>>> rather than in-built blocking feature ? Even though Blocking disabled, it
>>> may not act as send mediator.
>>>
>>> Can someone help to figure out this ?
>>>
>>> Thank you.
>>>
>>> --
>>> Best Regards,
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA
>>> WSO2, Inc.;http://wso2.com/
>>> 
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94773375185
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
>
> Mobile: +94773375185
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Senduran *
Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB]Blocking option of Call mediator

[Malintha Amarasinghe]

Hi Dilshani,

I and Prabath (from ESB team) had a similar discussion about this before.
AFAIU a call mediator without call-blocking=true (which is default) is not
same as send mediator. This is executed differently in thread level.

Say you have a config like below.




..

In thread level this will be executed like below when there's a call
mediator with blocking true.

 ---  executed by thread T1 and it will
end after registering a call back to process the response.
   --- response is received by a different thread  T2 via
callback. After that T2 takes care of executing mediators after that.
 --- executed by T2

With blocking false :

 ---  executed by thread T1 and the same
thread will wait till it get the response.
   --- response is received and same thread T1 takes care
of executing mediators after that.
 --- executed by T1

Hope this helps you to understand the difference.

When blocking false, there are no waiting threads till receiving responses
that consumes resources like blocking true.

Prabath, can you please correct if anything need to be changed.

Thanks,
Malintha

On Fri, Apr 1, 2016 at 11:53 AM, Dilshani Subasinghe 
wrote:

> Hi Kathees,
>
> Thank you for the response.
>
> If it is, When blocking disabled call mediator should work as just like
> send mediator. Right ? (Correct me If I am wrong) Because call mediator
> will send message to endpoint and do not wait for response.
>
> But it doesn't work in that manner. Any clarification ?
>
> Regards,
> Dilshani
>
>
> On Fri, Apr 1, 2016 at 11:47 AM, Kathees Rajendram 
> wrote:
>
>> Hi Dilshani,
>>
>> Call mediator blocking functionality [1] is similar to the Callout
>> mediator.
>>
>> When invoked in a asynchronous manner, the Call mediator performs a
>> blocking external service invocation during mediation. So when you send the
>> call to backend with blocking functionality (blocking=true), It will wait
>> for the response. When you send the call with non blocking, It will work in
>> a synchronous manner without waiting for the response.
>>
>> [1] - https://docs.wso2.com/display/ESB490/Call+Mediator
>>
>>
>> Thanks,
>> Kathees
>>
>> On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi ESB team,
>>>
>>> In call mediator, there is a separate option called "Blocking". AFAIK
>>> call mediator having default functionality of blocking mediation.
>>>
>>> What will be the different behavior can have through Enabling Blocking
>>> rather than in-built blocking feature ? Even though Blocking disabled, it
>>> may not act as send mediator.
>>>
>>> Can someone help to figure out this ?
>>>
>>> Thank you.
>>>
>>> --
>>> Best Regards,
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA
>>> WSO2, Inc.;http://wso2.com/
>>> 
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94773375185
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
>
> Mobile: +94773375185
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Malintha Amarasinghe
Software Engineer
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

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

Re: [Dev] [ESB]Blocking option of Call mediator

[Dilshani Subasinghe]

Hi Kathees,

Thank you for the response.

If it is, When blocking disabled call mediator should work as just like
send mediator. Right ? (Correct me If I am wrong) Because call mediator
will send message to endpoint and do not wait for response.

But it doesn't work in that manner. Any clarification ?

Regards,
Dilshani


On Fri, Apr 1, 2016 at 11:47 AM, Kathees Rajendram  wrote:

> Hi Dilshani,
>
> Call mediator blocking functionality [1] is similar to the Callout
> mediator.
>
> When invoked in a asynchronous manner, the Call mediator performs a
> blocking external service invocation during mediation. So when you send the
> call to backend with blocking functionality (blocking=true), It will wait
> for the response. When you send the call with non blocking, It will work in
> a synchronous manner without waiting for the response.
>
> [1] - https://docs.wso2.com/display/ESB490/Call+Mediator
>
>
> Thanks,
> Kathees
>
> On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe 
> wrote:
>
>> Hi ESB team,
>>
>> In call mediator, there is a separate option called "Blocking". AFAIK
>> call mediator having default functionality of blocking mediation.
>>
>> What will be the different behavior can have through Enabling Blocking
>> rather than in-built blocking feature ? Even though Blocking disabled, it
>> may not act as send mediator.
>>
>> Can someone help to figure out this ?
>>
>> Thank you.
>>
>> --
>> Best Regards,
>>
>> Dilshani Subasinghe
>> Software Engineer - QA
>> WSO2, Inc.;http://wso2.com/
>> 
>> lean.enterprise.middleware
>>
>> Mobile: +94773375185
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/

lean.enterprise.middleware

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

Re: [Dev] [ESB]Blocking option of Call mediator

[Kathees Rajendram]

Hi Dilshani,

Call mediator blocking functionality [1] is similar to the Callout mediator.

When invoked in a asynchronous manner, the Call mediator performs a
blocking external service invocation during mediation. So when you send the
call to backend with blocking functionality (blocking=true), It will wait
for the response. When you send the call with non blocking, It will work in
a synchronous manner without waiting for the response.

[1] - https://docs.wso2.com/display/ESB490/Call+Mediator


Thanks,
Kathees

On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe 
wrote:

> Hi ESB team,
>
> In call mediator, there is a separate option called "Blocking". AFAIK call
> mediator having default functionality of blocking mediation.
>
> What will be the different behavior can have through Enabling Blocking
> rather than in-built blocking feature ? Even though Blocking disabled, it
> may not act as send mediator.
>
> Can someone help to figure out this ?
>
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
>
> Mobile: +94773375185
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev