Re: [Dev] [Throttling] Moving throttle.core out from Synapse

[Amila De Silva]

Hi Isuru,

There aren't any changes to be merged on MEPClient and
SynapseCallbackReceiver. Changes that need merging are done on classes
residing under [1].

Let me clarify a bit what these changes are;

While fixing some throttling issues in AM 1.6.0, certain changes were done
on the part that replicates throttling counters. Earlier these counters
were replicated using a ClusterMessage, but after the fixes counters are
replicated using  Hazelcast AtomicLongs. The fixes were done on
org.wso2.carbon.throttle.core_4.2.0,
which is maintained in svn and after fixes were done, throttle.core needs
depending on com.hazelcast.wso2 component.

When moving synapse code on to Git, throttle.core has been absorbed into
synapse, and now it is kept under [1]. Parallel to the changes mentioned
above, some other fixes have been done on the throttling & synapse (which
now is on Git) and it's those changes that make synapse depend on throttle
core. The change is MEPClient and SynapseCallbackReceiver using a reference
of ConcurrentAccessController (you can find the specific code changes at
[2])


[1]
https://github.com/wso2/wso2-synapse/tree/master/modules/commons/src/main/java/org/apache/synapse/commons/throttle
[2]
https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/core/axis2/SynapseCallbackReceiver.java#L497-L515



On Mon, Sep 14, 2015 at 3:54 PM, Isuru Udana  wrote:

> Hi AmilaD,
>
> Can you please point us the changes need to be merged in synapse (in
> MEPClient and SynapseCallbackReceiver) ?
>
> On Mon, Sep 14, 2015 at 2:58 PM, Amila De Silva  wrote:
>
>> Hi All,
>>
>> While carrying out this task, came to a point where certain classes
>> cannot be moved out of synapse.
>>
>> For some of the improvements done recently, ConcurrentAccessController
>> (which is one of the classes that originally resided in throttle core) has
>> been used from SynapseCallbackReceiver and Axis2FlexibleMEPClient. So now
>> either ConcurrentAccessController has to reside inside synapse, or else it
>> has to go into another different component on which synapse would have to
>> depend on. The whole point of moving throttling related code out of synapse
>> is to prevent synapse depending on any carbon components.
>>
>> Since synapse depending on Hazelcast is not something that can be
>> eliminated completely, is it fine to keep throttle.core inside synapse and
>> merge new changes? When merging throttling fixes, either we have to
>> introduce a service component to synapse, which would
>> consume hazelcast.instance.service or we have to provide a method to set
>> the HazelcastInstance that will be used for replicating throttling counts.
>>
>> On Fri, Sep 11, 2015 at 9:01 PM, Amila De Silva  wrote:
>>
>>> Hi Chanaka,
>>>
>>> Since throttle core can be used on its own, thought of creating a
>>> separate feature out of that - so a new place to put throttle component. If
>>> we put it under mediation-throttle, that would imply two components have to
>>> be used together, isn't it?
>>>
>>> On Fri, Sep 11, 2015 at 6:45 PM, Chanaka Fernando 
>>> wrote:
>>>
 Hi Amila,

 You can find [1] which already has the throttle policy editor related
 packages and named as mediation-throttle. You can move the throttle-core
 packages to this component.

 [1]
 https://github.com/wso2/carbon-mediation/tree/master/components/mediation-throttle

 On Fri, Sep 11, 2015 at 6:23 PM, Sanjeewa Malalgoda 
 wrote:

> +1.
>
>
> On Fri, Sep 11, 2015 at 5:20 PM, Amila De Silva 
> wrote:
>
>> Will be moving throttle.core to a new component under
>> carbon-mediation. The new component name will be throttle-core and a new
>> feature with the same name will be created. Planning to do these changes 
>> on
>> carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.
>>
>> On Mon, Sep 7, 2015 at 6:25 PM, Amila De Silva 
>> wrote:
>>
>>> Hi All,
>>>
>>> One of the changes done while moving to Git was, moving source code
>>> which was under org.wso2.carbon.throttle.core to wso2-synapse. Throttle
>>> core is used by both ESB (in Throttle mediator) and by API Manager (in
>>> APIThrottleHandler - to keep track of the number of API calls made over 
>>> the
>>> cluster). At the time throttle core was moved, it was depending on Axis2
>>> only, making it possible to move the source code to wso2-synapse - 
>>> which is
>>> not depending on any carbon components.
>>>
>>> While doing several improvements on throttling, Hazelcast
>>> AtomicLongs were used for keeping cluster-wide counts, which now 
>>> creates a
>>> coupling between Hazelcast and Throttle Core. If these changes are to be
>>> merged with synapse, we would have to add a dependency to 

[Dev] [DEV] WSO2 Enterprise Store 2.0.0 Released

[Manuranga Perera]

WSO2 Enterprise Store 2.0.0 Release

This is the version 2.0.0 of the WSO2 Enterprise Store, which will create a
marketplace for your enterprise assets.

The WSO2 Enterprise Store (WSO2 ES) brings a user-friendly experience for
accessing and managing digital assets in a connected enterprise.
Development teams and business users alike can easily and rapidly discover,
subscribe, and utilize any digital enterprise asset to increase
productivity and efficiency of an organization. With features such as
customizable views of asset lifecycles and usage statistics, and the
ability to change and manage each asset lifecycle, WSO2 ES is a very
flexible and powerful platform to provision and manage digital assets.


To download the product please visit
http://wso2.com/products/enterprise-store/


How to Run

1. Extract the downloaded zip

2. Go to the bin directory in the extracted folder

3. Run the wso2server.sh or wso2server.bat as appropriate

4. Launch a web browser and navigate to https://localhost:9443/carbon
to access the admin console

5. Navigate to https://localhost:9443/publisher to access the publisher
webapp

6. Navigate to https://localhost:9443/store to access the store webapp

7. Use "admin", "admin" as the username and password to login as an
admin

WSO2 Enterprise Store 2.0.0 includes following new features, improvements
and bug fixes.
Bug

   -

   [STORE-550 ] - HTML tag,
   attribute "id" is not binding
   -

   [STORE-632 ] - [Publisher]
   Lifecycle state should be prominently displayed in the list view
   -

   [STORE-659 ] - Warning printed
   when access dependencies of registry extensions.
   -

   [STORE-731 ] - Store Front -
   Null appended to landing page URL
   -

   [STORE-765 ] - Dbscripts
   (POSTGRESQL,MSSQL,DB2) for social DB is missing in Latest ES pack
   -

   [STORE-792 ] - Tenant Users
   can't create assets Eg:-soap service
   -

   [STORE-793 ] - Searching by name
   field in store asset listing page is broken
   -

   [STORE-812 ] - 401 Error thrown
   when Internal/Reviewer try to access Copy page
   -

   [STORE-857 ] - Creating a new
   version of an asset - UI
   -

   [STORE-861 ] - 'null' in URL in
   top-assets page
   -

   [STORE-868 ] - Unable to remove
   a bookmark - UI
   -

   [STORE-883 ] - Error 500 when
   Bookmarked is clicked
   -

   [STORE-944 ] - Error in adding
   reviews when connected with Oracle
   -

   [STORE-992 ] - Advance search
   does not work when there are search results more than 100
   -

   [STORE-1001 ] - [Publisher]
   when artifacts are loaded with infinite scrolling at the end of resource
   set error is logged in back end.
   -

   [STORE-1002 ] -
   Internal/Reviewer can see the Edit of Assets in In Review state, but when
   clicked 401 error page displayed
   -

   [STORE-1003 ] - [Internet
   Explorer] - Nothing happens when Bookmark button is clicked from Store
   asset list view
   -

   [STORE-1007 ] - Assets filtered
   by store search will remain the same even after logged in to store or even
   after logged out from store
   -

   [STORE-1009 ] - [Copy Asset]
   When we create a new version of an already created asset, Tag Details are
   not copied
   -

   [STORE-1010 ] - basic auth
   logout doesn't work
   -

   [STORE-1015 ] - Tenants cannot
   see newly created asset types
   -

   [STORE-1017 ] - Disabled Delete
   page is accessible when opened in a new tab
   -

   [STORE-1019 ] - Users cannot be
   registered with email as Username from Store when Email as Username is
   enabled in Carbon.xml
   -

   [STORE-1028 ] - Carbon users
   can Bookmark, Rate, Access My Items page of Tenant Domain assets
   -

   [STORE-1030 ] - Existing assets
   can be updated with any version (even duplicates)
   -

   [STORE-1031 ] - Only 10 assets
   can be bookmarked from the same asset type.
   -

   [STORE-1034 ] - Life cycle
   

Re: [Dev] Help needed for pubsub in UES 2.0.0

[Lalanke Athauda]

Hi Ruchira/ Manuranga,
Thank you so much for your detailed email. It was really helpful for me to
understand the code. Manuranga helped me to figure out the unclear places
in code and solve it.
I really appreciate your help in resolving the problem..

On Mon, Sep 14, 2015 at 5:24 PM, Manuranga Perera  wrote:

> [adding dev]
>
> thanks for responding Ruchira,
> We had some trouble figuring out the random number based ID part. didn't
> realize it was done custom by you not part of shindig.
> ones we figured that part we could successfully publish messages from
> dashboard to gadget.
>
>
> On Mon, Sep 14, 2015 at 4:04 PM, ruchira wageesha <
> ruchira.wagee...@gmail.com> wrote:
>
>> UES uses [1], which is the underline framework of shinding as well, to do
>> secure communication between iframes.
>>
>> AFAICR, these is something called a manage hub which you create for a
>> page. Iframes can connect to that managed hub where manage hub mediates the
>> messages.
>>
>> A container called, inline container can also connect to the hub. Inline
>> container is used to send pub-sub messages from the web page to the hub.
>> Then, the hub distribute it to all connected containers.
>>
>> AFAIK, ues.hub variable which is created, is a managed hub. By default
>> when you publish a message to the hub with a channel, it will notify all
>> subscribers of that channel. But, I have done several overridings to the
>> default hub behaviour to enable wiring based data publishing. So, if there
>> is no matching connection between two containers, then it will not get
>> notified.
>>
>> I am adding manu as well. He might help you to understand any unclear
>> stuff.
>>
>> /Ruchira
>>
>> [1]
>> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification#Table_of_Contents
>> [2]
>> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Publish_Subscribe_Overview
>> [3]
>> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Managed_Hub_Overview
>> [4]
>> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Managed_Hub_APIs
>> [5]
>> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Managed_Hub_Containers
>> [6]
>> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Unmanaged_Hub
>>
>> On Thu, Sep 10, 2015 at 4:54 PM, Lalanke Athauda 
>> wrote:
>>
>>> Hi,
>>> I'm Lalanke, newly joined to UES team. I need a big help from you.
>>>
>>> You have created inter gadget pubsub communication nicely in UES 2.0.0.
>>> It works fine. We can check the communication by adding g1 and g2 gadgets.
>>> They are working fine when we wire g2 with g1. Though there are no
>>> documentation we can see the code and learn.
>>>
>>> My problem is about communication among dashboard and gadgets. I want to
>>> communicate from dashboard and gadgets by using pubsub. Is it supported in
>>> UES 2.0.0. Since there is no doc I don't know how to do it.
>>>
>>> I tried from my dashboard like this,
>>>
>>> ues.hub.publish("org.wso2.ues.token.ch", "msg");
>>>
>>> Then add following lines to my gadget,
>>>
>>> 
>>> 
>>> >> description="display access token">
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> my *access-token.js* file,
>>>
>>> gadgets.HubSettings.onConnect = function() {
>>>
>>> gadgets.Hub.subscribe('org.wso2.ues.token.ch', function(topic,
>>> data, subscriberData) {
>>>
>>> $('#output').append(data);
>>> });
>>>
>>> };
>>>
>>> When I run this, it doesn't do anything. There is a wiring we need to do
>>> if we communicate among gadgets. But here we don't have those.
>>>
>>> I really need your help to solve this problem. I look forward to your
>>> favourable response and thank you in advance for your time and
>>> consideration.
>>>
>>> --
>>> Lalanke Athauda
>>> Software Engineer
>>> WSO2 Inc.
>>> Mobile: 0772264301
>>>
>>
>>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
Lalanke Athauda
Software Engineer
WSO2 Inc.
Mobile: 0772264301
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Help needed for pubsub in UES 2.0.0

[Manuranga Perera]

[adding dev]

thanks for responding Ruchira,
We had some trouble figuring out the random number based ID part. didn't
realize it was done custom by you not part of shindig.
ones we figured that part we could successfully publish messages from
dashboard to gadget.


On Mon, Sep 14, 2015 at 4:04 PM, ruchira wageesha <
ruchira.wagee...@gmail.com> wrote:

> UES uses [1], which is the underline framework of shinding as well, to do
> secure communication between iframes.
>
> AFAICR, these is something called a manage hub which you create for a
> page. Iframes can connect to that managed hub where manage hub mediates the
> messages.
>
> A container called, inline container can also connect to the hub. Inline
> container is used to send pub-sub messages from the web page to the hub.
> Then, the hub distribute it to all connected containers.
>
> AFAIK, ues.hub variable which is created, is a managed hub. By default
> when you publish a message to the hub with a channel, it will notify all
> subscribers of that channel. But, I have done several overridings to the
> default hub behaviour to enable wiring based data publishing. So, if there
> is no matching connection between two containers, then it will not get
> notified.
>
> I am adding manu as well. He might help you to understand any unclear
> stuff.
>
> /Ruchira
>
> [1]
> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification#Table_of_Contents
> [2]
> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Publish_Subscribe_Overview
> [3]
> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Managed_Hub_Overview
> [4]
> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Managed_Hub_APIs
> [5]
> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Managed_Hub_Containers
> [6]
> http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Specification_Unmanaged_Hub
>
> On Thu, Sep 10, 2015 at 4:54 PM, Lalanke Athauda  wrote:
>
>> Hi,
>> I'm Lalanke, newly joined to UES team. I need a big help from you.
>>
>> You have created inter gadget pubsub communication nicely in UES 2.0.0.
>> It works fine. We can check the communication by adding g1 and g2 gadgets.
>> They are working fine when we wire g2 with g1. Though there are no
>> documentation we can see the code and learn.
>>
>> My problem is about communication among dashboard and gadgets. I want to
>> communicate from dashboard and gadgets by using pubsub. Is it supported in
>> UES 2.0.0. Since there is no doc I don't know how to do it.
>>
>> I tried from my dashboard like this,
>>
>> ues.hub.publish("org.wso2.ues.token.ch", "msg");
>>
>> Then add following lines to my gadget,
>>
>> 
>> 
>> > description="display access token">
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> my *access-token.js* file,
>>
>> gadgets.HubSettings.onConnect = function() {
>>
>> gadgets.Hub.subscribe('org.wso2.ues.token.ch', function(topic, data,
>> subscriberData) {
>>
>> $('#output').append(data);
>> });
>>
>> };
>>
>> When I run this, it doesn't do anything. There is a wiring we need to do
>> if we communicate among gadgets. But here we don't have those.
>>
>> I really need your help to solve this problem. I look forward to your
>> favourable response and thank you in advance for your time and
>> consideration.
>>
>> --
>> Lalanke Athauda
>> Software Engineer
>> WSO2 Inc.
>> Mobile: 0772264301
>>
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store

[Mariangela Hills]

Hi Shabir,
I have documented this in [1].

[1]
https://docs.wso2.com/display/ES200/Adding+a+New+Sample+Asset+for+an+Asset+Type+at+Server+Startup

Regards,
Mariangela


*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185

On Fri, Sep 11, 2015 at 3:32 PM, Mariangela Hills 
wrote:

> I created a JIRA [1] to track this task.
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-2366
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Fri, Sep 11, 2015 at 10:25 AM, Mariangela Hills 
> wrote:
>
>> Thanks, Shabir! I will add this to the docs!
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Thu, Sep 10, 2015 at 10:47 PM, Shabir Mohamed  wrote:
>>
>>> Also to be added to *Common Mistakes:*
>>>
>>>
>>>- The *"name" *attribute and the *"overview_name"* attribute, both
>>>needs to have the same Value, (Ex: 'RaspberryPi' & 'Raspberry Pi' will 
>>> not
>>>work). *"name"* is the Artifact-Name and "*overview_name*" is the
>>>value used when creating the resource path in the registry.
>>>
>>>
>>> -
>>> *Shabir Mohamed*
>>> *Software Engineer*
>>> WSO2 Inc.; http://wso2.com
>>> Email: sha...@wso2.com 
>>> Mobile: +94 77 3516019 | +94 71 6583393
>>>
>>> On Thu, Sep 10, 2015 at 9:10 PM, Shabir Mohamed  wrote:
>>>
 Hi,

 I have been trying to do $subject and found no relevant documentation.
 Hence, I backtracked the path as to how the existing sample-artifacts of
 the default asset-types (i.e.: gadget & site) are added when running the
 WSO2 - Enterprise Store 2.0.

 *As per my study these are the necessary steps required to do $subject:*

 Say the Asset-type for which we want to add a sample artifact has its
 *"RXT"* name as *"device.rxt". **(sample txt attached in the email)*

 1. *The sample artifacts per asset-type are found at path:*

-

 */repository/deployment/server/jaggeryapps/publisher/samples/assets*
- Create a folder by the plural-name of the asset-type(rxt) in this
path. In this example we make a folder by the name *"devices"*.
- All sample/default artifacts of asset-type *"device" *shall go
into this folder.

 2. The parent installation script - *"install.js"* - for all samples
 is found at the above mentioned path. Any *"install.js"* scripts found
 within sub-folders *(ex: devices, gadgets & sites)* of this path will
 over-ride the parent script to perform any specific operations relavant to
 that asset-type.

- copy the sample asset-specific *"install.js"** (attached with
this email)* into the folder created in the previous step.
- search and change the following tags appropriately in the copied
script:

   ** : LifeCycle definition to which
 the asset-type *(in this example "device") *needs to be attached to *(ex:
 DeviceLifeCycle)*. Should be one of the lifecycle definitions found
 inside:
 */repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles/*
   ** : The *"rxt"* name of the
 asset-type for which the samples are to be made *(in this
 example "device"). *

- Save and close the *"install.js"* script.

 3. Create a folder by the name of the sample-artifact inside the
 asset-specific-parent-folder created in Step 1. In this example lets call
 our sample artifact of asset-type *"device"* as *"firealarm"*. We can
 continue adding any number of folders *per artifact* of the asset-type 
 *(ex:
 firearm, raspberryPi, arduino & etc)*. Artifact specific details go
 into these folders.

 *The folder structure
 at- /repository/deployment/server/jaggeryapps/publisher/samples 
 should
 look as follows:*

 *.*

 *└── samples*

 *└── assets*

 *├── devices*

 *│   ├── firealarm*

 *│   │   ├── banner.png*

 *│   │   ├── device.json*

 *│   │   └── thumbnail.png*

 *│   └── install.js*

 *└── install.js*


 4. Now we have to specify the asset specific attributes to be used when
 creating our sample (firealarm) artifact. These details are provided as a 
 *"json"
 *file with the same name as the asset-type/rxt *(.json)*.


- In our example this is found inside 

Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store

[Shabir Mohamed]

Hi,

Thanks a lot:D

Regards

-
*Shabir Mohamed*
*Software Engineer*
WSO2 Inc.; http://wso2.com
Email: sha...@wso2.com 
Mobile: +94 77 3516019 | +94 71 6583393

On Mon, Sep 14, 2015 at 6:45 PM, Mariangela Hills 
wrote:

> Hi Shabir,
> I have documented this in [1].
>
> [1]
> https://docs.wso2.com/display/ES200/Adding+a+New+Sample+Asset+for+an+Asset+Type+at+Server+Startup
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Fri, Sep 11, 2015 at 3:32 PM, Mariangela Hills 
> wrote:
>
>> I created a JIRA [1] to track this task.
>>
>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2366
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Fri, Sep 11, 2015 at 10:25 AM, Mariangela Hills 
>> wrote:
>>
>>> Thanks, Shabir! I will add this to the docs!
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Thu, Sep 10, 2015 at 10:47 PM, Shabir Mohamed 
>>> wrote:
>>>
 Also to be added to *Common Mistakes:*


- The *"name" *attribute and the *"overview_name"* attribute, both
needs to have the same Value, (Ex: 'RaspberryPi' & 'Raspberry Pi' will 
 not
work). *"name"* is the Artifact-Name and "*overview_name*" is the
value used when creating the resource path in the registry.


 -
 *Shabir Mohamed*
 *Software Engineer*
 WSO2 Inc.; http://wso2.com
 Email: sha...@wso2.com 
 Mobile: +94 77 3516019 | +94 71 6583393

 On Thu, Sep 10, 2015 at 9:10 PM, Shabir Mohamed 
 wrote:

> Hi,
>
> I have been trying to do $subject and found no relevant documentation.
> Hence, I backtracked the path as to how the existing sample-artifacts of
> the default asset-types (i.e.: gadget & site) are added when running the
> WSO2 - Enterprise Store 2.0.
>
> *As per my study these are the necessary steps required to do
> $subject:*
>
> Say the Asset-type for which we want to add a sample artifact has its
> *"RXT"* name as *"device.rxt". **(sample txt attached in the email)*
>
> 1. *The sample artifacts per asset-type are found at path:*
>
>-
>
> */repository/deployment/server/jaggeryapps/publisher/samples/assets*
>- Create a folder by the plural-name of the asset-type(rxt) in
>this path. In this example we make a folder by the name *"devices"*
>.
>- All sample/default artifacts of asset-type *"device" *shall go
>into this folder.
>
> 2. The parent installation script - *"install.js"* - for all samples
> is found at the above mentioned path. Any *"install.js"* scripts
> found within sub-folders *(ex: devices, gadgets & sites)* of this
> path will over-ride the parent script to perform any specific operations
> relavant to that asset-type.
>
>- copy the sample asset-specific *"install.js"** (attached with
>this email)* into the folder created in the previous step.
>- search and change the following tags appropriately in the copied
>script:
>
>   ** : LifeCycle definition to which
> the asset-type *(in this example "device") *needs to be attached to *(ex:
> DeviceLifeCycle)*. Should be one of the lifecycle definitions found
> inside:
> */repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles/*
>   ** : The *"rxt"* name of the
> asset-type for which the samples are to be made *(in this
> example "device"). *
>
>- Save and close the *"install.js"* script.
>
> 3. Create a folder by the name of the sample-artifact inside the
> asset-specific-parent-folder created in Step 1. In this example lets call
> our sample artifact of asset-type *"device"* as *"firealarm"*. We can
> continue adding any number of folders *per artifact* of the
> asset-type *(ex: firearm, raspberryPi, arduino & etc)*. Artifact
> specific details go into these folders.
>
> *The folder structure
> at- /repository/deployment/server/jaggeryapps/publisher/samples 
> should
> look as follows:*
>
> *.*
>
> *└── samples*
>
> *└── assets*
>
> *├── devices*
>
> *│   ├── firealarm*
>
> *│   │   ├── banner.png*

Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store

[Shabir Mohamed]

Hi Mariangela,

I thought the "Common Mistakes"would also be useful for someone who reads
the documentation.

Isn't it within our documentation guidelines to add something like that???
If so that's fine :D

-
*Shabir Mohamed*
*Software Engineer*
WSO2 Inc.; http://wso2.com
Email: sha...@wso2.com 
Mobile: +94 77 3516019 | +94 71 6583393

On Mon, Sep 14, 2015 at 8:09 PM, Shabir Mohamed  wrote:

> Hi,
>
> Thanks a lot:D
>
> Regards
>
> -
> *Shabir Mohamed*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> Email: sha...@wso2.com 
> Mobile: +94 77 3516019 | +94 71 6583393
>
> On Mon, Sep 14, 2015 at 6:45 PM, Mariangela Hills 
> wrote:
>
>> Hi Shabir,
>> I have documented this in [1].
>>
>> [1]
>> https://docs.wso2.com/display/ES200/Adding+a+New+Sample+Asset+for+an+Asset+Type+at+Server+Startup
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>>
>> On Fri, Sep 11, 2015 at 3:32 PM, Mariangela Hills 
>> wrote:
>>
>>> I created a JIRA [1] to track this task.
>>>
>>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2366
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>> *Mariangela Hills*
>>> Senior Technical Writer - WSO2, Inc. http://wso2.com
>>> Committer and PMC member - Apache Stratos
>>> email:mariang...@wso2.com | mobile: +94 773 500185
>>>
>>> On Fri, Sep 11, 2015 at 10:25 AM, Mariangela Hills 
>>> wrote:
>>>
 Thanks, Shabir! I will add this to the docs!

 Regards,
 Mariangela


 *Mariangela Hills*
 Senior Technical Writer - WSO2, Inc. http://wso2.com
 Committer and PMC member - Apache Stratos
 email:mariang...@wso2.com | mobile: +94 773 500185

 On Thu, Sep 10, 2015 at 10:47 PM, Shabir Mohamed 
 wrote:

> Also to be added to *Common Mistakes:*
>
>
>- The *"name" *attribute and the *"overview_name"* attribute, both
>needs to have the same Value, (Ex: 'RaspberryPi' & 'Raspberry Pi' will 
> not
>work). *"name"* is the Artifact-Name and "*overview_name*" is the
>value used when creating the resource path in the registry.
>
>
> -
> *Shabir Mohamed*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> Email: sha...@wso2.com 
> Mobile: +94 77 3516019 | +94 71 6583393
>
> On Thu, Sep 10, 2015 at 9:10 PM, Shabir Mohamed 
> wrote:
>
>> Hi,
>>
>> I have been trying to do $subject and found no relevant
>> documentation. Hence, I backtracked the path as to how the existing
>> sample-artifacts of the default asset-types (i.e.: gadget & site) are 
>> added
>> when running the WSO2 - Enterprise Store 2.0.
>>
>> *As per my study these are the necessary steps required to do
>> $subject:*
>>
>> Say the Asset-type for which we want to add a sample artifact has its
>> *"RXT"* name as *"device.rxt". **(sample txt attached in the email)*
>>
>> 1. *The sample artifacts per asset-type are found at path:*
>>
>>-
>>
>> */repository/deployment/server/jaggeryapps/publisher/samples/assets*
>>- Create a folder by the plural-name of the asset-type(rxt) in
>>this path. In this example we make a folder by the name
>>*"devices"*.
>>- All sample/default artifacts of asset-type *"device" *shall go
>>into this folder.
>>
>> 2. The parent installation script - *"install.js"* - for all samples
>> is found at the above mentioned path. Any *"install.js"* scripts
>> found within sub-folders *(ex: devices, gadgets & sites)* of this
>> path will over-ride the parent script to perform any specific operations
>> relavant to that asset-type.
>>
>>- copy the sample asset-specific *"install.js"** (attached with
>>this email)* into the folder created in the previous step.
>>- search and change the following tags appropriately in the
>>copied script:
>>
>>   ** : LifeCycle definition to
>> which the asset-type *(in this example "device") *needs to be
>> attached to *(ex: DeviceLifeCycle)*. Should be one of the lifecycle
>> definitions found inside:
>> */repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles/*
>>   ** : The *"rxt"* name of the
>> asset-type for which the samples are to be made *(in this
>> example "device"). *
>>
>>- Save and close the *"install.js"* script.
>>
>> 3. Create a folder by the name of the sample-artifact inside the
>> asset-specific-parent-folder created in Step 1. In 

Re: [Dev] WARN messages in log while accessing dashboard

[Gokul Balakrishnan]

UES team, any suggestions for this?

On Thursday, 10 September 2015, Gokul Balakrishnan  wrote:

> Hi UES team,
>
> We're seeing the following warning repeatedly when accessing the
> dashboard, seems this has been known for a while. Are there any adverse
> effects, or is it OK to hide this warn from the console?
>
> [2015-09-10 17:34:26,149]  WARN {net.sf.ehcache.pool.sizeof.SizeOf} -  The
> configured limit of 1,000 object references was reached while attempting to
> calculate the size of the object graph. This can be avoided by adding stop
> points with @IgnoreSizeOf annotations. Since the CacheManger or Cache
>  elements maxDepthExceededBehavior is set to "abort", the
> sizing operation has stopped and the reported cache size is not accurate.
> If performance degradation is NOT an issue at the configured limit, raise
> the limit value using the CacheManager or Cache  elements
> maxDepth attribute. For more information, see the Ehcache configuration
> documentation.
>
> Thanks,
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>


-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Log Error with SolrClient when parsing date

[Jorge]

Hi folks,
In WSO2 DAS BETA 2 and in WSO2 ESB 4.9.0 I see this error in console:


[2015-09-14 10:46:34,239] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,239] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,242] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,244] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,246] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,249] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,248] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,250] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,248] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,252] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,248] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,248] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,248] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,256] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,247] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,246] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,258] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,258] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,257] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,257] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,256] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,255] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 10:46:34,255] ERROR
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Error when passing
date to create solr date format.java.text.ParseException: Unparseable date:
"Mon Sep 14 10:45:53 EDT 2015"
[2015-09-14 

[Dev] [IS] [SSO] How to increase SSO session time out

[Sumedha Kodithuwakku]

Hi IS team,

$subject. There is a SessionTimeOut under SSOService in identity.xml, but
it says for remember me session timeout.

Is there a way to increase the session time out for the SSO session.?

Thanks
SumedhaS

-- 
*Sumedha Kodithuwakku*
Senior Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware

Mobile: +94 71 808 1124
Blog: http://sumedhask.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Carbon Metrics UI OSGi Fragment Bundle issue

[Nirmal Fernando]

Hi All,

Any thoughts?

On Tue, Sep 8, 2015 at 3:11 PM, Isuru Perera  wrote:

> Hi,
>
> With WSO2 Carbon Metrics release 1.1.0 [1], WSO2 Products can extend the
> Metrics UI and show product specific metrics in Management Console.
>
> WSO2 Message Broker successfully use a Fragment Bundle to show Messaging
> Metrics [2].
>
> Now WSO2 Machine Learner product also wants show some ML specific metrics.
> When we create a similar component like [2], we encounter following issue.
>
> [2015-09-08 13:20:58,603] ERROR - ApplicationDispatcher Servlet.service()
> for servlet bridgeservlet threw exception
> javax.servlet.ServletException: File /metrics-view/index.jsp
> not found
>
> After further checking, we found out that the following properties in
> MANIFEST.MF causes the issue.
>
> Bundle-Name: org.wso2.carbon.ml.metrics.ui
> Bundle-SymbolicName: org.wso2.carbon.ml.metrics.ui
>
> For example, If we change the "ml" to "ma" (org.wso2.carbon.*ma*
> .metrics.ui), the Fragment Bundle works fine.
>
> The host bundle source is at [3].
>
> If anyone wants to try this, build the Metrics tag v1.1.0 [1] locally and
> install Metrics Feature to any WSO2 product via the Feature Manager. Please
> use the target/p2-repo directory found in [4].
>
> Then try copying Messaging Metrics UI jar [5] to dropins. The Messaging
> Metrics UI works. If we change the bundle name and symbolic name as
> mentioned above, there will be an error.
>
> Any idea how these bundle names affect the Fragment Bundle?
>
> Thanks!
>
> Best Regards,
>
> [1] https://github.com/wso2/carbon-metrics/releases/tag/v1.1.0
> [2]
> https://github.com/wso2/carbon-business-messaging/tree/master/components/metrics/org.wso2.carbon.messaging.metrics.ui
> [3]
> https://github.com/wso2/carbon-metrics/tree/v1.1.0/components/org.wso2.carbon.metrics.view.ui
> [4] https://github.com/wso2/carbon-metrics/tree/v1.1.0/features/repository
> [5]
> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/messaging/org.wso2.carbon.messaging.metrics.ui/2.6.1/
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] [SSO] How to increase SSO session time out

[Johann Nallathamby]

In IS 5.0.0 SP 01, session timeout cannot be changed. But remember timeout
can be changed. The configuration is in identity.xml
under JDBCPersistenceManager -> SessionDataPersist -> RememberMePeriod. We
will provide the capability to configure session timeouts and remember me
timeouts per tenant in the UI for IS 5.1.0.

Thanks.

On Mon, Sep 14, 2015 at 8:15 PM, Sumedha Kodithuwakku 
wrote:

> Hi IS team,
>
> $subject. There is a SessionTimeOut under SSOService in identity.xml, but
> it says for remember me session timeout.
>
> Is there a way to increase the session time out for the SSO session.?
>
> Thanks
> SumedhaS
>
> --
> *Sumedha Kodithuwakku*
> Senior Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> Mobile: +94 71 808 1124
> Blog: http://sumedhask.blogspot.com/
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Announcement] WSO2 Enterprise Service Bus Connector Store Released !!

[Kathees Rajendram]

WSO2 Platform Extensions team is pleased to announce the release of WSO2
Connector Store for WSO2 Enterprise Service Bus.


Connectors allow interacting with a third-party product's functionality and
data from WSO2 Enterprise Service Bus message flow, enabling you to connect
to and interact with third-party APIs and standard integration protocols.

WSO2 Enterprise Service Bus can be extended with the many extension points
to plug into. Connectors are build on top of this extensible framework.

To browse through WSO2 Connectors and to download a required connector, go
to https://store.wso2.com/store.

For more information on connectors and how to configure operations for each
connector, see.
https://docs.wso2.com/display/ESBCONNECTORS/WSO2+ESB+Connectors+Documentation
.

For information on how to work with connectors, see
https://docs.wso2.com/display/ESB490/Working+with+Connectors.


Following are the connectors available in WSO2 Connector Store:

*Billing and Accounting*

   - Billiving
   - Recurly
   - FreeAgent
   - Xero
   - Stripe
   - Chargebee
   - FreshBooks
   - Paypal
   - Billomat
   - Braintree
   - Ronin
   - QuickBooks

*Communication*

   - Mandrill
   - Nexmo
   - Gmail
   - CallRail
   - Amazon SES
   - Twilio
   - LiveChat

*Customer Relationship Management*

   - Base CRM
   - Zoho CRM
   - Nimble
   - Sirportly
   - Pipedrive
   - Salesforce
   - PipelineDeals
   - FreshDesk
   - Capsule CRM
   - Zendesk
   - Insightly
   - Clevertim CRM
   - SupportBee
   - Sugar CRM

*Developer Tools*

   - LDAP
   - BitBucket
   - Github
   - File
   - Amazon Simple Queue
   - Loggly
   - Amazon Simple DB
   - Amazon S3
   - Google Prediction

*E-commerce*



   - Shopify
   - Magento
   - eBay
   - Netsuite
   - TradeGecko

*Education*

   - Canvas

*Human Resource Management*

   - Zoho People
   - PeopleHR
   - Zoho Recruit
   - Deputy

*IOT*

   - Nest

*Issue Tracking and Project Management*

   - Podio
   - PagerDuty
   - Teamwork
   - Bugherd
   - Activecollab
   - Basecamp
   - Redmine
   - PivotalTracker
   - Prodpad
   - Cashboard
   - Agilezen
   - ProWorkflow
   - Jira

*Productivity Tools*

   - Delicious
   - EverNote
   - Confluence
   - GoToWebinar
   - Google Custom Search
   - SimpleNote
   - Tsheets
   - GoToTraining
   - Google Calendar
   - Formstack
   - Google Spreadsheet
   - Jotform
   - Wunderlist
   - Apple Push Notification
   - Google Tasks

*Sales and Marketing*

   - Eloqua Standard
   - Eloqua
   - Marketo
   - ExactTarget
   - ConstantContact
   - ActiveCampaign
   - SurveyGizmo
   - Campaign Monitor
   - VerticalResponse
   - MailChimp

*Social Media*

   - Wordpress
   - Instagram
   - GooglePlus
   - Foursquare
   - Spotify
   - Yelp
   - Yammer
   - Twitter
   - LinkedIn
   - Flickr

*Storage and Content Management*

   - Slideshare
   - Dropbox
   - Box
   - Google Blogger
   - Disqus

*Other*

   - OpenWeatherMap
   - Planyo
   - Concur
   - Eventbrite
   - Survey Monkey
   - Shippo
   - Clio

*How You Can Contribute*

You can create a connector and publish it in WSO2 store. For more
information, see.
https://docs.wso2.com/display/ESBCONNECTORS/Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Connector+Store
.

*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.


-- The WSO2 Platform Extensions Team --

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

Re: [Dev] cron job on MessageProcessor?

[John Hawkins]

Hi Folks,

Gentle nudge on this if I may - trying to write an article on this stuff so
any help would be much appreciated :-) Anyone know what the message is
that's sent to the deactive sequence?

many thanks,
john.

John Hawkins
Director: Solutions Architecture


On Fri, Sep 11, 2015 at 8:51 AM, John Hawkins  wrote:

> Thanks for your thoroughness folks !!
>
> I'm not sure, from the description, what gets sent to  the 
> message.processor.deactivate.sequence
> - is it the message that failed or just the reply from the server or both?
>
> cheers,
> John.
>
> John Hawkins
> Director: Solutions Architecture
>
>
> On Thu, Sep 10, 2015 at 7:47 PM, Vanjikumaran Sivajothy 
> wrote:
>
>>
>> [1] jira for the doc
>> https://wso2.org/jira/browse/DOCUMENTATION-952
>>
>> On Thu, Sep 10, 2015 at 11:44 AM, Vanjikumaran Sivajothy 
>> wrote:
>>
>>> Hi John,
>>>
>>>
>>> On Wed, Sep 9, 2015 at 4:51 AM, John Hawkins  wrote:
>>>
 Aargh - I meant "max.delivery.drop" ! I can't see that docced anywhere?

>>>
>>>
>>> This new parameter is introduced in ESB 4.9.0 onwards. It should be
>>> there in the 490 documentation according to [1]
>>>
>>> [1]  https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor
>>>
>>>
>>>
>>>
 So we are implementing a trigger sequence for when MessageProcessor
 gets de-activated? I think is the same thing I'm thinking of isn't it ?
 When the message fails to get sent after n retries then the sequence gets
 called - presumably with the message that's failing as part of the payload
 in the sequence - along with the error message from the server too?

 cheers for the clarifications !
 John.

 John Hawkins
 Director: Solutions Architecture


 On Wed, Sep 9, 2015 at 12:41 PM, Ravindra Ranwala 
 wrote:

> Hi John,
>
> Message Processor Max Delivery attempt parameter is clearly documented
> here [1].
>
>
> Anyway in ESB 4.9.0 version we have deactivateSequence, which can be
> triggered when the Message Processor is deactivated after reaching
> max-delivery-attempts. In that sequence you may implement DLC pattern.
>
> Also I understand that your requirement is valid, and you may create a
> public jira to track that. We may incorporate it in to the product in a
> future release.
>
>
>
> [1] https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor
>
>
>
> Thanks & Regards,
>
> On Wed, Sep 9, 2015 at 4:07 PM, John Hawkins  wrote:
>
>> Hi Ravindra,
>> I'm thinking about this a lot now
>> max.delivery.attempts is not documented anywhere nor is it in the
>> MessageProcessor wizard (but it is in a few JIRA's and blog entries). Is
>> this deliberate do you know - are we hiding it for some reason?
>>
>> Personally I would expect some kind of 'retries fail' sequence to be
>> an optional thing I can set. Then I could do what I wanted with the 
>> message
>> and the MessageProcessor can continue. Are you aware of any thoughts like
>> this at all? If not then I think I need to create a JIRA to at least
>> document this feature as-is.
>>
>> cheers,
>> john.
>>
>> John Hawkins
>> Director: Solutions Architecture
>>
>>
>> On Wed, Sep 9, 2015 at 11:03 AM, Ravindra Ranwala 
>> wrote:
>>
>>> Hi John,
>>>
>>> There is no DLC behaviour after reaching the max-retry-count at the
>>> moment.
>>>
>>>
>>> Thanks & Regards,
>>>
>>> On Wed, Sep 9, 2015 at 3:23 PM, John Hawkins  wrote:
>>>
 Another question - is there no Dead Letter Queue behaviour then if
 a message fails to get sent after max_retry is done?

 John Hawkins
 Director: Solutions Architecture


 On Thu, Sep 3, 2015 at 4:41 PM, Ravindra Ranwala  wrote:

> Hi John,
>
> The Cron expression in MP is used to create firing schedules such
> as "At 8:00am every Monday through Friday" [1]. If it is set the MP 
> will
> run according to that. Otherwise MP will poll the queue with the 
> specified
> interval value continuously.
>
> Also the MP has a parameter called max_delivery_attempts (defaults
> to 4), which defines the maximum retry attempts in case of a failure 
> in end
> point. By default if the MP could not send the message to the end 
> point
> after this number of retry count, it deactivates itself. But that 
> message
> remains in the queue. After that you have to activate the MP 
> explicitly to
> make the next schedule to be effective. Otherwise it will remain
> 

[Dev] WSO2 Identity Server 5.1.0 Alpha Released !!

[Hasintha Indrajee]

WSO2 Identity Server 5.1.0 Alpha Released !!
Date: 14th September 2015The WSO2 Identity Server team is pleased to
announce the release of WSO2 Identity Server 5.1.0 Alpha. You can download
this distribution from
*https://github.com/wso2/product-is/releases/tag/v5.1.0-alpha
*

Following list [1] contains all bug fixes and improvements available with
alpha release. We encourage you to report issues, improvements and feature
requests regarding WSO2 Identity Server through the public WSO2 Identity
Server JIRA 

~ The WSO2 Identity Server Team ~

[1] Release Notes - WSO2 Identity Server - Version 5.1.0-Alpha

Bug

   - [IDENTITY-836 ] - The
   pagination on the google chrome shows a box around the paginations numbers
   and next previous/ first last words
   - [IDENTITY-1163 ] - Disable
   use of a generated OAuth token by a user,when that user locked [removed
   from users-store] from current users-base.
   - [IDENTITY-1217 ] -
   Passwords in Ldap are stored in plain text
   - [IDENTITY-1830 ] - When a
   tenant is created in one node of the IS cluster; at the first attempt of
   login; if the request is redirected to the other node of the cluster; login
   will be failed
   - [IDENTITY-2512 ] -
   [Cluster setup] [Tenant mode] SAML2 SSO login fails in one node
   - [IDENTITY-2525 ] -
   [Cluster] [Tenant mode] Error observed in SAML -> SAML federated scenario
   - [IDENTITY-2553 ] -
   "ForceAuthn" parameter in SAML SSO request must be passed to federated
   SAML2 SSO authenticators by default
   - [IDENTITY-2585 ] -
   AuthnContextClassRef is hardcoded.
   - [IDENTITY-2602 ] - IDP are
   not loading in tenant mode under home realm discovery mode in Application
   authentication
   - [IDENTITY-2675 ] -
   NullPointerException thrown when trying to access an already authenticated
   session at IdP
   - [IDENTITY-2754 ] - SCIM
   filtering Eq not adhering to the SCIM 1.1 specification
   - [IDENTITY-2781 ] -
   updateRolesOfUser(String userName, String[] newUserList) in UserAdmin
   service does not working
   - [IDENTITY-2796 ] - Support
   for HTTP-POST binding for SAML2 SSO federated authenticator
   - [IDENTITY-2861 ] - Receive
   fault response from RemoteClaimManagerService
   - [IDENTITY-2904 ] -
   exception when searching for an internal user role
   - [IDENTITY-2983 ] - Define
   Custom SSL context SSO Agent client library.
   - [IDENTITY-3102 ] -
   Creating a identity provider with malformed certificate cause to disappear
   the IdP's edit view and certificate file content validation needed when
   adding IdP certificate
   - [IDENTITY-3152 ] - User
   name case sensitivity issue with Oracle as user store.
   - [IDENTITY-3195 ] - Add
   Identity Provider page of the carbon console doesn't validate "Identity
   Provider Public Certificate" uploaded by the user.
   - [IDENTITY-3230 ] - After
   setting a user store from Inbound Provisioning SCIM, for creating groups
   and listing users SCIM uses PRIMARY user store.
   - [IDENTITY-3236 ] - There
   is no UI Entry to add DisplayNameAttribute value when creating a Secondary
   user stores
   - [IDENTITY-3254 ] - Error
   when evaluate XAML request via Tryit tool
   - [IDENTITY-3301 ] - Users
   in different tenants can log in to non-saas apps when response/assertion
   signing disabled
   - [IDENTITY-3316 ] - OAuth
   clientid, client secret encryption does not work
   - [IDENTITY-3354 ] - SAML to
   OAuth Grant not working for Tenant (Travelocity)
   - [IDENTITY-3359 ] - When
   trying creating a role with existing name all the permissions get removed
   from the existing role
   - [IDENTITY-3370 ] - SSO
   with IWA broken after the security patch
   - [IDENTITY-3416 

Re: [Dev] Setting MVCC=TRUE causing null pointer issues in AppFactory - H2 DB

[Akila Ravihansa Perera]

Hi Aiyadurai,

I'm hitting the same issue in Apache Stratos when running integration
tests. It seems to be intermittent. Were you able to resolve this issue?

Thanks.

On Mon, Feb 2, 2015 at 6:19 PM, Aiyadurai Rajeevan 
wrote:

> Hi,
>
> While creating tenants concurrently in AppFactory we got the error [2]
>  and found a solution adding *MVCC=true* in the database URL as
> suggested in [1]  but its throwing null point exception [3]
> while logging to AppFactory for a fresh tenant which doesn't
> have any application.
>
> The modified URL in the master-datasources.xml looks like 
> *jdbc:h2:/mnt/192.168.16.2/appfactory/wso2appfactory-2.1.0-SNAPSHOT/repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6;MVCC=true
> *
>
> Any insight with regard to this would be much appreciated.
>
> [1]
> http://stackoverflow.com/questions/4162557/timeout-error-trying-to-lock-table-in-h2
>
> [2]
> Caused by: org.wso2.carbon.governance.api.exception.GovernanceException:
> Error in getting the path from the registry. Execute query failed with
> message : Timeout trying to lock table "REG_RESOURCE"; SQL statement:
> SELECT REG_PATH_ID, REG_NAME FROM REG_RESOURCE WHERE
> (REG_RESOURCE.REG_TENANT_ID=?) AND  REG_UUID = ? [50200-140]
> at
> org.wso2.carbon.governance.api.util.GovernanceUtils.getArtifactPath(GovernanceUtils.java:741)
> at
> org.wso2.carbon.governance.api.util.GovernanceUtils.retrieveGovernanceArtifactById(GovernanceUtils.java:858)
> at
> org.wso2.carbon.governance.api.common.GovernanceArtifactManager.getGovernanceArtifact(GovernanceArtifactManager.java:498)
> at
> org.wso2.carbon.governance.api.generic.GenericArtifactManager.getGenericArtifact(GenericArtifactManager.java:193)
> at
> org.wso2.carbon.appfactory.core.governance.ApplicationManager.getApplication(ApplicationManager.java:172)
> ... 65 more
> Caused by: org.wso2.carbon.registry.core.exceptions.RegistryException:
> Timeout trying to lock table "REG_RESOURCE"; SQL statement:
> SELECT REG_PATH_ID, REG_NAME FROM REG_RESOURCE WHERE
> (REG_RESOURCE.REG_TENANT_ID=?) AND  REG_UUID = ? [50200-140]
>
>
> [3]
> TID: [0] [AF] [2015-02-02 17:43:00,882] ERROR
> {module/application/get/list.jag} -
>  org.mozilla.javascript.WrappedException: Wrapped
> java.lang.NullPointerException (/appmgt/modules/application/get/list.jag#61)
> at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
> at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
> at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
> at
> org.jaggeryjs.rhino.appmgt.modules.application.get.c0._c_anonymous_3(/appmgt/modules/application/get/list.jag:61)
> at
> org.jaggeryjs.rhino.appmgt.modules.application.get.c0.call(/appmgt/modules/application/get/list.jag)
> at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
> at
> org.jaggeryjs.rhino.appmgt.modules.application.get.c0._c_anonymous_6(/appmgt/modules/application/get/list.jag:118)
> at
> org.jaggeryjs.rhino.appmgt.modules.application.get.c0.call(/appmgt/modules/application/get/list.jag)
> at
> org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
> at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
> at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
> at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
> at
> org.jaggeryjs.rhino.appmgt.modules.application.c0._c_anonymous_10(/appmgt/modules/application/module.jag:58)
> at
> org.jaggeryjs.rhino.appmgt.modules.application.c0.call(/appmgt/modules/application/module.jag)
> at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
> at
> org.jaggeryjs.rhino.appmgt.site.pages.c1._c_anonymous_1(/appmgt/site/pages/index.jag:38)
> at
> org.jaggeryjs.rhino.appmgt.site.pages.c1.call(/appmgt/site/pages/index.jag)
> at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
> at
> org.jaggeryjs.rhino.appmgt.site.pages.c1._c_script_0(/appmgt/site/pages/index.jag:23)
> at
> org.jaggeryjs.rhino.appmgt.site.pages.c1.call(/appmgt/site/pages/index.jag)
> at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
> at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
> at
> org.jaggeryjs.rhino.appmgt.site.pages.c1.call(/appmgt/site/pages/index.jag)
> at
> org.jaggeryjs.rhino.appmgt.site.pages.c1.exec(/appmgt/site/pages/index.jag)
> at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567)
> at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
> at
> org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:541)
> at 

Re: [Dev] Jenkins build became unstable: product-as #722

[Manuri Amaya Perera]

The problem is when OSGIServerBundleStatusTestCase is running with offset
9864. Yesterday when I was building on my machine I might have commented
out the two test cases in testng-server-mgt.xml inside which this test case
is in.

I kept it running last night too and now I saw it has failed in my machine
too it has failed.

When I use another port except 101 for OSGIServerBundleStatusTestCase, this
doesn't fail.

On Tue, Sep 15, 2015 at 7:25 AM, Supun Malinga  wrote:

> Adding dev@
>
> Issue is "Port already in use".
> Seems there is another server is running. I think some other test case is
> also using the same port. You might need to use different ports.
>
> thanks,
>
> On Tue, Sep 15, 2015 at 6:35 AM, Manuri Amaya Perera 
> wrote:
>
>> I'll look into this.
>>
>> On Tue, Sep 15, 2015 at 5:53 AM,  wrote:
>>
>>> See 
>>>
>>>
>>
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>



-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Migrate to data publisher agent on carbon-analytics-common

[Sumedha Rubasinghe]

Anjana,
IMO this is serious problem for all products that have been released and
trying to use new DAS.

I think this can be easily fixed by adhering a new package name for new DAS
based data publishers.



On Mon, Sep 14, 2015 at 10:53 AM, Ayyoob Hamza  wrote:

> Hi All,
> We are trying to integrate DAS Features to CDMF and we found that DAS uses
> the latest data publisher agent[1]. Wherein APIM and ES has used the one on
> carbon-commons[2]. This is raised a conflict on feature installation.
> Furthermore we have found that APIM is also dependent on a osgi service[3]
> which available on carbon-deployment, and this also requires the
> carbon-common publisher agent. So I believe we have to migrate from the
> carbon-common data publisher to the new one on all 3 components since the
> old one will not have any support anymore. WDYT ?.
>
> eg:
> Cannot complete the install because of a conflicting dependency.
>  Software being installed: WSO2 Carbon - Data Bridge - Data Publisher
> Aggregate Feature 4.4.7
> (org.wso2.carbon.databridge.datapublisher.feature.group 4.4.7) - Data
> Publisher under carbon commons
>
>  Software being installed: WSO2 Carbon - Data Bridge - Data Publisher
> Aggregate Feature 5.0.1
> (org.wso2.carbon.databridge.datapublisher.feature.group 5.0.1) - Data
> Publisher under carbon analytics commons
>
> Currently in order to work on the pack, did a small work around by
> including the thrift data publisher as a bundle within the feature. So that
> we can test the DAS features. But this is just for testing purposes.
>
> [1]
> https://github.com/wso2/carbon-analytics-common/tree/master/components/data-bridge
> [2]
> https://github.com/wso2/carbon-commons/tree/4.4.x/components/data-bridge
> [3]
> https://github.com/wso2/carbon-deployment/tree/v4.5.0/components/service-mgt/bam-data-agents/org.wso2.carbon.bam.service.data.publisher/src/main/java/org/wso2/carbon/bam/service/data/publisher
>
> Thanks,
> *Ayyoob Hamza*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>



-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF Tools] use "master" as the label for default branch instead of "trunk"

[Jasintha Dasanayake]

Hi Kavith

Yes , we should not keep any mapping in DevS side , once this change is
done  in AF this should be reflected into DevS so there shouldn't be
anything to change in DevS side right ?

Thanks and Regards
/Jasintha


On Mon, Sep 14, 2015 at 12:39 PM, Manjula Rathnayake 
wrote:

> Hi Kavith,
>
> IMO, we should not store any mapping in DevStuido level. This needs to be
> fixed in AF REST API level as well as in backends of AF and it require
> considerable time to test and do any data migration if required too.
> Since this is not a blocker, we will fix this in M6 milestone and you can
> incorporate the changes to next release of Dev Studio or do a AF feature
> release with other UX improvements.
>
> thank you.
>
>
> On Fri, Sep 11, 2015 at 6:06 PM, Danushka Fernando 
> wrote:
>
>> I guess we use trunk because we started this with svn and then moved on
>> to git. +1 for renaming. @Manjula WDYT?
>>
>> Thanks & Regards
>> Danushka Fernando
>> Senior Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>> On Fri, Sep 11, 2015 at 5:00 PM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi,
>>>
>>> This is regarding $subject raised in [1] and [2].
>>>
>>> Currently the default version of an application is given the version
>>> "trunk" (which corresponds to "master" branch of the git repo). When
>>> checking out a version, DevStudio checks whether the user is checking out
>>> the version "trunk" and if so, sets "master" as the branch to checkout.
>>> However, when labeling the list of apps in tree view, we are not doing a
>>> mapping from "trunk" to "master". Rather we display the list of versions
>>> returned from AF API as it is.
>>> To fix this, either we have to maintain such a mapping in DevStudio side
>>> or this can be fixed from the AF side itself - by renaming version "trunk"
>>> to "master".
>>> Most importantly, it will be a bad experience for the user if we use two
>>> different version names in AF UI and DevS UI, to display this  default
>>> version.
>>> Is it possible (or make sense) to change this from AppFactory? Please
>>> share your thoughts.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/TOOLS-3142
>>> [2] https://wso2.org/jira/browse/TOOLS-3143
>>>
>>> Thanks,
>>>
>>> --
>>> *Kavith Lokuhewage*
>>> Software Engineer
>>> WSO2 Inc. - http://wso2.com
>>> lean . enterprise . middleware
>>> Mobile - +9477-9-145-123 | +9471-455-6-401
>>> Linkedin 
>>> Twitter 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Manjula Rathnayaka
> Associate Technical Lead
> WSO2, Inc.
> Mobile:+94 77 743 1987
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Jasintha Dasanayake*

*Senior Software EngineerWSO2 Inc. | http://wso2.com lean
. enterprise . middleware*


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

Re: [Dev] Jenkins build became unstable: product-as #722

[Manuri Amaya Perera]

Mistake. "Running with offset 101"
On 15 Sep 2015 07:31, "Manuri Amaya Perera"  wrote:

> The problem is when OSGIServerBundleStatusTestCase is running with offset
> 9864. Yesterday when I was building on my machine I might have commented
> out the two test cases in testng-server-mgt.xml inside which this test case
> is in.
>
> I kept it running last night too and now I saw it has failed in my machine
> too it has failed.
>
> When I use another port except 101 for OSGIServerBundleStatusTestCase,
> this doesn't fail.
>
> On Tue, Sep 15, 2015 at 7:25 AM, Supun Malinga  wrote:
>
>> Adding dev@
>>
>> Issue is "Port already in use".
>> Seems there is another server is running. I think some other test case is
>> also using the same port. You might need to use different ports.
>>
>> thanks,
>>
>> On Tue, Sep 15, 2015 at 6:35 AM, Manuri Amaya Perera 
>> wrote:
>>
>>> I'll look into this.
>>>
>>> On Tue, Sep 15, 2015 at 5:53 AM,  wrote:
>>>
 See 


>>>
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> email: sup...@wso2.com 
>> mobile: +94 (0)71 56 91 321
>>
>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Jenkins build became unstable: product-as #722

[Supun Malinga]

Adding dev@

Issue is "Port already in use".
Seems there is another server is running. I think some other test case is
also using the same port. You might need to use different ports.

thanks,

On Tue, Sep 15, 2015 at 6:35 AM, Manuri Amaya Perera 
wrote:

> I'll look into this.
>
> On Tue, Sep 15, 2015 at 5:53 AM,  wrote:
>
>> See 
>>
>>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Setting MVCC=TRUE causing null pointer issues in AppFactory - H2 DB

[Aiyadurai Rajeevan]

Hi Akila,

Yes it was intermittent, But after setting the property we couldn't observe
such error for long time.

Thanks & Regards,
S.A.Rajeevan
Software Engineer WSO2 Inc
E-Mail: rajeev...@wso2.com | Mobile : +94776411636

On Mon, Sep 14, 2015 at 11:09 PM, Akila Ravihansa Perera  wrote:

> Hi Aiyadurai,
>
> I'm hitting the same issue in Apache Stratos when running integration
> tests. It seems to be intermittent. Were you able to resolve this issue?
>
> Thanks.
>
> On Mon, Feb 2, 2015 at 6:19 PM, Aiyadurai Rajeevan 
> wrote:
>
>> Hi,
>>
>> While creating tenants concurrently in AppFactory we got the error [2]
>>  and found a solution adding *MVCC=true* in the database URL
>> as suggested in [1]  but its throwing null point exception [3]
>> while logging to AppFactory for a fresh tenant which doesn't
>> have any application.
>>
>> The modified URL in the master-datasources.xml looks like 
>> *jdbc:h2:/mnt/192.168.16.2/appfactory/wso2appfactory-2.1.0-SNAPSHOT/repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6;MVCC=true
>> *
>>
>> Any insight with regard to this would be much appreciated.
>>
>> [1]
>> http://stackoverflow.com/questions/4162557/timeout-error-trying-to-lock-table-in-h2
>>
>> [2]
>> Caused by: org.wso2.carbon.governance.api.exception.GovernanceException:
>> Error in getting the path from the registry. Execute query failed with
>> message : Timeout trying to lock table "REG_RESOURCE"; SQL statement:
>> SELECT REG_PATH_ID, REG_NAME FROM REG_RESOURCE WHERE
>> (REG_RESOURCE.REG_TENANT_ID=?) AND  REG_UUID = ? [50200-140]
>> at
>> org.wso2.carbon.governance.api.util.GovernanceUtils.getArtifactPath(GovernanceUtils.java:741)
>> at
>> org.wso2.carbon.governance.api.util.GovernanceUtils.retrieveGovernanceArtifactById(GovernanceUtils.java:858)
>> at
>> org.wso2.carbon.governance.api.common.GovernanceArtifactManager.getGovernanceArtifact(GovernanceArtifactManager.java:498)
>> at
>> org.wso2.carbon.governance.api.generic.GenericArtifactManager.getGenericArtifact(GenericArtifactManager.java:193)
>> at
>> org.wso2.carbon.appfactory.core.governance.ApplicationManager.getApplication(ApplicationManager.java:172)
>> ... 65 more
>> Caused by: org.wso2.carbon.registry.core.exceptions.RegistryException:
>> Timeout trying to lock table "REG_RESOURCE"; SQL statement:
>> SELECT REG_PATH_ID, REG_NAME FROM REG_RESOURCE WHERE
>> (REG_RESOURCE.REG_TENANT_ID=?) AND  REG_UUID = ? [50200-140]
>>
>>
>> [3]
>> TID: [0] [AF] [2015-02-02 17:43:00,882] ERROR
>> {module/application/get/list.jag} -
>>  org.mozilla.javascript.WrappedException: Wrapped
>> java.lang.NullPointerException (/appmgt/modules/application/get/list.jag#61)
>> at
>> org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
>> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
>> at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
>> at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
>> at
>> org.jaggeryjs.rhino.appmgt.modules.application.get.c0._c_anonymous_3(/appmgt/modules/application/get/list.jag:61)
>> at
>> org.jaggeryjs.rhino.appmgt.modules.application.get.c0.call(/appmgt/modules/application/get/list.jag)
>> at
>> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
>> at
>> org.jaggeryjs.rhino.appmgt.modules.application.get.c0._c_anonymous_6(/appmgt/modules/application/get/list.jag:118)
>> at
>> org.jaggeryjs.rhino.appmgt.modules.application.get.c0.call(/appmgt/modules/application/get/list.jag)
>> at
>> org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
>> at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
>> at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
>> at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
>> at
>> org.jaggeryjs.rhino.appmgt.modules.application.c0._c_anonymous_10(/appmgt/modules/application/module.jag:58)
>> at
>> org.jaggeryjs.rhino.appmgt.modules.application.c0.call(/appmgt/modules/application/module.jag)
>> at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
>> at
>> org.jaggeryjs.rhino.appmgt.site.pages.c1._c_anonymous_1(/appmgt/site/pages/index.jag:38)
>> at
>> org.jaggeryjs.rhino.appmgt.site.pages.c1.call(/appmgt/site/pages/index.jag)
>> at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
>> at
>> org.jaggeryjs.rhino.appmgt.site.pages.c1._c_script_0(/appmgt/site/pages/index.jag:23)
>> at
>> org.jaggeryjs.rhino.appmgt.site.pages.c1.call(/appmgt/site/pages/index.jag)
>> at
>> org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
>> at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
>> at
>> 

[Dev] Derby Migration scripts to migrate from ESB 4.8.1 to 4.9.0 (carbon 4.2.0-4.4.0)

[Viraj Senevirathne]

Hi all,

I found several changes in derby script that exists in ESB 4.8.1 to that of
4.9.0. I created the derby script [1] to upgrade the ESB 4.8.1 derby
database to 4.9.0 database. But when adding new columns to old  database
should I put them as blank or should I update that column with new data?

Table changes are given below.

*New Table Addition*
UM_SYSTEM_ROLE
UM_SYSTEM_USER_ROLE
UM_SYSTEM_USER
UM_DOMAIN

*Adding columns to Existing tables*
ALTER TABLE UM_ROLE_PERMISSION ADD COLUMN UM_DOMAIN_ID INTEGER;

ALTER TABLE UM_CLAIM ADD UM_MAPPED_ATTRIBUTE_DOMAIN VARCHAR(255);

Is it necessary to put data to these columns or keep them blanks?

Thanks,

[1]
https://drive.google.com/a/wso2.com/file/d/0Byt7F9S8tb-DeGdVTlpOXzkyYTQ/view?usp=sharing
-- 
Viraj Senevirathne
Software Engineer; WSO2, Inc.

Mobile : +94 71 958 0269
Email : vir...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Carbon Metrics UI OSGi Fragment Bundle issue

[Kishanthan Thangarajah]

@Aruna, can you have a look on this?

On Mon, Sep 14, 2015 at 7:19 PM, Nirmal Fernando  wrote:

> Hi All,
>
> Any thoughts?
>
> On Tue, Sep 8, 2015 at 3:11 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> With WSO2 Carbon Metrics release 1.1.0 [1], WSO2 Products can extend the
>> Metrics UI and show product specific metrics in Management Console.
>>
>> WSO2 Message Broker successfully use a Fragment Bundle to show Messaging
>> Metrics [2].
>>
>> Now WSO2 Machine Learner product also wants show some ML specific
>> metrics. When we create a similar component like [2], we encounter
>> following issue.
>>
>> [2015-09-08 13:20:58,603] ERROR - ApplicationDispatcher Servlet.service()
>> for servlet bridgeservlet threw exception
>> javax.servlet.ServletException: File /metrics-view/index.jsp
>> not found
>>
>> After further checking, we found out that the following properties in
>> MANIFEST.MF causes the issue.
>>
>> Bundle-Name: org.wso2.carbon.ml.metrics.ui
>> Bundle-SymbolicName: org.wso2.carbon.ml.metrics.ui
>>
>> For example, If we change the "ml" to "ma" (org.wso2.carbon.*ma*
>> .metrics.ui), the Fragment Bundle works fine.
>>
>> The host bundle source is at [3].
>>
>> If anyone wants to try this, build the Metrics tag v1.1.0 [1] locally and
>> install Metrics Feature to any WSO2 product via the Feature Manager. Please
>> use the target/p2-repo directory found in [4].
>>
>> Then try copying Messaging Metrics UI jar [5] to dropins. The Messaging
>> Metrics UI works. If we change the bundle name and symbolic name as
>> mentioned above, there will be an error.
>>
>> Any idea how these bundle names affect the Fragment Bundle?
>>
>> Thanks!
>>
>> Best Regards,
>>
>> [1] https://github.com/wso2/carbon-metrics/releases/tag/v1.1.0
>> [2]
>> https://github.com/wso2/carbon-business-messaging/tree/master/components/metrics/org.wso2.carbon.messaging.metrics.ui
>> [3]
>> https://github.com/wso2/carbon-metrics/tree/v1.1.0/components/org.wso2.carbon.metrics.view.ui
>> [4]
>> https://github.com/wso2/carbon-metrics/tree/v1.1.0/features/repository
>> [5]
>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/messaging/org.wso2.carbon.messaging.metrics.ui/2.6.1/
>>
>> --
>> Isuru Perera
>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [AF] - unable to access appfactory; server certification failed

[Kavitha Subramaniyam]

Hi Danushka,

it's working now after line added. thank you.

On Mon, Sep 14, 2015 at 11:14 AM, Danushka Fernando 
wrote:

> Add following line to .bashrc and source the file or open a new terminal.
> *export GIT_SSL_NO_VERIFY=1*
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> On Mon, Sep 14, 2015 at 9:42 AM, Kavitha Subramaniyam 
> wrote:
>
>> I'm in a way to testing AF192.168.18.2 Setup as at 11th Sept 2015, and
>> try to add database. when am trying to clone my created project to my local
>> machine the 'git clone..' is asking for server certification.
>> Can anyone tell me whether is this required while we using git clone? if
>> so how to get added this server certification?
>>
>> please check attachment of cmd prompt.
>>
>> --
>> Kavitha.S
>> *Software Engineer -QA*
>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>> kavi...@wso2.com 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Kavitha.S
*Software Engineer -QA*
Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
kavi...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarifications on CEP

[Manorama Perera]

Yes, this is because ML uses carbon.analytics 1.0.3-SNAPSHOT which requires
carbon.analytics.common 5.0.2-SNAPSHOT version, but CEP uses
carbon.analytics.common 5.0.1.

We can change the carbon.analytics.common version to 5.0.1 in ML once DAS
team do the required version changes in carbon.analytics.

Thanks.

On Mon, Sep 14, 2015 at 11:53 AM, Nirmal Fernando  wrote:

> Thanks Sashika, I think this is due to recent version upgrades.
>
> @Mano could you please check?
>
> On Mon, Sep 14, 2015 at 11:30 AM, Sashika Wijesinghe 
> wrote:
>
>> Hi Nirmal,
>>
>> I tried to install 'Machine learner core' feature in a fresh CEP pack
>> (13th September Jenkins pack) , but couldn't continue installation due to
>> below issue.
>>
>> Cannot complete the install because of a conflicting dependency. Software
>> being installed: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
>> (org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) Software currently
>> installed: WSO2 Carbon - Event Publisher Feature 5.0.1
>> (org.wso2.carbon.event.publisher.feature.group 5.0.1) Only one of the
>> following can be installed at once: WSO2 Carbon - Event Output Email
>> Adapter Server Feature 5.0.1
>> (org.wso2.carbon.event.output.adapter.email.server.feature.jar 5.0.1) WSO2
>> Carbon - Event Output Email Adapter Server Feature 5.0.2.SNAPSHOT
>> (org.wso2.carbon.event.output.adapter.email.server.feature.jar
>> 5.0.2.SNAPSHOT) Cannot satisfy dependency: From: WSO2 Carbon - Event Output
>> Email Adapter Server Feature 5.0.1
>> (org.wso2.carbon.event.output.adapter.email.server.feature.group 5.0.1) To:
>> org.wso2.carbon.event.output.adapter.email.server.feature.jar [5.0.1]
>> Cannot satisfy dependency: From: WSO2 Carbon - Event Output Email Adapter
>> Server Feature 5.0.2.SNAPSHOT
>> (org.wso2.carbon.event.output.adapter.email.server.feature.group
>> 5.0.2.SNAPSHOT) To:
>> org.wso2.carbon.event.output.adapter.email.server.feature.jar
>> [5.0.2.SNAPSHOT] Cannot satisfy dependency: From: WSO2 Carbon - Event
>> Publisher Output Adapter Feature 5.0.1
>> (org.wso2.carbon.event.output.adapter.feature.group 5.0.1) To:
>> org.wso2.carbon.event.output.adapter.email.server.feature.group [5.0.1]
>> Cannot satisfy dependency: From: WSO2 Carbon - Event Publisher Feature
>> 5.0.1 (org.wso2.carbon.event.publisher.feature.group 5.0.1) To:
>> org.wso2.carbon.event.output.adapter.feature.group [5.0.1] Cannot satisfy
>> dependency: From: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
>> (org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) To:
>> org.wso2.carbon.event.output.adapter.email.server.feature.group
>> [5.0.2.SNAPSHOT,5.1.0)
>>
>> Appreciate your help on this matter.
>>
>> Thanks.
>>
>> On Mon, Sep 14, 2015 at 10:02 AM, Nirmal Fernando 
>> wrote:
>>
>>> Shared the ML p2-repo with Sashika.
>>>
>>> On Sun, Sep 13, 2015 at 10:40 PM, Shavantha Weerasinghe <
>>> shavan...@wso2.com> wrote:
>>>
 Hi Sashika

 I got the p2 from lasantha last week will share tomorrow
 On Sep 12, 2015 10:24 PM, "Sashika Wijesinghe" 
 wrote:

> Hi All,
>
> May I know the location to download P2 repository to add ML features
> for CEP?
>
> Thanks
>
> On Wed, Sep 9, 2015 at 12:02 PM, Sashika Wijesinghe 
> wrote:
>
>> Hi Lasantha,
>>
>> Thanks for the clarification.
>>
>> In the documentation it has mentioned that '-DworkerNode=true"
>> argument will deactivate the UI bundle, So I thought there should not be
>> any UI component when a user tried to access to the worker node.
>> And I felt its good if we are not enabling the login page. because
>> when I tried to login to the CEP using worker node I got '*login
>> failed*' error message.
>>
>> Thanks & Regards,
>>
>> On Wed, Sep 9, 2015 at 11:21 AM, Lasantha Fernando > > wrote:
>>
>>> Hi Sashika,
>>>
>>> Yes that is the usual behaviour for WSO2 servers when started with
>>> worker node true. The login page will be visible, but you won't be 
>>> allowed
>>> to login.
>>>
>>> Thanks,
>>>
>>> On 9 September 2015 at 11:16, Sashika Wijesinghe 
>>> wrote:
>>>
 Hi Suho/Lasantha,

 I'm working on CEP distributed mode set up. When a worker node is
 started using "-DworkerNode=true" argument, I expected that UI of the
 worker node should not be visible. However CEP login page is visible 
 when
 started with -DworkerNode=true argument, but can't access to CEP, 
 because
 login functionality is not functioning.

 Appreciate your clarification on above situation.

 Thank You

 On Wed, Sep 9, 2015 at 11:00 AM, Sriskandarajah Suhothayan <
 s...@wso2.com> wrote:

> Can you look into this

Re: [Dev] [AF Tools] use "master" as the label for default branch instead of "trunk"

[Manjula Rathnayake]

Hi Kavith,

IMO, we should not store any mapping in DevStuido level. This needs to be
fixed in AF REST API level as well as in backends of AF and it require
considerable time to test and do any data migration if required too.
Since this is not a blocker, we will fix this in M6 milestone and you can
incorporate the changes to next release of Dev Studio or do a AF feature
release with other UX improvements.

thank you.


On Fri, Sep 11, 2015 at 6:06 PM, Danushka Fernando 
wrote:

> I guess we use trunk because we started this with svn and then moved on to
> git. +1 for renaming. @Manjula WDYT?
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> On Fri, Sep 11, 2015 at 5:00 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi,
>>
>> This is regarding $subject raised in [1] and [2].
>>
>> Currently the default version of an application is given the version
>> "trunk" (which corresponds to "master" branch of the git repo). When
>> checking out a version, DevStudio checks whether the user is checking out
>> the version "trunk" and if so, sets "master" as the branch to checkout.
>> However, when labeling the list of apps in tree view, we are not doing a
>> mapping from "trunk" to "master". Rather we display the list of versions
>> returned from AF API as it is.
>> To fix this, either we have to maintain such a mapping in DevStudio side
>> or this can be fixed from the AF side itself - by renaming version "trunk"
>> to "master".
>> Most importantly, it will be a bad experience for the user if we use two
>> different version names in AF UI and DevS UI, to display this  default
>> version.
>> Is it possible (or make sense) to change this from AppFactory? Please
>> share your thoughts.
>>
>>
>> [1] https://wso2.org/jira/browse/TOOLS-3142
>> [2] https://wso2.org/jira/browse/TOOLS-3143
>>
>> Thanks,
>>
>> --
>> *Kavith Lokuhewage*
>> Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +9477-9-145-123 | +9471-455-6-401
>> Linkedin 
>> Twitter 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Manjula Rathnayaka
Associate Technical Lead
WSO2, Inc.
Mobile:+94 77 743 1987
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarifications on CEP

[Sashika Wijesinghe]

Hi Nirmal,

I tried to install 'Machine learner core' feature in a fresh CEP pack (13th
September Jenkins pack) , but couldn't continue installation due to below
issue.

Cannot complete the install because of a conflicting dependency. Software
being installed: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
(org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) Software currently
installed: WSO2 Carbon - Event Publisher Feature 5.0.1
(org.wso2.carbon.event.publisher.feature.group 5.0.1) Only one of the
following can be installed at once: WSO2 Carbon - Event Output Email
Adapter Server Feature 5.0.1
(org.wso2.carbon.event.output.adapter.email.server.feature.jar 5.0.1) WSO2
Carbon - Event Output Email Adapter Server Feature 5.0.2.SNAPSHOT
(org.wso2.carbon.event.output.adapter.email.server.feature.jar
5.0.2.SNAPSHOT) Cannot satisfy dependency: From: WSO2 Carbon - Event Output
Email Adapter Server Feature 5.0.1
(org.wso2.carbon.event.output.adapter.email.server.feature.group 5.0.1) To:
org.wso2.carbon.event.output.adapter.email.server.feature.jar [5.0.1]
Cannot satisfy dependency: From: WSO2 Carbon - Event Output Email Adapter
Server Feature 5.0.2.SNAPSHOT
(org.wso2.carbon.event.output.adapter.email.server.feature.group
5.0.2.SNAPSHOT) To:
org.wso2.carbon.event.output.adapter.email.server.feature.jar
[5.0.2.SNAPSHOT] Cannot satisfy dependency: From: WSO2 Carbon - Event
Publisher Output Adapter Feature 5.0.1
(org.wso2.carbon.event.output.adapter.feature.group 5.0.1) To:
org.wso2.carbon.event.output.adapter.email.server.feature.group [5.0.1]
Cannot satisfy dependency: From: WSO2 Carbon - Event Publisher Feature
5.0.1 (org.wso2.carbon.event.publisher.feature.group 5.0.1) To:
org.wso2.carbon.event.output.adapter.feature.group [5.0.1] Cannot satisfy
dependency: From: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
(org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) To:
org.wso2.carbon.event.output.adapter.email.server.feature.group
[5.0.2.SNAPSHOT,5.1.0)

Appreciate your help on this matter.

Thanks.

On Mon, Sep 14, 2015 at 10:02 AM, Nirmal Fernando  wrote:

> Shared the ML p2-repo with Sashika.
>
> On Sun, Sep 13, 2015 at 10:40 PM, Shavantha Weerasinghe <
> shavan...@wso2.com> wrote:
>
>> Hi Sashika
>>
>> I got the p2 from lasantha last week will share tomorrow
>> On Sep 12, 2015 10:24 PM, "Sashika Wijesinghe"  wrote:
>>
>>> Hi All,
>>>
>>> May I know the location to download P2 repository to add ML features for
>>> CEP?
>>>
>>> Thanks
>>>
>>> On Wed, Sep 9, 2015 at 12:02 PM, Sashika Wijesinghe 
>>> wrote:
>>>
 Hi Lasantha,

 Thanks for the clarification.

 In the documentation it has mentioned that '-DworkerNode=true" argument
 will deactivate the UI bundle, So I thought there should not be any UI
 component when a user tried to access to the worker node.
 And I felt its good if we are not enabling the login page. because when
 I tried to login to the CEP using worker node I got '*login failed*'
 error message.

 Thanks & Regards,

 On Wed, Sep 9, 2015 at 11:21 AM, Lasantha Fernando 
 wrote:

> Hi Sashika,
>
> Yes that is the usual behaviour for WSO2 servers when started with
> worker node true. The login page will be visible, but you won't be allowed
> to login.
>
> Thanks,
>
> On 9 September 2015 at 11:16, Sashika Wijesinghe 
> wrote:
>
>> Hi Suho/Lasantha,
>>
>> I'm working on CEP distributed mode set up. When a worker node is
>> started using "-DworkerNode=true" argument, I expected that UI of the
>> worker node should not be visible. However CEP login page is visible when
>> started with -DworkerNode=true argument, but can't access to CEP, because
>> login functionality is not functioning.
>>
>> Appreciate your clarification on above situation.
>>
>> Thank You
>>
>> On Wed, Sep 9, 2015 at 11:00 AM, Sriskandarajah Suhothayan <
>> s...@wso2.com> wrote:
>>
>>> Can you look into this
>>>
>>> Suho
>>>
>>> On Wed, Sep 9, 2015 at 10:59 AM, Shavantha Weerasinghe <
>>> shavan...@wso2.com> wrote:
>>>
 Hi Suho/Lasantha

 We observed the bellow exception when we set the hostName as
 *192.168.48.128* but the exception does not come if we set
 localhost. This is on the node that behaves as both manager and worker 
 on *192.168.48.128.
 *Do we need to set the /etc/hosts if we are to use the IP

 
 
 
 
 192.168.48.128*
 8904
 
 
 localhost
 11000
 
 

 
 

[Dev] Different versions of the same bundle getting packed into CEP

[Lasantha Fernando]

Hi carbon team,

Different versions of the same bundle are getting packed in CEP because of
dependent repos packing different versions.

Following features are having dependencies on the conflicting bundles

guava

org.wso2.carbon.databridge.core.server(carbon-analytics-common-5.0.1) :
com.google.guava-15.0.0
org.wso2.carbon.registry.contentsearch.server(carbon-registry-4.4.6) :
guava-12.0.0.wso2v1
org.wso2.carbon.logging.mgt.server(carbon-commons-4.4.7): 13.0.1

commons-io
-
org.wso2.carbon.core.common(carbon-commons-4.4.7): commons-io-2.0.0.wso2v2
org.wso2.carbon.registry.contentsearch.server(carbon-registry-4.4.6):
commons-io-2.4.0.wso2v1
org.wso2.carbon.registry.resource.properties.server(carbon-registry-4.4.6):
commons-io-2.4.0.wso2v1

slf4j.api

org.wso2.carbon.metrics.server(carbon-metrics-1.1.0): slf4j.api-1.7.12
org.wso2.carbon.metrics.ui(carbon-metrics-1.1.0): slf4j.api-1.7.12
org.wso2.carbon.event.receiver.server(carbon-analytics-common-5.0.1):slf4j.api-1.7.12
org.wso2.carbon.databridge.commons.thrift.server(carbon-analytics-common5.0.1):slf4j.api-1.7.12
org.wso2.carbon.ntask.core(carbon-commons-4.4.7):slf4j.api-1.6.1
org.wso2.carbon.logging.mgt.server(carbon-commons-4.4.7):slf4j.api-1.6.1

slf4j.log4j12
-
org.wso2.carbon.metrics.server(carbon-metrics-1.1.0):slf4j.log4j12-1.7.12
org.wso2.carbon.metrics.ui(carbon-metrics-1.1.0): slf4j.log4j12-1.7.12
org.wso2.carbon.databridge.commons.thrift.server(carbon-analytics-common-5.0.1):slf4j.log4j12-1.7.12
org.wso2.carbon.ntask.core(carbon-commons-4.4.7):slf4j.log4j12-1.6.1
org.wso2.carbon.logging.mgt.server(carbon-commons-4.4.7):slf4j.log4j12-1.6.1

More details can be found at [1]. Most of these conflicts can be resolved
if carbon-commons dependencies were upgraded to newer versions. Also we are
facing the issue reported in [2] as well for which we would need a new
carbon-commons release. Would it be possible to do an upgrade on these
third party dependencies and provide a release?

[1]
https://wso2.org/jira/browse/CEP-1344?focusedCommentId=107742=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-107742
[2] https://wso2.org/jira/browse/DAS-116

Thanks,
Lasantha

-- 
*Lasantha Fernando*
Senior Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: lasan...@wso2.com
mobile: (+94) 71 5247551
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Data Services Server 3.5.0 Alpha2 Released

[Rajith Vitharana]

WSO2 Data Services Team is pleased to announce WSO2 Data Service Server
3.5.0 Alpha2 Release. You can download the pack from location [1] and [2].
Javadocs can be found in [3]. Below are the improvements, bug fixes
included in the release

Bug

   - [DS-732 ] - Create data source
   admin service is not properly validated, exisisting data source will get
   updated when creating new data sources
   - [DS-896 ] - [Blocker] DB
   insertion insert null values with new datastax client
   - [DS-1073 ] - Faulty data service
   cannot be deleted from the UI
   - [DS-1094 ] - Add datasource page
   doesn't apear in jdk 8 runtime
   - [DS-1099 ] - Select operation
   does not work in Google spreadsheets when query mode is used
   - [DS-1100 ] - changing visibility
   when editing Google spreadsheet data source won't hide clientId fields
   - [DS-1102 ] - OData enable check
   box is not properly work for carbon datasources in UI
   - [DS-1103 ] - Existing
   Dataservice will modify when creating a new Data Services with existing
   data service

Improvement

   - [DS-907 ] - Carbon Application
   Deployment Handler for Data Sources
   - [DS-1051 ] - Support to pass
   Regular expressions in SQL Query
   - [DS-1105 ] - Send multiple
   operation requests in a single request support, deprecating boxcarring
   requests
   - [DS-1107 ] - Support E-Tag in
   OData
   - [DS-1108 ] - Support Batch
   Request in OData



[1] -
https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/Alpha2/wso2dss-3.5.0-SNAPSHOT.zip
[2] -
https://github.com/wso2/product-dss/releases/download/3.5.0-Alpha2/wso2dss-3.5.0-SNAPSHOT.zip
[3] -
https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/Alpha2/javaDocs/index.html

Thanks,
DSS Team.
-- 
Rajith Vitharana

Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94715883223
Blog : http://lankavitharana.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Observer for API in WSO2 ESB / API GW

[Vanjikumaran Sivajothy]

Hi Devs and ESB team,

I would like to observe the API in WSO2 ESB, Currently AFAIU proxy and some
other artifacts are supported [1]. However, I was not able to find the
observer for API.

Is there any option to do the $subject ? If i am missing something please
let me know. If we do not have any other option, Isn't that better to add
this improvement in synapse?


[1]
https://github.com/wso2/wso2-synapse/blob/e0edd18f3f42ea50751634709098ae58593f1ba2/modules/core/src/main/java/org/apache/synapse/config/AbstractSynapseObserver.java





-- 
Vanjikumaran Sivajothy
*Associate Technical Lead*
*WSO2 Inc. http://wso2.com *
*USA Mobile **+1-812-361-1286*
*Srilanka Mobile:+94-777-219-209*
[image: Facebook]  [image: Twitter]
 [image: LinkedIn]
 [image:
Blogger]  [image: SlideShare]


This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarifications on CEP

[Nirmal Fernando]

Thanks Sashika, I think this is due to recent version upgrades.

@Mano could you please check?

On Mon, Sep 14, 2015 at 11:30 AM, Sashika Wijesinghe 
wrote:

> Hi Nirmal,
>
> I tried to install 'Machine learner core' feature in a fresh CEP pack
> (13th September Jenkins pack) , but couldn't continue installation due to
> below issue.
>
> Cannot complete the install because of a conflicting dependency. Software
> being installed: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
> (org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) Software currently
> installed: WSO2 Carbon - Event Publisher Feature 5.0.1
> (org.wso2.carbon.event.publisher.feature.group 5.0.1) Only one of the
> following can be installed at once: WSO2 Carbon - Event Output Email
> Adapter Server Feature 5.0.1
> (org.wso2.carbon.event.output.adapter.email.server.feature.jar 5.0.1) WSO2
> Carbon - Event Output Email Adapter Server Feature 5.0.2.SNAPSHOT
> (org.wso2.carbon.event.output.adapter.email.server.feature.jar
> 5.0.2.SNAPSHOT) Cannot satisfy dependency: From: WSO2 Carbon - Event Output
> Email Adapter Server Feature 5.0.1
> (org.wso2.carbon.event.output.adapter.email.server.feature.group 5.0.1) To:
> org.wso2.carbon.event.output.adapter.email.server.feature.jar [5.0.1]
> Cannot satisfy dependency: From: WSO2 Carbon - Event Output Email Adapter
> Server Feature 5.0.2.SNAPSHOT
> (org.wso2.carbon.event.output.adapter.email.server.feature.group
> 5.0.2.SNAPSHOT) To:
> org.wso2.carbon.event.output.adapter.email.server.feature.jar
> [5.0.2.SNAPSHOT] Cannot satisfy dependency: From: WSO2 Carbon - Event
> Publisher Output Adapter Feature 5.0.1
> (org.wso2.carbon.event.output.adapter.feature.group 5.0.1) To:
> org.wso2.carbon.event.output.adapter.email.server.feature.group [5.0.1]
> Cannot satisfy dependency: From: WSO2 Carbon - Event Publisher Feature
> 5.0.1 (org.wso2.carbon.event.publisher.feature.group 5.0.1) To:
> org.wso2.carbon.event.output.adapter.feature.group [5.0.1] Cannot satisfy
> dependency: From: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
> (org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) To:
> org.wso2.carbon.event.output.adapter.email.server.feature.group
> [5.0.2.SNAPSHOT,5.1.0)
>
> Appreciate your help on this matter.
>
> Thanks.
>
> On Mon, Sep 14, 2015 at 10:02 AM, Nirmal Fernando  wrote:
>
>> Shared the ML p2-repo with Sashika.
>>
>> On Sun, Sep 13, 2015 at 10:40 PM, Shavantha Weerasinghe <
>> shavan...@wso2.com> wrote:
>>
>>> Hi Sashika
>>>
>>> I got the p2 from lasantha last week will share tomorrow
>>> On Sep 12, 2015 10:24 PM, "Sashika Wijesinghe"  wrote:
>>>
 Hi All,

 May I know the location to download P2 repository to add ML features
 for CEP?

 Thanks

 On Wed, Sep 9, 2015 at 12:02 PM, Sashika Wijesinghe 
 wrote:

> Hi Lasantha,
>
> Thanks for the clarification.
>
> In the documentation it has mentioned that '-DworkerNode=true"
> argument will deactivate the UI bundle, So I thought there should not be
> any UI component when a user tried to access to the worker node.
> And I felt its good if we are not enabling the login page. because
> when I tried to login to the CEP using worker node I got '*login
> failed*' error message.
>
> Thanks & Regards,
>
> On Wed, Sep 9, 2015 at 11:21 AM, Lasantha Fernando 
> wrote:
>
>> Hi Sashika,
>>
>> Yes that is the usual behaviour for WSO2 servers when started with
>> worker node true. The login page will be visible, but you won't be 
>> allowed
>> to login.
>>
>> Thanks,
>>
>> On 9 September 2015 at 11:16, Sashika Wijesinghe 
>> wrote:
>>
>>> Hi Suho/Lasantha,
>>>
>>> I'm working on CEP distributed mode set up. When a worker node is
>>> started using "-DworkerNode=true" argument, I expected that UI of the
>>> worker node should not be visible. However CEP login page is visible 
>>> when
>>> started with -DworkerNode=true argument, but can't access to CEP, 
>>> because
>>> login functionality is not functioning.
>>>
>>> Appreciate your clarification on above situation.
>>>
>>> Thank You
>>>
>>> On Wed, Sep 9, 2015 at 11:00 AM, Sriskandarajah Suhothayan <
>>> s...@wso2.com> wrote:
>>>
 Can you look into this

 Suho

 On Wed, Sep 9, 2015 at 10:59 AM, Shavantha Weerasinghe <
 shavan...@wso2.com> wrote:

> Hi Suho/Lasantha
>
> We observed the bellow exception when we set the hostName as
> *192.168.48.128* but the exception does not come if we set
> localhost. This is on the node that behaves as both manager and 
> worker on *192.168.48.128.
> *Do we need to set the /etc/hosts if we are to use the IP
>

Re: [Dev] Current development repos of IoTServer

[Shabir Mohamed]

Hi All,

Please find the updated Repos for WSO2 IoT-Server below. Please do note
that the repos are listed in the order that they need to be built:

(Note that the IoT-Server relevant repos are moved to WSO2-Incubator)
(Also [4] built the IoT-Server pack and [5] builds that Product-CDM)

   - carbon-apimgt[1] branch:snap-1.10.x
   - carbon-device-mgt[2] branch:master
   - device-cloud[3] branch:master
   - product-device-cloud[4] branch:master
   - product-cdm[5] branch:master


[1] https://github.com/charithag/carbon-apimg.git
[2] https://github.com/charithag/carbon-device-mgt.git
[3] https://github.com/wso2-incubator/device-cloud
[4] https://github.com/wso2-incubator/product-device-cloud
[5] https://github.com/charithag/product-cdm.git



-
*Shabir Mohamed*
*Software Engineer*
WSO2 Inc.; http://wso2.com
Email: sha...@wso2.com 
Mobile: +94 77 3516019 | +94 71 6583393

On Mon, Sep 14, 2015 at 11:24 AM, Sumedha Rubasinghe 
wrote:

> Guys,
> Are these still valid or have we updated the repo list?
>
> On Thu, Sep 10, 2015 at 11:25 AM, Charitha Goonetilleke <
> charit...@wso2.com> wrote:
>
>> Hi All,
>>
>> As we are working on IoTserver implementations with ES integration and
>> DAS integration, we made some changes to few of existing WSO2 repos. So
>> currently we are using forks from those repos and sending PRs to relevant
>> teams time to time to review and merge our PRs with WSO2 repos.
>>
>> This is the list of repos, which need to build in order to build current
>> version of IoTserver. Please note that product might not be fully stable
>> since it is a work in progress.
>>
>>- carbon-apimgt[1] branch:snap-1.10.x
>>- carbon-device-mgt[2] branch:master
>>- device-cloud[3] branch:master
>>- product-device-cloud[4] branch:master
>>- product-cdm[5] branch:master
>>
>> [1] https://github.com/charithag/carbon-apimg.git
>> [2] https://github.com/charithag/carbon-device-mgt.git
>> [3] https://github.com/wso2-dev/device-cloud.git
>> [4] https://github.com/wso2-dev/product-device-cloud.git
>> [5] https://github.com/charithag/product-cdm.git
>>
>> --
>> *Charitha Goonetilleke*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 751 3669 <%2B94777513669>
>> Twitter:@CharithaWs , fb: charithag
>> , linkedin: charithag
>> 
>>
>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Throttling] Moving throttle.core out from Synapse

[Amila De Silva]

Hi All,

While carrying out this task, came to a point where certain classes cannot
be moved out of synapse.

For some of the improvements done recently, ConcurrentAccessController
(which is one of the classes that originally resided in throttle core) has
been used from SynapseCallbackReceiver and Axis2FlexibleMEPClient. So now
either ConcurrentAccessController has to reside inside synapse, or else it
has to go into another different component on which synapse would have to
depend on. The whole point of moving throttling related code out of synapse
is to prevent synapse depending on any carbon components.

Since synapse depending on Hazelcast is not something that can be
eliminated completely, is it fine to keep throttle.core inside synapse and
merge new changes? When merging throttling fixes, either we have to
introduce a service component to synapse, which would
consume hazelcast.instance.service or we have to provide a method to set
the HazelcastInstance that will be used for replicating throttling counts.

On Fri, Sep 11, 2015 at 9:01 PM, Amila De Silva  wrote:

> Hi Chanaka,
>
> Since throttle core can be used on its own, thought of creating a separate
> feature out of that - so a new place to put throttle component. If we put
> it under mediation-throttle, that would imply two components have to be
> used together, isn't it?
>
> On Fri, Sep 11, 2015 at 6:45 PM, Chanaka Fernando 
> wrote:
>
>> Hi Amila,
>>
>> You can find [1] which already has the throttle policy editor related
>> packages and named as mediation-throttle. You can move the throttle-core
>> packages to this component.
>>
>> [1]
>> https://github.com/wso2/carbon-mediation/tree/master/components/mediation-throttle
>>
>> On Fri, Sep 11, 2015 at 6:23 PM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> +1.
>>>
>>>
>>> On Fri, Sep 11, 2015 at 5:20 PM, Amila De Silva  wrote:
>>>
 Will be moving throttle.core to a new component under carbon-mediation.
 The new component name will be throttle-core and a new feature with the
 same name will be created. Planning to do these changes on
 carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.

 On Mon, Sep 7, 2015 at 6:25 PM, Amila De Silva  wrote:

> Hi All,
>
> One of the changes done while moving to Git was, moving source code
> which was under org.wso2.carbon.throttle.core to wso2-synapse. Throttle
> core is used by both ESB (in Throttle mediator) and by API Manager (in
> APIThrottleHandler - to keep track of the number of API calls made over 
> the
> cluster). At the time throttle core was moved, it was depending on Axis2
> only, making it possible to move the source code to wso2-synapse - which 
> is
> not depending on any carbon components.
>
> While doing several improvements on throttling, Hazelcast AtomicLongs
> were used for keeping cluster-wide counts, which now creates a coupling
> between Hazelcast and Throttle Core. If these changes are to be merged 
> with
> synapse, we would have to add a dependency to Hazelcast.
>
> The other option is to move Throttle Core into carbon-mediation. Since
> this already depends on several carbon components adding Hazelcast as a
> dependancy won't be an issue.
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>


 --
 *Amila De Silva*

 WSO2 Inc.
 mobile :(+94) 775119302


>>>
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>> blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>> 
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>


-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release ES-2.0.0 RC 4

[Manuranga Perera]

Hi Devs and QA team,

Thanks for testing and verifying the WSO2 Enterprise Store RC 4. We are
closing this vote now. This vote has passed with 3 +1s and 0 -1s. And we
have received the go ahead from QA team. Therefore, we are proceeding with
the WSO2 Enterprise Store 2.0.0 release.

On behalf of ES team,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing RMSequence mediator from Developer Studio 3.8.0 ESB Palette

[Rajeevan Vimalanathan]

Hi all,

Thanks for your valuable feedback.

For now we are removing RMSequence mediator from ESB palette hence
Developer Studio 3.8.0 will not support ESB 4.8.0 for some extends.
But, as Awanthika suggested we should find a way to support multiple ESB
versions with Developer Studio since each release has new features, bug
fixes, etc. and users may expect to use Developer Studio latest version
with old ESB version development.
In that case we may need to have multiple virtual ESB palettes where user
can select ESB version and get the proper palette for that version. We need
multiple palettes here because each ESB release has considerable amount of
component and property level changes and corresponding synapse library
changes.

WDYT?

Thanks,
Rajeevan


On Fri, Sep 11, 2015 at 3:24 PM, Jasintha Dasanayake 
wrote:

>  only problem case is if user  waiting for a fix which will be coming with
> this release but that user may use older ESB version , but any way now we
> have to remove this , we have to educate  users via the documentations
>
> Thanks and Regards
> /Jasintha
>
> On Fri, Sep 11, 2015 at 3:09 PM, Harshana Eranga Martin <
> harshan...@gmail.com> wrote:
>
>> Hi Rajeevan,
>>
>> In that case you may recommend to use an older stable version of DevS
>> such as DevS 3.7.0 or 3.7.1 since that supports full feature set of ESB
>> 4.8.0.
>>
>> Thanks and Regards,
>> Harshana
>>
>>
>> On Friday, September 11, 2015, Rajeevan Vimalanathan 
>> wrote:
>>
>>> Hi,
>>>
>>> We have observed that RMSequence mediator has been removed from ESB
>>> 4.8.1. We also planning to remove that from ESB palette as well from
>>> Developer Studio 3.8.0 since synapse libraries have been updated
>>> accordingly.
>>> Here our concern is what if a user wants to develop ESB 4.8.0 stuff with
>>> Developer Studio 3.8.0? These features won't be supported anymore. In that
>>> case, can we suggest the user to use Developer Studio 3.7.1 which is a
>>> older version? Please appreciate your thoughts on this.
>>>
>>> Thanks,
>>> Rajeevan
>>>
>>> --
>>> Vimalanathan Rajeevan
>>> Software Engineer,
>>> WSO2, Inc. *http://wso2.com* 
>>> Lean.Enterprise.Middleware
>>>
>>> Mobile:
>>> *+94 773090875 <%2B94%20773090875>*
>>> LinkedIn:
>>> *https://www.linkedin.com/in/RajeevanVimalanathan
>>> *
>>>
>>
>>
>> --
>> Sent from Gmail Mobile for IPhone
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Jasintha Dasanayake*
>
> *Senior Software EngineerWSO2 Inc. | http://wso2.com
> lean . enterprise . middleware*
>
>
> *mobile :- 0711368118*
>



-- 
Vimalanathan Rajeevan
Software Engineer,
WSO2, Inc. *http://wso2.com* 
Lean.Enterprise.Middleware

Mobile:
*+94 773090875*
LinkedIn:
*https://www.linkedin.com/in/RajeevanVimalanathan
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Throttling] Moving throttle.core out from Synapse

[Isuru Udana]

Hi AmilaD,

Can you please point us the changes need to be merged in synapse (in
MEPClient and SynapseCallbackReceiver) ?

On Mon, Sep 14, 2015 at 2:58 PM, Amila De Silva  wrote:

> Hi All,
>
> While carrying out this task, came to a point where certain classes cannot
> be moved out of synapse.
>
> For some of the improvements done recently, ConcurrentAccessController
> (which is one of the classes that originally resided in throttle core) has
> been used from SynapseCallbackReceiver and Axis2FlexibleMEPClient. So now
> either ConcurrentAccessController has to reside inside synapse, or else it
> has to go into another different component on which synapse would have to
> depend on. The whole point of moving throttling related code out of synapse
> is to prevent synapse depending on any carbon components.
>
> Since synapse depending on Hazelcast is not something that can be
> eliminated completely, is it fine to keep throttle.core inside synapse and
> merge new changes? When merging throttling fixes, either we have to
> introduce a service component to synapse, which would
> consume hazelcast.instance.service or we have to provide a method to set
> the HazelcastInstance that will be used for replicating throttling counts.
>
> On Fri, Sep 11, 2015 at 9:01 PM, Amila De Silva  wrote:
>
>> Hi Chanaka,
>>
>> Since throttle core can be used on its own, thought of creating a
>> separate feature out of that - so a new place to put throttle component. If
>> we put it under mediation-throttle, that would imply two components have to
>> be used together, isn't it?
>>
>> On Fri, Sep 11, 2015 at 6:45 PM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Amila,
>>>
>>> You can find [1] which already has the throttle policy editor related
>>> packages and named as mediation-throttle. You can move the throttle-core
>>> packages to this component.
>>>
>>> [1]
>>> https://github.com/wso2/carbon-mediation/tree/master/components/mediation-throttle
>>>
>>> On Fri, Sep 11, 2015 at 6:23 PM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 +1.


 On Fri, Sep 11, 2015 at 5:20 PM, Amila De Silva 
 wrote:

> Will be moving throttle.core to a new component under
> carbon-mediation. The new component name will be throttle-core and a new
> feature with the same name will be created. Planning to do these changes 
> on
> carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.
>
> On Mon, Sep 7, 2015 at 6:25 PM, Amila De Silva 
> wrote:
>
>> Hi All,
>>
>> One of the changes done while moving to Git was, moving source code
>> which was under org.wso2.carbon.throttle.core to wso2-synapse. Throttle
>> core is used by both ESB (in Throttle mediator) and by API Manager (in
>> APIThrottleHandler - to keep track of the number of API calls made over 
>> the
>> cluster). At the time throttle core was moved, it was depending on Axis2
>> only, making it possible to move the source code to wso2-synapse - which 
>> is
>> not depending on any carbon components.
>>
>> While doing several improvements on throttling, Hazelcast AtomicLongs
>> were used for keeping cluster-wide counts, which now creates a coupling
>> between Hazelcast and Throttle Core. If these changes are to be merged 
>> with
>> synapse, we would have to add a dependency to Hazelcast.
>>
>> The other option is to move Throttle Core into carbon-mediation.
>> Since this already depends on several carbon components adding Hazelcast 
>> as
>> a dependancy won't be an issue.
>>
>> --
>> *Amila De Silva*
>>
>> WSO2 Inc.
>> mobile :(+94) 775119302
>>
>>
>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>


 --

 *Sanjeewa Malalgoda*
 WSO2 Inc.
 Mobile : +94713068779

 blog
 :http://sanjeewamalalgoda.blogspot.com/
 



>>>
>>>
>>> --
>>> --
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Amila De Silva*
>>
>> WSO2 Inc.
>> mobile :(+94) 775119302
>>
>>
>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev