Hi All,
Please find the methods which will implement under each connector:
*FreeAgent Connector*
createContact - Create a new contact.
listContacts - List all contacts.
getContact - Get a single contact by id.
createProject - Create a new project.
listProjects - List all projects.
getProject -
Hi all,
I have started working on $subject, which is will serve to add another
back-end record storage atop which the BAM 3.0 Data Layer would be able to
operate. In this implementation, all records will be stored in a Hadoop
Distributed Filesystem (HDFS) deployment, and it will provide a new
Hi All,
Please find the methods which will implement under each connector:
*Clio Connector*
createContact - Create a new Person or Company as a Contact.
getContact - Get a Contact (Person or Company) by ID.
listContacts - List all Contacts.
updateContact - Update an exsiting Contact.
Hi Dilan,
I do agree that there is an issue with this UI. As per the UI the final
policy will be calculated correspondent to the device rather than the user,
role or platform. Hence the more accurate UI would be to have one segment
at a time by allowing multiple selections in the listbox.
Hi Dilshan,
Thanks for the feedback.
It is true that we need to go for some algorithm of doing the necessary
intersection + union calculations when resources from multiple resource
levels are attached.
But the key point that I am trying to figure out is that when we are
assigning resources from
This is already included in AM 1.9.0 plan and already being worked out.
On Fri, Jan 23, 2015 at 9:01 AM, Prabath Abeysekera praba...@wso2.com
wrote:
Hi Everyone,
Just wondering where we are on $subject and if we've got any plans to
support this anytime soon.
I believe, CDM has a definite
Hi Everyone,
Just wondering where we are on $subject and if we've got any plans to
support this anytime soon.
I believe, CDM has a definite use-case for dynamic client registration in
which we need a mechanism to let the agent applications (that run on some
devices such as mobile, etc to
Great. Thanks Sumedha for the prompt response.
Cheers,
Prabath
On Fri, Jan 23, 2015 at 9:03 AM, Sumedha Rubasinghe sume...@wso2.com
wrote:
This is already included in AM 1.9.0 plan and already being worked out.
On Fri, Jan 23, 2015 at 9:01 AM, Prabath Abeysekera praba...@wso2.com
wrote:
Hi all,
This is just a quick update on Metrics integration.
- We decided to use a separate repository for metrics [1]. The main
reason is that we want to integrate Metrics to upcoming releases and it
will take a longer time for products to use a new Carbon Kernel version.
- Developed
I suggest one of the following:
* The ESB already has very advanced metrics. So a good test would be to see
if we can get all of those easily with the new component. That would
quickly get the new component up to a high quality.
* The Identity Server market is becoming much more performance
10 matches
Mail list logo