On Thu, Dec 10, 2015 at 11:57 AM, Sameera Jayasoma wrote:
> +1. We need to do this change in C5 :)
>
Noted. Created a jira to track this [1]
[1]. https://wso2.org/jira/browse/CARBON-15723
>
> Thanks,
> Sameera
>
> On Thu, Dec 10, 2015 at 11:37 AM, Afkham Azeez wrote:
>
>> For example, the MSS
+1. We need to do this change in C5 :)
Thanks,
Sameera
On Thu, Dec 10, 2015 at 11:37 AM, Afkham Azeez wrote:
> For example, the MSS deployment dir is
> $CARBON_HOME/repository/deployment/server/mss
>
> We no longer need the server part because this was a concept to do with
> Axis2 server & clie
Hi Isuru,
I've used it in a mediation sequence where I use a POJO to generate a
unique customer id given a couple of parameters and there's a checksum
added to the end. I already had written this code and it was quite simple
and straightforward to reuse it with a POJOCommand mediator. I feel the
s
IMO best option in that case is have connectors supporting different spring
versions, similar to what we are doing for EJBs. Having a mediator will
only limit for single version.
On Thu, Dec 10, 2015 at 11:35 AM, Maheeka Jayasuriya
wrote:
> Hi,
>
> I've observed spring mediator being used extens
For example, the MSS deployment dir is
$CARBON_HOME/repository/deployment/server/mss
We no longer need the server part because this was a concept to do with
Axis2 server & client ConfigContext creation, which we no longer have in
Carbon 5.
So the MSS deployment directory should be;
$CARBON_HOME/r
Hi,
I've observed spring mediator being used extensively in situations where
maintaining the domain model useful (class mediators are the alternative
with a POJO domain model). This allows maintainability and is easily
extensible. However, Spring mediator right now does not explore best of
Spring
[2015-12-10 11:34:09,012] INFO
{org.wso2.carbon.mss.internal.deployer.MSSDeployer} - Deploying artifact:
/Users/azeez/projects/github/wso2/product-mss/product/target/wso2mss-1.0.0-SNAPSHOT/repository/deployment/server/mss/README.txt
[2015-12-10 11:34:09,013] ERROR
{org.wso2.carbon.kernel.internal
Hi,
I think we will have to test call mediator in blocking mode for some
different use cases. Then we will have to update Documentation about
blocking capability of call mediator. For example the Call Mediator
Documentation for ESB 4.9.0 [1] does not contain any information about
blocking behavior
Hi Kathees,
I think we should do a comparison once more to make sure that we have
covered everything before removing Callout. NTLM one which Harshana pointed
out may be due to absence of initClientOptions configuration option.
Hi Vidura,
Point you raised on the POJOCommand mediator is really inte
+1 to deprecate Callout mediator since we have the Callout mediator
functionalities in Call mediator.
On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya
wrote:
> I've found DBReport / DBLookup to be quite useful for simple DB operations
> as they are easy to do OOTB. While DB Lookup mediator
Hi Natasha,
You can use the format used in Activiti rest api documentations [1] for
this also. It includes response codes and sample success responses.
@Dinithi, we are doing basic authentication using the security handler [2]
AFAIK.
[1] - http://www.activiti.org/userguide/#_get_a_deployment
[2]
Hi Natasha,
How are you going to ensure the security of the APIs? Have you thought of
using any security models?
You can use permission/role based model in order to achieve this. Just
make sure which APIs need the administrative privileges.
Thanks.
On Wed, Dec 9, 2015 at 9:30 PM, Nuwan Pallew
I've found DBReport / DBLookup to be quite useful for simple DB operations
as they are easy to do OOTB. While DB Lookup mediator maybe limited in it's
ability to only being able to return a single row of data, DB Report
mediator is still quite useful in writing to a database, especially when we
use
Is it going to be complete functional Deprecate? If yes, there will be not
forward compatibility during the upgrades.
On Wed, Dec 9, 2015 at 10:23 AM, Isuru Udana wrote:
> Hi Harshana,
>
> On Wed, Dec 9, 2015 at 6:46 PM, Harshana Eranga Martin <
> harshan...@gmail.com> wrote:
>
>> Hi Kasun,
>>
>
Hi Harshana,
On Wed, Dec 9, 2015 at 6:46 PM, Harshana Eranga Martin wrote:
> Hi Kasun,
>
> Please see the comments inline.
>
> Thanks and Regards,
> Harshana
> --
> Harshana Eranga Martin
>
> Committer - Eclipse ECF: http://www.eclipse.org/ecf/
> Blog: http://harshana05.blogspot.com
> Profile: h
Hi Natasha,
Great work.
What happens if an invalid request or request with an illegal argument sent
to the API ?
It is better to have those response messages or response status code also
in the documentation.
Thanks,
Nuwan
On Wed, Dec 9, 2015 at 5:08 PM, Natasha Wijesekara wrote:
> Hi,
>
> I
Hi Kasun,
Please see the comments inline.
Thanks and Regards,
Harshana
--
Harshana Eranga Martin
Committer - Eclipse ECF: http://www.eclipse.org/ecf/
Blog: http://harshana05.blogspot.com
Profile: https://www.google.com/profiles/harshana05
On 9 December 2015 at 17:41, Kasun Indrasiri wrote:
>
In my experience using DB mediator we can cover some of the use cases
using ESB out of the box, which I find very handy.
Also use case of integrating with stored procs can easily covered with
this.
However there are limits like batch update or getting multiple rows.
I guess we can argue both w
Hi,
I documented a user guide which contains details about the new rest API
implemented to generate the statistics for bpmn.
Appreciate any suggestions and comments.
Thanks,
Natasha
On Tue, Dec 8, 2015 at 4:44 PM, Vinod Kavinda wrote:
> [Adding Architecture group]
>
> On Tue, Dec 8, 2015 at 2
On Wed, Dec 9, 2015 at 3:32 PM, Malaka Silva wrote:
> +1 except DBReport/DBLookup mediators
>
> DBReport and DBLookup only offer a very limited set of capabilities. IMO,
for any real integration scenario, we can't use them. :).
> On Wed, Dec 9, 2015 at 2:00 PM, Yumani Ranaweera wrote:
>
>> Is
+1 except DBReport/DBLookup mediators
On Wed, Dec 9, 2015 at 2:00 PM, Yumani Ranaweera wrote:
> Is it possible to provide sufficient documentation to help the customers
> who would be migrating in future.
>
> Thanks,
> Yumani
>
>
> On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando
> wrote:
>
>>
Is it possible to provide sufficient documentation to help the customers
who would be migrating in future.
Thanks,
Yumani
On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando wrote:
> *- Callout mediator :*
> All the callout functionality is supported with 'call' mediator with
> blocking=true. Ha
*- Callout mediator :*
All the callout functionality is supported with 'call' mediator with
blocking=true. Having two similar mediators will be create a bit of a
confusion.
It will make a lot of confusion when we have more than one mediators to do
the same thing. Therefore, better to deprecate th
23 matches
Mail list logo