Hi
IMO, I still could't separate the drastic different between using POJO
vs ClassMediator (forget about performance aspects), if think in a
developer perspective I am more comfortable with Classmediator btw (just a
thought)
for e.g let look at twitter search...
serialization view
On Thu, Aug 1, 2013 at 12:09 PM, Sanjiva Weerawarana wrote:
> Kasun please don't do org.apace.* for WSO2 written connectors!
>
> Yeah, sure.
>
> On Wed, Jul 31, 2013 at 2:20 PM, Kasun Indrasiri wrote:
>
>> We are in the process of implementing several components which involves
>> java sdks (twit
Kasun please don't do org.apace.* for WSO2 written connectors!
On Wed, Jul 31, 2013 at 2:20 PM, Kasun Indrasiri wrote:
> We are in the process of implementing several components which involves
> java sdks (twitter), although the class mediator approach works fine, it
> seems to introduce some u
On Thu, Aug 1, 2013 at 9:49 AM, Miyuru Wanninayaka wrote:
> Hi Kasun,
>
> Main drawback of the pojo mediator is, it does not have access to message
> context, so everything it need to access need to pass as parameters in
> sequence. Also in most custom mediator cases, it is required to modify
> c
My understanding is that the performance issues of reflection have been
minimized a lot over the years. There is still a performance overhead, but
I would focus on usability first and optimize performance later. If there
is a real performance issue we can do some compilation style approach later
to
Hi Kasun,
Main drawback of the pojo mediator is, it does not have access to message
context, so everything it need to access need to pass as parameters in
sequence. Also in most custom mediator cases, it is required to modify
contents of message context which is not possible with pojo mediator.
I
Also we would need to be able to use a config. based approach rather than
ui for this..
thanks,
On Wed, Jul 31, 2013 at 8:25 PM, Afkham Azeez wrote:
> An important aspect to keep in mind is monitoring artifacts deployed on a
> cluster. The stats from multiple nodes have to be summarized & an
>
Can we create aPaaS, iPaaS, API, Mobile etc. profiles for App Factory?
We've initially thought of these as App Types and solution bundles. Sounds
like profiles makes much more sense (though Integration, API, etc. App
Types will still be present).
On Wed, Jul 31, 2013 at 8:47 PM, Afkham Azeez wro
I think we should wait for Isabelle to provide explanation. I am also not
clear of what is the exact requirement.
Isabelle, This is regarding "Feature #72: Extension Point to associate
sequences to inbound/outbound/fault flows" . Could you elaborate bit more
please?
On Wed, Jul 31, 2013 at 9:07
Hi all,
We have agreed on the architecture of the publisher and store for mobile.
We will be following the same caramel standard. We have forked the store
project and using it as the base for the publisher as well. The only
changes required for this implementation is regarding the presentation. AP
On Wed, Jul 31, 2013 at 1:20 PM, Vijayaratha Vijayasingam
wrote:
> Hi all;
>
> *Our requirement*
>
> Allow users to create their own sequences and make them available in the
> API configuration. A developer creates the necessary sequences to say log,
> audit requests, may be add authorization via
Hi,
Attached is the architecture of mobile device management. The MDM build is
compiled on top of carbon by using necessary features. Build consist of
these layers modules/components.
1) MDM web console - MDM Jaggery app where you have the MDM core
functionality.
2) MDM admin console - This is f
It is good to think about profiles at a product level. It is also possible
to "host" new profiles after we ship the product. For example, let's say we
come across a use case or customer scenario where a subset of the features
is needed in certain runtimes. We can create profiles for that. We also
n
An important aspect to keep in mind is monitoring artifacts deployed on a
cluster. The stats from multiple nodes have to be summarized & an
aggregated view should be shown. Our current System statistics UI is broken
in terms of showing stats in a cluster.
Azeez
On Wed, Jul 31, 2013 at 6:00 PM, M
Hi,
At present Service Statistics and Activity Service data are configured to
be published at a single global location. That means all the service
statistics data should go to a single stream and all the activity data
should also go to a single stream.
But in practice the user may host different
Yes.. How about the following. I think we should use singular names as the
profile names.
1. Web apps - webapp
2. Services - axis2service
3. DS - dataservice
4. Jaggery -jaggery
5. MS - mashup
On Wed, Jul 31, 2013 at 12:25 PM, Kasun Gajasinghe wrote:
>
>> Yes. The list
On Wed, Jul 31, 2013 at 1:20 PM, Vijayaratha Vijayasingam
wrote:
> Hi all;
>
> *Our requirement*
>
> Allow users to create their own sequences and make them available in the
> API configuration. A developer creates the necessary sequences to say log,
> audit requests, may be add authorization via
What would happen to old sequence? should we delete it or let both to be
around?
Using a name pattern can work, but is it a bad thing if we explicitly tell
what to run?
--Srinath
On Wed, Jul 31, 2013 at 1:20 PM, Vijayaratha Vijayasingam
wrote:
> Hi all;
>
> *Our requirement*
>
> Allow users
Hi Kasun,
Can we make it work such that we use java code to get frequent parameters?
but for others we use reflection. That way we can have best of both worlds.
--Srinath
On Wed, Jul 31, 2013 at 2:20 PM, Kasun Indrasiri wrote:
> We are in the process of implementing several components which
We are in the process of implementing several components which involves
java sdks (twitter), although the class mediator approach works fine, it
seems to introduce some usability issues.
- Basically, a given class mediator simply get all the required properties
from the message context where prope
Hi all;
*Our requirement*
Allow users to create their own sequences and make them available in the
API configuration. A developer creates the necessary sequences to say log,
audit requests, may be add authorization via XACML , whatever is needed and
pushes those with a description to the API publ
On Wed, Jul 31, 2013 at 12:25 PM, Kasun Gajasinghe wrote:
> Yes. The list is as follows.
>
> 1. Web apps
> 2. Services
> 2. DS
> 4. Jaggery
> 5. MS
>
We might want to use some meaningful names here rather than these
abbreviations.
> Thanks,
> KasunG
>
>
> On Wed, Jul 31, 2013 at 11:53 AM, Isur
22 matches
Mail list logo
