Looks good!
Are all these updates available in the latest pull request? If not can you
send a pull request with updates.
One minor question: can we draw each chevron as a svg, without using an
existing image? If that is possible, I think we get more control over what
is in the canvas.
Regards,
+1
Regards,
Chathura
On Mon, Jan 12, 2015 at 7:24 PM, Milinda Perera milin...@wso2.com wrote:
Hi,
We are planning to add form generation to HumanTask-explorer webapp [1].
*Current situation as follows:*
Currently HumanTask author create separate .jsp files and embed them
in Main
@Chathura I have made a new pull request with updated code. I will look
into drawing a chevron rather than using an image.
@Nandika yes that can be done by changing some styling properties. Will
include it .
Regards,
Himasha
On Wed, Jan 14, 2015 at 9:53 AM, Nandika Jayawardana
Hi,
On 14 January 2015 at 00:32, Joseph Fonseka jos...@wso2.com wrote:
Hi
With related to CORS the headers they should be set in the gateway as well
since we are configuring CORS in gateway so the headers should be as the
configuration of the gateway not the back-end.
+1. OPTIONS verb
On Wed, Jan 14, 2015 at 8:33 AM, Lakmali Baminiwatta lakm...@wso2.com
wrote:
Hi,
On 14 January 2015 at 00:32, Joseph Fonseka jos...@wso2.com wrote:
Hi
With related to CORS the headers they should be set in the gateway as
well since we are configuring CORS in gateway so the headers should
Also, is there a way to merge the text box into the chevron itself so that
outlining of the text box is not visible.
Regards
Nandika
On Wed, Jan 14, 2015 at 9:36 AM, Chathura Ekanayake chath...@wso2.com
wrote:
Looks good!
Are all these updates available in the latest pull request? If not
If we draw the chevron, text box and everything that has to be included in
a chevron as svgs, we can overcome the problems such as textbox border,
color differences, etc.
On Wed, Jan 14, 2015 at 10:05 AM, Himasha Guruge himas...@wso2.com wrote:
@Chathura I have made a new pull request with
At the time we receive the response, user has already logged in to the
system. And the response we receive has the information as to which
organisation the user logged into. We just need to use that information to
populate the group-name (or whichever) session variable.
Thanks,
NuwanD.
On Wed,
Hi Lakshman,
Can you explain a bit about when this is invoked, and for what tasks this
is going to be used? If we are trying to provide an extension point to run
a custom code after a user logs in, I think then we should try to use
WorkflowExecutor
I don't think we should be calling this LoginInterceptor since it actually
doesn't intercept a login request. Its more of a login workflow, a function
that executes after login.
Thanks,
NuwanD.
On Tue, Jan 13, 2015 at 1:22 PM, Lakshman Udayakantha lakshm...@wso2.com
wrote:
Hi All,
I am
Yes, we may rename this as login listener/post login executor or something
like that(since we listen login and perform something). Once we extracted
organization ID we need to go to next level. Since we are going to
implement this for API store we need to pass this organization id for all
places
Hi Asanka,
+1 for the design. Also, i think we might need to consider the situation
where the number of topics with retain true being scaled up in size, given
the fact that this will go through an iteration cycle through all the
topics in the table each time a subscription is created. WDYT ?
On Tue, Jan 13, 2015 at 3:37 PM, Sanjeewa Malalgoda sanje...@wso2.com
wrote:
On Tue, Jan 13, 2015 at 11:40 AM, Joseph Fonseka jos...@wso2.com wrote:
Hi
Currently in API Manager we send the OPTIONS call to the back-end server
to respond. But if the API does not expose all the HTTP methods
On Tue, Jan 13, 2015 at 2:54 PM, Nuwan Dias nuw...@wso2.com wrote:
Ok, so I think we need to have a property which can be enabled/disabled.
This property decides whether the OPTIONS request should be forwarded to
the back-end or not. Whenever the Max-Forwards header is not present in the
Hi All,
How about refactoring the interface like below.
public interface LoginPostExecutor {
public String getGroupingIdentifier(String response);
}
@Amila: I thought to call the implementation of that interface in
the jsFunction_login() method of StoreHostObject and assign the returned
Ok, so I think we need to have a property which can be enabled/disabled.
This property decides whether the OPTIONS request should be forwarded to
the back-end or not. Whenever the Max-Forwards header is not present in the
request, this property gets prominence. When present, Max-Forwards get
Doing this as a mediation extension would make it more re-usable IMO.
On Tue, Jan 13, 2015 at 3:10 PM, Ruwan Yatawara ruw...@wso2.com wrote:
On Tue, Jan 13, 2015 at 2:54 PM, Nuwan Dias nuw...@wso2.com wrote:
Ok, so I think we need to have a property which can be enabled/disabled.
This
Hi,
To control the puppet catalog run on each newly spawned instances as soon
as an instance is spawned, we suspend the instance.
Once all the instances are spawned, we resume instances one by one.
It is during this stage that the product packs are being extracted and
servers are being started
Hi all,
Disable giving System governance and System Config registries via
CarbonContext to App Developers. Why do we need to give Registry to app
developers?
- To be used as a repository. So simply give an empty repository. It could
be backed by a DB, or persistent cache.
Why is it more
Hi All,
FFI, following methods will be implemented under following connectors:
*Recurly Connector *
createSubscription - Create a new subscription.
listSubscriptions - List all subscriptions.
getSubscriptionById - Get a subscription by the ID.
createPlan - Create a plan.
listPlans - List
Hi
With related to CORS the headers they should be set in the gateway as well
since we are configuring CORS in gateway so the headers should be as the
configuration of the gateway not the back-end.
Also we can capture allowed domains per API basis. Allowed methods and
headers are already
21 matches
Mail list logo
