Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-05 Thread Chaminda Jayawardena 
How about this for apim integration? APIM has dipsync use case. KM needs
the same userstore to be shared with. In a distributed setup which has both
Greg and APIM nodes(may be multiple KM, GW as well), what would be the
suggestion?

On Fri, Sep 4, 2015 at 3:23 PM, Sagara Gunathunga  wrote:

>
>
> On Fri, Sep 4, 2015 at 2:11 PM, Chandana Napagoda 
> wrote:
>
>> Hi Pavithra,
>>
>> As a workaround one can use rsync or copy secondary user store
>> configuration in to other nodes.
>>
>
> I'm not quite sure whether dev or qa team have tested DipSync in G-Reg
> ever, because we don't have any such direct use case, even current context
> DipSync came in to the picture because of secondary user store requirement,
> may be we can test this from next release.
>
> Other concern is enabling DipSync among G-Reg nodes just because of
> secondary user store ( which also not frequently change) support may
> complicate the deployment architecture instead rsync or manual sync of
> secondary user store definition files is much preferable, hence IMHO this
> should be a less priority item.
>
> Thanks !
>
>>
>> Regards,
>> Chandana
>>
>> On Fri, Sep 4, 2015 at 12:39 PM, Pavithra Madurangi 
>> wrote:
>>
>>>
>>>
>>> On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga 
>>> wrote:
>>>


 On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:

> Thanks Prasanna. Please update the JIRA as well.
>
> In between there was a dep sync issue reported with ESB [1] with the
> recent fix from carbon commons. Just want to find out whether this has any
> effect on GREG product for scenarios like secondary user store, API-M
> integration (May not be an issue since we suggest to use APIM 1.9.1 for 
> GW)
> or install WSO2 AS features and use it (which is anyway very unlikely
> scenario).
>

 It's hard to think about DipSync use cases in G-Reg.

>>>
>>> ​Agree to this.
>>>
>>> But our concern was secondary user stores. If we have secondary user
>>> stores in a multi node deployment, won't there be any issues because of
>>> this bug (since it's one place where depSync is needed)?
>>>
>>> There's a possibility of managing secondary user stores without having
>>> depSync. What we wanted to get clarified was whether that's the
>>> approach/workaround we suggest ?
>>>
>>> Regards,
>>> pavithra
>>>

 Thanks !

>
> 1. ESBJAVA-4156 
>
>
>
>
>
> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
> wrote:
>
>> Hi Thayalan,
>>
>> We fixed the issue REGISTRY-2927
>>  . Now users can
>> re-login from the same window in a fresh pack.
>>
>> Thanks
>>
>> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>>
>>> Hi Team,
>>>
>>> I've observed from the standalone pack without any changes user has
>>> not been allowed to re-login  to the store [1]. However this is working
>>> fine for publisher. As per the suggestion in [1] hostname has to be set 
>>> in
>>> carbon.xml. However in the default pack SSO enabled for store/publisher 
>>> and
>>> Hostname tag is commented. Even uncomment them and set to IP or 
>>> localhost
>>> too not working as suggested in the JIRA. From the end user perspective
>>> user should allow to re-login from the same window session from the 
>>> fresh
>>> pack. Is this is something we need to fix before releasing them?
>>>
>>> 1.REGISTRY-2927 
>>>
>>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda >> > wrote:
>>>
 -1,

 We found an issue with solr related logging configuration and this
 issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.

 Step to reproduce this issue:

 Go to Main --> Registry search and search by any value.
 Then navigate to Configure --> Logging section.
 Exceptions are logged in console and "Global Log4J Configuration"
 and "Configure Log4J Appenders" views are not loading due to the above
 issue.

 Created a JIRA[1] to track above issue and will release release
 G-Reg 5.0.0 RC3 pack ASAP.

 [1]. https://wso2.org/jira/browse/WSAS-2120

 Regards,
 Chandana


 On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda <
 chand...@wso2.com> wrote:

> Hi Pubudu,
>
> Since we have already released RC2 pack and component repos, we
> can not update above pages now. We will update context specific pages 
> for
> coming up 5.0.1 release. Meantime, you can refer wiki

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-05 Thread Chandana Napagoda 
Hi Chaminda,

APIM  1.9.1 will  be used as GW and KM nodes. Since it is based on carbon
4.2.0, this won't be an issue.

Regards,
Chandana
How about this for apim integration? APIM has dipsync use case. KM needs
the same userstore to be shared with. In a distributed setup which has both
Greg and APIM nodes(may be multiple KM, GW as well), what would be the
suggestion?

On Fri, Sep 4, 2015 at 3:23 PM, Sagara Gunathunga  wrote:

>
>
> On Fri, Sep 4, 2015 at 2:11 PM, Chandana Napagoda 
> wrote:
>
>> Hi Pavithra,
>>
>> As a workaround one can use rsync or copy secondary user store
>> configuration in to other nodes.
>>
>
> I'm not quite sure whether dev or qa team have tested DipSync in G-Reg
> ever, because we don't have any such direct use case, even current context
> DipSync came in to the picture because of secondary user store requirement,
> may be we can test this from next release.
>
> Other concern is enabling DipSync among G-Reg nodes just because of
> secondary user store ( which also not frequently change) support may
> complicate the deployment architecture instead rsync or manual sync of
> secondary user store definition files is much preferable, hence IMHO this
> should be a less priority item.
>
> Thanks !
>
>>
>> Regards,
>> Chandana
>>
>> On Fri, Sep 4, 2015 at 12:39 PM, Pavithra Madurangi 
>> wrote:
>>
>>>
>>>
>>> On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga 
>>> wrote:
>>>


 On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:

> Thanks Prasanna. Please update the JIRA as well.
>
> In between there was a dep sync issue reported with ESB [1] with the
> recent fix from carbon commons. Just want to find out whether this has any
> effect on GREG product for scenarios like secondary user store, API-M
> integration (May not be an issue since we suggest to use APIM 1.9.1 for 
> GW)
> or install WSO2 AS features and use it (which is anyway very unlikely
> scenario).
>

 It's hard to think about DipSync use cases in G-Reg.

>>>
>>> ​Agree to this.
>>>
>>> But our concern was secondary user stores. If we have secondary user
>>> stores in a multi node deployment, won't there be any issues because of
>>> this bug (since it's one place where depSync is needed)?
>>>
>>> There's a possibility of managing secondary user stores without having
>>> depSync. What we wanted to get clarified was whether that's the
>>> approach/workaround we suggest ?
>>>
>>> Regards,
>>> pavithra
>>>

 Thanks !

>
> 1. ESBJAVA-4156 
>
>
>
>
>
> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
> wrote:
>
>> Hi Thayalan,
>>
>> We fixed the issue REGISTRY-2927
>>  . Now users can
>> re-login from the same window in a fresh pack.
>>
>> Thanks
>>
>> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>>
>>> Hi Team,
>>>
>>> I've observed from the standalone pack without any changes user has
>>> not been allowed to re-login  to the store [1]. However this is working
>>> fine for publisher. As per the suggestion in [1] hostname has to be set 
>>> in
>>> carbon.xml. However in the default pack SSO enabled for store/publisher 
>>> and
>>> Hostname tag is commented. Even uncomment them and set to IP or 
>>> localhost
>>> too not working as suggested in the JIRA. From the end user perspective
>>> user should allow to re-login from the same window session from the 
>>> fresh
>>> pack. Is this is something we need to fix before releasing them?
>>>
>>> 1.REGISTRY-2927 
>>>
>>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda >> > wrote:
>>>
 -1,

 We found an issue with solr related logging configuration and this
 issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.

 Step to reproduce this issue:

 Go to Main --> Registry search and search by any value.
 Then navigate to Configure --> Logging section.
 Exceptions are logged in console and "Global Log4J Configuration"
 and "Configure Log4J Appenders" views are not loading due to the above
 issue.

 Created a JIRA[1] to track above issue and will release release
 G-Reg 5.0.0 RC3 pack ASAP.

 [1]. https://wso2.org/jira/browse/WSAS-2120

 Regards,
 Chandana


 On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda <
 chand...@wso2.com> wrote:

> Hi Pubudu,
>
> Since we have already released RC2 pack and component repos, we
> can not update

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-04 Thread Sagara Gunathunga 
On Fri, Sep 4, 2015 at 2:11 PM, Chandana Napagoda  wrote:

> Hi Pavithra,
>
> As a workaround one can use rsync or copy secondary user store
> configuration in to other nodes.
>

I'm not quite sure whether dev or qa team have tested DipSync in G-Reg
ever, because we don't have any such direct use case, even current context
DipSync came in to the picture because of secondary user store requirement,
may be we can test this from next release.

Other concern is enabling DipSync among G-Reg nodes just because of
secondary user store ( which also not frequently change) support may
complicate the deployment architecture instead rsync or manual sync of
secondary user store definition files is much preferable, hence IMHO this
should be a less priority item.

Thanks !

>
> Regards,
> Chandana
>
> On Fri, Sep 4, 2015 at 12:39 PM, Pavithra Madurangi 
> wrote:
>
>>
>>
>> On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga 
>> wrote:
>>
>>>
>>>
>>> On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:
>>>
 Thanks Prasanna. Please update the JIRA as well.

 In between there was a dep sync issue reported with ESB [1] with the
 recent fix from carbon commons. Just want to find out whether this has any
 effect on GREG product for scenarios like secondary user store, API-M
 integration (May not be an issue since we suggest to use APIM 1.9.1 for GW)
 or install WSO2 AS features and use it (which is anyway very unlikely
 scenario).

>>>
>>> It's hard to think about DipSync use cases in G-Reg.
>>>
>>
>> ​Agree to this.
>>
>> But our concern was secondary user stores. If we have secondary user
>> stores in a multi node deployment, won't there be any issues because of
>> this bug (since it's one place where depSync is needed)?
>>
>> There's a possibility of managing secondary user stores without having
>> depSync. What we wanted to get clarified was whether that's the
>> approach/workaround we suggest ?
>>
>> Regards,
>> pavithra
>>
>>>
>>> Thanks !
>>>

 1. ESBJAVA-4156 





 On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
 wrote:

> Hi Thayalan,
>
> We fixed the issue REGISTRY-2927
>  . Now users can re-login
> from the same window in a fresh pack.
>
> Thanks
>
> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>
>> Hi Team,
>>
>> I've observed from the standalone pack without any changes user has
>> not been allowed to re-login  to the store [1]. However this is working
>> fine for publisher. As per the suggestion in [1] hostname has to be set 
>> in
>> carbon.xml. However in the default pack SSO enabled for store/publisher 
>> and
>> Hostname tag is commented. Even uncomment them and set to IP or localhost
>> too not working as suggested in the JIRA. From the end user perspective
>> user should allow to re-login from the same window session from the fresh
>> pack. Is this is something we need to fix before releasing them?
>>
>> 1.REGISTRY-2927 
>>
>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
>> wrote:
>>
>>> -1,
>>>
>>> We found an issue with solr related logging configuration and this
>>> issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>>>
>>> Step to reproduce this issue:
>>>
>>> Go to Main --> Registry search and search by any value.
>>> Then navigate to Configure --> Logging section.
>>> Exceptions are logged in console and "Global Log4J Configuration"
>>> and "Configure Log4J Appenders" views are not loading due to the above
>>> issue.
>>>
>>> Created a JIRA[1] to track above issue and will release release
>>> G-Reg 5.0.0 RC3 pack ASAP.
>>>
>>> [1]. https://wso2.org/jira/browse/WSAS-2120
>>>
>>> Regards,
>>> Chandana
>>>
>>>
>>> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda <
>>> chand...@wso2.com> wrote:
>>>
 Hi Pubudu,

 Since we have already released RC2 pack and component repos, we can
 not update above pages now. We will update context specific pages for
 coming up 5.0.1 release. Meantime, you can refer wiki based 
 documentation
 available here [1].

 [1].
 https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation

 Regards,
 Chandana

 On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan  wrote:

> Hi Chandana,
>
> Since the Help page, context specific pages are out-dated we need
> to update those to reflect most recent

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-04 Thread Sagara Gunathunga 
On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:

> Thanks Prasanna. Please update the JIRA as well.
>
> In between there was a dep sync issue reported with ESB [1] with the
> recent fix from carbon commons. Just want to find out whether this has any
> effect on GREG product for scenarios like secondary user store, API-M
> integration (May not be an issue since we suggest to use APIM 1.9.1 for GW)
> or install WSO2 AS features and use it (which is anyway very unlikely
> scenario).
>

It's hard to think about DipSync use cases in G-Reg.

Thanks !

>
> 1. ESBJAVA-4156 
>
>
>
>
>
> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
> wrote:
>
>> Hi Thayalan,
>>
>> We fixed the issue REGISTRY-2927
>>  . Now users can re-login
>> from the same window in a fresh pack.
>>
>> Thanks
>>
>> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>>
>>> Hi Team,
>>>
>>> I've observed from the standalone pack without any changes user has not
>>> been allowed to re-login  to the store [1]. However this is working fine
>>> for publisher. As per the suggestion in [1] hostname has to be set in
>>> carbon.xml. However in the default pack SSO enabled for store/publisher and
>>> Hostname tag is commented. Even uncomment them and set to IP or localhost
>>> too not working as suggested in the JIRA. From the end user perspective
>>> user should allow to re-login from the same window session from the fresh
>>> pack. Is this is something we need to fix before releasing them?
>>>
>>> 1.REGISTRY-2927 
>>>
>>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
>>> wrote:
>>>
 -1,

 We found an issue with solr related logging configuration and this
 issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.

 Step to reproduce this issue:

 Go to Main --> Registry search and search by any value.
 Then navigate to Configure --> Logging section.
 Exceptions are logged in console and "Global Log4J Configuration" and
 "Configure Log4J Appenders" views are not loading due to the above issue.

 Created a JIRA[1] to track above issue and will release release G-Reg
 5.0.0 RC3 pack ASAP.

 [1]. https://wso2.org/jira/browse/WSAS-2120

 Regards,
 Chandana


 On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
 wrote:

> Hi Pubudu,
>
> Since we have already released RC2 pack and component repos, we can
> not update above pages now. We will update context specific pages for
> coming up 5.0.1 release. Meantime, you can refer wiki based documentation
> available here [1].
>
> [1].
> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>
> Regards,
> Chandana
>
> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
> wrote:
>
>> Hi Chandana,
>>
>> Since the Help page, context specific pages are out-dated we need to
>> update those to reflect most recent information. Can you please address
>> this issue as required? Please find the relevant ticket below. Thanks.
>>
>> https://wso2.org/jira/browse/REGISTRY-2910
>>
>> Cheers,
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <
>> nirde...@wso2.com> wrote:
>>
>>> The context sensitive help links are in the product UIs. AFAIK,
>>> these links are component-based rather than product based? Please 
>>> correct
>>> me if I am wrong.
>>>
>>> If they are component-based, we cannot link to the wiki of a
>>> specific product from there as many other products might also be using 
>>> the
>>> same component.
>>>
>>> Maybe we should simply disable these help links until we find a
>>> better way to maintain them.
>>>
>>> Thanks,
>>> -Nirdesha
>>>
>>> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hi Nirdesha,

 Can we please point the current context sensitive help pages to
 relevant product documentation of GReg 5.0.0 release?

 Cheers,

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

 On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
 wrote:

>
>
> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
> evanth...@wso2.com> wrote:
>
>> Ack!
>>
>> @Chalitha/Thaya/Pubudu. Please note.
>>
>
> And all the context sensitive help pages  are outdated .
>

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-04 Thread Lalaji Sureshika 
Hi Thayalan,

On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:

> Thanks Prasanna. Please update the JIRA as well.
>
> In between there was a dep sync issue reported with ESB [1] with the
> recent fix from carbon commons. Just want to find out whether this has any
> effect on GREG product for scenarios like secondary user store, API-M
> integration (May not be an issue since we suggest to use APIM 1.9.1 for GW)
> or install WSO2 AS features and use it (which is anyway very unlikely
> scenario).
>

   From APIM integration,we don't need dep-sync feature between publisher
and store assets..Only needed for GW node [which is AM 1.9.1]  as you
mentioned..

Thanks;

>
> 1. ESBJAVA-4156 
>
>
>
>
>
> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
> wrote:
>
>> Hi Thayalan,
>>
>> We fixed the issue REGISTRY-2927
>>  . Now users can re-login
>> from the same window in a fresh pack.
>>
>> Thanks
>>
>> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>>
>>> Hi Team,
>>>
>>> I've observed from the standalone pack without any changes user has not
>>> been allowed to re-login  to the store [1]. However this is working fine
>>> for publisher. As per the suggestion in [1] hostname has to be set in
>>> carbon.xml. However in the default pack SSO enabled for store/publisher and
>>> Hostname tag is commented. Even uncomment them and set to IP or localhost
>>> too not working as suggested in the JIRA. From the end user perspective
>>> user should allow to re-login from the same window session from the fresh
>>> pack. Is this is something we need to fix before releasing them?
>>>
>>> 1.REGISTRY-2927 
>>>
>>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
>>> wrote:
>>>
 -1,

 We found an issue with solr related logging configuration and this
 issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.

 Step to reproduce this issue:

 Go to Main --> Registry search and search by any value.
 Then navigate to Configure --> Logging section.
 Exceptions are logged in console and "Global Log4J Configuration" and
 "Configure Log4J Appenders" views are not loading due to the above issue.

 Created a JIRA[1] to track above issue and will release release G-Reg
 5.0.0 RC3 pack ASAP.

 [1]. https://wso2.org/jira/browse/WSAS-2120

 Regards,
 Chandana


 On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
 wrote:

> Hi Pubudu,
>
> Since we have already released RC2 pack and component repos, we can
> not update above pages now. We will update context specific pages for
> coming up 5.0.1 release. Meantime, you can refer wiki based documentation
> available here [1].
>
> [1].
> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>
> Regards,
> Chandana
>
> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
> wrote:
>
>> Hi Chandana,
>>
>> Since the Help page, context specific pages are out-dated we need to
>> update those to reflect most recent information. Can you please address
>> this issue as required? Please find the relevant ticket below. Thanks.
>>
>> https://wso2.org/jira/browse/REGISTRY-2910
>>
>> Cheers,
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <
>> nirde...@wso2.com> wrote:
>>
>>> The context sensitive help links are in the product UIs. AFAIK,
>>> these links are component-based rather than product based? Please 
>>> correct
>>> me if I am wrong.
>>>
>>> If they are component-based, we cannot link to the wiki of a
>>> specific product from there as many other products might also be using 
>>> the
>>> same component.
>>>
>>> Maybe we should simply disable these help links until we find a
>>> better way to maintain them.
>>>
>>> Thanks,
>>> -Nirdesha
>>>
>>> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hi Nirdesha,

 Can we please point the current context sensitive help pages to
 relevant product documentation of GReg 5.0.0 release?

 Cheers,

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

 On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
 wrote:

>
>
> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
> evanth...@wso2.com> wrote:
>
>> Ack!
>>
>>

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-04 Thread Pavithra Madurangi 
On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga  wrote:

>
>
> On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:
>
>> Thanks Prasanna. Please update the JIRA as well.
>>
>> In between there was a dep sync issue reported with ESB [1] with the
>> recent fix from carbon commons. Just want to find out whether this has any
>> effect on GREG product for scenarios like secondary user store, API-M
>> integration (May not be an issue since we suggest to use APIM 1.9.1 for GW)
>> or install WSO2 AS features and use it (which is anyway very unlikely
>> scenario).
>>
>
> It's hard to think about DipSync use cases in G-Reg.
>

​Agree to this.

But our concern was secondary user stores. If we have secondary user stores
in a multi node deployment, won't there be any issues because of this bug
(since it's one place where depSync is needed)?

There's a possibility of managing secondary user stores without having
depSync. What we wanted to get clarified was whether that's the
approach/workaround we suggest ?

Regards,
pavithra

>
> Thanks !
>
>>
>> 1. ESBJAVA-4156 
>>
>>
>>
>>
>>
>> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
>> wrote:
>>
>>> Hi Thayalan,
>>>
>>> We fixed the issue REGISTRY-2927
>>>  . Now users can re-login
>>> from the same window in a fresh pack.
>>>
>>> Thanks
>>>
>>> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>>>
 Hi Team,

 I've observed from the standalone pack without any changes user has not
 been allowed to re-login  to the store [1]. However this is working fine
 for publisher. As per the suggestion in [1] hostname has to be set in
 carbon.xml. However in the default pack SSO enabled for store/publisher and
 Hostname tag is commented. Even uncomment them and set to IP or localhost
 too not working as suggested in the JIRA. From the end user perspective
 user should allow to re-login from the same window session from the fresh
 pack. Is this is something we need to fix before releasing them?

 1.REGISTRY-2927 

 On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
 wrote:

> -1,
>
> We found an issue with solr related logging configuration and this
> issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>
> Step to reproduce this issue:
>
> Go to Main --> Registry search and search by any value.
> Then navigate to Configure --> Logging section.
> Exceptions are logged in console and "Global Log4J Configuration" and
> "Configure Log4J Appenders" views are not loading due to the above issue.
>
> Created a JIRA[1] to track above issue and will release release G-Reg
> 5.0.0 RC3 pack ASAP.
>
> [1]. https://wso2.org/jira/browse/WSAS-2120
>
> Regards,
> Chandana
>
>
> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
> wrote:
>
>> Hi Pubudu,
>>
>> Since we have already released RC2 pack and component repos, we can
>> not update above pages now. We will update context specific pages for
>> coming up 5.0.1 release. Meantime, you can refer wiki based documentation
>> available here [1].
>>
>> [1].
>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>
>> Regards,
>> Chandana
>>
>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Chandana,
>>>
>>> Since the Help page, context specific pages are out-dated we need to
>>> update those to reflect most recent information. Can you please address
>>> this issue as required? Please find the relevant ticket below. Thanks.
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2910
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <
>>> nirde...@wso2.com> wrote:
>>>
 The context sensitive help links are in the product UIs. AFAIK,
 these links are component-based rather than product based? Please 
 correct
 me if I am wrong.

 If they are component-based, we cannot link to the wiki of a
 specific product from there as many other products might also be using 
 the
 same component.

 Maybe we should simply disable these help links until we find a
 better way to maintain them.

 Thanks,
 -Nirdesha

 On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan  wrote:

> Hi Nirdesha,
>
> Can we please point the current context sensitive help pages

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-04 Thread Thayalan 
Hi Team,

Could you please let us know the ETA for RC3 pack and planned GA
rescheduled date? This is to reduce the scope and test accordingly.

On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda  wrote:

> -1,
>
> We found an issue with solr related logging configuration and this issue
> is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>
> Step to reproduce this issue:
>
> Go to Main --> Registry search and search by any value.
> Then navigate to Configure --> Logging section.
> Exceptions are logged in console and "Global Log4J Configuration" and
> "Configure Log4J Appenders" views are not loading due to the above issue.
>
> Created a JIRA[1] to track above issue and will release release G-Reg
> 5.0.0 RC3 pack ASAP.
>
> [1]. https://wso2.org/jira/browse/WSAS-2120
>
> Regards,
> Chandana
>
>
> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
> wrote:
>
>> Hi Pubudu,
>>
>> Since we have already released RC2 pack and component repos, we can not
>> update above pages now. We will update context specific pages for coming up
>> 5.0.1 release. Meantime, you can refer wiki based documentation available
>> here [1].
>>
>> [1].
>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>
>> Regards,
>> Chandana
>>
>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Chandana,
>>>
>>> Since the Help page, context specific pages are out-dated we need to
>>> update those to reflect most recent information. Can you please address
>>> this issue as required? Please find the relevant ticket below. Thanks.
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2910
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe 
>>> wrote:
>>>
 The context sensitive help links are in the product UIs. AFAIK, these
 links are component-based rather than product based? Please correct me if I
 am wrong.

 If they are component-based, we cannot link to the wiki of a specific
 product from there as many other products might also be using the same
 component.

 Maybe we should simply disable these help links until we find a better
 way to maintain them.

 Thanks,
 -Nirdesha

 On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
 wrote:

> Hi Nirdesha,
>
> Can we please point the current context sensitive help pages to
> relevant product documentation of GReg 5.0.0 release?
>
> Cheers,
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
> wrote:
>
>>
>>
>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
>> evanth...@wso2.com> wrote:
>>
>>> Ack!
>>>
>>> @Chalitha/Thaya/Pubudu. Please note.
>>>
>>
>> And all the context sensitive help pages  are outdated .
>>
>> -Ajith
>>
>>
>>>
>>> Regards,
>>> Evanthika Amarasiri
>>> Senior Technical Lead  - Quality Assurance
>>> Mobile: +94773125935
>>> Blog: evanthika.blogspot.com
>>>
>>> wso2.com lean.enterprise.middleware
>>>
>>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
>>> wrote:
>>>
 Hi All

 This is non a bug but please fix the about page if possible because
 this is a major release. (find the attached image)

 -Ajith





 On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <
 prasa...@wso2.com> wrote:

> Hi All,
>
> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>
> This release fixes the following issues:
>
> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
> https://wso2.org/jira/browse/REGISTRY-2908
>
> Please download, test and vote. Please refer the release
> verification guide for detailed information on verifying this release.
>
> *Source & binary distribution files:*
>
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>
> *Maven staging repo:*
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>
> *The tag to be voted upon:*
>
> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>
>
>
> [*+*] Stable - go ahead and release
>
> [*-*]  Broken - do not release (explain why)
>
> Thanks and Regards
> G-Reg team
>
> Prasanna Dangalla
> Software Engineer, WSO2, Inc.; http://wso2.com/
>

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-04 Thread Chandana Napagoda 
Hi Pavithra,

As a workaround one can use rsync or copy secondary user store
configuration in to other nodes.

Regards,
Chandana

On Fri, Sep 4, 2015 at 12:39 PM, Pavithra Madurangi 
wrote:

>
>
> On Fri, Sep 4, 2015 at 12:01 PM, Sagara Gunathunga 
> wrote:
>
>>
>>
>> On Fri, Sep 4, 2015 at 11:04 AM, Thayalan  wrote:
>>
>>> Thanks Prasanna. Please update the JIRA as well.
>>>
>>> In between there was a dep sync issue reported with ESB [1] with the
>>> recent fix from carbon commons. Just want to find out whether this has any
>>> effect on GREG product for scenarios like secondary user store, API-M
>>> integration (May not be an issue since we suggest to use APIM 1.9.1 for GW)
>>> or install WSO2 AS features and use it (which is anyway very unlikely
>>> scenario).
>>>
>>
>> It's hard to think about DipSync use cases in G-Reg.
>>
>
> ​Agree to this.
>
> But our concern was secondary user stores. If we have secondary user
> stores in a multi node deployment, won't there be any issues because of
> this bug (since it's one place where depSync is needed)?
>
> There's a possibility of managing secondary user stores without having
> depSync. What we wanted to get clarified was whether that's the
> approach/workaround we suggest ?
>
> Regards,
> pavithra
>
>>
>> Thanks !
>>
>>>
>>> 1. ESBJAVA-4156 
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla 
>>> wrote:
>>>
 Hi Thayalan,

 We fixed the issue REGISTRY-2927
  . Now users can re-login
 from the same window in a fresh pack.

 Thanks

 On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:

> Hi Team,
>
> I've observed from the standalone pack without any changes user has
> not been allowed to re-login  to the store [1]. However this is working
> fine for publisher. As per the suggestion in [1] hostname has to be set in
> carbon.xml. However in the default pack SSO enabled for store/publisher 
> and
> Hostname tag is commented. Even uncomment them and set to IP or localhost
> too not working as suggested in the JIRA. From the end user perspective
> user should allow to re-login from the same window session from the fresh
> pack. Is this is something we need to fix before releasing them?
>
> 1.REGISTRY-2927 
>
> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
> wrote:
>
>> -1,
>>
>> We found an issue with solr related logging configuration and this
>> issue is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>>
>> Step to reproduce this issue:
>>
>> Go to Main --> Registry search and search by any value.
>> Then navigate to Configure --> Logging section.
>> Exceptions are logged in console and "Global Log4J Configuration" and
>> "Configure Log4J Appenders" views are not loading due to the above issue.
>>
>> Created a JIRA[1] to track above issue and will release release G-Reg
>> 5.0.0 RC3 pack ASAP.
>>
>> [1]. https://wso2.org/jira/browse/WSAS-2120
>>
>> Regards,
>> Chandana
>>
>>
>> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda > > wrote:
>>
>>> Hi Pubudu,
>>>
>>> Since we have already released RC2 pack and component repos, we can
>>> not update above pages now. We will update context specific pages for
>>> coming up 5.0.1 release. Meantime, you can refer wiki based 
>>> documentation
>>> available here [1].
>>>
>>> [1].
>>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>>
>>> Regards,
>>> Chandana
>>>
>>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hi Chandana,

 Since the Help page, context specific pages are out-dated we need
 to update those to reflect most recent information. Can you please 
 address
 this issue as required? Please find the relevant ticket below. Thanks.

 https://wso2.org/jira/browse/REGISTRY-2910

 Cheers,

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

 On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <
 nirde...@wso2.com> wrote:

> The context sensitive help links are in the product UIs. AFAIK,
> these links are component-based rather than product based? Please 
> correct
> me if I am wrong.
>
> If they are component-based, we cannot link to the wiki of a
> specific product from there as many other products might also be 
> using the
> same

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-03 Thread Thayalan 
Hi Team,

I've observed from the standalone pack without any changes user has not
been allowed to re-login  to the store [1]. However this is working fine
for publisher. As per the suggestion in [1] hostname has to be set in
carbon.xml. However in the default pack SSO enabled for store/publisher and
Hostname tag is commented. Even uncomment them and set to IP or localhost
too not working as suggested in the JIRA. From the end user perspective
user should allow to re-login from the same window session from the fresh
pack. Is this is something we need to fix before releasing them?

1.REGISTRY-2927 

On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda  wrote:

> -1,
>
> We found an issue with solr related logging configuration and this issue
> is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>
> Step to reproduce this issue:
>
> Go to Main --> Registry search and search by any value.
> Then navigate to Configure --> Logging section.
> Exceptions are logged in console and "Global Log4J Configuration" and
> "Configure Log4J Appenders" views are not loading due to the above issue.
>
> Created a JIRA[1] to track above issue and will release release G-Reg
> 5.0.0 RC3 pack ASAP.
>
> [1]. https://wso2.org/jira/browse/WSAS-2120
>
> Regards,
> Chandana
>
>
> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
> wrote:
>
>> Hi Pubudu,
>>
>> Since we have already released RC2 pack and component repos, we can not
>> update above pages now. We will update context specific pages for coming up
>> 5.0.1 release. Meantime, you can refer wiki based documentation available
>> here [1].
>>
>> [1].
>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>
>> Regards,
>> Chandana
>>
>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Chandana,
>>>
>>> Since the Help page, context specific pages are out-dated we need to
>>> update those to reflect most recent information. Can you please address
>>> this issue as required? Please find the relevant ticket below. Thanks.
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2910
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe 
>>> wrote:
>>>
 The context sensitive help links are in the product UIs. AFAIK, these
 links are component-based rather than product based? Please correct me if I
 am wrong.

 If they are component-based, we cannot link to the wiki of a specific
 product from there as many other products might also be using the same
 component.

 Maybe we should simply disable these help links until we find a better
 way to maintain them.

 Thanks,
 -Nirdesha

 On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
 wrote:

> Hi Nirdesha,
>
> Can we please point the current context sensitive help pages to
> relevant product documentation of GReg 5.0.0 release?
>
> Cheers,
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
> wrote:
>
>>
>>
>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
>> evanth...@wso2.com> wrote:
>>
>>> Ack!
>>>
>>> @Chalitha/Thaya/Pubudu. Please note.
>>>
>>
>> And all the context sensitive help pages  are outdated .
>>
>> -Ajith
>>
>>
>>>
>>> Regards,
>>> Evanthika Amarasiri
>>> Senior Technical Lead  - Quality Assurance
>>> Mobile: +94773125935
>>> Blog: evanthika.blogspot.com
>>>
>>> wso2.com lean.enterprise.middleware
>>>
>>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
>>> wrote:
>>>
 Hi All

 This is non a bug but please fix the about page if possible because
 this is a major release. (find the attached image)

 -Ajith





 On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <
 prasa...@wso2.com> wrote:

> Hi All,
>
> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>
> This release fixes the following issues:
>
> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
> https://wso2.org/jira/browse/REGISTRY-2908
>
> Please download, test and vote. Please refer the release
> verification guide for detailed information on verifying this release.
>
> *Source & binary distribution files:*
>
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>
> *Maven staging repo:*
>

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-03 Thread Thayalan 
Thanks Prasanna. Please update the JIRA as well.

In between there was a dep sync issue reported with ESB [1] with the recent
fix from carbon commons. Just want to find out whether this has any effect
on GREG product for scenarios like secondary user store, API-M integration
(May not be an issue since we suggest to use APIM 1.9.1 for GW) or install
WSO2 AS features and use it (which is anyway very unlikely scenario).

1. ESBJAVA-4156 





On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla  wrote:

> Hi Thayalan,
>
> We fixed the issue REGISTRY-2927
>  . Now users can re-login
> from the same window in a fresh pack.
>
> Thanks
>
> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>
>> Hi Team,
>>
>> I've observed from the standalone pack without any changes user has not
>> been allowed to re-login  to the store [1]. However this is working fine
>> for publisher. As per the suggestion in [1] hostname has to be set in
>> carbon.xml. However in the default pack SSO enabled for store/publisher and
>> Hostname tag is commented. Even uncomment them and set to IP or localhost
>> too not working as suggested in the JIRA. From the end user perspective
>> user should allow to re-login from the same window session from the fresh
>> pack. Is this is something we need to fix before releasing them?
>>
>> 1.REGISTRY-2927 
>>
>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
>> wrote:
>>
>>> -1,
>>>
>>> We found an issue with solr related logging configuration and this issue
>>> is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>>>
>>> Step to reproduce this issue:
>>>
>>> Go to Main --> Registry search and search by any value.
>>> Then navigate to Configure --> Logging section.
>>> Exceptions are logged in console and "Global Log4J Configuration" and
>>> "Configure Log4J Appenders" views are not loading due to the above issue.
>>>
>>> Created a JIRA[1] to track above issue and will release release G-Reg
>>> 5.0.0 RC3 pack ASAP.
>>>
>>> [1]. https://wso2.org/jira/browse/WSAS-2120
>>>
>>> Regards,
>>> Chandana
>>>
>>>
>>> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
>>> wrote:
>>>
 Hi Pubudu,

 Since we have already released RC2 pack and component repos, we can not
 update above pages now. We will update context specific pages for coming up
 5.0.1 release. Meantime, you can refer wiki based documentation available
 here [1].

 [1].
 https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation

 Regards,
 Chandana

 On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
 wrote:

> Hi Chandana,
>
> Since the Help page, context specific pages are out-dated we need to
> update those to reflect most recent information. Can you please address
> this issue as required? Please find the relevant ticket below. Thanks.
>
> https://wso2.org/jira/browse/REGISTRY-2910
>
> Cheers,
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <
> nirde...@wso2.com> wrote:
>
>> The context sensitive help links are in the product UIs. AFAIK, these
>> links are component-based rather than product based? Please correct me 
>> if I
>> am wrong.
>>
>> If they are component-based, we cannot link to the wiki of a specific
>> product from there as many other products might also be using the same
>> component.
>>
>> Maybe we should simply disable these help links until we find a
>> better way to maintain them.
>>
>> Thanks,
>> -Nirdesha
>>
>> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Nirdesha,
>>>
>>> Can we please point the current context sensitive help pages to
>>> relevant product documentation of GReg 5.0.0 release?
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
>>> wrote:
>>>


 On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
 evanth...@wso2.com> wrote:

> Ack!
>
> @Chalitha/Thaya/Pubudu. Please note.
>

 And all the context sensitive help pages  are outdated .

 -Ajith


>
> Regards,
> Evanthika Amarasiri
> Senior Technical Lead  - Quality Assurance
> Mobile: +94773125935
> Blog: evanthika.blogspot.com
>
> wso2.com lean.enterprise.middleware
>
> On Wed,

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-03 Thread Prasanna Dangalla 
Hi Thayalan,

We fixed the issue REGISTRY-2927
 . Now users can re-login from
the same window in a fresh pack.

Thanks

On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:

> Hi Team,
>
> I've observed from the standalone pack without any changes user has not
> been allowed to re-login  to the store [1]. However this is working fine
> for publisher. As per the suggestion in [1] hostname has to be set in
> carbon.xml. However in the default pack SSO enabled for store/publisher and
> Hostname tag is commented. Even uncomment them and set to IP or localhost
> too not working as suggested in the JIRA. From the end user perspective
> user should allow to re-login from the same window session from the fresh
> pack. Is this is something we need to fix before releasing them?
>
> 1.REGISTRY-2927 
>
> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
> wrote:
>
>> -1,
>>
>> We found an issue with solr related logging configuration and this issue
>> is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>>
>> Step to reproduce this issue:
>>
>> Go to Main --> Registry search and search by any value.
>> Then navigate to Configure --> Logging section.
>> Exceptions are logged in console and "Global Log4J Configuration" and
>> "Configure Log4J Appenders" views are not loading due to the above issue.
>>
>> Created a JIRA[1] to track above issue and will release release G-Reg
>> 5.0.0 RC3 pack ASAP.
>>
>> [1]. https://wso2.org/jira/browse/WSAS-2120
>>
>> Regards,
>> Chandana
>>
>>
>> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
>> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Since we have already released RC2 pack and component repos, we can not
>>> update above pages now. We will update context specific pages for coming up
>>> 5.0.1 release. Meantime, you can refer wiki based documentation available
>>> here [1].
>>>
>>> [1].
>>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>>
>>> Regards,
>>> Chandana
>>>
>>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hi Chandana,

 Since the Help page, context specific pages are out-dated we need to
 update those to reflect most recent information. Can you please address
 this issue as required? Please find the relevant ticket below. Thanks.

 https://wso2.org/jira/browse/REGISTRY-2910

 Cheers,

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

 On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe  wrote:

> The context sensitive help links are in the product UIs. AFAIK, these
> links are component-based rather than product based? Please correct me if 
> I
> am wrong.
>
> If they are component-based, we cannot link to the wiki of a specific
> product from there as many other products might also be using the same
> component.
>
> Maybe we should simply disable these help links until we find a better
> way to maintain them.
>
> Thanks,
> -Nirdesha
>
> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
> wrote:
>
>> Hi Nirdesha,
>>
>> Can we please point the current context sensitive help pages to
>> relevant product documentation of GReg 5.0.0 release?
>>
>> Cheers,
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
>> wrote:
>>
>>>
>>>
>>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
>>> evanth...@wso2.com> wrote:
>>>
 Ack!

 @Chalitha/Thaya/Pubudu. Please note.

>>>
>>> And all the context sensitive help pages  are outdated .
>>>
>>> -Ajith
>>>
>>>

 Regards,
 Evanthika Amarasiri
 Senior Technical Lead  - Quality Assurance
 Mobile: +94773125935
 Blog: evanthika.blogspot.com

 wso2.com lean.enterprise.middleware

 On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
 wrote:

> Hi All
>
> This is non a bug but please fix the about page if possible
> because this is a major release. (find the attached image)
>
> -Ajith
>
>
>
>
>
> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <
> prasa...@wso2.com> wrote:
>
>> Hi All,
>>
>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>
>> This release fixes the following issues:
>>
>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>>

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-02 Thread Chandana Napagoda 
Hi Pubudu,

Since we have already released RC2 pack and component repos, we can not
update above pages now. We will update context specific pages for coming up
5.0.1 release. Meantime, you can refer wiki based documentation available
here [1].

[1].
https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation

Regards,
Chandana

On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan  wrote:

> Hi Chandana,
>
> Since the Help page, context specific pages are out-dated we need to
> update those to reflect most recent information. Can you please address
> this issue as required? Please find the relevant ticket below. Thanks.
>
> https://wso2.org/jira/browse/REGISTRY-2910
>
> Cheers,
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe 
> wrote:
>
>> The context sensitive help links are in the product UIs. AFAIK, these
>> links are component-based rather than product based? Please correct me if I
>> am wrong.
>>
>> If they are component-based, we cannot link to the wiki of a specific
>> product from there as many other products might also be using the same
>> component.
>>
>> Maybe we should simply disable these help links until we find a better
>> way to maintain them.
>>
>> Thanks,
>> -Nirdesha
>>
>> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Nirdesha,
>>>
>>> Can we please point the current context sensitive help pages to relevant
>>> product documentation of GReg 5.0.0 release?
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana  wrote:
>>>


 On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
 evanth...@wso2.com> wrote:

> Ack!
>
> @Chalitha/Thaya/Pubudu. Please note.
>

 And all the context sensitive help pages  are outdated .

 -Ajith


>
> Regards,
> Evanthika Amarasiri
> Senior Technical Lead  - Quality Assurance
> Mobile: +94773125935
> Blog: evanthika.blogspot.com
>
> wso2.com lean.enterprise.middleware
>
> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
> wrote:
>
>> Hi All
>>
>> This is non a bug but please fix the about page if possible because
>> this is a major release. (find the attached image)
>>
>> -Ajith
>>
>>
>>
>>
>>
>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla > > wrote:
>>
>>> Hi All,
>>>
>>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>>
>>> This release fixes the following issues:
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>>> https://wso2.org/jira/browse/REGISTRY-2908
>>>
>>> Please download, test and vote. Please refer the release
>>> verification guide for detailed information on verifying this release.
>>>
>>> *Source & binary distribution files:*
>>>
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>>>
>>> *Maven staging repo:*
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>>>
>>> *The tag to be voted upon:*
>>>
>>> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>>>
>>>
>>>
>>> [*+*] Stable - go ahead and release
>>>
>>> [*-*]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards
>>> G-Reg team
>>>
>>> Prasanna Dangalla
>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> cell: +94 718 11 27 51
>>> twitter: @prasa77
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ajith Vitharana.
>>
>> WSO2 Inc. - http://wso2.com
>> Email  : aji...@wso2.com
>> Blog: http://vitharana.org
>> Mobile : +1-812-360-5335
>>
>>
>


 --
 Ajith Vitharana.

 WSO2 Inc. - http://wso2.com
 Email  : aji...@wso2.com
 Blog: http://vitharana.org
 Mobile : +1-812-360-5335


>>>
>>
>>
>> --
>>
>> Thanks,
>>
>> Nirdesha Munasinghe,
>> WSO2 Inc.
>> Web:http://wso2.com
>>
>> Mobile: +94 776321920
>>
>
>


-- 
*Chandana Napagoda*
Senior Software Engineer
WSO2 Inc. - http://wso2.org

*Email  :  chand...@wso2.com **Mobile : +94718169299*

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

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-02 Thread Chandana Napagoda 
-1,

We found an issue with solr related logging configuration and this issue is
reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.

Step to reproduce this issue:

Go to Main --> Registry search and search by any value.
Then navigate to Configure --> Logging section.
Exceptions are logged in console and "Global Log4J Configuration" and
"Configure Log4J Appenders" views are not loading due to the above issue.

Created a JIRA[1] to track above issue and will release release G-Reg 5.0.0
RC3 pack ASAP.

[1]. https://wso2.org/jira/browse/WSAS-2120

Regards,
Chandana


On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
wrote:

> Hi Pubudu,
>
> Since we have already released RC2 pack and component repos, we can not
> update above pages now. We will update context specific pages for coming up
> 5.0.1 release. Meantime, you can refer wiki based documentation available
> here [1].
>
> [1].
> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>
> Regards,
> Chandana
>
> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
> wrote:
>
>> Hi Chandana,
>>
>> Since the Help page, context specific pages are out-dated we need to
>> update those to reflect most recent information. Can you please address
>> this issue as required? Please find the relevant ticket below. Thanks.
>>
>> https://wso2.org/jira/browse/REGISTRY-2910
>>
>> Cheers,
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe 
>> wrote:
>>
>>> The context sensitive help links are in the product UIs. AFAIK, these
>>> links are component-based rather than product based? Please correct me if I
>>> am wrong.
>>>
>>> If they are component-based, we cannot link to the wiki of a specific
>>> product from there as many other products might also be using the same
>>> component.
>>>
>>> Maybe we should simply disable these help links until we find a better
>>> way to maintain them.
>>>
>>> Thanks,
>>> -Nirdesha
>>>
>>> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hi Nirdesha,

 Can we please point the current context sensitive help pages to
 relevant product documentation of GReg 5.0.0 release?

 Cheers,

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

 On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
 wrote:

>
>
> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
> evanth...@wso2.com> wrote:
>
>> Ack!
>>
>> @Chalitha/Thaya/Pubudu. Please note.
>>
>
> And all the context sensitive help pages  are outdated .
>
> -Ajith
>
>
>>
>> Regards,
>> Evanthika Amarasiri
>> Senior Technical Lead  - Quality Assurance
>> Mobile: +94773125935
>> Blog: evanthika.blogspot.com
>>
>> wso2.com lean.enterprise.middleware
>>
>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
>> wrote:
>>
>>> Hi All
>>>
>>> This is non a bug but please fix the about page if possible because
>>> this is a major release. (find the attached image)
>>>
>>> -Ajith
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <
>>> prasa...@wso2.com> wrote:
>>>
 Hi All,

 *This is the RC 2 release candidate of G-Reg 5.0.0 *

 This release fixes the following issues:

 https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
 https://wso2.org/jira/browse/REGISTRY-2908

 Please download, test and vote. Please refer the release
 verification guide for detailed information on verifying this release.

 *Source & binary distribution files:*


 http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/

 *Maven staging repo:*

 http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/

 *The tag to be voted upon:*

 https://github.com/wso2/product-greg/tree/v5.0.0-rc2



 [*+*] Stable - go ahead and release

 [*-*]  Broken - do not release (explain why)

 Thanks and Regards
 G-Reg team

 Prasanna Dangalla
 Software Engineer, WSO2, Inc.; http://wso2.com/
 lean.enterprise.middleware

 cell: +94 718 11 27 51
 twitter: @prasa77

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


>>>
>>>
>>> --
>>> Ajith Vitharana.
>>>
>>> WSO2 Inc. - http://wso2.com
>>> Email  :

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-01 Thread Pubudu Priyashan 
Hi Nirdesha,

Can we please point the current context sensitive help pages to relevant
product documentation of GReg 5.0.0 release?

Cheers,

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

On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana  wrote:

>
>
> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri 
> wrote:
>
>> Ack!
>>
>> @Chalitha/Thaya/Pubudu. Please note.
>>
>
> And all the context sensitive help pages  are outdated .
>
> -Ajith
>
>
>>
>> Regards,
>> Evanthika Amarasiri
>> Senior Technical Lead  - Quality Assurance
>> Mobile: +94773125935
>> Blog: evanthika.blogspot.com
>>
>> wso2.com lean.enterprise.middleware
>>
>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana  wrote:
>>
>>> Hi All
>>>
>>> This is non a bug but please fix the about page if possible because this
>>> is a major release. (find the attached image)
>>>
>>> -Ajith
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
>>> wrote:
>>>
 Hi All,

 *This is the RC 2 release candidate of G-Reg 5.0.0 *

 This release fixes the following issues:

 https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
 https://wso2.org/jira/browse/REGISTRY-2908

 Please download, test and vote. Please refer the release verification
 guide for detailed information on verifying this release.

 *Source & binary distribution files:*


 http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/

 *Maven staging repo:*

 http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/

 *The tag to be voted upon:*

 https://github.com/wso2/product-greg/tree/v5.0.0-rc2



 [*+*] Stable - go ahead and release

 [*-*]  Broken - do not release (explain why)

 Thanks and Regards
 G-Reg team

 Prasanna Dangalla
 Software Engineer, WSO2, Inc.; http://wso2.com/
 lean.enterprise.middleware

 cell: +94 718 11 27 51
 twitter: @prasa77

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


>>>
>>>
>>> --
>>> Ajith Vitharana.
>>>
>>> WSO2 Inc. - http://wso2.com
>>> Email  : aji...@wso2.com
>>> Blog: http://vitharana.org
>>> Mobile : +1-812-360-5335
>>>
>>>
>>
>
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-01 Thread Evanthika Amarasiri 
Ack!

@Chalitha/Thaya/Pubudu. Please note.

Regards,
Evanthika Amarasiri
Senior Technical Lead  - Quality Assurance
Mobile: +94773125935
Blog: evanthika.blogspot.com

wso2.com lean.enterprise.middleware

On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana  wrote:

> Hi All
>
> This is non a bug but please fix the about page if possible because this
> is a major release. (find the attached image)
>
> -Ajith
>
>
>
>
>
> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
> wrote:
>
>> Hi All,
>>
>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>
>> This release fixes the following issues:
>>
>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>> https://wso2.org/jira/browse/REGISTRY-2908
>>
>> Please download, test and vote. Please refer the release verification
>> guide for detailed information on verifying this release.
>>
>> *Source & binary distribution files:*
>>
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>>
>> *Maven staging repo:*
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>>
>> *The tag to be voted upon:*
>>
>> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>>
>>
>>
>> [*+*] Stable - go ahead and release
>>
>> [*-*]  Broken - do not release (explain why)
>>
>> Thanks and Regards
>> G-Reg team
>>
>> Prasanna Dangalla
>> Software Engineer, WSO2, Inc.; http://wso2.com/
>> lean.enterprise.middleware
>>
>> cell: +94 718 11 27 51
>> twitter: @prasa77
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-01 Thread Nirdesha Munasinghe 
The context sensitive help links are in the product UIs. AFAIK, these links
are component-based rather than product based? Please correct me if I am
wrong.

If they are component-based, we cannot link to the wiki of a specific
product from there as many other products might also be using the same
component.

Maybe we should simply disable these help links until we find a better way
to maintain them.

Thanks,
-Nirdesha

On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan  wrote:

> Hi Nirdesha,
>
> Can we please point the current context sensitive help pages to relevant
> product documentation of GReg 5.0.0 release?
>
> Cheers,
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana  wrote:
>
>>
>>
>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri 
>> wrote:
>>
>>> Ack!
>>>
>>> @Chalitha/Thaya/Pubudu. Please note.
>>>
>>
>> And all the context sensitive help pages  are outdated .
>>
>> -Ajith
>>
>>
>>>
>>> Regards,
>>> Evanthika Amarasiri
>>> Senior Technical Lead  - Quality Assurance
>>> Mobile: +94773125935
>>> Blog: evanthika.blogspot.com
>>>
>>> wso2.com lean.enterprise.middleware
>>>
>>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana  wrote:
>>>
 Hi All

 This is non a bug but please fix the about page if possible because
 this is a major release. (find the attached image)

 -Ajith





 On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
 wrote:

> Hi All,
>
> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>
> This release fixes the following issues:
>
> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
> https://wso2.org/jira/browse/REGISTRY-2908
>
> Please download, test and vote. Please refer the release verification
> guide for detailed information on verifying this release.
>
> *Source & binary distribution files:*
>
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>
> *Maven staging repo:*
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>
> *The tag to be voted upon:*
>
> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>
>
>
> [*+*] Stable - go ahead and release
>
> [*-*]  Broken - do not release (explain why)
>
> Thanks and Regards
> G-Reg team
>
> Prasanna Dangalla
> Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
> cell: +94 718 11 27 51
> twitter: @prasa77
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Ajith Vitharana.

 WSO2 Inc. - http://wso2.com
 Email  : aji...@wso2.com
 Blog: http://vitharana.org
 Mobile : +1-812-360-5335


>>>
>>
>>
>> --
>> Ajith Vitharana.
>>
>> WSO2 Inc. - http://wso2.com
>> Email  : aji...@wso2.com
>> Blog: http://vitharana.org
>> Mobile : +1-812-360-5335
>>
>>
>


-- 

Thanks,

Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com

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

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-01 Thread Pubudu Priyashan 
Hi Chandana,

Since the Help page, context specific pages are out-dated we need to update
those to reflect most recent information. Can you please address this issue
as required? Please find the relevant ticket below. Thanks.

https://wso2.org/jira/browse/REGISTRY-2910

Cheers,

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

On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe 
wrote:

> The context sensitive help links are in the product UIs. AFAIK, these
> links are component-based rather than product based? Please correct me if I
> am wrong.
>
> If they are component-based, we cannot link to the wiki of a specific
> product from there as many other products might also be using the same
> component.
>
> Maybe we should simply disable these help links until we find a better way
> to maintain them.
>
> Thanks,
> -Nirdesha
>
> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
> wrote:
>
>> Hi Nirdesha,
>>
>> Can we please point the current context sensitive help pages to relevant
>> product documentation of GReg 5.0.0 release?
>>
>> Cheers,
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana  wrote:
>>
>>>
>>>
>>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri >> > wrote:
>>>
 Ack!

 @Chalitha/Thaya/Pubudu. Please note.

>>>
>>> And all the context sensitive help pages  are outdated .
>>>
>>> -Ajith
>>>
>>>

 Regards,
 Evanthika Amarasiri
 Senior Technical Lead  - Quality Assurance
 Mobile: +94773125935
 Blog: evanthika.blogspot.com

 wso2.com lean.enterprise.middleware

 On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
 wrote:

> Hi All
>
> This is non a bug but please fix the about page if possible because
> this is a major release. (find the attached image)
>
> -Ajith
>
>
>
>
>
> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
> wrote:
>
>> Hi All,
>>
>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>
>> This release fixes the following issues:
>>
>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>> https://wso2.org/jira/browse/REGISTRY-2908
>>
>> Please download, test and vote. Please refer the release verification
>> guide for detailed information on verifying this release.
>>
>> *Source & binary distribution files:*
>>
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>>
>> *Maven staging repo:*
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>>
>> *The tag to be voted upon:*
>>
>> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>>
>>
>>
>> [*+*] Stable - go ahead and release
>>
>> [*-*]  Broken - do not release (explain why)
>>
>> Thanks and Regards
>> G-Reg team
>>
>> Prasanna Dangalla
>> Software Engineer, WSO2, Inc.; http://wso2.com/
>> lean.enterprise.middleware
>>
>> cell: +94 718 11 27 51
>> twitter: @prasa77
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>

>>>
>>>
>>> --
>>> Ajith Vitharana.
>>>
>>> WSO2 Inc. - http://wso2.com
>>> Email  : aji...@wso2.com
>>> Blog: http://vitharana.org
>>> Mobile : +1-812-360-5335
>>>
>>>
>>
>
>
> --
>
> Thanks,
>
> Nirdesha Munasinghe,
> WSO2 Inc.
> Web:http://wso2.com
>
> Mobile: +94 776321920
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-01 Thread Ajith Vitharana 
On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri 
wrote:

> Ack!
>
> @Chalitha/Thaya/Pubudu. Please note.
>

And all the context sensitive help pages  are outdated .

-Ajith


>
> Regards,
> Evanthika Amarasiri
> Senior Technical Lead  - Quality Assurance
> Mobile: +94773125935
> Blog: evanthika.blogspot.com
>
> wso2.com lean.enterprise.middleware
>
> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana  wrote:
>
>> Hi All
>>
>> This is non a bug but please fix the about page if possible because this
>> is a major release. (find the attached image)
>>
>> -Ajith
>>
>>
>>
>>
>>
>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
>> wrote:
>>
>>> Hi All,
>>>
>>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>>
>>> This release fixes the following issues:
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>>> https://wso2.org/jira/browse/REGISTRY-2908
>>>
>>> Please download, test and vote. Please refer the release verification
>>> guide for detailed information on verifying this release.
>>>
>>> *Source & binary distribution files:*
>>>
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>>>
>>> *Maven staging repo:*
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>>>
>>> *The tag to be voted upon:*
>>>
>>> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>>>
>>>
>>>
>>> [*+*] Stable - go ahead and release
>>>
>>> [*-*]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards
>>> G-Reg team
>>>
>>> Prasanna Dangalla
>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> cell: +94 718 11 27 51
>>> twitter: @prasa77
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ajith Vitharana.
>>
>> WSO2 Inc. - http://wso2.com
>> Email  : aji...@wso2.com
>> Blog: http://vitharana.org
>> Mobile : +1-812-360-5335
>>
>>
>


-- 
Ajith Vitharana.

WSO2 Inc. - http://wso2.com
Email  : aji...@wso2.com
Blog: http://vitharana.org
Mobile : +1-812-360-5335
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-01 Thread Pubudu Priyashan 
Noted. I have created following ticket in JIRA to address the About page
now.

https://wso2.org/jira/browse/REGISTRY-2909

Cheers,

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

On Wed, Sep 2, 2015 at 9:38 AM, Evanthika Amarasiri 
wrote:

> Ack!
>
> @Chalitha/Thaya/Pubudu. Please note.
>
> Regards,
> Evanthika Amarasiri
> Senior Technical Lead  - Quality Assurance
> Mobile: +94773125935
> Blog: evanthika.blogspot.com
>
> wso2.com lean.enterprise.middleware
>
> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana  wrote:
>
>> Hi All
>>
>> This is non a bug but please fix the about page if possible because this
>> is a major release. (find the attached image)
>>
>> -Ajith
>>
>>
>>
>>
>>
>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
>> wrote:
>>
>>> Hi All,
>>>
>>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>>
>>> This release fixes the following issues:
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>>> https://wso2.org/jira/browse/REGISTRY-2908
>>>
>>> Please download, test and vote. Please refer the release verification
>>> guide for detailed information on verifying this release.
>>>
>>> *Source & binary distribution files:*
>>>
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>>>
>>> *Maven staging repo:*
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/
>>>
>>> *The tag to be voted upon:*
>>>
>>> https://github.com/wso2/product-greg/tree/v5.0.0-rc2
>>>
>>>
>>>
>>> [*+*] Stable - go ahead and release
>>>
>>> [*-*]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards
>>> G-Reg team
>>>
>>> Prasanna Dangalla
>>> Software Engineer, WSO2, Inc.; http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> cell: +94 718 11 27 51
>>> twitter: @prasa77
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ajith Vitharana.
>>
>> WSO2 Inc. - http://wso2.com
>> Email  : aji...@wso2.com
>> Blog: http://vitharana.org
>> Mobile : +1-812-360-5335
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

2015-09-01 Thread Ajith Vitharana 
Hi All.

I got this error when I click on the "Logging" UI. Seems this pack also not
good candidate to release.

*Caused by: java.lang.NullPointerException*
* at java.lang.String.compareTo(String.java:1139)*
* at
org.wso2.carbon.logging.service.LoggingAdmin$2.compare(LoggingAdmin.java:484)*
* at java.util.TimSort.countRunAndMakeAscending(TimSort.java:324)*
* at java.util.TimSort.sort(TimSort.java:189)*
* at java.util.TimSort.sort(TimSort.java:173)*
* at java.util.Arrays.sort(Arrays.java:659)*
* at
org.wso2.carbon.logging.service.LoggingAdmin.getAllAppenderData(LoggingAdmin.java:479)*
* at
org.wso2.carbon.logging.service.LoggingAdmin.getSystemLog(LoggingAdmin.java:96)*
* ... 66 more*
*TID: [-1234] [] [2015-09-02 00:18:39,184] ERROR
{org.apache.catalina.core.StandardWrapperValve} -  Servlet.service() for
servlet [bridgeservlet] in context with path [/] threw exception [An
exception occurred processing JSP page
/log-admin/globalLogConfig-ajaxprocessor.jsp at line 44*

*41: globalLogData = client.getSysLog();*
*42:  } catch (Exception e) {*
*43: %>*
*44: *
*45: <%*
*46: return;*
*47: }*


*Stacktrace:] with root cause
{org.apache.catalina.core.StandardWrapperValve}*

-Ajith

On Wed, Sep 2, 2015 at 12:12 AM, Ajith Vitharana  wrote:

>
>
> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri 
> wrote:
>
>> Ack!
>>
>> @Chalitha/Thaya/Pubudu. Please note.
>>
>
> And all the context sensitive help pages  are outdated .
>
> -Ajith
>
>
>>
>> Regards,
>> Evanthika Amarasiri
>> Senior Technical Lead  - Quality Assurance
>> Mobile: +94773125935
>> Blog: evanthika.blogspot.com
>>
>> wso2.com lean.enterprise.middleware
>>
>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana  wrote:
>>
>>> Hi All
>>>
>>> This is non a bug but please fix the about page if possible because this
>>> is a major release. (find the attached image)
>>>
>>> -Ajith
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla 
>>> wrote:
>>>
 Hi All,

 *This is the RC 2 release candidate of G-Reg 5.0.0 *

 This release fixes the following issues:

 https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
 https://wso2.org/jira/browse/REGISTRY-2908

 Please download, test and vote. Please refer the release verification
 guide for detailed information on verifying this release.

 *Source & binary distribution files:*


 http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/

 *Maven staging repo:*

 http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/

 *The tag to be voted upon:*

 https://github.com/wso2/product-greg/tree/v5.0.0-rc2



 [*+*] Stable - go ahead and release

 [*-*]  Broken - do not release (explain why)

 Thanks and Regards
 G-Reg team

 Prasanna Dangalla
 Software Engineer, WSO2, Inc.; http://wso2.com/
 lean.enterprise.middleware

 cell: +94 718 11 27 51
 twitter: @prasa77

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


>>>
>>>
>>> --
>>> Ajith Vitharana.
>>>
>>> WSO2 Inc. - http://wso2.com
>>> Email  : aji...@wso2.com
>>> Blog: http://vitharana.org
>>> Mobile : +1-812-360-5335
>>>
>>>
>>
>
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>


-- 
Ajith Vitharana.

WSO2 Inc. - http://wso2.com
Email  : aji...@wso2.com
Blog: http://vitharana.org
Mobile : +1-812-360-5335
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev