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 11:21 AM, Shelan Perera she...@wso2.com wrote:
Hi,
Appreciate if you could apply this patch as well.
Thanks
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
[2013-09-20 11:49:30,417] INFO
{org.wso2.carbon.server.util.PatchUtils.console} - Patch verification
started
[2013-09-20 11:49:30,845] INFO
{org.wso2.carbon.server.util.PatchUtils.console} - Patch verification
successfully completed without encountering any issues.
I guess this can be
tests module was broken down as above mentioned sub modules. Since We still
use tests module , those sub modules are not enabled by setting skipTests
true/skipTests in surefire configurations. once we can verify that all
tests are passed, we can enable sub modules and remove the tests module.
On
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
On Fri, Sep 20, 2013 at 11:53 AM, Sumedha Rubasinghe sume...@wso2.comwrote:
[2013-09-20 11:49:30,417] INFO
{org.wso2.carbon.server.util.PatchUtils.console} - Patch verification
started
[2013-09-20 11:49:30,845] INFO
{org.wso2.carbon.server.util.PatchUtils.console} - Patch verification
+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
+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.
Hi,
Please commit the patch attached to jira
IDENTITY-1847https://wso2.org/jira/browse/IDENTITY-1847
.
Regards,
Venura
--
Senior Software Engineer
Mobile: +94 71 82 300 20
___
Dev mailing list
Dev@wso2.org
Adding Manoj
On Fri, Sep 20, 2013 at 12:49 PM, Venura Kahawala ven...@wso2.com wrote:
Hi,
Please commit the patch attached to jira
IDENTITY-1847https://wso2.org/jira/browse/IDENTITY-1847
.
Regards,
Venura
--
Senior Software Engineer
Mobile: +94 71 82 300 20
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 nuw...@wso2.com wrote:
Adding Manoj
On Fri, Sep 20, 2013 at 12:49 PM, Venura Kahawala
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
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
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 sen...@wso2.com wrote:
Please $subject, as soon as possible,
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 nuw...@wso2.com wrote:
Hi,
This is regarding the issue [1]. When an OAuth2 token is initially
created, it is
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.comwrote:
It's not rights to update the TIME_CREATED every time we update the record.
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:
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
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 same...@wso2.com wrote:
Hi Senaka,
There are some API
Hi,
L1 (2)
---
REGISTRY-1988 https://wso2.org/jira/browse/REGISTRY-1988 [Fixed to be
committed by Kernel Team]
REGISTRY-1957 https://wso2.org/jira/browse/REGISTRY-1957 [Darshana is
looking into this ]
L2 (0)
Thanks
--
*Shelan Perera*
Senior Software Engineer
**
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 nuw...@wso2.com 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 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 gay...@wso2.com wrote:
Hi Udara,
I'm afraid it is not. We are given a git repo when
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 ma...@wso2.com wrote:
Hi,
Noted.
Thanks,
Best Regards..
Manoj Kumara
Software
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
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 nuw...@wso2.com wrote:
No. Just TIMESTAMP. We thought of manually setting the created time to what
it originally was.
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 sume...@wso2.comwrote:
MySQL by default updates this. (see
http://dev.mysql.com/doc/refman/5.0/en/timestamp-initialization.html)
You
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
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 she...@wso2.com wrote:
Hi Sameera,
Just get the confirmation from Senaka
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 ma...@wso2.com wrote:
Hi,
Noted.
Thanks,
Best Regards..
Manoj
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.
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
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.*
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
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 sanje...@wso2.comwrote:
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
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 nir...@wso2.com wrote:
With this ELB pack, https://wso2.org/jira/browse/LB-104 should be fixed.
QA team can
Cool.
On Sat, Sep 21, 2013 at 10:39 AM, Sumedha Rubasinghe sume...@wso2.comwrote:
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 nir...@wso2.com wrote:
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 ka...@wso2.com wrote:
I'm experiencing the $subject. This happens with both publisher and store.
Once I've provided the
Thanks.
On Sat, Sep 21, 2013 at 10:36 AM, Manoj Kumara ma...@wso2.com 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:
Still is this frozen?
Thanks,
sanjeewa.
On Fri, Sep 20, 2013 at 10:51 AM, Dhanushka Ranasinghe
dhanush...@wso2.comwrote:
Granted
Thank You
Dhanushka
On Fri, Sep 20, 2013 at 9:38 AM, Kasun Indrasiri ka...@wso2.com wrote:
Also please grant commit rights to following people (We will be
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 nir...@wso2.com wrote:
Cool.
On Sat, Sep 21, 2013 at 10:39 AM, Sumedha
41 matches
Mail list logo
