Hi Suresh,
We have identified above fail points as mandatory to the app creation
process. But as you said , for the optional cases, we can do this in
configurable manner in appfactory configuration. Then user can select those
optional cases as mandatory or not.
But if we allow to create app
Yes, I think we can add these as improvements in next milestones after
discussing.
On Mon, Jan 6, 2014 at 1:37 PM, Harsha Thirimanna hars...@wso2.com wrote:
Hi Suresh,
We have identified above fail points as mandatory to the app creation
process. But as you said , for the optional cases, we
Hi Ashansa,
Now what we are going to do is deleting all the stuff related to the
current failed application and give a message to the user saying failed.
After refresh the page then there will not be any information regarding
this failed app.
Instead of doing that how about if we keep the failed
Hi All,
New feature that is going to be introduced to AppFactory is creating a new
application by uploading exiting binary file of an application. e.g WAR
*User Scenario*
1. User logs on to the system, goes to the application creation page.
2. In there user provides basic information related to
Hi Shamika,
On Mon, Jan 6, 2014 at 4:43 PM, Shamika Ariyawansa sham...@wso2.com wrote:
Hi All,
New feature that is going to be introduced to AppFactory is creating a new
application by uploading exiting binary file of an application. e.g WAR
*User Scenario*
1. User logs on to the
As I feel creating an application pointing to an existing code base is
different than allowing to upload an artifact and create an application,
since this will not include any source code management. So we should
consider those as two different use cases.
IMO we can relate the use case that Janaka
Hi all,
On Mon, Jan 6, 2014 at 6:48 PM, Ashansa Perera asha...@wso2.com wrote:
As I feel creating an application pointing to an existing code base is
different than allowing to upload an artifact and create an application,
since this will not include any source code management. So we should
Hi Shamika,
In this case, do we restrict exposing repository URL to user to
checkout/checkin this artifact ? Because even though we not show this URL
in AppFactory UI , user can see this after login to the Git server.
thanks
*Harsha Thirimanna*
Senior Software Engineer; WSO2, Inc.;
Please find the attached diff files for the changes done, as per the
offline chat had with Sagara regarding this problem.
Here are the load test results
No of Threads Without the fix (tps) With the
fix (tps)
1
410 400
5
2100
Today I was thinking of more examples to help explain my previous email.
Here is one example from the eclipse world:
Package: eclipse-jdt (3.8.0~rc4-1) -
http://packages.debian.org/wheezy/eclipse-jdt
dep: default-jre Standard Java or Java compatible Runtime
or java5-runtime virtual package
Hi Chanika,
IMO we can do little improvements to your code.
1. Please use string constants in 'getRegexForLocation' method.
2. In 'getRegexForLocation' method you can use StringBuilder.append instead
of concatenating strings with + operator
3. In 'getRegexForLocation' you can use
Hi Janaka,
This is not only for WAR files and will be supported all the other
application types which are currently supported by AppFactory like Jaggery.
IMO how about doing the scenario you mentioned like this as
a separate feature.
1. User creates the application in normal way where selecting
On Mon, Jan 6, 2014 at 4:43 PM, Shamika Ariyawansa sham...@wso2.com wrote:
Hi All,
New feature that is going to be introduced to AppFactory is creating a
new application by uploading exiting binary file of an application. e.gWAR
*User Scenario*
1. User logs on to the system, goes to the
On Tue, Jan 7, 2014 at 11:05 AM, Ajanthan Balachandran ajant...@wso2.comwrote:
On Mon, Jan 6, 2014 at 4:43 PM, Shamika Ariyawansa sham...@wso2.comwrote:
Hi All,
New feature that is going to be introduced to AppFactory is creating a
new application by uploading exiting binary file of an
Hi Harsha,
On Mon, Jan 6, 2014 at 8:09 PM, Harsha Thirimanna hars...@wso2.com wrote:
Hi Shamika,
In this case, do we restrict exposing repository URL to user to
checkout/checkin this artifact ? Because even though we not show this URL
in AppFactory UI , user can see this after login to the
Hi Manjula,
On Tue, Jan 7, 2014 at 11:05 AM, Manjula Rathnayake manju...@wso2.comwrote:
Hi Janaka,
On Tue, Jan 7, 2014 at 10:41 AM, Janaka Ranabahu jan...@wso2.com wrote:
Hi Manjula,
While I completely agree that this feature is something different from
what I've stated, I'm trying to
Hi Janaka,
On Tue, Jan 7, 2014 at 11:33 AM, Janaka Ranabahu jan...@wso2.com wrote:
Hi Manjula,
On Tue, Jan 7, 2014 at 11:05 AM, Manjula Rathnayake manju...@wso2.comwrote:
Hi Janaka,
On Tue, Jan 7, 2014 at 10:41 AM, Janaka Ranabahu jan...@wso2.com wrote:
Hi Manjula,
While I
*please look at the comment.*
On Tue, Jan 7, 2014 at 11:33 AM, Janaka Ranabahu jan...@wso2.com wrote:
Hi Manjula,
On Tue, Jan 7, 2014 at 11:05 AM, Manjula Rathnayake manju...@wso2.comwrote:
Hi Janaka,
On Tue, Jan 7, 2014 at 10:41 AM, Janaka Ranabahu jan...@wso2.com wrote:
Hi
Hi Manjula,
Thanks for the clarifications. Seems good.
Thanks,
Janaka
On Tue, Jan 7, 2014 at 11:54 AM, Manjula Rathnayake manju...@wso2.comwrote:
Hi Janaka,
On Tue, Jan 7, 2014 at 11:33 AM, Janaka Ranabahu jan...@wso2.com wrote:
Hi Manjula,
On Tue, Jan 7, 2014 at 11:05 AM, Manjula
19 matches
Mail list logo
