Re: [Dev] Issues while using Store REST API

[Sivaramya Sivanathan]

Thank you for the response. Now it's working with the WUM update pack.

Sivaramya Sivanathan
Associate Software Engineer | WSO2
Tel: 0770874960
WSO2 Inc : http://wso2.org

LinkedIn | www.linkedin.com/in/sivaramya

On Fri, Feb 16, 2018 at 12:30 PM, Malintha Amarasinghe 
wrote:

>
>
> On Fri, Feb 16, 2018 at 12:28 PM, Malintha Amarasinghe  > wrote:
>
>> Hi Sivaramya,
>>
>> On Fri, Feb 16, 2018 at 12:13 PM, Sivaramya Sivanathan <
>> sivara...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I followed the following steps,
>>>
>>> 1) Download the fresh package *wso2am-2.1.0*
>>>
>> This API is not included in the fresh pack. This is available in the
>> latest WUM update pack or one of the released updates (2.1.0-updateX). Take
>> the latest one if possible.
>>
>> On a seperate note, this doc need to be updated mentioning those
>> information.
>>
>> Thanks!
>>
>>
>>>
>>> 2) Obtain the *clientId* and *clientSecret* from the token endpoint and
>>>  then get the *access_token. * (*access_token* : 3abb5d89-ddea
>>> -39ae-aca4-c94ec3b4c1d1)
>>> 3) Send that access token as a header in the API call.
>>> 4) When I get the details of the application using the curl command as
>>> below.
>>> curl -k -H "Authorization: Bearer 
>>> 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
>>> "https://localhost:9443/api/am/store/v0.11/applications/a2dc
>>> 9825-8a75-42d5-b1d9-4987612ea8f5"
>>>
>>> I got the response as follows,
>>>
>>> {
>>>"applicationId":"a2dc9825-8a75-42d5-b1d9-4987612ea8f5",
>>>"name":"sampleapp",
>>>"subscriber":"admin",
>>>"throttlingTier":"Unlimited",
>>>"callbackUrl":"http://my.server.com/callback";,
>>>"description":"sample app description",
>>>"status":"APPROVED",
>>>"groupId":null,
>>> "keys":[{
>>>"consumerKey":"RhKMetERTwVWOd
>>> 9UvEU0v14Sflka","consumerSecret":"XWiufquXgT7MfEadNRDdtF_v1Q
>>> ga","supportedGrantTypes":null,"keyState":"COMPLETED","keyTy
>>> pe":"PRODUCTION",
>>>"token":{"accessToken":"58c1d
>>> 49f-7710-342e-85a9-b288f10ba323","tokenScopes":["am_applicat
>>> ion_scope","default"],"validityTime":3600}
>>> }]
>>> }
>>>
>>> 5) But when I used the following curl command to get the key details of
>>> a given type I didn't get any response messages as I mentioned above.
>>>curl -k -H "Authorization: Bearer 
>>> 3abb5d89-ddea-39ae-aca4-c94ec3b4c1d1"
>>> "https://localhost:9443/api/am/store/v0.11/applications/a2dc
>>> 9825-8a75-42d5-b1d9-4987612ea8f5/keys/PRODUCTION"
>>>
>>> Regards,
>>>
>>> Sivaramya Sivanathan
>>> Associate Software Engineer | WSO2
>>> Tel: 0770874960
>>> WSO2 Inc : http://wso2.org
>>> 
>>> LinkedIn | www.linkedin.com/in/sivaramya
>>>
>>> On Fri, Feb 16, 2018 at 10:40 AM, Menaka Jayawardena 
>>> wrote:
>>>
 Hi Sivaramya,

 The basic information related to getting authorization code generation
 is in the Getting Started section of the documentation. For every request
 in the documentation, you have to follow the proper request format as
 Viduranga has mentioned.

 @Documenatation Team
 It's not clear in the API documentation because in Request section it
 just says,

 GET https://localhost:9443/api/am/store/v0.11/apis

 There is no indication about the authorization header or the correct
 curl. IMO it's better if we could restructure this documentation because it
 will also be used by the other users as well. As this is an autogenerated
 doc by the swagger file, we have to modify the swagger file with proper
 information.

 Thanks and Regards,
 Menaka

 On Fri, Feb 16, 2018 at 10:00 AM, Viduranga Gunarathne <
 vidura...@wso2.com> wrote:

> Hi Sivaramya,
>
> I checked the store REST API and the specific resource to get the key
> details of an individual application that you have mentioned and couldn't
> replicate the issue that you stated.
>
> These are the steps that I followed.
>
> 1) Obtain the *clientId * and *clientSecret *from the token endpoint
> [1] and then get the *accessToken *[1]
> 2) Send that access token as a header in the API call
> 3) This is the request path that I used
>
> *https://localhost:9443/api/am/store/v0.11/applications/0bb05b1b-7cde-4797-89bf-967f0fb6a856/keys/PRODUCTION
> *
>
>
> Can you please state the exact steps that you followed?
>
> [1] https://docs.wso2.com/display/AM2xx/apidocs/store/index.html#guide
>
> Thanks,
> Viduranga.
>
> On Thu, Feb 15, 2018 at 5:36 PM, Sivaramya Sivanathan <
> sivara...@wso2.com> wrote:
>
>> Hi all,
>>
>> I'm tryi

[Dev] Go back to the previous user task in a process instance

[Thomas LEGRAND]

Hello,

I have a process where I have 3 sequential user task (something like Task 1
-> Task 2 -> Task 3). So, to validate the Task 3, I have to validate the
Task 1, then the Task 2.

My goal is to be able to go back to the previous task without modifying my
process definition. To do so, I found a way thanks to the need of another
Activiti user in [1]. But, it seems that his previous tasks are not
"finished" whereas mine, once validated, disappear from the ACT_RU_TASK
table but can be found in the ACT_HI_TASKINST.

So, I implemented a Command like he did but I don't manage to make my
execution to point to the previous task. Algorithm should be something like:

- Retrieve the current task
- Get the process instance of the current task
- Get the historic tasks of the process instance
- From the list of the historic tasks, deduce the previous one
- Create a new task from the previous historic task
- Make the execution to point on this new task

Here is my code:

public class MoveTokenCmd implements Command {

protected String fromTaskId;


public MoveTokenCmd(String fromTaskId) {
this.fromTaskId = fromTaskId;

}

public Void execute(CommandContext commandContext) {
HistoricTaskInstanceEntity currentUserTaskEntity =
commandContext.getHistoricTaskInstanceEntityManager()
.findHistoricTaskInstanceById(fromTaskId);
ExecutionEntity currentExecution =
commandContext.getExecutionEntityManager()
.findExecutionById(currentUserTaskEntity.getExecutionId());

// Get process Instance
HistoricProcessInstanceEntity historicProcessInstanceEntity =
commandContext
.getHistoricProcessInstanceEntityManager()

.findHistoricProcessInstance(currentUserTaskEntity.getProcessInstanceId());

HistoricTaskInstanceQueryImpl historicTaskInstanceQuery = new
HistoricTaskInstanceQueryImpl();

historicTaskInstanceQuery.processInstanceId(historicProcessInstanceEntity.getId()).orderByExecutionId().desc();
List historicTaskInstances =
commandContext.getHistoricTaskInstanceEntityManager()

.findHistoricTaskInstancesByQueryCriteria(historicTaskInstanceQuery);

int index = 0;
for (HistoricTaskInstance historicTaskInstance :
historicTaskInstances) {
if
(historicTaskInstance.getId().equals(currentUserTaskEntity.getId())) {
break;
}
index++;
}

if (index > 0) {
HistoricTaskInstance previousTask =
historicTaskInstances.get(index - 1);

TaskEntity newTaskEntity =
createTaskFromHistoricTask(previousTask, commandContext);
currentExecution.addTask(newTaskEntity);

commandContext.getTaskEntityManager().insert(newTaskEntity);


AtomicOperation.TRANSITION_CREATE_SCOPE.execute(currentExecution);
} else {
// TODO: find the last task of the previous process instance
}

// To overcome the "Task cannot be deleted because is part of a
running
// process"
TaskEntity currentUserTask =
commandContext.getTaskEntityManager().findTaskById(fromTaskId);
if (currentUserTask != null) {
currentUserTask.setExecutionId(null);

commandContext.getTaskEntityManager().deleteTask(currentUserTask, "jumped
to another task", true);
}

return null;
}

private TaskEntity createTaskFromHistoricTask(HistoricTaskInstance
historicTaskInstance,
CommandContext commandContext) {

TaskEntity newTaskEntity = new TaskEntity();


newTaskEntity.setProcessDefinitionId(historicTaskInstance.getProcessDefinitionId());
newTaskEntity.setName(historicTaskInstance.getName());

newTaskEntity.setTaskDefinitionKey(historicTaskInstance.getTaskDefinitionKey());

newTaskEntity.setProcessInstanceId(historicTaskInstance.getExecutionId());
newTaskEntity.setExecutionId(historicTaskInstance.getExecutionId());

return newTaskEntity;
}

Can you help me, please?

Regards,

Thomas

[1] https://community.alfresco.com/thread/224300-user-task-rollback
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Metrics databases for IS and EI

[Ruwan Abeykoon]

Hi Lahiru,
Regarding Metrics on IS,
Is there any support issue we could solve or any issue we could have done
better with having Metrics.

I am asking because, I have not seen much importance on metics. But only
saw issues when Metrics DB per each node needs to be created and configured
over the cluster, and problems in auto-scaling.
I am more inclined to remove the metrics support from IS.

Cheers,
Ruwan


On Fri, Feb 16, 2018 at 11:01 AM, Lahiru Sandaruwan 
wrote:

> Hi,
>
> We have metrics databases for APIM 2.x.x[1] and IS 5.1.0[2].
> But latest IS versions and EI does not have DBs to store metrics, even
> though EI has a list of MBeans supported at [3].
>
> This is an useful feature for tracking information if users don't want to
> setup advanced monitoring tools. Are we planning to add this feature in the
> future?
>
> [1] https://docs.wso2.com/display/AM2xx/Enabling+Metrics+and+Storage+Types
> [2] https://docs.wso2.com/display/IS510/Enabling+Metrics+and+Storage+Types
> [3] https://docs.wso2.com/display/EI611/JMX+Monitoring
>
> Thanks.
>
> --
> --
>
> Lahiru Sandaruwan
> WSO2 Inc., http://wso2.com
>
> lean.enterprise.middleware
>
> m: +1 901 530 2379 <(901)%20530-2379>
> e: lahi...@wso2.com b: https://medium.com/@lahirugmg
> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 API Manager 2.1.0-update11 Released !

[Chamalee De Silva]

The WSO2 API Manager team is pleased to announce the release of version
2.1.0-update11 of API Manager.

WSO2 API Manager is a platform for creating, managing, consuming and
monitoring APIs. It employs proven SOA best practices to solve a wide range
of API management challenges such as API provisioning, API governance, API
security and API monitoring. It combines some of the most powerful and
mature components of the WSO2's state-of-the-art Carbon platform to deliver
a smooth and end-to-end API management experience while catering to both
API publisher and API consumer requirements.

WSO2 API Manager is comprised of several modules.

   -

   API Provider: Define new APIs and manage them
   -

   API Store: Browse published APIs and subscribe to them
   -

   API Gateway: The underlying API runtime based on WSO2 ESB
   -

   API Key Manager: Performs Key Generation and Key Validation
   functionalities
   -

   API Traffic Manager: Performs Rate Limiting of API Requests

For more information on WSO2 API Manager please visit
http://wso2.com/products/api-manager. Also, take a look at the online
product documentation
.

DistributionWSO2 APIM 2.1.0-update11.zip


WSO2 APIM Analytics 2.1.0-update6.zip

How to Run

   1.

   Extract the downloaded zip
   2.

   Go to the bin directory in the extracted folder
   3.

   Run the wso2server.sh or wso2server.bat as appropriate
   4.

   Launch a web browser and navigate to https://localhost:9443/publisher to
   access the API publisher webapp
   5.

   Navigate to https://localhost:9443/store to access the API store
   6.

   Navigate to https://localhost:9443/admin to access Admin Portal
   7.

   Use "admin", "admin" as the username and password to login as an admin

Bug Fixes And Improvements in 2.1.0-update11

Please refer following locations for WSO2 API Manager 2.1.0-update11 Bug
fixes and Improvements.


   -

   JIRA 
   -

   GitHub (Product-apim
   
,
   Carbon-apimgt
   

   )

Known Issues

All the open issues pertaining to WSO2 API Manager are reported at the
following location:

   -

   JIRA 
   -

   GitHub (Product-apim
   
,
   Carbon-apimgt
   

   )

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   -

   Developer List: dev@wso2.org | Subscribe | Mail Archive
   -

   User List: u...@wso2.org | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 API Manager through the public API Manager Git Repo
.
 -- The WSO2 API Manager Team --
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Metrics databases for IS and EI

[Isuru Perera]

To see the importance of Metrics, IS product should expose useful metrics.
The metrics are useful to understand the runtime behavior of the product.
The product team never prioritized this [1] requirement. Weren't there any
issues that could have solved easily if you had more details about the
runtime behavior?

Metrics DB can be shared among nodes. What are the problems with Metrics
when autoscaling?

[1] https://wso2.org/jira/browse/IDENTITY-6089

On Fri, Feb 16, 2018 at 3:25 PM, Ruwan Abeykoon  wrote:

> Hi Lahiru,
> Regarding Metrics on IS,
> Is there any support issue we could solve or any issue we could have done
> better with having Metrics.
>
> I am asking because, I have not seen much importance on metics. But only
> saw issues when Metrics DB per each node needs to be created and configured
> over the cluster, and problems in auto-scaling.
> I am more inclined to remove the metrics support from IS.
>
> Cheers,
> Ruwan
>
>
> On Fri, Feb 16, 2018 at 11:01 AM, Lahiru Sandaruwan 
> wrote:
>
>> Hi,
>>
>> We have metrics databases for APIM 2.x.x[1] and IS 5.1.0[2].
>> But latest IS versions and EI does not have DBs to store metrics, even
>> though EI has a list of MBeans supported at [3].
>>
>> This is an useful feature for tracking information if users don't want to
>> setup advanced monitoring tools. Are we planning to add this feature in the
>> future?
>>
>> [1] https://docs.wso2.com/display/AM2xx/Enabling+Metrics+
>> and+Storage+Types
>> [2] https://docs.wso2.com/display/IS510/Enabling+Metrics+
>> and+Storage+Types
>> [3] https://docs.wso2.com/display/EI611/JMX+Monitoring
>>
>> Thanks.
>>
>> --
>> --
>>
>> Lahiru Sandaruwan
>> WSO2 Inc., http://wso2.com
>>
>> lean.enterprise.middleware
>>
>> m: +1 901 530 2379 <(901)%20530-2379>
>> e: lahi...@wso2.com b: https://medium.com/@lahirugmg
>> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
>


-- 
Isuru Perera
Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Using useOriginalwsdl parameter in ESB proxy service

[Gayan Dhanushka]

Hi all,

Came across a requirement where it was needed to publish the exact same
WSDL that we create in a ESB proxy service.

When we use the publishWSDL mediator to publish the contract that we had
developed, the ESB generates its own version of the WSDL. Therefore we had
to use the following parameter in the proxy service implementation to
preserve the original WSDL.

true

Is there any harm or other implications in using this in the proxy services
? Is it essential to have more parameters along with this parameters?

Thanks in advance.

-- 
Gayan Dhanuska
Senior Software Engineer
http://wso2.com/
Lean Enterprise Middleware

Mobile - LK- 071 666 2327
Mobile USA - 612-244-4873


Office
Tel   : 94 11 214 5345
Fax  : 94 11 214 5300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture] WSO2 Identity Server 5.5.0-Alpha Released!

[Sathya Bandara]

WSO2 Identity and Access Management team is pleased to announce the release
of Identity Server 5.5.0 Alpha!
Download

You can download WSO2 Identity Server 5.5.0 Alpha distributions from
following locations.

Identity Server:
https://github.com/wso2/product-is/releases/download/v5.5.0-alpha


IS Analytics: https://github.com/wso2/analytics-is/releases/tag/v5.5.0-alpha

How to run

1. Extract the downloaded zip file.

2. Go to the bin directory in the extracted folder.

3. Run the wso2server.sh file if you are on a Linux/Mac OS or run the
wso2server.bat file if you are on a Windows OS.



What's new in WSO2 Identity Server 5.5.0 Alpha

WSO2 Identity Server 5.5.0-Alpha is designed based on privacy best
practices and adhering to GDPR. Your GDPR compliance in IAM and API
security space can be fulfilled with WSO2 IS. Following includes major GDPR
related features provided in WSO2 IS 5.5.0-Alpha.



   -

   Privacy Tool Kit
   

-
   Supports removing references to a deleted user's identity as and when
   required.
   

   -

   Personal Information Export Capability
   

   - End users can retrieve  personal information stored in WSO2 Identity
   Server.
   
   -

   User Consent for Single-Sign-On
   
   - Provides users with choice and control over sharing their personal data.
   
   -

   User Consent for Self Sign Up
   
   - Capability to provide consent when a user self registers to WSO2 Identity
   Server. 
   -

   Consent Purposes Management
    -  An
   interactive UI to manage consent purposes/PII categories.
   

   -

   Private Key JWT Client Authentication
   

   - Facilitating client authentication using a signed JWT.
   -

   Encrypted ID token for OIDC Flow
   

   - Capability to encrypt ID tokens with a registered public key.

A list of all the new features and bug fixes shipped with this release can
be found here 

Online documentation is available at
https://docs.wso2.com/display/IS550/WSO2+Identity+Server+Documentation.


Known Issues

All the open issues pertaining to WSO2 Identity Server are reported at the
following location:

   -

   IS Runtime 
   -

   IS Analytics 



How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer list: dev@wso2.org | Subscribe | Mail Archive


User forum: StackOverflow


Reporting Issues

We encourage you to report issues, improvements, documentation faults, and
feature requests regarding WSO2 Identity Server through WSO2 Identity
Server GIT Issues .

For more information about WSO2 Identity Server, please see
https://wso2.com/identity-and-access-management or visit the WSO2 Oxygen
Tank  developer portal for additional resources.


~ The WSO2 Identity and Access Management Team ~


-- 
Sathya Bandara
Software Engineer
WSO2 Inc. http://wso2.com
Mobile: (+94) 715 360 421 <+94%2071%20411%205032>

<+94%2071%20411%205032>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Implementing a DSS-call mediator for invocation of data services.

[Gayan Dhanushka]

Hi Kasthuriraajan,

If we can improve the DBLookup mediator to retrieve more than a single row
in a database I think that is definitely an improvement.

If you are implementing this improvement, it seems to me like the name
"DSS-Call" is a bit misleading since we will not be doing an actual call.

How about something like "ExtendedDBLookup" or something similar ?

I am not clear on whether all the CRUD operations be supported with this
mediator. Then we would need to use a different name altogether.

+1 for the idea of bypassing the transport layers and directly talking to
the data service components to execute the queries.

Regards
Gayan

On Fri, Feb 16, 2018 at 1:25 AM, Kasthuriraajan Ratnasingam <
kasthuriraa...@wso2.com> wrote:

>
>
> Hi all,
>
> I am working on a project to implement a DSS-call mediator .
>
>
> * If we need to consume DSS service from an ESB sequence, we have to do a
> HTTP call using send or call mediator (just like any other remote HTTP
> service). This is a very inefficient way as HTTP call will introduce an
> additional latency and performance overhead. EI product comes with DSS
> feature built in but there is no way to properly avoid remote HTTP call
> when calling data service which hosted in the same server. We can avoid the
> HTTP call using local transport in the EI. However axis2 service invocation
> overhead is still there and we need to build a new request payload to
> invoke DSS service even with local transport.Even local transport gives a
> better performance than HTTP call, it is not a fully optimized solution.
> That's why this new project idea to build new DSS-Call mediator which can
> do direct data service calls without going through send or call mediator
> and http request (in JVM DSS invocation). The new approach is to come up
> with a DBLookup mediator style invocation for data service. DBLookup
> mediator can fetch only one row of the result of a query. Because of that
> we are using data service. So that the new mediator should have the
> privileges to invoke all the facilities of a data service with the in JVM
> call. *
> Please give your comments and suggestions regarding this project.
>
> Thank you.
>
> Regards,
> R.Kasthuriraajan.
>
> --
> R.Kasthuriraajan
> Software Engineering Intern | WSO2
> LinkedIn: https://www.linkedin.com/in/ratnasingam-kasthuriraajan-2a6892121
>
> Email: kasthuriraa...@wso2.com
> Mobile : +94779893005 <+94%2077%20989%203005>
> Web: http://wso2.com 
>
>


-- 
Gayan Dhanuska
Senior Software Engineer
http://wso2.com/
Lean Enterprise Middleware

Mobile - LK- 071 666 2327
Mobile USA - 612-244-4873


Office
Tel   : 94 11 214 5345
Fax  : 94 11 214 5300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Implementing a DSS-call mediator for invocation of data services.

[Prabushi Samarakoon]

Hi Kasthuriraajan,

This project would be a combination of both DB Lookup and DB Report [1]
 mediators in WSO2
EI to support all CRUD operations with additional capabilities (eg:
retrieving multiple rows as the result element). Therefore, I think it
would be better if we can use a functionality specific name rather than an
existing mediator specific name.

Thanks,
Prabushi

[1] - https://docs.wso2.com/display/EI611/DB+Report+Mediator

On Sat, Feb 17, 2018 at 7:11 AM, Gayan Dhanushka  wrote:

> Hi Kasthuriraajan,
>
> If we can improve the DBLookup mediator to retrieve more than a single row
> in a database I think that is definitely an improvement.
>
> If you are implementing this improvement, it seems to me like the name
> "DSS-Call" is a bit misleading since we will not be doing an actual call.
>
> How about something like "ExtendedDBLookup" or something similar ?
>
> I am not clear on whether all the CRUD operations be supported with this
> mediator. Then we would need to use a different name altogether.
>
> +1 for the idea of bypassing the transport layers and directly talking to
> the data service components to execute the queries.
>
> Regards
> Gayan
>
> On Fri, Feb 16, 2018 at 1:25 AM, Kasthuriraajan Ratnasingam <
> kasthuriraa...@wso2.com> wrote:
>
>>
>>
>> Hi all,
>>
>> I am working on a project to implement a DSS-call mediator .
>>
>>
>> * If we need to consume DSS service from an ESB sequence, we have to do a
>> HTTP call using send or call mediator (just like any other remote HTTP
>> service). This is a very inefficient way as HTTP call will introduce an
>> additional latency and performance overhead. EI product comes with DSS
>> feature built in but there is no way to properly avoid remote HTTP call
>> when calling data service which hosted in the same server. We can avoid the
>> HTTP call using local transport in the EI. However axis2 service invocation
>> overhead is still there and we need to build a new request payload to
>> invoke DSS service even with local transport.Even local transport gives a
>> better performance than HTTP call, it is not a fully optimized solution.
>> That's why this new project idea to build new DSS-Call mediator which can
>> do direct data service calls without going through send or call mediator
>> and http request (in JVM DSS invocation). The new approach is to come up
>> with a DBLookup mediator style invocation for data service. DBLookup
>> mediator can fetch only one row of the result of a query. Because of that
>> we are using data service. So that the new mediator should have the
>> privileges to invoke all the facilities of a data service with the in JVM
>> call. *
>> Please give your comments and suggestions regarding this project.
>>
>> Thank you.
>>
>> Regards,
>> R.Kasthuriraajan.
>>
>> --
>> R.Kasthuriraajan
>> Software Engineering Intern | WSO2
>> LinkedIn: https://www.linkedin.com/in/ratnasingam-kasthurira
>> ajan-2a6892121
>>
>> Email: kasthuriraa...@wso2.com
>> Mobile : +94779893005 <+94%2077%20989%203005>
>> Web: http://wso2.com 
>>
>>
>
>
> --
> Gayan Dhanuska
> Senior Software Engineer
> http://wso2.com/
> Lean Enterprise Middleware
>
> Mobile - LK- 071 666 2327
> Mobile USA - 612-244-4873 <(612)%20244-4873>
>
>
> Office
> Tel   : 94 11 214 5345
> Fax  : 94 11 214 5300
>



-- 
*Prabushi Samarakoon*
Software Engineer
Mobile: +94715434580
Email: prabus...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev