Re: [Dev] Please Apply patch to kernel for L1 REGISTRY-1988

[Manoj Kumara]

Hi Senaka, Shelan,

Due to this commit I found that some test cases are failed on*org.wso2.user.core
*. Can you please have a look. Here I attache the test results.


Results :

Tests in error:
  org.wso2.carbon.user.core.claim.AdvancedClaimManagerTest#testClaimManger
Exception

org.wso2.carbon.user.core.claim.ClaimDAOTest#testClaimsAndProfilePersisting
Exception
  org.wso2.carbon.user.core.authman.AdvancedPermissionTreeTest#testStuff
Exception
  org.wso2.carbon.user.core.tenant.TestTenantManager#testTenantManager
Exception

org.wso2.carbon.user.core.hybrid.AdvancedHybridRoleManagerTest#testHybridRoleManager
Exception

org.wso2.carbon.user.core.hybrid.HybridRoleManagerTest#testHybridRoleManager
Exception
  org.wso2.carbon.user.core.jdbc.JDBCRealmTest#testStuff Exception Error
occurre...
  org.wso2.carbon.user.core.jdbc.ReadOnlyJDBCRealmTest#testStuff Exception
Error...
  org.wso2.carbon.user.core.jdbc.PermissionTest#testStuff Exception Error
occurr...
  org.wso2.carbon.user.core.jdbc.AdvancedJDBCRealmTest#testStuff Exception
Error...
  org.wso2.carbon.user.core.jdbc.AdvancedReadOnlyJDBCRealmTest#testStuff
Exception

org.wso2.carbon.user.core.profile.AdvancedProfileConfigManagerTest#testProfileConfigManager
Exception

Tests run: 16, Failures: 0, Errors: 12, Skipped: 0

[INFO]

[INFO] BUILD FAILURE
[INFO]




Thanks,
Manoj



Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Fri, Sep 20, 2013 at 11:21 AM, Shelan Perera  wrote:

> Hi,
>
> Appreciate if you could apply this patch as well.
>
> Thanks
>
>
> On Thu, Sep 19, 2013 at 7:57 PM, Senaka Fernando  wrote:
>
>> Please $subject, as soon as possible, since it is required for further
>> testing. The patch is available @
>> https://wso2.org/jira/browse/REGISTRY-1988.
>>
>> Thanks,
>> Senaka.
>>
>> --
>> * 
>> *
>> *
>> *
>> *Senaka Fernando*
>> Senior Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :   blog.shelan.org
> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API-M 1.4 - Publisher/Sore UI logging is slow

[Kasun Indrasiri]

Hi Sumedha,

As discussed offline, I tried disconnecting from the nw and it seems to
resolve the issue. So, looks like some lookup happening even if we set host
name as localhost.
Will check this on 1.5 build as well.


On Sat, Sep 21, 2013 at 11:37 AM, Kasun Indrasiri  wrote:

>
>
>
> On Sat, Sep 21, 2013 at 10:49 AM, Sumedha Rubasinghe wrote:
>
>> Nope. I assume your using the default pack with H2.
>> Can you try fixing the HostName in carbon.xml to localhost?
>>
>> Yeah, I'm using the default pack with H2. Using HostName doesn't seems to
> improve the loggin time. I will also try with the latest 1.5 packs.
>
>>
>> On Sat, Sep 21, 2013 at 10:39 AM, Kasun Indrasiri  wrote:
>>
>>> I'm experiencing the $subject. This happens with both publisher and
>>> store. Once I've provided the credentials, it takes around 20-30s to direct
>>> to the publisher/store ui.
>>> Is this the normal behavior?
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API-M 1.4 - Publisher/Sore UI logging is slow

[Kasun Indrasiri]

On Sat, Sep 21, 2013 at 10:49 AM, Sumedha Rubasinghe wrote:

> Nope. I assume your using the default pack with H2.
> Can you try fixing the HostName in carbon.xml to localhost?
>
> Yeah, I'm using the default pack with H2. Using HostName doesn't seems to
improve the loggin time. I will also try with the latest 1.5 packs.

>
> On Sat, Sep 21, 2013 at 10:39 AM, Kasun Indrasiri  wrote:
>
>> I'm experiencing the $subject. This happens with both publisher and
>> store. Once I've provided the credentials, it takes around 20-30s to direct
>> to the publisher/store ui.
>> Is this the normal behavior?
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Nightly Build Packs - 21/09/2013

[Sanjeewa Malalgoda]

Please find the latest packs[2] with updated with patch provided by
darshana.

[2]http://builder3.us1.wso2.org/builds/chunk-02/21-sept-2013-v1/

Thanks,
sanjeewa.


On Sat, Sep 21, 2013 at 10:40 AM, Nirmal Fernando  wrote:

> Cool.
>
>
> On Sat, Sep 21, 2013 at 10:39 AM, Sumedha Rubasinghe wrote:
>
>> Nirmal,
>> Sanjeewa is re-building with the patch for
>> https://wso2.org/jira/browse/REGISTRY-1957. We should wait for new packs
>> to come.
>>
>>
>> On Sat, Sep 21, 2013 at 10:22 AM, Nirmal Fernando wrote:
>>
>>> With this ELB pack, https://wso2.org/jira/browse/LB-104 should be
>>> fixed. QA team can you please verify, the normal session affinity stuff
>>> works and also this particular scenario work with the new pack?
>>>
>>> Thanks.
>>>
>>>
>>> On Sat, Sep 21, 2013 at 8:50 AM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 Hi Team,

 Packs from revision 186029 (API Manager, GREG, CEP, ELB) can be
 downloaded from [1].

 [1] : http://builder3.us1.wso2.org/builds/chunk-02/21-sept-2013/



 Thanks and Regards,
 Sanjeewa.
 --
 *
 *
 *Sanjeewa Malalgoda*
 Senior Software Engineer
 WSO2 Inc.
 Mobile : +94713068779

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



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


>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Senior Software Engineer- Platform 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
>>>
>>>
>>
>>
>> --
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>


-- 
*
*
*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

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

Re: [Dev] Code Freeze for Carbon 4.2.0 - chunk 02 release - after 3pm today

[Sumedha Rubasinghe]

Yes. Until release is done. But you should be able to commit.


On Sat, Sep 21, 2013 at 10:58 AM, Sanjeewa Malalgoda wrote:

> Still is this frozen?
>
> Thanks,
> sanjeewa.
>
>
> On Fri, Sep 20, 2013 at 10:51 AM, Dhanushka Ranasinghe <
> dhanush...@wso2.com> wrote:
>
>> Granted
>>
>> Thank You
>> Dhanushka
>>
>>
>> On Fri, Sep 20, 2013 at 9:38 AM, Kasun Indrasiri  wrote:
>>
>>> Also please grant commit rights to following people (We will be only
>>> committing to 2.1.2 synapse only).
>>>
>>> - Vanji, Miyuru, Malaka, IsuruU, Kasun
>>>
>>>
>>> On Wed, Sep 18, 2013 at 3:57 PM, Dhanushka Ranasinghe <
>>> dhanush...@wso2.com> wrote:
>>>
 Done

 Thank You
 Dhanushka


 On Wed, Sep 18, 2013 at 3:47 PM, Kasun Indrasiri wrote:

> Please grant commit rights to Ravi and Dushan from ESB team.
>
>
> On Wed, Sep 18, 2013 at 11:12 AM, Sumedha Rubasinghe  > wrote:
>
>> Devs,
>> Carbon 4.2.0 branch will be frozen for commits after 3pm today in
>> preparation for chunk02 release.
>> It will still remain open for teams who are releasing.
>>
>>
>> --
>> /sumedha
>> b :  bit.ly/sumedha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>



 --
 Dhanushka Ranasinghe,
 WSO2 lnc  http://wso2.com
 E-mail : dhanush...@wso2.com
 Mobile : +94771928269

>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> Dhanushka Ranasinghe,
>> WSO2 lnc  http://wso2.com
>> E-mail : dhanush...@wso2.com
>> Mobile : +94771928269
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *
> *
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Code Freeze for Carbon 4.2.0 - chunk 02 release - after 3pm today

[Sanjeewa Malalgoda]

Still is this frozen?

Thanks,
sanjeewa.


On Fri, Sep 20, 2013 at 10:51 AM, Dhanushka Ranasinghe
wrote:

> Granted
>
> Thank You
> Dhanushka
>
>
> On Fri, Sep 20, 2013 at 9:38 AM, Kasun Indrasiri  wrote:
>
>> Also please grant commit rights to following people (We will be only
>> committing to 2.1.2 synapse only).
>>
>> - Vanji, Miyuru, Malaka, IsuruU, Kasun
>>
>>
>> On Wed, Sep 18, 2013 at 3:57 PM, Dhanushka Ranasinghe <
>> dhanush...@wso2.com> wrote:
>>
>>> Done
>>>
>>> Thank You
>>> Dhanushka
>>>
>>>
>>> On Wed, Sep 18, 2013 at 3:47 PM, Kasun Indrasiri  wrote:
>>>
 Please grant commit rights to Ravi and Dushan from ESB team.


 On Wed, Sep 18, 2013 at 11:12 AM, Sumedha Rubasinghe 
 wrote:

> Devs,
> Carbon 4.2.0 branch will be frozen for commits after 3pm today in
> preparation for chunk02 release.
> It will still remain open for teams who are releasing.
>
>
> --
> /sumedha
> b :  bit.ly/sumedha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 71 536 4128
 Blog : http://kasunpanorama.blogspot.com/

>>>
>>>
>>>
>>> --
>>> Dhanushka Ranasinghe,
>>> WSO2 lnc  http://wso2.com
>>> E-mail : dhanush...@wso2.com
>>> Mobile : +94771928269
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> Dhanushka Ranasinghe,
> WSO2 lnc  http://wso2.com
> E-mail : dhanush...@wso2.com
> Mobile : +94771928269
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*
*
*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

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

Re: [Dev] Please Apply patch to kernel for L1 REGISTRY-1988

[Sanjeewa Malalgoda]

Thanks.


On Sat, Sep 21, 2013 at 10:36 AM, Manoj Kumara  wrote:

> Hi,
>
> Fixed the relative path of javax.cache.wso2. Sorry about the trouble.
>
> Thanks,
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Sat, Sep 21, 2013 at 1:00 AM, Sanjeewa Malalgoda wrote:
>
>> Hi,
>> I can see relative patch issue in kernel patch 001. Please apply this
>> patch.
>>
>> Thanks,
>> sanjeewa.
>>
>>
>> On Fri, Sep 20, 2013 at 4:11 PM, Manoj Kumara  wrote:
>>
>>> Hi,
>>>
>>> Commited under 185980.
>>>
>>> Thanks,
>>>
>>> Best Regards..
>>>
>>>
>>> Manoj Kumara
>>> Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Twitter:  http://twitter.com/ManKuma
>>> Mobile: +94713448188
>>>
>>>
>>> On Fri, Sep 20, 2013 at 3:08 PM, Shelan Perera  wrote:
>>>
 Hi Sameera,

 Just get the confirmation from Senaka that there are only internally
 visible API changes to registry core and no harm for other components.
 Please go ahead and commit.

 Thanks


 On Fri, Sep 20, 2013 at 2:11 PM, Sameera Jayasoma wrote:

> Hi Senaka,
>
> There are some API changes in this patch. I.e. Removal of some public
> methods. Can you please confirm whether there are no effects to other
> components?
>
> Thanks,
> Sameera.
>
>
> On Thu, Sep 19, 2013 at 7:57 PM, Senaka Fernando wrote:
>
>> Please $subject, as soon as possible, since it is required for
>> further testing. The patch is available @
>> https://wso2.org/jira/browse/REGISTRY-1988.
>>
>> Thanks,
>> Senaka.
>>
>> --
>> * 
>> *
>> *
>> *
>> *Senaka Fernando*
>> Senior Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sameera Jayasoma,
> Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
>
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Shelan Perera*

 Senior Software Engineer
 **
 Integration Technology Group
 *WSO2, Inc. : wso2.com*
 lean.enterprise.middleware.

 *Blog* :   blog.shelan.org
 *Linked-i*n  :
 http://www.linkedin.com/pub/shelan-perera/a/194/465
 *Twitter* :https://twitter.com/#!/shelan

 *Mobile*  : +94 772 604 402


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


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *
>> *
>> *Sanjeewa Malalgoda*
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  blog
>> :http://sanjeewamalalgoda.blogspot.com/
>>
>>
>>
>


-- 
*
*
*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

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

Re: [Dev] API-M 1.4 - Publisher/Sore UI logging is slow

[Sumedha Rubasinghe]

Nope. I assume your using the default pack with H2.
Can you try fixing the HostName in carbon.xml to localhost?


On Sat, Sep 21, 2013 at 10:39 AM, Kasun Indrasiri  wrote:

> I'm experiencing the $subject. This happens with both publisher and store.
> Once I've provided the credentials, it takes around 20-30s to direct to the
> publisher/store ui.
> Is this the normal behavior?
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Nightly Build Packs - 21/09/2013

[Nirmal Fernando]

Cool.


On Sat, Sep 21, 2013 at 10:39 AM, Sumedha Rubasinghe wrote:

> Nirmal,
> Sanjeewa is re-building with the patch for
> https://wso2.org/jira/browse/REGISTRY-1957. We should wait for new packs
> to come.
>
>
> On Sat, Sep 21, 2013 at 10:22 AM, Nirmal Fernando  wrote:
>
>> With this ELB pack, https://wso2.org/jira/browse/LB-104 should be fixed.
>> QA team can you please verify, the normal session affinity stuff works and
>> also this particular scenario work with the new pack?
>>
>> Thanks.
>>
>>
>> On Sat, Sep 21, 2013 at 8:50 AM, Sanjeewa Malalgoda wrote:
>>
>>> Hi Team,
>>>
>>> Packs from revision 186029 (API Manager, GREG, CEP, ELB) can be
>>> downloaded from [1].
>>>
>>> [1] : http://builder3.us1.wso2.org/builds/chunk-02/21-sept-2013/
>>>
>>>
>>>
>>> Thanks and Regards,
>>> Sanjeewa.
>>> --
>>> *
>>> *
>>> *Sanjeewa Malalgoda*
>>> Senior Software Engineer
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>>  blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform 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
>>
>>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform 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] Nightly Build Packs - 21/09/2013

[Sumedha Rubasinghe]

Nirmal,
Sanjeewa is re-building with the patch for
https://wso2.org/jira/browse/REGISTRY-1957. We should wait for new packs to
come.


On Sat, Sep 21, 2013 at 10:22 AM, Nirmal Fernando  wrote:

> With this ELB pack, https://wso2.org/jira/browse/LB-104 should be fixed.
> QA team can you please verify, the normal session affinity stuff works and
> also this particular scenario work with the new pack?
>
> Thanks.
>
>
> On Sat, Sep 21, 2013 at 8:50 AM, Sanjeewa Malalgoda wrote:
>
>> Hi Team,
>>
>> Packs from revision 186029 (API Manager, GREG, CEP, ELB) can be
>> downloaded from [1].
>>
>> [1] : http://builder3.us1.wso2.org/builds/chunk-02/21-sept-2013/
>>
>>
>>
>> Thanks and Regards,
>> Sanjeewa.
>> --
>> *
>> *
>> *Sanjeewa Malalgoda*
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  blog
>> :http://sanjeewamalalgoda.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform 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
>
>


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

[Dev] API-M 1.4 - Publisher/Sore UI logging is slow

[Kasun Indrasiri]

I'm experiencing the $subject. This happens with both publisher and store.
Once I've provided the credentials, it takes around 20-30s to direct to the
publisher/store ui.
Is this the normal behavior?

-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please Apply patch to kernel for L1 REGISTRY-1988

[Manoj Kumara]

Hi,

Fixed the relative path of javax.cache.wso2. Sorry about the trouble.

Thanks,

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Sat, Sep 21, 2013 at 1:00 AM, Sanjeewa Malalgoda wrote:

> Hi,
> I can see relative patch issue in kernel patch 001. Please apply this
> patch.
>
> Thanks,
> sanjeewa.
>
>
> On Fri, Sep 20, 2013 at 4:11 PM, Manoj Kumara  wrote:
>
>> Hi,
>>
>> Commited under 185980.
>>
>> Thanks,
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Fri, Sep 20, 2013 at 3:08 PM, Shelan Perera  wrote:
>>
>>> Hi Sameera,
>>>
>>> Just get the confirmation from Senaka that there are only internally
>>> visible API changes to registry core and no harm for other components.
>>> Please go ahead and commit.
>>>
>>> Thanks
>>>
>>>
>>> On Fri, Sep 20, 2013 at 2:11 PM, Sameera Jayasoma wrote:
>>>
 Hi Senaka,

 There are some API changes in this patch. I.e. Removal of some public
 methods. Can you please confirm whether there are no effects to other
 components?

 Thanks,
 Sameera.


 On Thu, Sep 19, 2013 at 7:57 PM, Senaka Fernando wrote:

> Please $subject, as soon as possible, since it is required for further
> testing. The patch is available @
> https://wso2.org/jira/browse/REGISTRY-1988.
>
> Thanks,
> Senaka.
>
> --
> * 
> *
> *
> *
> *Senaka Fernando*
> Senior Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Sameera Jayasoma,
 Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://sameera.adahas.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 0094776364456


 Lean . Enterprise . Middleware

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


>>>
>>>
>>> --
>>> *Shelan Perera*
>>>
>>> Senior Software Engineer
>>> **
>>> Integration Technology Group
>>> *WSO2, Inc. : wso2.com*
>>> lean.enterprise.middleware.
>>>
>>> *Blog* :   blog.shelan.org
>>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>>> *Twitter* :https://twitter.com/#!/shelan
>>>
>>> *Mobile*  : +94 772 604 402
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *
> *
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Nightly Build Packs - 21/09/2013

[Nirmal Fernando]

With this ELB pack, https://wso2.org/jira/browse/LB-104 should be fixed. QA
team can you please verify, the normal session affinity stuff works and
also this particular scenario work with the new pack?

Thanks.


On Sat, Sep 21, 2013 at 8:50 AM, Sanjeewa Malalgoda wrote:

> Hi Team,
>
> Packs from revision 186029 (API Manager, GREG, CEP, ELB) can be downloaded
> from [1].
>
> [1] : http://builder3.us1.wso2.org/builds/chunk-02/21-sept-2013/
>
>
>
> Thanks and Regards,
> Sanjeewa.
> --
> *
> *
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform 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

[Dev] Nightly Build Packs - 21/09/2013

[Sanjeewa Malalgoda]

Hi Team,

Packs from revision 186029 (API Manager, GREG, CEP, ELB) can be downloaded
from [1].

[1] : http://builder3.us1.wso2.org/builds/chunk-02/21-sept-2013/



Thanks and Regards,
Sanjeewa.
-- 
*
*
*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

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

[Dev] Is it possible to upgrade JUST the tomcat embedded in WSO2 ESB 4.0.3?

[Abhijit Diwan]

Hi Dev WSO2

I have another question here,

WSO2 ESB 4.0.3 runs on top of Apache Tomcat/7.0.14. This version of tomcat has 
found many security vulnarabilties ( http://tomcat.apache.org/security-7.html)

I am trying to see if we can upgrade the tomcat version in WSO2 ESB 4.0.3 to 
latest in 7.* version?

If yes how can I cleanly do that?

It is big company and they would love to have secure WSO2 ESB 4.0.3 
implementation with Data Services they love.

thanks again for help.



 Abhijit


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

Re: [Dev] Please Apply patch to kernel for L1 REGISTRY-1988

[Sanjeewa Malalgoda]

Hi,
I can see relative patch issue in kernel patch 001. Please apply this patch.

Thanks,
sanjeewa.


On Fri, Sep 20, 2013 at 4:11 PM, Manoj Kumara  wrote:

> Hi,
>
> Commited under 185980.
>
> Thanks,
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Fri, Sep 20, 2013 at 3:08 PM, Shelan Perera  wrote:
>
>> Hi Sameera,
>>
>> Just get the confirmation from Senaka that there are only internally
>> visible API changes to registry core and no harm for other components.
>> Please go ahead and commit.
>>
>> Thanks
>>
>>
>> On Fri, Sep 20, 2013 at 2:11 PM, Sameera Jayasoma wrote:
>>
>>> Hi Senaka,
>>>
>>> There are some API changes in this patch. I.e. Removal of some public
>>> methods. Can you please confirm whether there are no effects to other
>>> components?
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>> On Thu, Sep 19, 2013 at 7:57 PM, Senaka Fernando wrote:
>>>
 Please $subject, as soon as possible, since it is required for further
 testing. The patch is available @
 https://wso2.org/jira/browse/REGISTRY-1988.

 Thanks,
 Senaka.

 --
 * 
 *
 *
 *
 *Senaka Fernando*
 Senior Technical Lead; WSO2 Inc.; http://wso2.com*
 Member; Apache Software Foundation; http://apache.org

 E-mail: senaka AT wso2.com
 **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
 Linked-In: http://linkedin.com/in/senakafernando

 *Lean . Enterprise . Middleware

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


>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Shelan Perera*
>>
>> Senior Software Engineer
>> **
>> Integration Technology Group
>> *WSO2, Inc. : wso2.com*
>> lean.enterprise.middleware.
>>
>> *Blog* :   blog.shelan.org
>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>> *Twitter* :https://twitter.com/#!/shelan
>>
>> *Mobile*  : +94 772 604 402
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*
*
*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

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


kernalpach.diff
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Error at application creation

[Dimuthu Leelarathne]

Hi,

I will look into this ...

thanks,
dimuthu



On Fri, Sep 20, 2013 at 9:43 PM, Danushka Fernando wrote:

> Hi all
> I am getting following exception at app creation. After lot of debugging I
> found that its from the Jenkins listner for app creation event.
> The user in the carbon context is admin and tenant domain is passed there.
> So there the code is building the user name by cancatinating them. Which
> makes ad...@dan001.com
>
> String tenantUserName = CarbonContext.getCurrentContext().getUsername() +
> "@" + tenantDomain;
>
> Please look in to this.
>
> And the log *'ad...@dan001.com [1]' logged in *is looks wrong. (since
> there are no users in my domain named admin).
>
> [2013-09-20 21:26:34,010]  INFO
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - * '
> ad...@dan001.com [1]' logged in* at [2013-09-20 21:26:34,010+0530]
> [2013-09-20 21:26:34,016]  WARN
> {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
>  Illegal access attempt at [2013-09-20 21:26:34,0016] from IP address
> 127.0.0.1 : Service is ApplicationDeployer
> [2013-09-20 21:26:34,017] ERROR {org.apache.axis2.engine.AxisEngine} -
>  Access Denied. Please login first.
> org.apache.axis2.AxisFault: Access Denied. Please login first.
> at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:97)
>  at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:66)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>  at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>  at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>  at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
>  at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>  at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>  at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
> at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
>  at
> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>  at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>  at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe

[Dev] [AF] Error at application creation

[Danushka Fernando]

Hi all
I am getting following exception at app creation. After lot of debugging I
found that its from the Jenkins listner for app creation event.
The user in the carbon context is admin and tenant domain is passed there.
So there the code is building the user name by cancatinating them. Which
makes ad...@dan001.com

String tenantUserName = CarbonContext.getCurrentContext().getUsername() +
"@" + tenantDomain;

Please look in to this.

And the log *'ad...@dan001.com [1]' logged in *is looks wrong. (since there
are no users in my domain named admin).

[2013-09-20 21:26:34,010]  INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - * '
ad...@dan001.com [1]' logged in* at [2013-09-20 21:26:34,010+0530]
[2013-09-20 21:26:34,016]  WARN
{org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
 Illegal access attempt at [2013-09-20 21:26:34,0016] from IP address
127.0.0.1 : Service is ApplicationDeployer
[2013-09-20 21:26:34,017] ERROR {org.apache.axis2.engine.AxisEngine} -
 Access Denied. Please login first.
org.apache.axis2.AxisFault: Access Denied. Please login first.
at
org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:97)
at
org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:66)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)


Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [API-Manager] Publisher login page does not have front end validation

[Amila Maha Arachchi]

Hi AM team,

When I go to the publisher login page, set the cursor in the username filed
and hit enter, it submits the data and tries to log me in.

User creds should be submitted only if we hit the enter button when we are
in the password box and then also, there should be some input validation.

Its better if you can fix this before the release. If this is already
fixed, then please ignore this.

Regards,
AmilaM.

-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please apply the patch IDENTITY-1847

[Manoj Kumara]

Hi,

committed under 185980.

Thanks,

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Fri, Sep 20, 2013 at 1:01 PM, Manoj Kumara  wrote:

> Hi,
>
> Noted.
>
> Thanks,
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Fri, Sep 20, 2013 at 1:00 PM, Nuwan Dias  wrote:
>
>> Adding Manoj
>>
>>
>> On Fri, Sep 20, 2013 at 12:49 PM, Venura Kahawala wrote:
>>
>>> Hi,
>>>
>>> Please commit the patch attached to jira 
>>> IDENTITY-1847
>>> .
>>>
>>> Regards,
>>> Venura
>>>
>>> --
>>> Senior Software Engineer
>>>
>>> Mobile: +94 71 82 300 20
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Senior Software Engineer - 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] Please Apply patch to kernel for L1 REGISTRY-1988

[Manoj Kumara]

Hi,

Commited under 185980.

Thanks,

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Fri, Sep 20, 2013 at 3:08 PM, Shelan Perera  wrote:

> Hi Sameera,
>
> Just get the confirmation from Senaka that there are only internally
> visible API changes to registry core and no harm for other components.
> Please go ahead and commit.
>
> Thanks
>
>
> On Fri, Sep 20, 2013 at 2:11 PM, Sameera Jayasoma wrote:
>
>> Hi Senaka,
>>
>> There are some API changes in this patch. I.e. Removal of some public
>> methods. Can you please confirm whether there are no effects to other
>> components?
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Thu, Sep 19, 2013 at 7:57 PM, Senaka Fernando  wrote:
>>
>>> Please $subject, as soon as possible, since it is required for further
>>> testing. The patch is available @
>>> https://wso2.org/jira/browse/REGISTRY-1988.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> --
>>> * 
>>> *
>>> *
>>> *
>>> *Senaka Fernando*
>>> Senior Technical Lead; WSO2 Inc.; http://wso2.com*
>>> Member; Apache Software Foundation; http://apache.org
>>>
>>> E-mail: senaka AT wso2.com
>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>> Linked-In: http://linkedin.com/in/senakafernando
>>>
>>> *Lean . Enterprise . Middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>>
>> Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :   blog.shelan.org
> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Provide an existing GIT url in AppFactory

[Asanka Dissanayake]

Since appfactory maintains it's own Git repository user can't bring his own
one to the party :). If he wants to use appfactory, or continue his
application development with appfactory, he can simply check-in his halfway
developed code to the GIT provided by the appfactory and continue.

we use a plugin in the git server which handles the authorization and
stuffs. So obviously we can't use GitHub.



On Fri, Sep 20, 2013 at 3:19 PM, Udara Liyanage  wrote:

> Thanks for the response.
> Is n't it a valid scenario? Lets say a user has a app with a GIT url (or
> in GIT Hub) which he wants to develop and deploy with AppFac.
>
>
> On Fri, Sep 20, 2013 at 2:39 PM, Gayan Dhanushka  wrote:
>
>> Hi Udara,
>>
>> I'm afraid it is not. We are given a git repo when we are creating the
>> application. It is a git repo created for your application. We can't give
>> an existing git url during the application creation.
>>
>> Thanks.
>> Gayan
>>
>> Gayan Dhanuska
>> Software Engineer
>> http://wso2.com/
>> Lean Enterprise Middleware
>>
>> Mobile
>> 071 666 2327
>>
>> Office
>> Tel   : 94 11 214 5345
>> Fax  : 94 11 214 5300
>>
>> Twitter : https://twitter.com/gayanlggd
>>
>>
>> On Fri, Sep 20, 2013 at 2:28 PM, Udara Liyanage  wrote:
>>
>>>  Hi,
>>>
>>> When creating an app in AppFactory we are provided a GIT url where we
>>> can develop our applications. Is there any way we can give our existing GIT
>>> url when creating a application?
>>>
>>> --
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: asan...@wso2.com ,   blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
8373821*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OAuth2 - Having the TIME_CREATED column as a TIMESTAMP type

[Nuwan Dias]

Thanks Sumedha, that worked.

IS guys, please note to update your db scripts accordingly.

Thanks,
NuwanD.


On Fri, Sep 20, 2013 at 3:39 PM, Sumedha Rubasinghe wrote:

> MySQL by default updates this. (see
> http://dev.mysql.com/doc/refman/5.0/en/timestamp-initialization.html)
> You need to explicitly turn this off by
>
> TIME_CREATED TIMESTAMP DEFAULT 0,
>
>
>
>
> On Fri, Sep 20, 2013 at 3:34 PM, Prabath Siriwardena wrote:
>
>> Can you please change the script to following and see..
>>
>> TIME_CREATED TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
>>
>> Thanks & regards,
>> -Prabath
>>
>> On Fri, Sep 20, 2013 at 3:27 PM, Nuwan Dias  wrote:
>> > No. Just TIMESTAMP. We thought of manually setting the created time to
>> what
>> > it originally was. Since changing the column type requires some effort
>> which
>> > will include a need of migrating older version users as well.
>> >
>> > Thanks,
>> > NuwanD.
>> >
>> >
>> > On Fri, Sep 20, 2013 at 3:19 PM, Prabath Siriwardena 
>> > wrote:
>> >>
>> >> Do you have "ON UPDATE CURRENT_TIMESTAMP"  against the TIME_CREATED
>> column
>> >> ?
>> >>
>> >> Thanks & regards,
>> >> -Prabath
>> >>
>> >> On Fri, Sep 20, 2013 at 2:26 PM, Nuwan Dias  wrote:
>> >> > We can, but this would mean that we need to change the code and set
>> the
>> >> > time
>> >> > in all places that do an INSERT to this table.
>> >> >
>> >> > Thanks,
>> >> > NuwanD.
>> >> >
>> >> >
>> >> > On Fri, Sep 20, 2013 at 2:22 PM, Prabath Siriwardena <
>> prab...@wso2.com>
>> >> > wrote:
>> >> >>
>> >> >> It's not rights to update the TIME_CREATED every time we update the
>> >> >> record.
>> >> >>
>> >> >> Can we update it to DATETIME?
>> >> >>
>> >> >> Thanks & regards,
>> >> >> -Prabath
>> >> >>
>> >> >>
>> >> >> On Fri, Sep 20, 2013 at 2:12 PM, Nuwan Dias 
>> wrote:
>> >> >>>
>> >> >>> Hi,
>> >> >>>
>> >> >>> This is regarding the issue [1]. When an OAuth2 token is initially
>> >> >>> created, it is created in the 'Active' state. When revoking a
>> token,
>> >> >>> its
>> >> >>> state is changed to 'REVOKED'. But this time, the TIME_CREATED
>> value
>> >> >>> of that
>> >> >>> particular database entry is also updated.
>> >> >>>
>> >> >>> When looking at the issue, I found that the TIME_CREATED column
>> has a
>> >> >>> TIMESTAMP type. According to [2], in MySQL databases this means
>> that
>> >> >>> the
>> >> >>> TIME_CREATED column is always updated whenever that row is updated.
>> >> >>> Hence
>> >> >>> the cause for the issue [1]. Is it right to have this column type
>> as
>> >> >>> TIMESTAMP?
>> >> >>>
>> >> >>> [1] - https://wso2.org/jira/browse/APIMANAGER-1696
>> >> >>> [2] -
>> http://stackoverflow.com/questions/409286/datetime-vs-timestamp
>> >> >>>
>> >> >>> Thanks,
>> >> >>> NuwanD.
>> >> >>>
>> >> >>> --
>> >> >>> Nuwan Dias
>> >> >>>
>> >> >>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>> >> >>> email : nuw...@wso2.com
>> >> >>> Phone : +94 777 775 729
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Thanks & Regards,
>> >> >> Prabath
>> >> >>
>> >> >> Mobile : +94 71 809 6732
>> >> >>
>> >> >> http://blog.facilelogin.com
>> >> >> http://RampartFAQ.com
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Nuwan Dias
>> >> >
>> >> > Senior Software Engineer - WSO2, Inc. http://wso2.com
>> >> > email : nuw...@wso2.com
>> >> > Phone : +94 777 775 729
>> >>
>> >>
>> >>
>> >> --
>> >> Thanks & Regards,
>> >> Prabath
>> >>
>> >> Mobile : +94 71 809 6732
>> >>
>> >> http://blog.facilelogin.com
>> >> http://RampartFAQ.com
>> >
>> >
>> >
>> >
>> > --
>> > Nuwan Dias
>> >
>> > Senior Software Engineer - WSO2, Inc. http://wso2.com
>> > email : nuw...@wso2.com
>> > Phone : +94 777 775 729
>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Mobile : +94 71 809 6732
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



-- 
Nuwan Dias

Senior Software Engineer - 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] OAuth2 - Having the TIME_CREATED column as a TIMESTAMP type

[Sumedha Rubasinghe]

MySQL by default updates this. (see
http://dev.mysql.com/doc/refman/5.0/en/timestamp-initialization.html)
You need to explicitly turn this off by

TIME_CREATED TIMESTAMP DEFAULT 0,




On Fri, Sep 20, 2013 at 3:34 PM, Prabath Siriwardena wrote:

> Can you please change the script to following and see..
>
> TIME_CREATED TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
>
> Thanks & regards,
> -Prabath
>
> On Fri, Sep 20, 2013 at 3:27 PM, Nuwan Dias  wrote:
> > No. Just TIMESTAMP. We thought of manually setting the created time to
> what
> > it originally was. Since changing the column type requires some effort
> which
> > will include a need of migrating older version users as well.
> >
> > Thanks,
> > NuwanD.
> >
> >
> > On Fri, Sep 20, 2013 at 3:19 PM, Prabath Siriwardena 
> > wrote:
> >>
> >> Do you have "ON UPDATE CURRENT_TIMESTAMP"  against the TIME_CREATED
> column
> >> ?
> >>
> >> Thanks & regards,
> >> -Prabath
> >>
> >> On Fri, Sep 20, 2013 at 2:26 PM, Nuwan Dias  wrote:
> >> > We can, but this would mean that we need to change the code and set
> the
> >> > time
> >> > in all places that do an INSERT to this table.
> >> >
> >> > Thanks,
> >> > NuwanD.
> >> >
> >> >
> >> > On Fri, Sep 20, 2013 at 2:22 PM, Prabath Siriwardena <
> prab...@wso2.com>
> >> > wrote:
> >> >>
> >> >> It's not rights to update the TIME_CREATED every time we update the
> >> >> record.
> >> >>
> >> >> Can we update it to DATETIME?
> >> >>
> >> >> Thanks & regards,
> >> >> -Prabath
> >> >>
> >> >>
> >> >> On Fri, Sep 20, 2013 at 2:12 PM, Nuwan Dias  wrote:
> >> >>>
> >> >>> Hi,
> >> >>>
> >> >>> This is regarding the issue [1]. When an OAuth2 token is initially
> >> >>> created, it is created in the 'Active' state. When revoking a token,
> >> >>> its
> >> >>> state is changed to 'REVOKED'. But this time, the TIME_CREATED value
> >> >>> of that
> >> >>> particular database entry is also updated.
> >> >>>
> >> >>> When looking at the issue, I found that the TIME_CREATED column has
> a
> >> >>> TIMESTAMP type. According to [2], in MySQL databases this means that
> >> >>> the
> >> >>> TIME_CREATED column is always updated whenever that row is updated.
> >> >>> Hence
> >> >>> the cause for the issue [1]. Is it right to have this column type as
> >> >>> TIMESTAMP?
> >> >>>
> >> >>> [1] - https://wso2.org/jira/browse/APIMANAGER-1696
> >> >>> [2] -
> http://stackoverflow.com/questions/409286/datetime-vs-timestamp
> >> >>>
> >> >>> Thanks,
> >> >>> NuwanD.
> >> >>>
> >> >>> --
> >> >>> Nuwan Dias
> >> >>>
> >> >>> Senior Software Engineer - WSO2, Inc. http://wso2.com
> >> >>> email : nuw...@wso2.com
> >> >>> Phone : +94 777 775 729
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Thanks & Regards,
> >> >> Prabath
> >> >>
> >> >> Mobile : +94 71 809 6732
> >> >>
> >> >> http://blog.facilelogin.com
> >> >> http://RampartFAQ.com
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Nuwan Dias
> >> >
> >> > Senior Software Engineer - WSO2, Inc. http://wso2.com
> >> > email : nuw...@wso2.com
> >> > Phone : +94 777 775 729
> >>
> >>
> >>
> >> --
> >> Thanks & Regards,
> >> Prabath
> >>
> >> Mobile : +94 71 809 6732
> >>
> >> http://blog.facilelogin.com
> >> http://RampartFAQ.com
> >
> >
> >
> >
> > --
> > Nuwan Dias
> >
> > Senior Software Engineer - WSO2, Inc. http://wso2.com
> > email : nuw...@wso2.com
> > Phone : +94 777 775 729
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



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

Re: [Dev] OAuth2 - Having the TIME_CREATED column as a TIMESTAMP type

[Prabath Siriwardena]

Can you please change the script to following and see..

TIME_CREATED TIMESTAMP DEFAULT CURRENT_TIMESTAMP,

Thanks & regards,
-Prabath

On Fri, Sep 20, 2013 at 3:27 PM, Nuwan Dias  wrote:
> No. Just TIMESTAMP. We thought of manually setting the created time to what
> it originally was. Since changing the column type requires some effort which
> will include a need of migrating older version users as well.
>
> Thanks,
> NuwanD.
>
>
> On Fri, Sep 20, 2013 at 3:19 PM, Prabath Siriwardena 
> wrote:
>>
>> Do you have "ON UPDATE CURRENT_TIMESTAMP"  against the TIME_CREATED column
>> ?
>>
>> Thanks & regards,
>> -Prabath
>>
>> On Fri, Sep 20, 2013 at 2:26 PM, Nuwan Dias  wrote:
>> > We can, but this would mean that we need to change the code and set the
>> > time
>> > in all places that do an INSERT to this table.
>> >
>> > Thanks,
>> > NuwanD.
>> >
>> >
>> > On Fri, Sep 20, 2013 at 2:22 PM, Prabath Siriwardena 
>> > wrote:
>> >>
>> >> It's not rights to update the TIME_CREATED every time we update the
>> >> record.
>> >>
>> >> Can we update it to DATETIME?
>> >>
>> >> Thanks & regards,
>> >> -Prabath
>> >>
>> >>
>> >> On Fri, Sep 20, 2013 at 2:12 PM, Nuwan Dias  wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> This is regarding the issue [1]. When an OAuth2 token is initially
>> >>> created, it is created in the 'Active' state. When revoking a token,
>> >>> its
>> >>> state is changed to 'REVOKED'. But this time, the TIME_CREATED value
>> >>> of that
>> >>> particular database entry is also updated.
>> >>>
>> >>> When looking at the issue, I found that the TIME_CREATED column has a
>> >>> TIMESTAMP type. According to [2], in MySQL databases this means that
>> >>> the
>> >>> TIME_CREATED column is always updated whenever that row is updated.
>> >>> Hence
>> >>> the cause for the issue [1]. Is it right to have this column type as
>> >>> TIMESTAMP?
>> >>>
>> >>> [1] - https://wso2.org/jira/browse/APIMANAGER-1696
>> >>> [2] - http://stackoverflow.com/questions/409286/datetime-vs-timestamp
>> >>>
>> >>> Thanks,
>> >>> NuwanD.
>> >>>
>> >>> --
>> >>> Nuwan Dias
>> >>>
>> >>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>> >>> email : nuw...@wso2.com
>> >>> Phone : +94 777 775 729
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Thanks & Regards,
>> >> Prabath
>> >>
>> >> Mobile : +94 71 809 6732
>> >>
>> >> http://blog.facilelogin.com
>> >> http://RampartFAQ.com
>> >
>> >
>> >
>> >
>> > --
>> > Nuwan Dias
>> >
>> > Senior Software Engineer - WSO2, Inc. http://wso2.com
>> > email : nuw...@wso2.com
>> > Phone : +94 777 775 729
>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Mobile : +94 71 809 6732
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>
>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729



-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

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

Re: [Dev] Please apply the patch REGISTRY-1851

[Shelan Perera]

Thanks.


On Fri, Sep 20, 2013 at 3:23 PM, Manoj Kumara  wrote:

> Hi,
>
> Committed
>
> Thanks,
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Fri, Sep 20, 2013 at 10:50 AM, Manoj Kumara  wrote:
>
>> Hi,
>>
>> Noted.
>>
>> Thanks,
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Fri, Sep 20, 2013 at 10:36 AM, Sameera Jayasoma wrote:
>>
>>> Hi Manoj,
>>>
>>> Can you apply this patch?
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>> On Fri, Sep 20, 2013 at 10:30 AM, Shelan Perera  wrote:
>>>
 $Subject please.

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

 This patch was reviewed by Azeez too.

 Thanks
 --
 *Shelan Perera*

 Senior Software Engineer
 **
 Integration Technology Group
 *WSO2, Inc. : wso2.com*
 lean.enterprise.middleware.

 *Blog* :   blog.shelan.org
 *Linked-i*n  :
 http://www.linkedin.com/pub/shelan-perera/a/194/465
 *Twitter* :https://twitter.com/#!/shelan

 *Mobile*  : +94 772 604 402


>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>


-- 
*Shelan Perera*

Senior Software Engineer
**
Integration Technology Group
*WSO2, Inc. : wso2.com*
lean.enterprise.middleware.

*Blog* :   blog.shelan.org
*Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
*Twitter* :https://twitter.com/#!/shelan

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

Re: [Dev] OAuth2 - Having the TIME_CREATED column as a TIMESTAMP type

[Nuwan Dias]

No. Just TIMESTAMP. We thought of manually setting the created time to what
it originally was. Since changing the column type requires some effort
which will include a need of migrating older version users as well.

Thanks,
NuwanD.


On Fri, Sep 20, 2013 at 3:19 PM, Prabath Siriwardena wrote:

> Do you have "ON UPDATE CURRENT_TIMESTAMP"  against the TIME_CREATED column
> ?
>
> Thanks & regards,
> -Prabath
>
> On Fri, Sep 20, 2013 at 2:26 PM, Nuwan Dias  wrote:
> > We can, but this would mean that we need to change the code and set the
> time
> > in all places that do an INSERT to this table.
> >
> > Thanks,
> > NuwanD.
> >
> >
> > On Fri, Sep 20, 2013 at 2:22 PM, Prabath Siriwardena 
> > wrote:
> >>
> >> It's not rights to update the TIME_CREATED every time we update the
> >> record.
> >>
> >> Can we update it to DATETIME?
> >>
> >> Thanks & regards,
> >> -Prabath
> >>
> >>
> >> On Fri, Sep 20, 2013 at 2:12 PM, Nuwan Dias  wrote:
> >>>
> >>> Hi,
> >>>
> >>> This is regarding the issue [1]. When an OAuth2 token is initially
> >>> created, it is created in the 'Active' state. When revoking a token,
> its
> >>> state is changed to 'REVOKED'. But this time, the TIME_CREATED value
> of that
> >>> particular database entry is also updated.
> >>>
> >>> When looking at the issue, I found that the TIME_CREATED column has a
> >>> TIMESTAMP type. According to [2], in MySQL databases this means that
> the
> >>> TIME_CREATED column is always updated whenever that row is updated.
> Hence
> >>> the cause for the issue [1]. Is it right to have this column type as
> >>> TIMESTAMP?
> >>>
> >>> [1] - https://wso2.org/jira/browse/APIMANAGER-1696
> >>> [2] - http://stackoverflow.com/questions/409286/datetime-vs-timestamp
> >>>
> >>> Thanks,
> >>> NuwanD.
> >>>
> >>> --
> >>> Nuwan Dias
> >>>
> >>> Senior Software Engineer - WSO2, Inc. http://wso2.com
> >>> email : nuw...@wso2.com
> >>> Phone : +94 777 775 729
> >>
> >>
> >>
> >>
> >> --
> >> Thanks & Regards,
> >> Prabath
> >>
> >> Mobile : +94 71 809 6732
> >>
> >> http://blog.facilelogin.com
> >> http://RampartFAQ.com
> >
> >
> >
> >
> > --
> > Nuwan Dias
> >
> > Senior Software Engineer - WSO2, Inc. http://wso2.com
> > email : nuw...@wso2.com
> > Phone : +94 777 775 729
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>



-- 
Nuwan Dias

Senior Software Engineer - 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] Please apply the patch REGISTRY-1851

[Manoj Kumara]

Hi,

Committed

Thanks,

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Fri, Sep 20, 2013 at 10:50 AM, Manoj Kumara  wrote:

> Hi,
>
> Noted.
>
> Thanks,
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Fri, Sep 20, 2013 at 10:36 AM, Sameera Jayasoma wrote:
>
>> Hi Manoj,
>>
>> Can you apply this patch?
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Fri, Sep 20, 2013 at 10:30 AM, Shelan Perera  wrote:
>>
>>> $Subject please.
>>>
>>> https://wso2.org/jira/browse/REGISTRY-1851
>>>
>>> This patch was reviewed by Azeez too.
>>>
>>> Thanks
>>> --
>>> *Shelan Perera*
>>>
>>> Senior Software Engineer
>>> **
>>> Integration Technology Group
>>> *WSO2, Inc. : wso2.com*
>>> lean.enterprise.middleware.
>>>
>>> *Blog* :   blog.shelan.org
>>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>>> *Twitter* :https://twitter.com/#!/shelan
>>>
>>> *Mobile*  : +94 772 604 402
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>> Lean . Enterprise . Middleware
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Provide an existing GIT url in AppFactory

[Udara Liyanage]

Thanks for the response.
Is n't it a valid scenario? Lets say a user has a app with a GIT url (or in
GIT Hub) which he wants to develop and deploy with AppFac.


On Fri, Sep 20, 2013 at 2:39 PM, Gayan Dhanushka  wrote:

> Hi Udara,
>
> I'm afraid it is not. We are given a git repo when we are creating the
> application. It is a git repo created for your application. We can't give
> an existing git url during the application creation.
>
> Thanks.
> Gayan
>
> Gayan Dhanuska
> Software Engineer
> http://wso2.com/
> Lean Enterprise Middleware
>
> Mobile
> 071 666 2327
>
> Office
> Tel   : 94 11 214 5345
> Fax  : 94 11 214 5300
>
> Twitter : https://twitter.com/gayanlggd
>
>
> On Fri, Sep 20, 2013 at 2:28 PM, Udara Liyanage  wrote:
>
>>  Hi,
>>
>> When creating an app in AppFactory we are provided a GIT url where we can
>> develop our applications. Is there any way we can give our existing GIT url
>> when creating a application?
>>
>> --
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OAuth2 - Having the TIME_CREATED column as a TIMESTAMP type

[Prabath Siriwardena]

Do you have "ON UPDATE CURRENT_TIMESTAMP"  against the TIME_CREATED column ?

Thanks & regards,
-Prabath

On Fri, Sep 20, 2013 at 2:26 PM, Nuwan Dias  wrote:
> We can, but this would mean that we need to change the code and set the time
> in all places that do an INSERT to this table.
>
> Thanks,
> NuwanD.
>
>
> On Fri, Sep 20, 2013 at 2:22 PM, Prabath Siriwardena 
> wrote:
>>
>> It's not rights to update the TIME_CREATED every time we update the
>> record.
>>
>> Can we update it to DATETIME?
>>
>> Thanks & regards,
>> -Prabath
>>
>>
>> On Fri, Sep 20, 2013 at 2:12 PM, Nuwan Dias  wrote:
>>>
>>> Hi,
>>>
>>> This is regarding the issue [1]. When an OAuth2 token is initially
>>> created, it is created in the 'Active' state. When revoking a token, its
>>> state is changed to 'REVOKED'. But this time, the TIME_CREATED value of that
>>> particular database entry is also updated.
>>>
>>> When looking at the issue, I found that the TIME_CREATED column has a
>>> TIMESTAMP type. According to [2], in MySQL databases this means that the
>>> TIME_CREATED column is always updated whenever that row is updated. Hence
>>> the cause for the issue [1]. Is it right to have this column type as
>>> TIMESTAMP?
>>>
>>> [1] - https://wso2.org/jira/browse/APIMANAGER-1696
>>> [2] - http://stackoverflow.com/questions/409286/datetime-vs-timestamp
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Mobile : +94 71 809 6732
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>
>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729



-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

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

[Dev] Registry L1/L2 Status

[Shelan Perera]

Hi,

L1 (2)
---
REGISTRY-1988  [Fixed to be
committed by Kernel Team]
REGISTRY-1957  [Darshana is
looking into this ]

L2 (0)


Thanks

-- 
*Shelan Perera*

Senior Software Engineer
**
Integration Technology Group
*WSO2, Inc. : wso2.com*
lean.enterprise.middleware.

*Blog* :   blog.shelan.org
*Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
*Twitter* :https://twitter.com/#!/shelan

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

Re: [Dev] Please Apply patch to kernel for L1 REGISTRY-1988

[Shelan Perera]

Hi Sameera,

Just get the confirmation from Senaka that there are only internally
visible API changes to registry core and no harm for other components.
Please go ahead and commit.

Thanks


On Fri, Sep 20, 2013 at 2:11 PM, Sameera Jayasoma  wrote:

> Hi Senaka,
>
> There are some API changes in this patch. I.e. Removal of some public
> methods. Can you please confirm whether there are no effects to other
> components?
>
> Thanks,
> Sameera.
>
>
> On Thu, Sep 19, 2013 at 7:57 PM, Senaka Fernando  wrote:
>
>> Please $subject, as soon as possible, since it is required for further
>> testing. The patch is available @
>> https://wso2.org/jira/browse/REGISTRY-1988.
>>
>> Thanks,
>> Senaka.
>>
>> --
>> * 
>> *
>> *
>> *
>> *Senaka Fernando*
>> Senior Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sameera Jayasoma,
> Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
>
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Shelan Perera*

Senior Software Engineer
**
Integration Technology Group
*WSO2, Inc. : wso2.com*
lean.enterprise.middleware.

*Blog* :   blog.shelan.org
*Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
*Twitter* :https://twitter.com/#!/shelan

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

Re: [Dev] Provide an existing GIT url in AppFactory

[Gayan Dhanushka]

Hi Udara,

I'm afraid it is not. We are given a git repo when we are creating the
application. It is a git repo created for your application. We can't give
an existing git url during the application creation.

Thanks.
Gayan

Gayan Dhanuska
Software Engineer
http://wso2.com/
Lean Enterprise Middleware

Mobile
071 666 2327

Office
Tel   : 94 11 214 5345
Fax  : 94 11 214 5300

Twitter : https://twitter.com/gayanlggd


On Fri, Sep 20, 2013 at 2:28 PM, Udara Liyanage  wrote:

> Hi,
>
> When creating an app in AppFactory we are provided a GIT url where we can
> develop our applications. Is there any way we can give our existing GIT url
> when creating a application?
>
> --
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Provide an existing GIT url in AppFactory

[Udara Liyanage]

Hi,

When creating an app in AppFactory we are provided a GIT url where we can
develop our applications. Is there any way we can give our existing GIT url
when creating a application?

-- 
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OAuth2 - Having the TIME_CREATED column as a TIMESTAMP type

[Nuwan Dias]

We can, but this would mean that we need to change the code and set the
time in all places that do an INSERT to this table.

Thanks,
NuwanD.


On Fri, Sep 20, 2013 at 2:22 PM, Prabath Siriwardena wrote:

> It's not rights to update the TIME_CREATED every time we update the record.
>
> Can we update it to DATETIME?
>
> Thanks & regards,
> -Prabath
>
>
> On Fri, Sep 20, 2013 at 2:12 PM, Nuwan Dias  wrote:
>
>> Hi,
>>
>> This is regarding the issue [1]. When an OAuth2 token is initially
>> created, it is created in the 'Active' state. When revoking a token, its
>> state is changed to 'REVOKED'. But this time, the TIME_CREATED value of
>> that particular database entry is also updated.
>>
>> When looking at the issue, I found that the TIME_CREATED column has a
>> TIMESTAMP type. According to [2], in MySQL databases this means that the
>> TIME_CREATED column is always updated whenever that row is updated. Hence
>> the cause for the issue [1]. Is it right to have this column type as
>> TIMESTAMP?
>>
>> [1] - https://wso2.org/jira/browse/APIMANAGER-1696
>> [2] - http://stackoverflow.com/questions/409286/datetime-vs-timestamp
>>
>> Thanks,
>> NuwanD.
>>
>> --
>> Nuwan Dias
>>
>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>



-- 
Nuwan Dias

Senior Software Engineer - 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] OAuth2 - Having the TIME_CREATED column as a TIMESTAMP type

[Prabath Siriwardena]

It's not rights to update the TIME_CREATED every time we update the record.

Can we update it to DATETIME?

Thanks & regards,
-Prabath


On Fri, Sep 20, 2013 at 2:12 PM, Nuwan Dias  wrote:

> Hi,
>
> This is regarding the issue [1]. When an OAuth2 token is initially
> created, it is created in the 'Active' state. When revoking a token, its
> state is changed to 'REVOKED'. But this time, the TIME_CREATED value of
> that particular database entry is also updated.
>
> When looking at the issue, I found that the TIME_CREATED column has a
> TIMESTAMP type. According to [2], in MySQL databases this means that the
> TIME_CREATED column is always updated whenever that row is updated. Hence
> the cause for the issue [1]. Is it right to have this column type as
> TIMESTAMP?
>
> [1] - https://wso2.org/jira/browse/APIMANAGER-1696
> [2] - http://stackoverflow.com/questions/409286/datetime-vs-timestamp
>
> Thanks,
> NuwanD.
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

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

Re: [Dev] Please Apply patch to kernel for L1 REGISTRY-1988

[Sameera Jayasoma]

Hi Senaka,

There are some API changes in this patch. I.e. Removal of some public
methods. Can you please confirm whether there are no effects to other
components?

Thanks,
Sameera.


On Thu, Sep 19, 2013 at 7:57 PM, Senaka Fernando  wrote:

> Please $subject, as soon as possible, since it is required for further
> testing. The patch is available @
> https://wso2.org/jira/browse/REGISTRY-1988.
>
> Thanks,
> Senaka.
>
> --
> * 
> *
> *
> *
> *Senaka Fernando*
> Senior Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sameera Jayasoma,
Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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

[Dev] OAuth2 - Having the TIME_CREATED column as a TIMESTAMP type

[Nuwan Dias]

Hi,

This is regarding the issue [1]. When an OAuth2 token is initially created,
it is created in the 'Active' state. When revoking a token, its state is
changed to 'REVOKED'. But this time, the TIME_CREATED value of that
particular database entry is also updated.

When looking at the issue, I found that the TIME_CREATED column has a
TIMESTAMP type. According to [2], in MySQL databases this means that the
TIME_CREATED column is always updated whenever that row is updated. Hence
the cause for the issue [1]. Is it right to have this column type as
TIMESTAMP?

[1] - https://wso2.org/jira/browse/APIMANAGER-1696
[2] - http://stackoverflow.com/questions/409286/datetime-vs-timestamp

Thanks,
NuwanD.

-- 
Nuwan Dias

Senior Software Engineer - 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] API Manager 1.5.0 integration test failures

[Sanjeewa Malalgoda]

I will look into this,

Thanks,
Sanjeewa.


On Fri, Sep 20, 2013 at 11:43 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Fixed the typo - now there are two test method failures.
>
> org.wso2.jmeter.tests.PassthroughTestCase - assert failures and one add
> api failure
>
> To check the failures, you have to open the relevant jmeter result file
> (.jtl) and look for http samples with s="false" status
>
> Thanks
>
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation.
> Mobile: +94  599 18; blog: http://opensource-soa.blogspot.com/
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>
>
> On Fri, Sep 20, 2013 at 11:23 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Please find the attach report containing test results. It seems like most
>> failures are due to typo in host name.
>>
>> Tests run: 7, Failures: 3, Errors: 0, Skipped: 0,
>>
>>
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation.
>> Mobile: +94  599 18; blog: http://opensource-soa.blogspot.com/
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middlewear.
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*
*
*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

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

Re: [Dev] Please apply the patch IDENTITY-1847

[Manoj Kumara]

Hi,

Noted.

Thanks,

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Fri, Sep 20, 2013 at 1:00 PM, Nuwan Dias  wrote:

> Adding Manoj
>
>
> On Fri, Sep 20, 2013 at 12:49 PM, Venura Kahawala  wrote:
>
>> Hi,
>>
>> Please commit the patch attached to jira 
>> IDENTITY-1847
>> .
>>
>> Regards,
>> Venura
>>
>> --
>> Senior Software Engineer
>>
>> Mobile: +94 71 82 300 20
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - 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] Please apply the patch IDENTITY-1847

[Nuwan Dias]

Adding Manoj


On Fri, Sep 20, 2013 at 12:49 PM, Venura Kahawala  wrote:

> Hi,
>
> Please commit the patch attached to jira 
> IDENTITY-1847
> .
>
> Regards,
> Venura
>
> --
> Senior Software Engineer
>
> Mobile: +94 71 82 300 20
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Senior Software Engineer - 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

[Dev] Please apply the patch IDENTITY-1847

[Venura Kahawala]

Hi,

Please commit the patch attached to jira
IDENTITY-1847
.

Regards,
Venura

-- 
Senior Software Engineer

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

Re: [Dev] [AS] Creating a product level p2 repo for feature installation test scenarios

[Supun Malinga]

+1.

thanks,


On Fri, Sep 20, 2013 at 12:35 PM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> +1, this would be the best option until we sort out current p2-repo
> availability issues in product build time.
>
> Thanks,
>
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation.
> Mobile: +94  599 18; blog: http://opensource-soa.blogspot.com/
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>
>
> On Fri, Sep 20, 2013 at 12:22 PM, Piyum Fernando  wrote:
>
>> As we face few problems when writing tests for feature installation test
>> scenarios (eg: J2EE test cases) I think it's better to create a product
>> level p2 repo with features only needed for the test cases and copy it to
>> the test resource location at the build time.
>>
>> Then we can point to this repo inside test cases.
>>
>> This is similar to keeping the test artifact source codes and copying
>> them after building from source.
>>
>> WDYT?
>>
>> --
>> Piyum Fernando
>> Software Engineer
>>
>> Mobile: +94 77 22 93 880
>> Home:  +94 31 22 75 715
>>
>
>


-- 
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] [AS] Creating a product level p2 repo for feature installation test scenarios

[Krishantha Samaraweera]

+1, this would be the best option until we sort out current p2-repo
availability issues in product build time.

Thanks,

Krishantha Samaraweera
Senior Technical Lead - Test Automation.
Mobile: +94  599 18; blog: http://opensource-soa.blogspot.com/
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.


On Fri, Sep 20, 2013 at 12:22 PM, Piyum Fernando  wrote:

> As we face few problems when writing tests for feature installation test
> scenarios (eg: J2EE test cases) I think it's better to create a product
> level p2 repo with features only needed for the test cases and copy it to
> the test resource location at the build time.
>
> Then we can point to this repo inside test cases.
>
> This is similar to keeping the test artifact source codes and copying them
> after building from source.
>
> WDYT?
>
> --
> Piyum Fernando
> Software Engineer
>
> Mobile: +94 77 22 93 880
> Home:  +94 31 22 75 715
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev