Hi Tanya,
I like to express few suggestions regarding the gadget structure.
*Generated gadget structure*
>
> └── test_gadget
> ├── conf.json
> ├── gadget-controller.jag
> ├── gadget.json
> ├── index.png
> ├── index.xml
> ├── libs
> │ └── vendorName_version
> │
>
> ... "uninstall" is NOT a REST, even though it looks like REST.
"uninstall" does not looks like REST. It looks like RPC.
On Mon, Apr 25, 2016 at 10:43 AM, Ruwan Abeykoon wrote:
> I disagree Manu, The point is this is not "DELETE" action on a "resource".
> This is an action
[+ Frank]
On Mon, Apr 25, 2016 at 11:49 AM, SajithAR Ariyarathna <sajit...@wso2.com>
wrote:
> ... "uninstall" is NOT a REST, even though it looks like REST.
>
> "uninstall" does not looks like REST. It looks like RPC.
>
> On Mon, Apr 25, 2016 at 10:43 A
Hi Sudharma,
In the browser (client-side), you can do AJAX calls to the necessary REST
APIs. However, doing HTTP requests from UI backend (which runs on the
server-side) to REST APIs (which also runs on the server-side) is not
recommended. Instead of that you should call OSGi services. Calling
etween UI back-end and the actual server
>>>>> (e.g. BPS runtime)? i.e. both always run in the same jvm?
>>>>>
>>>>> On Thu, May 19, 2016 at 11:47 PM, Manuranga Perera <m...@wso2.com>
>>>>> wrote:
>>>>>
>>>&g
Hi Manu,
> Permissions for UI pages
> I think there is no need to introduce a separate permission namespace for
> UI (or use a very limited one). Actual customer is concerned about giving
> permission to a real resource (topic, API, proxy ...) not to a UI
> URL. Ideally, for each page, we
On Wed, Feb 1, 2017 at 5:12 PM, KasunG Gajasinghe wrote:
> Hi Shariq,
>
> On Wed, Feb 1, 2017 at 4:45 PM, Muhammed Shariq wrote:
>
>>
>> On Wed, Feb 1, 2017 at 1:10 AM, KasunG Gajasinghe
>> wrote:
>>
>>> Hi Manu,
>>>
>>> #1. Because UUF's
Hi All,
Creating a reusable Store component was one of goals we had in our minds at
UUF initial discussions. At that time there was couple of products APIM,
AppM, EMM mobile store, GReg etc. that need a Store UI. So developing a
generalized Store component was a requirement. However with the new
> need to take into consideration the release dependencies, version
> incompatibilities, etc, etc. Isn't this the same thing we tried to do once
> with Enterprise Store?
>
>>
>> Regards,
>> Chandana
>>
>>
>> On Tue, Sep 27, 2016 at 8:01 PM, SajithAR Ariyarathn
Hi Danesh,
Do we really need the @Ignore annotation? IMO, we can ignore frields wich
are not marked with @Element annotation, thus we don't need a separate
annotation.
Thanks.
On Mon, Nov 21, 2016 at 11:32 PM, Danesh Kuruppu wrote:
> Hi all,
>
> In Carbon C5, we are going to
Wed, Dec 14, 2016 at 10:47 AM, Joseph Fonseka <jos...@wso2.com> wrote:
>
>> Hi Sajith
>>
>> On Wed, Dec 14, 2016 at 8:44 AM, SajithAR Ariyarathna <sajit...@wso2.com>
>> wrote:
>>
>>>
>>> 2. Why did we use comments to propagate Zones
be OVERWRITE.
> 2. Why did we use comments to propagate Zones to the client side instead
> of Divs.
>
> Thanks
> Jo
>
>
>
> On Tue, Dec 13, 2016 at 10:37 PM, SajithAR Ariyarathna <sajit...@wso2.com>
> wrote:
>
>> Hi All,
>>
>> To do $subje
tch them and
> render.
>
> What will be the location of these fragments? If it's the same as server
> side fragments it will give control over different UUF components IMO.
>
> thanks,
> Chanaka
>
> On Tue, Dec 13, 2016 at 10:37 PM, SajithAR Ariyarathna <sajit...@wso2.
s...@wso2.com> wrote:
>
>> Hi
>>
>> +1, few clarifications bellow.
>>
>> 1. I guess the default mode will be OVERWRITE.
>> 2. Why did we use comments to propagate Zones to the client side instead
>> of Divs.
>>
>> Thanks
>> Jo
>>
Hi All,
To do $subject, we are hoping to give a UUF client JS library. With the
client-side library, webapp developers will be able to render fragments and
push to zones similar to the server-side.
Functions in the library:
UUF.renderFragment(fragmentFullyQualifedName, templateFillingObject,
Hi All,
We are hoping to do $subject.
*UUF Component:*
Currently a UUF component has two configuration files, 'component.yaml' and
'config.yaml'. 'component.yaml' contains APIs entries and bindings (see
mail thread [1] for more details); 'config.yaml' contains business-logic
related
le, widget related information can be kept
> in the component.yaml or do we need to have separate files for this?
>
> Regards,
> Chandana
>
> On Fri, Jan 6, 2017 at 3:23 PM, SajithAR Ariyarathna <sajit...@wso2.com>
> wrote:
>
>> Hi All,
>>
>> We are h
Hi All,
We are pleased to announce the *ninth milestone* of WSO2 Carbon Unified UI
Framework (UUF). You can download the UUF server distribution at [1].
UUF is an UI framework that let webapp developers to build shareable UI
components and to build webapps by composing those UI components.
Hi Johann,
Once you login using CAAS (carbon authentication and authorization service)
> components you will get a CAAS User object [1]. This User object is a proxy
> object which can be used to call all the underlying identity store and
> authorization store methods. Ideally you will store this
>
> [1] - https://github.com/thanujalk/carbon-identity-mgt/
> blob/master/components/org.wso2.carbon.identity.mgt/src/
> main/java/org/wso2/carbon/identity/mgt/User.java
>
> Thanks,
> Thanuja
>
> On Mon, Jan 9, 2017 at 12:45 PM, SajithAR Ariyarathna <sa
ragment. Need to know what will happen if we
> implemented to get the JSON object (which will be used to fill the
> fragment's template) by calling an OSGI service, in the onRequest() method
> of the fragment. That will replace the "templateFillingObject" passed in
> the UUF.re
rate it in here?
>>>
>>> Regards,
>>> Chandana
>>>
>>> On Wed, May 17, 2017 at 10:08 AM, Imesh Gunaratne <im...@wso2.com>
>>> wrote:
>>>
>>>> As we discussed offline I think it would be better to provide a default
>
Hi All,
We are in the process of doing $subject.
# What is sendToClient() function?
Its a server-side JS function provided by UUF that can be used to send a
server-side value to the client-side.
function onGet(env) {
sendToClient("contextPath", env.contextPath);
}
Which will produce
still it has a meaning that it stores app data instead of
> HTML document metadata.
>
> Cheers,
>
> On Wed, May 31, 2017 at 4:50 PM, SajithAR Ariyarathna <sajit...@wso2.com>
> wrote:
>
>> Hi Jerad,
>>
>> On Wed, May 31, 2017 at 4:05 PM, Jerad Rutnam <
Hi Dilan,
The purpose of the SessionHandler and SessionManager is different.
SessionManager is an extension point (a plugin for UUF) for webapp
developers. SessionHandler is meant to be passed for other plugins (e.g.
Authenticator) as a way do session related operations (e.g. create a new
Hi All,
We are in the process of introducing an extensible authorizer for Carbon
UUF.
At the moment authorization is done via the
org.wso2.carbon.uuf.spi.auth.User interface [1]. When creating an user
session, implementation of the User interface (e.g. CaasUser [2]) should be
passed. The main
Hi All,
We encountered an issue in the Startup Order Resolver when incorporating
the Carbon Deployment framework into the Carbon UI Server.
Problem:
Carbon UI Server binds each web app to the transport layer via a
microservice (MSF4J). For each web app that will be deployed in the Carbon
UI
be useful to add a new page to the store app. But we will have to write the
>> react app client side routing to pick the extension as a new route.
>>
>>
>> thanks,
>> Chanaka
>>
>> On Mon, Sep 11, 2017 at 3:35 PM, SajithAR Ariyarathna <sajit...@wso2.com&
.
On Tue, Oct 10, 2017 at 2:31 PM, SajithAR Ariyarathna <sajit...@wso2.com>
wrote:
> Hi Kishanthan,
>
> On Fri, Sep 22, 2017 at 10:50 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>>
>>
>> On Fri, Sep 15, 2017 at 8:49 PM, SajithAR Ariyar
Hi All,
*What is app context path?*
In http://localhost:8080/store/apis/1234 URL, the app context path is /store.
Customer might want to deploy the Store app in /my-store context path (in
that case the URL will be http://localhost:8080/my-store/apis/1234).
Currently in React based web apps,
Hi All,
We are in the process of developing $subject. Tentatively this webapp
server is named as "Carbon UI Server".
# Major goals of this webapp server are following:
- Enforcing security measures.
- Setting proper cache headers
- Setting recommended security related HTTP
Hi Thusitha,
On Mon, Aug 14, 2017 at 12:08 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:
> Hi Jayanga,
>
> From the beginning of C5, we tried to achieve a clear separation between,
>> User(Custom) space and Server space.
>> IMO, having just a single deployment directory (for both
ill have to write the
> react app client side routing to pick the extension as a new route.
>
Extensions are React components.
Thanks.
>
>
> thanks,
> Chanaka
>
> On Mon, Sep 11, 2017 at 3:35 PM, SajithAR Ariyarathna <sajit...@wso2.com>
> wrote:
>
>> Hi All
Hi All,
The WSO2 Analytics team is pleased to announce the release of *WSO2
Stream Processor Version
4.0.0 Beta*.
WSO2 Analytics let digital business creating real-time, intelligent,
actionable business insights, and data products which are achieved by WSO2
Stream Processor's real-time,
Hi All,
We are in the process of implementing the option for customers to customize
(by overriding or adding new things) React based web apps.
*Overriding:*
Customer can override a file of a web app by putting the custom version of
that file in the same relative path inside the
r
>> WSO2, Inc.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> <https://maps.google.com/?q=20,+Palm+Grove,+Colombo+03,+Sri+Lanka=gmail=g>
>> Mobile: +94 (71) 214 1576 <+94%2071%20214%201576>
>> Email: lasant...@wso2.com
>> Web:www.wso
Hi Devs,
We are pleased to announce the release candidate of WSO2 Stream Processor
4.0.0.
This is the Release Candidate version 1 of the WSO2 Stream Processor 4.0.0
Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Known issues:
Hi Devs,
We are pleased to announce the release candidate of WSO2 Stream Processor
4.0.0.
This is the Release Candidate version 2 of the WSO2 Stream Processor 4.0.0
Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Known issues:
Hi Devs,
On Tue, Feb 20, 2018 at 7:06 PM, Irindu Nugawela wrote:
> Hi All,
> I am implementing a feature for Widget Configuration Panel of Carbon
> Dashboard's designer view,
> to allow users(dashboard designers) to configure the properties of the
> widgets such as the widget
Hi All,
We are calling off this vote. We will do a RC2 release soon.
Thanks.
On Thu, Mar 15, 2018 at 8:54 AM, Sriskandarajah Suhothayan
wrote:
> -1
> In Mac, the graphics of the editor event flow is not rendering correctly.
>
> Please check the attached image.
>
> On Thu, Mar
Hi All,
We are closing this vote, we will announce RC2 release soon.
Thanks.
On Thu, Mar 15, 2018 at 11:18 AM, Anusha Jayasundara
wrote:
> -1 ,
>
> Missing client-truststore.jks file in several samples directories
> including smart-home and apim-stats
>
>
>
> On Thu, Mar 15,
41 matches
Mail list logo