[Dev] Stopping RXT attributes from being added as resource properties

2014-09-10 Thread Pulasthi Supun 
Hi All,

Currently with RXT's all the attributes of the RXT are being added as
properties in the resource. The process of adding them as properties
executes a significant amount of DB calls which is big performance hit.
AFAIK there is no use of these properties hence we should be able to stop
this and reduce a large amount of DB calls in the process.

@Nuwan
As for the the offline discussion we had a while back regarding this i
assume that these properties are not been used in the APIM side ( Not
properties in general just the properties that are created for RXT
attributes ).

Since we do not have any real use for this properties shall we remove
these, WDYT?


Regards,
Pulasthi


-- 
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping RXT attributes from being added as resource properties

2014-09-10 Thread Nuwan Dias 
+1 for removing these. APIM doesn't deal with properties in RXTs but with
the RXT attributes directly. So APIM won't have any effects by this change.

Thanks,
NuwanD.

On Wed, Sep 10, 2014 at 1:52 PM, Pulasthi Supun  wrote:

> Hi All,
>
> Currently with RXT's all the attributes of the RXT are being added as
> properties in the resource. The process of adding them as properties
> executes a significant amount of DB calls which is big performance hit.
> AFAIK there is no use of these properties hence we should be able to stop
> this and reduce a large amount of DB calls in the process.
>
> @Nuwan
> As for the the offline discussion we had a while back regarding this i
> assume that these properties are not been used in the APIM side ( Not
> properties in general just the properties that are created for RXT
> attributes ).
>
> Since we do not have any real use for this properties shall we remove
> these, WDYT?
>
>
> Regards,
> Pulasthi
>
>
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: pulas...@wso2.com
> Mobile: +94 (71) 9258281
> Blog : http://pulasthisupun.blogspot.com/
> Git hub profile: https://github.com/pulasthi
>



-- 
Nuwan Dias

Associate Tech Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping RXT attributes from being added as resource properties

2014-09-10 Thread Senaka Fernando 
Hi all,

This has nothing to do with API-M actually.

Subash, this was added for JCR support (IINM, by you, :)..). And, I'm most
certain that the JCR-based repository-browsers only reads what's listed as
properties. Can you'll have a look into that? Or we'll endup breaking that
without knowing its broken.

Thanks,
Senaka.

On Wed, Sep 10, 2014 at 10:02 AM, Nuwan Dias  wrote:

> +1 for removing these. APIM doesn't deal with properties in RXTs but with
> the RXT attributes directly. So APIM won't have any effects by this change.
>
> Thanks,
> NuwanD.
>
> On Wed, Sep 10, 2014 at 1:52 PM, Pulasthi Supun  wrote:
>
>> Hi All,
>>
>> Currently with RXT's all the attributes of the RXT are being added as
>> properties in the resource. The process of adding them as properties
>> executes a significant amount of DB calls which is big performance hit.
>> AFAIK there is no use of these properties hence we should be able to stop
>> this and reduce a large amount of DB calls in the process.
>>
>> @Nuwan
>> As for the the offline discussion we had a while back regarding this i
>> assume that these properties are not been used in the APIM side ( Not
>> properties in general just the properties that are created for RXT
>> attributes ).
>>
>> Since we do not have any real use for this properties shall we remove
>> these, WDYT?
>>
>>
>> Regards,
>> Pulasthi
>>
>>
>> --
>> --
>> Pulasthi Supun
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> Email: pulas...@wso2.com
>> Mobile: +94 (71) 9258281
>> Blog : http://pulasthisupun.blogspot.com/
>> Git hub profile: https://github.com/pulasthi
>>
>
>
>
> --
> Nuwan Dias
>
> Associate Tech Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 


*[image: http://wso2.com] Senaka Fernando*
Software Architect; WSO2 Inc.; http://wso2.com



*Member; Apache Software Foundation; http://apache.org
E-mail: senaka AT wso2.com **P: +1 408
754 7388 <%2B1%20408%20754%207388>; ext: 51736*;


*M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
http://linkedin.com/in/senakafernando
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping RXT attributes from being added as resource properties

2014-09-10 Thread Subash Chaturanga 
Hi Senaka,
Sure will do and update you. Btw I am not the one who add it ;-).

On Thu, Sep 11, 2014 at 2:50 AM, Senaka Fernando  wrote:

> Hi all,
>
> This has nothing to do with API-M actually.
>
> Subash, this was added for JCR support (IINM, by you, :)..). And, I'm most
> certain that the JCR-based repository-browsers only reads what's listed as
> properties. Can you'll have a look into that? Or we'll endup breaking that
> without knowing its broken.
>
> Thanks,
> Senaka.
>
> On Wed, Sep 10, 2014 at 10:02 AM, Nuwan Dias  wrote:
>
>> +1 for removing these. APIM doesn't deal with properties in RXTs but with
>> the RXT attributes directly. So APIM won't have any effects by this change.
>>
>> Thanks,
>> NuwanD.
>>
>> On Wed, Sep 10, 2014 at 1:52 PM, Pulasthi Supun 
>> wrote:
>>
>>> Hi All,
>>>
>>> Currently with RXT's all the attributes of the RXT are being added as
>>> properties in the resource. The process of adding them as properties
>>> executes a significant amount of DB calls which is big performance hit.
>>> AFAIK there is no use of these properties hence we should be able to stop
>>> this and reduce a large amount of DB calls in the process.
>>>
>>> @Nuwan
>>> As for the the offline discussion we had a while back regarding this i
>>> assume that these properties are not been used in the APIM side ( Not
>>> properties in general just the properties that are created for RXT
>>> attributes ).
>>>
>>> Since we do not have any real use for this properties shall we remove
>>> these, WDYT?
>>>
>>>
>>> Regards,
>>> Pulasthi
>>>
>>>
>>> --
>>> --
>>> Pulasthi Supun
>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>> Email: pulas...@wso2.com
>>> Mobile: +94 (71) 9258281
>>> Blog : http://pulasthisupun.blogspot.com/
>>> Git hub profile: https://github.com/pulasthi
>>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Associate Tech Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
>
>
> *[image: http://wso2.com] Senaka Fernando*
> Software Architect; WSO2 Inc.; http://wso2.com
>
>
>
> *Member; Apache Software Foundation; http://apache.org
> E-mail: senaka AT wso2.com **P: +1
> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>
>
> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
> http://linkedin.com/in/senakafernando
> *Lean . Enterprise . Middleware
>



-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer & Lead WSO2 Governance Registry
Platform TG; WSO2 Inc. http://wso2.com
Contact:
email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping RXT attributes from being added as resource properties

2014-09-11 Thread Subash Chaturanga 
Hi Senaka,
In JCR handler it writes artifact properties to the resource and vice
versa. As you know JCR repository does not understand any RXT related
resorce content. Can you explain WDYM by "JCR-based repository-browsers
only reads what's listed as properties" ? You mean viewing jcr resources in
registry browser ? For JCR it stores its nodes as registry Collections and
Properties as registry resources + properties.

Pulasthi found [1] as a related JIRA.

[1] -  https://wso2.org/jira/browse/REGISTRY-1928

On Thu, Sep 11, 2014 at 2:50 AM, Senaka Fernando  wrote:

> Hi all,
>
> This has nothing to do with API-M actually.
>
> Subash, this was added for JCR support (IINM, by you, :)..). And, I'm most
> certain that the JCR-based repository-browsers only reads what's listed as
> properties. Can you'll have a look into that? Or we'll endup breaking that
> without knowing its broken.
>
> Thanks,
> Senaka.
>
> On Wed, Sep 10, 2014 at 10:02 AM, Nuwan Dias  wrote:
>
>> +1 for removing these. APIM doesn't deal with properties in RXTs but with
>> the RXT attributes directly. So APIM won't have any effects by this change.
>>
>> Thanks,
>> NuwanD.
>>
>> On Wed, Sep 10, 2014 at 1:52 PM, Pulasthi Supun 
>> wrote:
>>
>>> Hi All,
>>>
>>> Currently with RXT's all the attributes of the RXT are being added as
>>> properties in the resource. The process of adding them as properties
>>> executes a significant amount of DB calls which is big performance hit.
>>> AFAIK there is no use of these properties hence we should be able to stop
>>> this and reduce a large amount of DB calls in the process.
>>>
>>> @Nuwan
>>> As for the the offline discussion we had a while back regarding this i
>>> assume that these properties are not been used in the APIM side ( Not
>>> properties in general just the properties that are created for RXT
>>> attributes ).
>>>
>>> Since we do not have any real use for this properties shall we remove
>>> these, WDYT?
>>>
>>>
>>> Regards,
>>> Pulasthi
>>>
>>>
>>> --
>>> --
>>> Pulasthi Supun
>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>> Email: pulas...@wso2.com
>>> Mobile: +94 (71) 9258281
>>> Blog : http://pulasthisupun.blogspot.com/
>>> Git hub profile: https://github.com/pulasthi
>>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Associate Tech Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
>
>
> *[image: http://wso2.com] Senaka Fernando*
> Software Architect; WSO2 Inc.; http://wso2.com
>
>
>
> *Member; Apache Software Foundation; http://apache.org
> E-mail: senaka AT wso2.com **P: +1
> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>
>
> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
> http://linkedin.com/in/senakafernando
> *Lean . Enterprise . Middleware
>



-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer & Lead WSO2 Governance Registry
Platform TG; WSO2 Inc. http://wso2.com
Contact:
email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping RXT attributes from being added as resource properties

2014-09-11 Thread Shariq Muhammed 
Hi folks,

So what is the verdict? In API-M when adding an API, we noticed that there
were so many INSERTs when adding RXT attributes as properties, by stopping
this, the number of INSERT statements has been reduced significantly and we
see a great improvement while saving API's etc in the Cloud. So it we would
be best if we could stop adding attributes as resources. Is it a major
change to incorporate?



On Thu, Sep 11, 2014 at 1:55 PM, Subash Chaturanga  wrote:

> Hi Senaka,
> In JCR handler it writes artifact properties to the resource and vice
> versa. As you know JCR repository does not understand any RXT related
> resorce content. Can you explain WDYM by "JCR-based repository-browsers
> only reads what's listed as properties" ? You mean viewing jcr resources
> in registry browser ? For JCR it stores its nodes as registry Collections
> and Properties as registry resources + properties.
>
> Pulasthi found [1] as a related JIRA.
>
> [1] -  https://wso2.org/jira/browse/REGISTRY-1928
>
> On Thu, Sep 11, 2014 at 2:50 AM, Senaka Fernando  wrote:
>
>> Hi all,
>>
>> This has nothing to do with API-M actually.
>>
>> Subash, this was added for JCR support (IINM, by you, :)..). And, I'm
>> most certain that the JCR-based repository-browsers only reads what's
>> listed as properties. Can you'll have a look into that? Or we'll endup
>> breaking that without knowing its broken.
>>
>> Thanks,
>> Senaka.
>>
>> On Wed, Sep 10, 2014 at 10:02 AM, Nuwan Dias  wrote:
>>
>>> +1 for removing these. APIM doesn't deal with properties in RXTs but
>>> with the RXT attributes directly. So APIM won't have any effects by this
>>> change.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Wed, Sep 10, 2014 at 1:52 PM, Pulasthi Supun 
>>> wrote:
>>>
 Hi All,

 Currently with RXT's all the attributes of the RXT are being added as
 properties in the resource. The process of adding them as properties
 executes a significant amount of DB calls which is big performance hit.
 AFAIK there is no use of these properties hence we should be able to stop
 this and reduce a large amount of DB calls in the process.

 @Nuwan
 As for the the offline discussion we had a while back regarding this i
 assume that these properties are not been used in the APIM side ( Not
 properties in general just the properties that are created for RXT
 attributes ).

 Since we do not have any real use for this properties shall we remove
 these, WDYT?


 Regards,
 Pulasthi


 --
 --
 Pulasthi Supun
 Software Engineer; WSO2 Inc.; http://wso2.com,
 Email: pulas...@wso2.com
 Mobile: +94 (71) 9258281
 Blog : http://pulasthisupun.blogspot.com/
 Git hub profile: https://github.com/pulasthi

>>>
>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Associate Tech Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>>
>> --
>>
>>
>> *[image: http://wso2.com] Senaka Fernando*
>> Software Architect; WSO2 Inc.; http://wso2.com
>>
>>
>>
>> *Member; Apache Software Foundation; http://apache.org
>> E-mail: senaka AT wso2.com **P: +1
>> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>>
>>
>> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In:
>> http://linkedin.com/in/senakafernando
>> *Lean . Enterprise . Middleware
>>
>
>
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer & Lead WSO2 Governance Registry
> Platform TG; WSO2 Inc. http://wso2.com
> Contact:
> email: sub...@wso2.com
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>



-- 
Thanks,
Shariq
Senior Software Engineer
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev