Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Sriskandarajah Suhothayan]

Since Option 2 is now possible I think you can move to it now. The
advantage is, with this approach you are not restricted to emails and you
can now use SOAP, REST and other adopters to trigger some actions based on
notifications, which will make IS much more powerful than just sending
emails.

I'm available from 2.30 pm at PG.

Regards
Suho

On Tue, Jul 19, 2016 at 11:17 AM, Johann Nallathamby 
wrote:

> Hi Suho,
>
> On Mon, Jul 18, 2016 at 11:44 PM, Sriskandarajah Suhothayan  > wrote:
>
>> Hi
>>
>> Based on the request of IS team we have recently added support for
>> loading template files from the registry.
>> I think with this feature we can do the mapping at Event Publisher side,
>> then IS can send only the core data for the notification. I think building
>> the whole message at IS is too much customization for emails.
>>
>
> As discussed previously both methods should work.
>
> Replacing placeholder with data in the arbitrary data map was in the
> master at the time and now it should have been release AFAIU. This is what
> Indunil was trying.
>
> And also you guys have added the support to pick registry templates based
> on some place holder values in the registry path. What we discussed was to
> send the 'locale' value as a stream attribute for our use case. If this
> approach works this is also fine for us.
>
> We tried with option1 just to get something working quickly.
>
>
>>
>> Please set up a meeting so we can discuss the possible ways to
>> implementing this.
>>
>> Regards
>> Suho
>>
>> On Mon, Jul 18, 2016 at 5:52 PM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We are trying to do some improvements to the notification sending module
>>> where we have integrated analytics common features in IS, in order to send
>>> several notifications (ex:Email, SMS).
>>>
>>> Current implementation is in [1], there only the email notification was
>>> focused where we are directly publishing to the EmailEventAdapter.
>>>
>>> Now we are trying to send notifications via publishing an event to the
>>> Event stream without directly calling an Output Adapter. The approach we
>>> have taken is as follows.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *1) In server start up following will be created.i) A stream for each
>>> and every notification type including the necessary attributes.Ex:
>>> Email Notification - a Stream with the subject, body and footer as
>>> attributesii) Event Publishers, registered for each and every stream in the
>>> required Output event adapter type. Ex: Email Notification - event
>>> Publisher in email output event adapter type.2) Publishing an event to
>>> EventStreamService, which includes an arbitrary data map with the necessary
>>> data needed for the specific notification type.  Ex: Email Notification
>>> - Please find the code segments in [2] for having a better understanding.*
>>>
>>> There in IS side, we are selecting a specific email template and will be
>>> filled out the place holders before sending the subject, body and footer as
>>> arbitrary map attributes.
>>>
>>> But even-though we passed an arbitrary data map, when we are sending an
>>> email from the EmailEventAdapter, it won't filter out the subject, body or
>>> header from that arbitrary data map.
>>> As I have understood, if someone pass an event with an arbitrary data
>>> map, the email body will be set as [3] (Refer [4]), it won't filter out the
>>> content(Refer [5]).
>>> Is this has to be worked if we provide *output mappings* for event
>>> publisher as* {{subject}{body}{footer}}* to convert the event to the
>>> supported format?
>>>
>>> I have gone through the code [6], where the event data will be passed
>>> through EventStreamProducer, but there also seems like it's not
>>> possible to send an email in required format(subject, body and footer).
>>>
>>> Really appreciate your comments/suggestions to understand the correct
>>> approach to be taken.
>>>
>>> [1]
>>> https://github.com/wso2-extensions/identity-event-handler-email/blob/master/components/event-handler-email/org.wso2.carbon.identity.event.handler.email/src/main/java/org.wso2.carbon.identity.event.handler.email/handler/EmailEventHandler.java#L164
>>> [2]
>>> https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBY00yYVpGelZJNms/view?usp=sharing
>>> [3]
>>> https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBNEMtYjJvSFB2emM/view?usp=sharing
>>> [4]
>>> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/type/text/TextOutputMapper.java#L139
>>> [5]
>>> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/event-output-adapters/org.wso2.carbon.event.output.adapter.email/src/main/java/org/wso2/carbon/event/output/adapter/email/EmailEventAdapter.java#L233
>>> [6]
>>> https://github.com/wso2/carbon-event-processing/blob/master/components/event-simulator/

Re: [Dev] Disable DefaultInboundUserProvisioningListener by default

[Johann Nallathamby]

We set this default behaviour to make the OOTB experience better for the
user.

First you need to check if it's a problem with the code that make the
performance bad. IMO here it's a problem with the code if I understood this
correctly where it goes and unnecessarily check for the SP, because the SP
has already been identified in the inbound side, so that information should
be available for the outbound side as well. Probably through the context
variable, or alternatively as a threadlocal, if not it's a problem in the
code IMO.

If we decide not to fix in the code then it has to enabled by default and
in the production deployment guideline recommend to turn it off if we are
not using outbound provisioning.

On Tue, Jul 19, 2016 at 9:13 AM, Gayan Gunawardana  wrote:

> Hi All,
>
> Currently if we do not define DefaultIdentityUserProvisioningListener in
>  (identity.xml) default behavior is to enable listener.
> This behavior is fine if you have outbound provisioning user story but if
> you do not have outbound provisioning user story at all, having
> DefaultIdentityUserProvisioningListener enable make additional overhead to
> all user CRUD operations.
>
> Specially we retrieve Service provider information for each user operation
> which is totally unnecessary if there is no outbound provisioning user
> story.
>
> Shall we change default behavior to make it disable ?
>
> Thanks,
> Gayan
>
> --
> Gayan Gunawardana
> Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Johann Nallathamby]

Hi Suho,

On Mon, Jul 18, 2016 at 11:44 PM, Sriskandarajah Suhothayan 
wrote:

> Hi
>
> Based on the request of IS team we have recently added support for loading
> template files from the registry.
> I think with this feature we can do the mapping at Event Publisher side,
> then IS can send only the core data for the notification. I think building
> the whole message at IS is too much customization for emails.
>

As discussed previously both methods should work.

Replacing placeholder with data in the arbitrary data map was in the master
at the time and now it should have been release AFAIU. This is what Indunil
was trying.

And also you guys have added the support to pick registry templates based
on some place holder values in the registry path. What we discussed was to
send the 'locale' value as a stream attribute for our use case. If this
approach works this is also fine for us.

We tried with option1 just to get something working quickly.


>
> Please set up a meeting so we can discuss the possible ways to
> implementing this.
>
> Regards
> Suho
>
> On Mon, Jul 18, 2016 at 5:52 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> We are trying to do some improvements to the notification sending module
>> where we have integrated analytics common features in IS, in order to send
>> several notifications (ex:Email, SMS).
>>
>> Current implementation is in [1], there only the email notification was
>> focused where we are directly publishing to the EmailEventAdapter.
>>
>> Now we are trying to send notifications via publishing an event to the
>> Event stream without directly calling an Output Adapter. The approach we
>> have taken is as follows.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *1) In server start up following will be created.i) A stream for each and
>> every notification type including the necessary attributes.Ex: Email
>> Notification - a Stream with the subject, body and footer as attributesii)
>> Event Publishers, registered for each and every stream in the required
>> Output event adapter type. Ex: Email Notification - event Publisher in
>> email output event adapter type.2) Publishing an event to
>> EventStreamService, which includes an arbitrary data map with the necessary
>> data needed for the specific notification type.  Ex: Email Notification
>> - Please find the code segments in [2] for having a better understanding.*
>>
>> There in IS side, we are selecting a specific email template and will be
>> filled out the place holders before sending the subject, body and footer as
>> arbitrary map attributes.
>>
>> But even-though we passed an arbitrary data map, when we are sending an
>> email from the EmailEventAdapter, it won't filter out the subject, body or
>> header from that arbitrary data map.
>> As I have understood, if someone pass an event with an arbitrary data
>> map, the email body will be set as [3] (Refer [4]), it won't filter out the
>> content(Refer [5]).
>> Is this has to be worked if we provide *output mappings* for event
>> publisher as* {{subject}{body}{footer}}* to convert the event to the
>> supported format?
>>
>> I have gone through the code [6], where the event data will be passed
>> through EventStreamProducer, but there also seems like it's not possible
>> to send an email in required format(subject, body and footer).
>>
>> Really appreciate your comments/suggestions to understand the correct
>> approach to be taken.
>>
>> [1]
>> https://github.com/wso2-extensions/identity-event-handler-email/blob/master/components/event-handler-email/org.wso2.carbon.identity.event.handler.email/src/main/java/org.wso2.carbon.identity.event.handler.email/handler/EmailEventHandler.java#L164
>> [2]
>> https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBY00yYVpGelZJNms/view?usp=sharing
>> [3]
>> https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBNEMtYjJvSFB2emM/view?usp=sharing
>> [4]
>> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/type/text/TextOutputMapper.java#L139
>> [5]
>> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/event-output-adapters/org.wso2.carbon.event.output.adapter.email/src/main/java/org/wso2/carbon/event/output/adapter/email/EmailEventAdapter.java#L233
>> [6]
>> https://github.com/wso2/carbon-event-processing/blob/master/components/event-simulator/org.wso2.carbon.event.simulator.core/src/main/java/org/wso2/carbon/event/simulator/core/internal/CarbonEventSimulator.java#L183
>>
>> Thanks and Regards
>> --
>> Indunil Upeksha Rathnayake
>> Software Engineer | WSO2 Inc
>> Emailindu...@wso2.com
>> Mobile   0772182255
>>
>
>
>
> --
>
> *S. Suhothayan*
> Technical Lead & Team Lead of WSO2 Complex Event Processor
> *WSO2 Inc. *http://wso2.com
> * *
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | b

Re: [Dev] [ESB] DataMapper issue

[Viraj Rajaguru]

Hi Godwin,

In this use case, JSON schema generator will consider all the datatypes,
but it will get the datatype of the last value of the array. See the below
JSON representation of the XML

{
   "employees":{
  "firstname":"Demo",
  "lastname":"Demo",
  "addresses":{
 "address":[
{
   "add1":"No 827/B",
   "add2":"Gemunu Mawatha"
},
{
   "add1":321,
   "add2":"Mount Lavinia"
}
 ]
  }
   }
}

Since the datatype of last "add1" is a NUMBER it will take that for the
JSON schema. Hence we see it in the graphical tree.

Issue is we have to select one of the datatypes among all the datatypes for
the schema. Currently the convention is to get the last datatype. But as a
fix, we can set high priority to STRING when we have to select one from
multiple datatypes.

Until we figure out that conventional issue, you can change the datatype of
"add1" from the graphical view. Right click on the "add1" element from the
tree --> Click "Edit Field" and then change the Schema type.

Thanks,
Viraj.

On Tue, Jul 19, 2016 at 9:02 AM, Nuwan Pallewela  wrote:

> Adding Sohani
>
> On Tue, Jul 19, 2016 at 12:42 AM, Godwin Shrimal  wrote:
>
>> Hi All,
>>
>> When load following xml file in to data mapper (input/output), the add1
>> data type takes as NUMBER as in screenshot . It looks when there is at
>> least one record in the array with NUMBER it takes as NUMBER. I think It
>> should consider all the values in the array.
>>
>> 
>> Demo
>> Demo
>>
>> 
>>   
>>   *No 827/B*
>> Gemunu Mawatha
>>   
>>   
>> *321*
>> Mount Lavinia
>>   
>> 
>> 
>>
>> [image: Inline image 2]
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Last updated date in our docs

[Susinda Perera]

Got it, Thanks


On Tue, Jul 19, 2016 at 9:33 AM, Sherene Mahanama  wrote:

> Hi Susinda,
>
> If you navigate to* Tools>Page History* found on the right hand corner on
> any page in the documentation, you will be able to see when that page was
> last edited and by whom (see attached screenshots).
>
> On Tue, Jul 19, 2016 at 9:16 AM, Susinda Perera  wrote:
>
>> WDYT on $subject, then we know how uptodate the doc is.
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Documentation Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to documentation+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> Sherene Mahanama
> Associate Technical Writer
>
> WSO2 (pvt.) Ltd.
> Colombo, Sri Lanka
> (+94) 777 <%28%2B94%29%20773131798>*994805*
>



-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Last updated date in our docs

[Susinda Perera]

WDYT on $subject, then we know how uptodate the doc is.

-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] DataMapper issue

[Susinda Perera]

Yes, In that case it should be string (when we have multiple data types).
This issue is may be due to that we check the data type from json. Fix
should go in that place i believe.

On Tue, Jul 19, 2016 at 9:02 AM, Nuwan Pallewela  wrote:

> Adding Sohani
>
> On Tue, Jul 19, 2016 at 12:42 AM, Godwin Shrimal  wrote:
>
>> Hi All,
>>
>> When load following xml file in to data mapper (input/output), the add1
>> data type takes as NUMBER as in screenshot . It looks when there is at
>> least one record in the array with NUMBER it takes as NUMBER. I think It
>> should consider all the values in the array.
>>
>> 
>> Demo
>> Demo
>>
>> 
>>   
>>   *No 827/B*
>> Gemunu Mawatha
>>   
>>   
>> *321*
>> Mount Lavinia
>>   
>> 
>> 
>>
>> [image: Inline image 2]
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Disable DefaultInboundUserProvisioningListener by default

[Gayan Gunawardana]

Hi All,

Currently if we do not define DefaultIdentityUserProvisioningListener in
 (identity.xml) default behavior is to enable listener.
This behavior is fine if you have outbound provisioning user story but if
you do not have outbound provisioning user story at all, having
DefaultIdentityUserProvisioningListener enable make additional overhead to
all user CRUD operations.

Specially we retrieve Service provider information for each user operation
which is totally unnecessary if there is no outbound provisioning user
story.

Shall we change default behavior to make it disable ?

Thanks,
Gayan

-- 
Gayan Gunawardana
Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] DataMapper issue

[Nuwan Pallewela]

Adding Sohani

On Tue, Jul 19, 2016 at 12:42 AM, Godwin Shrimal  wrote:

> Hi All,
>
> When load following xml file in to data mapper (input/output), the add1
> data type takes as NUMBER as in screenshot . It looks when there is at
> least one record in the array with NUMBER it takes as NUMBER. I think It
> should consider all the values in the array.
>
> 
> Demo
> Demo
>
> 
>   
>   *No 827/B*
> Gemunu Mawatha
>   
>   
> *321*
> Mount Lavinia
>   
> 
> 
>
> [image: Inline image 2]
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Indunil Upeksha Rathnayake]

Hi,

Thanks for the response. As you suggested, It's better to discuss and find
a possible way of implementing this. Shall I arrange a meeting
tomorrow(19/7/2016)? If possible, please let me know an available time slot.

Thanks and Regards

On Mon, Jul 18, 2016 at 11:44 PM, Sriskandarajah Suhothayan 
wrote:

> Hi
>
> Based on the request of IS team we have recently added support for loading
> template files from the registry.
> I think with this feature we can do the mapping at Event Publisher side,
> then IS can send only the core data for the notification. I think building
> the whole message at IS is too much customization for emails.
>
> Please set up a meeting so we can discuss the possible ways to
> implementing this.
>
> Regards
> Suho
>
> On Mon, Jul 18, 2016 at 5:52 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> We are trying to do some improvements to the notification sending module
>> where we have integrated analytics common features in IS, in order to send
>> several notifications (ex:Email, SMS).
>>
>> Current implementation is in [1], there only the email notification was
>> focused where we are directly publishing to the EmailEventAdapter.
>>
>> Now we are trying to send notifications via publishing an event to the
>> Event stream without directly calling an Output Adapter. The approach we
>> have taken is as follows.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *1) In server start up following will be created.i) A stream for each and
>> every notification type including the necessary attributes.Ex: Email
>> Notification - a Stream with the subject, body and footer as attributesii)
>> Event Publishers, registered for each and every stream in the required
>> Output event adapter type. Ex: Email Notification - event Publisher in
>> email output event adapter type.2) Publishing an event to
>> EventStreamService, which includes an arbitrary data map with the necessary
>> data needed for the specific notification type.  Ex: Email Notification
>> - Please find the code segments in [2] for having a better understanding.*
>>
>> There in IS side, we are selecting a specific email template and will be
>> filled out the place holders before sending the subject, body and footer as
>> arbitrary map attributes.
>>
>> But even-though we passed an arbitrary data map, when we are sending an
>> email from the EmailEventAdapter, it won't filter out the subject, body or
>> header from that arbitrary data map.
>> As I have understood, if someone pass an event with an arbitrary data
>> map, the email body will be set as [3] (Refer [4]), it won't filter out the
>> content(Refer [5]).
>> Is this has to be worked if we provide *output mappings* for event
>> publisher as* {{subject}{body}{footer}}* to convert the event to the
>> supported format?
>>
>> I have gone through the code [6], where the event data will be passed
>> through EventStreamProducer, but there also seems like it's not possible
>> to send an email in required format(subject, body and footer).
>>
>> Really appreciate your comments/suggestions to understand the correct
>> approach to be taken.
>>
>> [1]
>> https://github.com/wso2-extensions/identity-event-handler-email/blob/master/components/event-handler-email/org.wso2.carbon.identity.event.handler.email/src/main/java/org.wso2.carbon.identity.event.handler.email/handler/EmailEventHandler.java#L164
>> [2]
>> https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBY00yYVpGelZJNms/view?usp=sharing
>> [3]
>> https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBNEMtYjJvSFB2emM/view?usp=sharing
>> [4]
>> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/type/text/TextOutputMapper.java#L139
>> [5]
>> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/event-output-adapters/org.wso2.carbon.event.output.adapter.email/src/main/java/org/wso2/carbon/event/output/adapter/email/EmailEventAdapter.java#L233
>> [6]
>> https://github.com/wso2/carbon-event-processing/blob/master/components/event-simulator/org.wso2.carbon.event.simulator.core/src/main/java/org/wso2/carbon/event/simulator/core/internal/CarbonEventSimulator.java#L183
>>
>> Thanks and Regards
>> --
>> Indunil Upeksha Rathnayake
>> Software Engineer | WSO2 Inc
>> Emailindu...@wso2.com
>> Mobile   0772182255
>>
>
>
>
> --
>
> *S. Suhothayan*
> Technical Lead & Team Lead of WSO2 Complex Event Processor
> *WSO2 Inc. *http://wso2.com
> * *
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>



-- 
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailind

[Dev] [VOTE] Release WSO2 API Manager 2.0.0 RC2

[Abimaran Kugathasan]

Hi Devs,

*WSO2 API Manager 2.0.0-RC2 Released*

This is the 2nd Release Candidate of the WSO2 API Manager 2.0.0

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Refer to github readme for guides.

The distribution is available to download at [1]

[1] : *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc2
*

*WSO2 **API Manager Analytics 2.0.0 RC2** Released*

This is the 2nd Release Candidate of the WSO2 API Manager Analytics 2.0.0

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Refer to github readme for guides.

The distribution is available to download  [2]

Fixed Issue in [3], known issues [4]

[2] : *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc2
*
[3] : https://wso2.org/jira/issues/?filter=13138
[4] : https://wso2.org/jira/issues/?filter=13139



Please vote as follows.
[+] Stable - go ahead and release
[-]  Broken - do not release (please explain why)

-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer

Email : abima...@wso2.com
Mobile : +94 773922820


  
  
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] WSO2 App Manager 1.2.0 RC2

[Lahiru Cooray]

Hi Devs,

This is the 2nd Release Candidate of the WSO2 App Manager 1.2.0

Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Refer to github readme for guides.

The distribution is available to download at [1]

[1] :
https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC2/wso2appm-1.2.0.zip

Fixed Issue in [2], known issues [3], tag to be vote upon [4]

[2] : https://wso2.org/jira/issues/?filter=13104
[3] : https://wso2.org/jira/issues/?filter=13148
[4] : https://github.com/wso2/carbon-appmgt/tree/v1.2.1

Please vote as follows.
[+] Stable - go ahead and release
[-]  Broken - do not release (please explain why)

Thanks,
App Manager Team

-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] DataMapper issue

[Godwin Shrimal]

Hi All,

When load following xml file in to data mapper (input/output), the add1
data type takes as NUMBER as in screenshot . It looks when there is at
least one record in the array with NUMBER it takes as NUMBER. I think It
should consider all the values in the array.


Demo
Demo


  
  *No 827/B*
Gemunu Mawatha
  
  
*321*
Mount Lavinia
  



[image: Inline image 2]
Thanks
Godwin

-- 
*Godwin Amila Shrimal*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Sriskandarajah Suhothayan]

Hi

Based on the request of IS team we have recently added support for loading
template files from the registry.
I think with this feature we can do the mapping at Event Publisher side,
then IS can send only the core data for the notification. I think building
the whole message at IS is too much customization for emails.

Please set up a meeting so we can discuss the possible ways to implementing
this.

Regards
Suho

On Mon, Jul 18, 2016 at 5:52 PM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi,
>
> We are trying to do some improvements to the notification sending module
> where we have integrated analytics common features in IS, in order to send
> several notifications (ex:Email, SMS).
>
> Current implementation is in [1], there only the email notification was
> focused where we are directly publishing to the EmailEventAdapter.
>
> Now we are trying to send notifications via publishing an event to the
> Event stream without directly calling an Output Adapter. The approach we
> have taken is as follows.
>
>
>
>
>
>
>
>
>
> *1) In server start up following will be created.i) A stream for each and
> every notification type including the necessary attributes.Ex: Email
> Notification - a Stream with the subject, body and footer as attributesii)
> Event Publishers, registered for each and every stream in the required
> Output event adapter type. Ex: Email Notification - event Publisher in
> email output event adapter type.2) Publishing an event to
> EventStreamService, which includes an arbitrary data map with the necessary
> data needed for the specific notification type.  Ex: Email Notification
> - Please find the code segments in [2] for having a better understanding.*
>
> There in IS side, we are selecting a specific email template and will be
> filled out the place holders before sending the subject, body and footer as
> arbitrary map attributes.
>
> But even-though we passed an arbitrary data map, when we are sending an
> email from the EmailEventAdapter, it won't filter out the subject, body or
> header from that arbitrary data map.
> As I have understood, if someone pass an event with an arbitrary data map,
> the email body will be set as [3] (Refer [4]), it won't filter out the
> content(Refer [5]).
> Is this has to be worked if we provide *output mappings* for event
> publisher as* {{subject}{body}{footer}}* to convert the event to the
> supported format?
>
> I have gone through the code [6], where the event data will be passed
> through EventStreamProducer, but there also seems like it's not possible
> to send an email in required format(subject, body and footer).
>
> Really appreciate your comments/suggestions to understand the correct
> approach to be taken.
>
> [1]
> https://github.com/wso2-extensions/identity-event-handler-email/blob/master/components/event-handler-email/org.wso2.carbon.identity.event.handler.email/src/main/java/org.wso2.carbon.identity.event.handler.email/handler/EmailEventHandler.java#L164
> [2]
> https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBY00yYVpGelZJNms/view?usp=sharing
> [3]
> https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBNEMtYjJvSFB2emM/view?usp=sharing
> [4]
> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/type/text/TextOutputMapper.java#L139
> [5]
> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/event-output-adapters/org.wso2.carbon.event.output.adapter.email/src/main/java/org/wso2/carbon/event/output/adapter/email/EmailEventAdapter.java#L233
> [6]
> https://github.com/wso2/carbon-event-processing/blob/master/components/event-simulator/org.wso2.carbon.event.simulator.core/src/main/java/org/wso2/carbon/event/simulator/core/internal/CarbonEventSimulator.java#L183
>
> Thanks and Regards
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
> Mobile   0772182255
>



-- 

*S. Suhothayan*
Technical Lead & Team Lead of WSO2 Complex Event Processor
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Imesh Gunaratne]

On Mon, Jul 18, 2016 at 5:44 PM, Manula Waidyanatha  wrote:


> What is the reason for checking `@clustering['aws']` in every line in
> aws.erb[1] file?
> It doesn't do any harm, but there is no point in checking it since
> aws.erb file is included to axis2.xml.erb only in the aws clustering
> mode.


​Thanks for pointing Manula! It was my mistake!​

On Mon, Jul 18, 2016 at 6:05 PM, Lakmal Warusawithana 
wrote:

> @Imesh, Shall we remove unnecessary if conditions in aws.erb.
>
> ​Yes Lakmal! I fixed it and pushed changes. Please see the latest template
and sample Hiera data config [1], [2]:

[1]
https://github.com/wso2/puppet-modules/blob/master/modules/wso2base/templates/clustering/aws.erb
[2]
https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2bps/3.5.1/default/manager.yaml#L36

Thanks
​


> thanks
>
> On Mon, Jul 18, 2016 at 2:39 PM, Imesh Gunaratne  wrote:
>
>> I just added AWS membership scheme template and a sample configuration to
>> BPS 3.5.1 [1].
>> @Rasanjaya: Would you mind trying this out?
>>
>> [1]
>> https://github.com/wso2/puppet-modules/commit/af14b15d2361f311f6de328141c3ad2cb57428d9
>>
>> Thanks
>>
>> On Mon, Jul 18, 2016 at 2:23 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Devs,
>>>
>>> It looks like we have missed $subject:
>>>
>>> https://github.com/wso2/puppet-modules/tree/master/modules/wso2base/templates/clustering
>>> https://docs.wso2.com/display/CLUSTER44x/Setting+up+a+Cluster+in+AWS+Mode
>>>
>>> Thanks
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>> lean. enterprise. middleware
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lakmal Warusawithana
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Manula Waidyanatha]

Hi Imesh,
What is the reason for checking `@clustering['aws']` in every line in
aws.erb[1] file?
It doesn't do any harm, but there is no point in checking it since
aws.erb file is included to axis2.xml.erb only in the aws clustering
mode.

[1] 
https://github.com/wso2/puppet-modules/blob/af14b15d2361f311f6de328141c3ad2cb57428d9/modules/wso2base/templates/clustering/aws.erb

On Mon, Jul 18, 2016 at 2:39 PM, Imesh Gunaratne  wrote:
> I just added AWS membership scheme template and a sample configuration to
> BPS 3.5.1 [1].
> @Rasanjaya: Would you mind trying this out?
>
> [1]
> https://github.com/wso2/puppet-modules/commit/af14b15d2361f311f6de328141c3ad2cb57428d9
>
> Thanks
>
> On Mon, Jul 18, 2016 at 2:23 PM, Imesh Gunaratne  wrote:
>>
>> Hi Devs,
>>
>> It looks like we have missed $subject:
>>
>> https://github.com/wso2/puppet-modules/tree/master/modules/wso2base/templates/clustering
>> https://docs.wso2.com/display/CLUSTER44x/Setting+up+a+Cluster+in+AWS+Mode
>>
>> Thanks
>>
>> --
>> Imesh Gunaratne
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>
>
>
> --
> Imesh Gunaratne
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Regards,
Manula Waidyanatha
Systems Engineer, WSO2, Inc.
Blog: blog.manula.org
LinkedIn: linkedin.manula.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Lakmal Warusawithana]

@Imesh, Shall we remove unnecessary if conditions in aws.erb.

thanks

On Mon, Jul 18, 2016 at 2:39 PM, Imesh Gunaratne  wrote:

> I just added AWS membership scheme template and a sample configuration to
> BPS 3.5.1 [1].
> @Rasanjaya: Would you mind trying this out?
>
> [1]
> https://github.com/wso2/puppet-modules/commit/af14b15d2361f311f6de328141c3ad2cb57428d9
>
> Thanks
>
> On Mon, Jul 18, 2016 at 2:23 PM, Imesh Gunaratne  wrote:
>
>> Hi Devs,
>>
>> It looks like we have missed $subject:
>>
>> https://github.com/wso2/puppet-modules/tree/master/modules/wso2base/templates/clustering
>> https://docs.wso2.com/display/CLUSTER44x/Setting+up+a+Cluster+in+AWS+Mode
>>
>> Thanks
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lakmal Warusawithana
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Indunil Upeksha Rathnayake]

Hi,

We are trying to do some improvements to the notification sending module
where we have integrated analytics common features in IS, in order to send
several notifications (ex:Email, SMS).

Current implementation is in [1], there only the email notification was
focused where we are directly publishing to the EmailEventAdapter.

Now we are trying to send notifications via publishing an event to the
Event stream without directly calling an Output Adapter. The approach we
have taken is as follows.









*1) In server start up following will be created.i) A stream for each and
every notification type including the necessary attributes.Ex: Email
Notification - a Stream with the subject, body and footer as attributesii)
Event Publishers, registered for each and every stream in the required
Output event adapter type. Ex: Email Notification - event Publisher in
email output event adapter type.2) Publishing an event to
EventStreamService, which includes an arbitrary data map with the necessary
data needed for the specific notification type.  Ex: Email Notification
- Please find the code segments in [2] for having a better understanding.*

There in IS side, we are selecting a specific email template and will be
filled out the place holders before sending the subject, body and footer as
arbitrary map attributes.

But even-though we passed an arbitrary data map, when we are sending an
email from the EmailEventAdapter, it won't filter out the subject, body or
header from that arbitrary data map.
As I have understood, if someone pass an event with an arbitrary data map,
the email body will be set as [3] (Refer [4]), it won't filter out the
content(Refer [5]).
Is this has to be worked if we provide *output mappings* for event
publisher as* {{subject}{body}{footer}}* to convert the event to the
supported format?

I have gone through the code [6], where the event data will be passed
through EventStreamProducer, but there also seems like it's not possible to
send an email in required format(subject, body and footer).

Really appreciate your comments/suggestions to understand the correct
approach to be taken.

[1]
https://github.com/wso2-extensions/identity-event-handler-email/blob/master/components/event-handler-email/org.wso2.carbon.identity.event.handler.email/src/main/java/org.wso2.carbon.identity.event.handler.email/handler/EmailEventHandler.java#L164
[2]
https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBY00yYVpGelZJNms/view?usp=sharing
[3]
https://drive.google.com/a/wso2.com/file/d/0Bz_EQkE2mOgBNEMtYjJvSFB2emM/view?usp=sharing
[4]
https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/type/text/TextOutputMapper.java#L139
[5]
https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/event-output-adapters/org.wso2.carbon.event.output.adapter.email/src/main/java/org/wso2/carbon/event/output/adapter/email/EmailEventAdapter.java#L233
[6]
https://github.com/wso2/carbon-event-processing/blob/master/components/event-simulator/org.wso2.carbon.event.simulator.core/src/main/java/org/wso2/carbon/event/simulator/core/internal/CarbonEventSimulator.java#L183

Thanks and Regards
-- 
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailindu...@wso2.com
Mobile   0772182255
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update - Provide runtime environment for jaggery apps in AS6

[Sinthuja Ragendran]

Hi KasunG,

On Mon, Jul 18, 2016 at 5:31 PM, KasunG Gajasinghe  wrote:

>
>
> On Mon, Jul 18, 2016 at 2:45 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi KasunG,
>>
>> Yes.This is the branch. Currently we are maintaining two branches as this
>> tomcat version(tomcat 8) will not work with carbon 4.4.x products due to
>> the tomcat API changes.
>>
>
>
>> So we have to maintain two branches now. But we will move the current
>> master to branch 0.12.x branch and merger tomcat-8.0.x-jaggery to master.
>> Then its a two different versions, not a feature branch.
>>
>
> Since the code bases are pretty similar, it would be much better if these
> two can be merged together instead! What are the possible alternatives we
> have?
>

As there are many API changes in the tomcat level, and we have removed all
carbon dependencies from the jaggery-core due to the tomcat integration
effort. Also some of the host objects such as registry, database, etc which
are based on carbon are moved out of jaggery core during this. Therefore I
don't think it's very easy to merge all these together as it will just
impose more complicated code, and many if conditions.


>
> Maintaining two different branches in the same repo would mean that we
> will need to have two major versions. One for the existing development, and
> another for the new development.
>

Not really, in the jaggery perspective we are not doing any active
development or feature implementation. And once all our products have moved
to away from carbon 4.4.x, the 0.12.x branch will not be used. Therefore I
don't see much issue on having two branches.

Thanks,
Sinthuja.


>
> Thanks,
> KasunG
>
>
>> Thanks,
>> Nisala
>>
>> On Mon, Jul 18, 2016 at 2:05 PM, KasunG Gajasinghe 
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> On Thu, Jun 30, 2016 at 7:17 AM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi all,

 Please find the branch here.

 [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery

>>>
>>>
>>> From what I understood, this is a feature branch, is it not? Then, this
>>> does not really need a separate jenkins job since you will merge this into
>>> master soon. Please note that, you shouldn't have two diverged features in
>>> branches of the same repo.
>>>
>>> Thanks,
>>> KasunG
>>>
>>>

 Thanks,
 Nisala

 On Thu, Jun 30, 2016 at 7:12 AM, Nisala Nanayakkara 
 wrote:

> Hi all,
>
> We have created a seperate branch[1] with the changes required for
> providing runtime environment for jaggery apps in AS6. Currently there is
> no jenkins builder setup for this, Please get the 1.0.0-SNAPSHOT version 
> by
> building the branch in local repo. Please inform me if there are any 
> issues.
>
> Thanks,
> Nisala
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>



 --
 *Nisala Niroshana Nanayakkara,*
 Software Engineer
 Mobile:(+94)717600022
 WSO2 Inc., http://wso2.com/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>
>>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>>> email: kasung AT spamfree wso2.com
>>> linked-in: http://lk.linkedin.com/in/gajasinghe
>>> blog: http://kasunbg.org
>>>
>>>
>>>
>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile:(+94)717600022
>> WSO2 Inc., http://wso2.com/
>>
>
>
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sinthuja Rajendran*
Technical Lead
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update - Provide runtime environment for jaggery apps in AS6

[KasunG Gajasinghe]

On Mon, Jul 18, 2016 at 2:45 PM, Nisala Nanayakkara  wrote:

> Hi KasunG,
>
> Yes.This is the branch. Currently we are maintaining two branches as this
> tomcat version(tomcat 8) will not work with carbon 4.4.x products due to
> the tomcat API changes.
>


> So we have to maintain two branches now. But we will move the current
> master to branch 0.12.x branch and merger tomcat-8.0.x-jaggery to master.
> Then its a two different versions, not a feature branch.
>

Since the code bases are pretty similar, it would be much better if these
two can be merged together instead! What are the possible alternatives we
have?

Maintaining two different branches in the same repo would mean that we will
need to have two major versions. One for the existing development, and
another for the new development.

Thanks,
KasunG


> Thanks,
> Nisala
>
> On Mon, Jul 18, 2016 at 2:05 PM, KasunG Gajasinghe 
> wrote:
>
>> Hi Nisala,
>>
>> On Thu, Jun 30, 2016 at 7:17 AM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi all,
>>>
>>> Please find the branch here.
>>>
>>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>>
>>
>>
>> From what I understood, this is a feature branch, is it not? Then, this
>> does not really need a separate jenkins job since you will merge this into
>> master soon. Please note that, you shouldn't have two diverged features in
>> branches of the same repo.
>>
>> Thanks,
>> KasunG
>>
>>
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Thu, Jun 30, 2016 at 7:12 AM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi all,

 We have created a seperate branch[1] with the changes required for
 providing runtime environment for jaggery apps in AS6. Currently there is
 no jenkins builder setup for this, Please get the 1.0.0-SNAPSHOT version by
 building the branch in local repo. Please inform me if there are any 
 issues.

 Thanks,
 Nisala

 --
 *Nisala Niroshana Nanayakkara,*
 Software Engineer
 Mobile:(+94)717600022
 WSO2 Inc., http://wso2.com/

>>>
>>>
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>>
>>
>>
>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>



-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 AS integration with TomEE

[Kishanthan Thangarajah]

On Mon, Jul 18, 2016 at 11:55 AM, Lakshman Udayakantha 
wrote:

> Hi,
>
> As a part of this we will migrate samples and test cases from AS 5.3.0.
> There are 45+ samples in AS 5.3.0. As per the offline chat with KasunG, It
> will exclude axis2 samples from migration. Other JaxWS-RS, JavaEE samples
> etc. and relevant test cases will be include in new AS.
>

+1.

These samples will be shipped with AS and we also need to provide the
similar ant run script / maven to build and deploy them.


> Thanks
>
> On Fri, Jul 15, 2016 at 10:50 AM, Lakshman Udayakantha  > wrote:
>
>> [Adding KalpaW]
>>
>> On Thu, Jul 14, 2016 at 10:05 PM, Lakshman Udayakantha <
>> lakshm...@wso2.com> wrote:
>>
>>> Pull request is in [1]
>>>
>>> [1] https://github.com/wso2/product-as/pull/351
>>>
>>> Thanks
>>>
>>> On Thu, Jul 14, 2016 at 10:04 PM, Lakshman Udayakantha <
>>> lakshm...@wso2.com> wrote:
>>>
 Hi Carbon Team,

 Could you review and merge the pull which is done for the TomEE
 integration? After the offline discussion with KasunG, added a dummy
 runtime as well.

 Thanks

 On Thu, Jul 14, 2016 at 4:34 PM, KasunG Gajasinghe 
 wrote:

>
>
> On Thu, Jul 14, 2016 at 4:27 PM, Lakshman Udayakantha <
> lakshm...@wso2.com> wrote:
>
>> Hi KasunG,
>>
>> This was almost done except jaxrs_basic web app not deploying
>> properly. Got exception [1]. Anyway I checked for the class which says 
>> CNF
>> and it was there in classpath.  This jaxrs_basic  web app needs CXF 
>> runtime
>> jars and this web app using to demonstrate custom runtime environment
>> support. Anyhow TomEE already bundling CXF runtime, it seems not
>> appropriate CXF as a separate runtime. right?.
>>
>
> Yes, that seems to be the case. Since CXF is coming from TomEE, CXF is
> not needed as a runtime. But, TomEE only packs CXF's jax-rs related libs.
> We need to ship jax-ws libs as well.
>
>
>> How about creating a separate run time rather than CXF and creating
>> another web app to test that and bundling current CXF jars in lib itself?
>>
>> [1]  SEVERE [localhost-startStop-1]
>> org.apache.catalina.core.StandardContext.listenerStart Exception sending
>> context initialized event to listener instance of class
>> org.springframework.web.context.ContextLoaderListener
>>
>>  org.springframework.beans.factory.BeanDefinitionStoreException:
>> Unexpected exception parsing XML document from ServletContext resource
>> [/WEB-INF/customBeans.xml]; nested exception is
>> org.springframework.beans.FatalBeanException: Invalid NamespaceHandler
>> class [org.apache.cxf.jaxrs.spring.NamespaceHandler] for namespace [
>> http://cxf.apache.org/jaxrs]: problem with handler class file or
>> dependent class; nested exception is java.lang.NoClassDefFoundError:
>> org/springframework/beans/factory/xml/NamespaceHandlerSupport
>>
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:414)
>>
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
>>
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
>>
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181)
>>
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217)
>>
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188)
>>
>> at
>> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125)
>>
>> at
>> org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:94)
>>
>> at
>> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129)
>>
>> at
>> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:609)
>>
>> at
>> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:510)
>>
>> at
>> org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:444)
>>
>> at
>> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:326)
>>
>> at
>> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107)
>>
>> at

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Akila Ravihansa Perera]

Hi Imesh,

I've switched to command based health check for MySQL services. It will
basically run "mysqladmin -u $MYSQL_USER -p$MYSQL_PASSWORD status". This
will ensure MySQL service is ready to serve SQL requests.

Thanks.

On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne  wrote:

>
>
> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi,
>>
>> Yes, myself and Pubudu also faced this issue, lets fix it properly.
>>
>> On Wed, Jul 6, 2016 at 10:57 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Akila,
>>>
>>> Yes we faced several issues related to this. Apart from what you have
>>> mentioned, we encountered mysql app name is not getting resolved. This
>>> could be the delay in updating Mesos DNS. For these issues we looking into
>>> following options.
>>>
>>> *Option 1:*
>>> Use a sleep before deploying a carbon server. Not the best option.
>>>
>>> *Option 2:*
>>> Depend on the health status results.
>>>
>>> Currently, we do use a health check for mysql apps. Using dcos CLI we
>>> can check the status of the app whether the app is alive or not. But this
>>> cannot guarantee the DBs are ready to serve requests and Mesos DNS is
>>> updated.
>>>
>>
>
>> What if we query the Mesos DNS in addition to port checking to see if its
>> updated? AFAIR what we are seeing is an java.net.UnknownHostException,
>> related to the DB hostname.
>>
>
> ​May be we can wait for MySQL sockets as we do for Carbon server
> transports.
>
> Thanks​
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

Blog: http://ravihansa3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Bhaviour of OIDC 'prompt=none' when logged in

[Hasanthi Purnima Dissanayake]

Hi Johann,

No the spec directly says 'If does not have *per-configured consent*'.
Those days when we were implementing this we interpreted per-configured
session as 'approve-always' or file based 'skip-consent=true'.

Anyway I will raise this to OIDC community.

Thanks,

Hasanthi Dissanayake

Software Engineer | WSO2

E: hasan...@wso2.com
M :0718407133| http://wso2.com 

On Mon, Jul 18, 2016 at 4:11 PM, Johann Nallathamby  wrote:

> Hmm.. does the spec say anything related to this. If not better we send a
> mail to OIDC community and check this out. But if the compliance tests are
> failing lets go ahead with this new behaviour but let's introduce a
> property to turn back the old behaviour and make the new the default.
>
> On Mon, Jul 18, 2016 at 4:05 PM, Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi All,
>> According to the spec [1] when prompt=none the result should as below.
>>
>>> The Authorization Server MUST NOT display any authentication or consent
>>> user interface pages. An error is returned if an End-User is not already
>>> authenticated or the Client does not have per-configured consent for the
>>> requested Claims or does not fulfill other conditions for processing the
>>> request
>>
>>
>> So if we consider a scenario like
>> 1. User sends authorization request without any prompt value to the IS
>> server
>> 2. Server gives the login page
>> 3. User provides credentials
>> 4. Authentication successful and server returns consent page
>> 5. User provides consent as 'Approve'
>> 6. User send a authorization request with prompt =none
>>
>> According to our current implementation it gives an error page with
>> consent-required error as the server does not have "trusted_always" in the
>> db table or "skipConsent=true" in file. But when executing the OIDC
>> compliance test cases in such a scenario it expects this as a successful
>> authentication as we have set the consent as approve in the same session.
>>
>> So if we are doing this we need to skip the consent page if the their is
>> a session with consent=approve. Do we need to change our implementation
>> according to this? Any suggestions will be highly appreciated.
>>
>>
>> The output of the test case is as below.
>> Trace output
>>
>>
>> 0.000497  AuthorizationRequest 
>> 0.000903 --> URL: 
>> https://210.90.95.XXX:9443/oauth2/authorize?scope=openid&state=hwcw3vhktnBaM99R&redirect_uri=https%3A%2F%2Fop.certification.openid.net%3A60746%2Fauthz_cb&response_type=code&client_id=4rYClwGnY4CE_XXAkMCoWuI4mnIa
>> 0.000910 --> BODY: None
>> 70.472175 <-- 
>> code=de0696cf-7183-3c31-a13c-92695101e589&state=hwcw3vhktnBaM99R&session_state=927dc2d850b486e4a5d76a5f0d0dd3c1829b4e0007e11e58b1a9fbf17a3fff18._ynyYSwWWERr2-QI1X8sDg
>> 70.472683 AuthorizationResponse: {
>>   "code": "de0696cf-7183-3c31-a13c-92695101e589",
>>   "session_state": 
>> "927dc2d850b486e4a5d76a5f0d0dd3c1829b4e0007e11e58b1a9fbf17a3fff18._ynyYSwWWERr2-QI1X8sDg",
>>   "state": "hwcw3vhktnBaM99R"
>> }
>> 70.473121  AccessTokenRequest 
>> 70.473556 --> URL: https://210.90.95.XXX:9443/oauth2/token
>> 70.473561 --> BODY: 
>> code=de0696cf-7183-3c31-a13c-92695101e589&grant_type=authorization_code&redirect_uri=https%3A%2F%2Fop.certification.openid.net%3A60746%2Fauthz_cb
>> 70.473575 --> HEADERS: {'Content-Type': 'application/x-www-form-urlencoded', 
>> 'Authorization': u'Basic 
>> NHJZQ2x3R25ZNENFX1hYQWtNQ29XdUk0bW5JYTpBdE8wenhmNjJLb1lhc1lUb2JPR1JYVlJaWHNh'}
>> 74.644260 <-- STATUS: 200
>> 74.644479 <-- BODY: 
>> {"access_token":"399d4582-967f-3083-831e-f5c4a6665e4a","refresh_token":"e9f533c3-a867-3758-8edc-2c10b2be0cd3","scope":"openid","id_token":"eyJ4NXQiOiJObUptT0dVeE16WmxZak0yWkRSaE5UWmxZVEExWXpkaFpUUmlPV0UwTldJMk0ySm1PVGMxWkEiLCJraWQiOiIxNTA4MzI3Zjg1M2RlODkzZWVhYTg2YzIwMTUyNjg5NWQxZTk1MTQzIiwiYWxnIjoiUlMyNTYifQ.eyJhdF9oYXNoIjoiQ1dSTWNFSkNDUURWeUtGMVlDWklmZyIsInN1YiI6ImFkbWluIiwiYXVkIjpbIjRyWUNsd0duWTRDRV9YWEFrTUNvV3VJNG1uSWEiXSwiYXpwIjoiNHJZQ2x3R25ZNENFX1hYQWtNQ29XdUk0bW5JYSIsImF1dGhfdGltZSI6MTQ2ODgzNTEwMCwiaXNzIjoiaHR0cHM6XC9cLzIwMy45NC45NS4yMTU6OTQ0M1wvIiwiZXhwIjoxNDY4ODM5OTQ0LCJpYXQiOjE0Njg4MzYzNDR9.M3Er8G4M05JPXmm-YOsOVcimGrzr9GwSmKeqGQBMTP0ZCpJ9NlFN-SR5HJ9xcH8Tc-dh201euilqPLzkfq2annbIS8V7gkS2ttnryjp0eTDIX3p4gKoLo1HfEARb4iB6r6ovDIzqytYMPacZj5t7uxBxSz2Aiu6qjkNOb5uY7Ss","token_type":"Bearer","expires_in":2056}
>> 76.777209 AccessTokenResponse: {
>>   "access_token": "399d4582-967f-3083-831e-f5c4a6665e4a",
>>   "expires_in": 2056,
>>   "id_token": {
>> "claims": {
>>   "at_hash": "CWRMcEJCCQDVyKF1YCZIfg",
>>   "aud": [
>> "4rYClwGnY4CE_XXAkMCoWuI4mnIa"
>>   ],
>>   "auth_time": 1468835100,
>>   "azp": "4rYClwGnY4CE_XXAkMCoWuI4mnIa",
>>   "exp": 1468839944,
>>   "iat": 1468836344,
>>   "iss": "https://210.90.95.XXX:9443/";,
>>   "sub": "admin"
>> },
>> "jws header parameters": {
>>   "alg": "RS256",
>>   "kid": "1508327f853de893eeaa86c20152

[Dev] AS 6.0.0 SSO Quick Start Guide

[Kishanthan Thangarajah]

Hi ChanakaS,

Let's work on $subject. Basically, what we need is to provide minimum
number of steps needed to get an SSO sample working with AS and IS.

Requirements.

   1. A script to automate the IS side configuration (setting up the SP and
   stuffs)
   2. A webapp sample at AS side with all the configuration setup and
   script to automatically build and/or directly deploy.

We can perform the above with the single script. Users do not have to do
any config changes, but they would just execute the script/goal which would
perform above tasks and its related sub tasks. With this, we can come up
with the structure for all the quick start sample guides to follow from AS
side.

Thanks,

-- 
*Kishanthan Thangarajah*
Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

This is the progress so far.

*Auto scaling*


Azure supports two paradigms of auto scaling, vertical and horizontal.
Vertical scaling, also known as scale up and scale down, means increasing
or decreasing virtual machine (VM) sizes in response to a workload. As I
explained in one of my previous emails, vertical auto scaling is achieved
through monitoring rules. We can set it to trigger an alarm when certain
conditions are met and also as the action we can set up a runbook to scale
up or down. I could successfully get VMs to scale up and down using this
feature.


Horizontal scaling, also referred to as scale out and scale in, where the
number of VMs is altered depending on the workload. Horizontal scaling is
achieved through virtual machine scale sets (VMSS). One important thing
about VMSS is that the VMs included should be of the same size and have the
same OS image. All the VMs in the scale set are added to the load balancer,
as a backend pool. Backend pool is a pool of VMs which share the traffic
coming via the load balancer. We can add auto scale rules, as to when
additional VMs should be added and removed, based on the conditions. I
could test some auto scale rules and observed VMs getting added to the
backend pool. But one problem is that when these VMs getting added, it’s a
whole new VM.  I’m trying to add custom made VMs which has a wso2 product
installed and configured.


Note: only a limited horizontal scaling features are supported in the azure
portal yet so I’m using REST API to create and manage auto scaling features.


*Centralized logging*


I was able to get log to Log Analytics using custom logs. I have collected
logs generated from 2 wso2 application servers. You only have to add
respective VMs to the Log analytics and set the path where logs are
located. This feature was under public preview, which might have been one
reason why it didn’t work last time when I tried.


Thanks,

On Mon, Jul 18, 2016 at 8:21 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Please accept my apologies I have messed up names in my last email. I'm
> not going to be available today due to an unavoidable circumstance so can
> we please have the meeting on Wednesday? Extremely sorry if it made any
> inconvenience. I will update you with a detailed email today for sure.
>
> Thanks in advance,
>
> On Fri, Jul 15, 2016 at 4:04 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Can you send a detailed updated on the current status? Shall we have a
>> meeting on Monday to review the progress.
>>
>> On Tue, Jul 12, 2016 at 2:03 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> About dynamically adding members to the load balancer, I will cross
>>> check it with auto-scaling. I couldn't look into that from auto-scaling end
>>> since I couldn't test it yet.
>>>
>>> about monitoring, yes we can do a POC on that.
>>>
>>> thanks,
>>>
>>> On Tue, Jul 12, 2016 at 12:53 PM, Imesh Gunaratne 
>>> wrote:
>>>
 On Tue, Jul 12, 2016 at 12:09 PM, Osura Rathnayake 
 wrote:

> Hi Imesh,
>
> About centralized logging, I'm trying to get logs to the Log Analytics
> using few methods supported in azure. We can either parse logs in to
> syslogs and send to the Log Analytics or create custom logs specifying the
> logs location. As you said, logs shouldn't be in .txt extension, I got it
> clarified from a azure blog. Will update you soon after I could resolve 
> it.
>
> ​Right, thanks for the update!​


> No you can't dynamically add VMs to the load balancer. Backend pool,
> where all the VMs reside, should be predefined.
>

 ​Technically that capability should be there. Otherwise we would not be
 able to autoscale a server cluster dynamically.
 ​


> you can auto-scale using scale sets(I'm still researching about it),
> that's the equivalent of AWS auto scaling group . also you can scale up or
> down a VM if it exceeds a certain parameter like CPU usage, using
> monitoring rules.
>
> *Monitoring *
>
>
> Azure has a native monitoring tool which involves collecting and
> tracking metrics, analyzing log files, defining custom metrics and logging
> generated by specific applications or workloads running in Virtual
> Machines. Azure represents monitored data in a graphical manner using
> charts. Monitoring also facilitates triggering alarms when certain
> conditions are met and also it can be configured to take actions on the 
> met
> conditions. Monitoring is done by the Diagnostic Extension and it has
> following capabilities.
>
> · Collects and uploads the system performance information
> from the Linux VM to the user's storage table, including diagnostic and
> syslog information.
>
> · Enables users to customize the data metrics that will be
> collected and uploaded.
>
> · Enables users to upload specif

Re: [Dev] Bhaviour of OIDC 'prompt=none' when logged in

[Johann Nallathamby]

Hmm.. does the spec say anything related to this. If not better we send a
mail to OIDC community and check this out. But if the compliance tests are
failing lets go ahead with this new behaviour but let's introduce a
property to turn back the old behaviour and make the new the default.

On Mon, Jul 18, 2016 at 4:05 PM, Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:

> Hi All,
> According to the spec [1] when prompt=none the result should as below.
>
>> The Authorization Server MUST NOT display any authentication or consent
>> user interface pages. An error is returned if an End-User is not already
>> authenticated or the Client does not have per-configured consent for the
>> requested Claims or does not fulfill other conditions for processing the
>> request
>
>
> So if we consider a scenario like
> 1. User sends authorization request without any prompt value to the IS
> server
> 2. Server gives the login page
> 3. User provides credentials
> 4. Authentication successful and server returns consent page
> 5. User provides consent as 'Approve'
> 6. User send a authorization request with prompt =none
>
> According to our current implementation it gives an error page with
> consent-required error as the server does not have "trusted_always" in the
> db table or "skipConsent=true" in file. But when executing the OIDC
> compliance test cases in such a scenario it expects this as a successful
> authentication as we have set the consent as approve in the same session.
>
> So if we are doing this we need to skip the consent page if the their is a
> session with consent=approve. Do we need to change our implementation
> according to this? Any suggestions will be highly appreciated.
>
>
> The output of the test case is as below.
> Trace output
>
>
> 0.000497  AuthorizationRequest 
> 0.000903 --> URL: 
> https://210.90.95.XXX:9443/oauth2/authorize?scope=openid&state=hwcw3vhktnBaM99R&redirect_uri=https%3A%2F%2Fop.certification.openid.net%3A60746%2Fauthz_cb&response_type=code&client_id=4rYClwGnY4CE_XXAkMCoWuI4mnIa
> 0.000910 --> BODY: None
> 70.472175 <-- 
> code=de0696cf-7183-3c31-a13c-92695101e589&state=hwcw3vhktnBaM99R&session_state=927dc2d850b486e4a5d76a5f0d0dd3c1829b4e0007e11e58b1a9fbf17a3fff18._ynyYSwWWERr2-QI1X8sDg
> 70.472683 AuthorizationResponse: {
>   "code": "de0696cf-7183-3c31-a13c-92695101e589",
>   "session_state": 
> "927dc2d850b486e4a5d76a5f0d0dd3c1829b4e0007e11e58b1a9fbf17a3fff18._ynyYSwWWERr2-QI1X8sDg",
>   "state": "hwcw3vhktnBaM99R"
> }
> 70.473121  AccessTokenRequest 
> 70.473556 --> URL: https://210.90.95.XXX:9443/oauth2/token
> 70.473561 --> BODY: 
> code=de0696cf-7183-3c31-a13c-92695101e589&grant_type=authorization_code&redirect_uri=https%3A%2F%2Fop.certification.openid.net%3A60746%2Fauthz_cb
> 70.473575 --> HEADERS: {'Content-Type': 'application/x-www-form-urlencoded', 
> 'Authorization': u'Basic 
> NHJZQ2x3R25ZNENFX1hYQWtNQ29XdUk0bW5JYTpBdE8wenhmNjJLb1lhc1lUb2JPR1JYVlJaWHNh'}
> 74.644260 <-- STATUS: 200
> 74.644479 <-- BODY: 
> {"access_token":"399d4582-967f-3083-831e-f5c4a6665e4a","refresh_token":"e9f533c3-a867-3758-8edc-2c10b2be0cd3","scope":"openid","id_token":"eyJ4NXQiOiJObUptT0dVeE16WmxZak0yWkRSaE5UWmxZVEExWXpkaFpUUmlPV0UwTldJMk0ySm1PVGMxWkEiLCJraWQiOiIxNTA4MzI3Zjg1M2RlODkzZWVhYTg2YzIwMTUyNjg5NWQxZTk1MTQzIiwiYWxnIjoiUlMyNTYifQ.eyJhdF9oYXNoIjoiQ1dSTWNFSkNDUURWeUtGMVlDWklmZyIsInN1YiI6ImFkbWluIiwiYXVkIjpbIjRyWUNsd0duWTRDRV9YWEFrTUNvV3VJNG1uSWEiXSwiYXpwIjoiNHJZQ2x3R25ZNENFX1hYQWtNQ29XdUk0bW5JYSIsImF1dGhfdGltZSI6MTQ2ODgzNTEwMCwiaXNzIjoiaHR0cHM6XC9cLzIwMy45NC45NS4yMTU6OTQ0M1wvIiwiZXhwIjoxNDY4ODM5OTQ0LCJpYXQiOjE0Njg4MzYzNDR9.M3Er8G4M05JPXmm-YOsOVcimGrzr9GwSmKeqGQBMTP0ZCpJ9NlFN-SR5HJ9xcH8Tc-dh201euilqPLzkfq2annbIS8V7gkS2ttnryjp0eTDIX3p4gKoLo1HfEARb4iB6r6ovDIzqytYMPacZj5t7uxBxSz2Aiu6qjkNOb5uY7Ss","token_type":"Bearer","expires_in":2056}
> 76.777209 AccessTokenResponse: {
>   "access_token": "399d4582-967f-3083-831e-f5c4a6665e4a",
>   "expires_in": 2056,
>   "id_token": {
> "claims": {
>   "at_hash": "CWRMcEJCCQDVyKF1YCZIfg",
>   "aud": [
> "4rYClwGnY4CE_XXAkMCoWuI4mnIa"
>   ],
>   "auth_time": 1468835100,
>   "azp": "4rYClwGnY4CE_XXAkMCoWuI4mnIa",
>   "exp": 1468839944,
>   "iat": 1468836344,
>   "iss": "https://210.90.95.XXX:9443/";,
>   "sub": "admin"
> },
> "jws header parameters": {
>   "alg": "RS256",
>   "kid": "1508327f853de893eeaa86c201526895d1e95143",
>   "x5t": "NmJmOGUxMzZlYjM2ZDRhNTZlYTA1YzdhZTRiOWE0NWI2M2JmOTc1ZA"
> }
>   },
>   "refresh_token": "e9f533c3-a867-3758-8edc-2c10b2be0cd3",
>   "scope": "openid",
>   "token_type": "Bearer"
> }
> 76.788640  AuthorizationRequest 
> 76.789114 --> URL: 
> https://210.90.95.XXX:9443/oauth2/authorize?prompt=none&state=AstNRnS88v73aAjI&redirect_uri=https%3A%2F%2Fop.certification.openid.net%3A60746%2Fauthz_cb&response_type=code&client_id=4rYClwGnY4CE_XXAkMCoWuI4mnIa&scope=openid
> 76.789121 --> BOD

[Dev] Bhaviour of OIDC 'prompt=none' when logged in

[Hasanthi Purnima Dissanayake]

Hi All,
According to the spec [1] when prompt=none the result should as below.

> The Authorization Server MUST NOT display any authentication or consent
> user interface pages. An error is returned if an End-User is not already
> authenticated or the Client does not have per-configured consent for the
> requested Claims or does not fulfill other conditions for processing the
> request


So if we consider a scenario like
1. User sends authorization request without any prompt value to the IS
server
2. Server gives the login page
3. User provides credentials
4. Authentication successful and server returns consent page
5. User provides consent as 'Approve'
6. User send a authorization request with prompt =none

According to our current implementation it gives an error page with
consent-required error as the server does not have "trusted_always" in the
db table or "skipConsent=true" in file. But when executing the OIDC
compliance test cases in such a scenario it expects this as a successful
authentication as we have set the consent as approve in the same session.

So if we are doing this we need to skip the consent page if the their is a
session with consent=approve. Do we need to change our implementation
according to this? Any suggestions will be highly appreciated.


The output of the test case is as below.
Trace output


0.000497  AuthorizationRequest 
0.000903 --> URL:
https://210.90.95.XXX:9443/oauth2/authorize?scope=openid&state=hwcw3vhktnBaM99R&redirect_uri=https%3A%2F%2Fop.certification.openid.net%3A60746%2Fauthz_cb&response_type=code&client_id=4rYClwGnY4CE_XXAkMCoWuI4mnIa
0.000910 --> BODY: None
70.472175 <-- 
code=de0696cf-7183-3c31-a13c-92695101e589&state=hwcw3vhktnBaM99R&session_state=927dc2d850b486e4a5d76a5f0d0dd3c1829b4e0007e11e58b1a9fbf17a3fff18._ynyYSwWWERr2-QI1X8sDg
70.472683 AuthorizationResponse: {
  "code": "de0696cf-7183-3c31-a13c-92695101e589",
  "session_state":
"927dc2d850b486e4a5d76a5f0d0dd3c1829b4e0007e11e58b1a9fbf17a3fff18._ynyYSwWWERr2-QI1X8sDg",
  "state": "hwcw3vhktnBaM99R"
}
70.473121  AccessTokenRequest 
70.473556 --> URL: https://210.90.95.XXX:9443/oauth2/token
70.473561 --> BODY:
code=de0696cf-7183-3c31-a13c-92695101e589&grant_type=authorization_code&redirect_uri=https%3A%2F%2Fop.certification.openid.net%3A60746%2Fauthz_cb
70.473575 --> HEADERS: {'Content-Type':
'application/x-www-form-urlencoded', 'Authorization': u'Basic
NHJZQ2x3R25ZNENFX1hYQWtNQ29XdUk0bW5JYTpBdE8wenhmNjJLb1lhc1lUb2JPR1JYVlJaWHNh'}
74.644260 <-- STATUS: 200
74.644479 <-- BODY:
{"access_token":"399d4582-967f-3083-831e-f5c4a6665e4a","refresh_token":"e9f533c3-a867-3758-8edc-2c10b2be0cd3","scope":"openid","id_token":"eyJ4NXQiOiJObUptT0dVeE16WmxZak0yWkRSaE5UWmxZVEExWXpkaFpUUmlPV0UwTldJMk0ySm1PVGMxWkEiLCJraWQiOiIxNTA4MzI3Zjg1M2RlODkzZWVhYTg2YzIwMTUyNjg5NWQxZTk1MTQzIiwiYWxnIjoiUlMyNTYifQ.eyJhdF9oYXNoIjoiQ1dSTWNFSkNDUURWeUtGMVlDWklmZyIsInN1YiI6ImFkbWluIiwiYXVkIjpbIjRyWUNsd0duWTRDRV9YWEFrTUNvV3VJNG1uSWEiXSwiYXpwIjoiNHJZQ2x3R25ZNENFX1hYQWtNQ29XdUk0bW5JYSIsImF1dGhfdGltZSI6MTQ2ODgzNTEwMCwiaXNzIjoiaHR0cHM6XC9cLzIwMy45NC45NS4yMTU6OTQ0M1wvIiwiZXhwIjoxNDY4ODM5OTQ0LCJpYXQiOjE0Njg4MzYzNDR9.M3Er8G4M05JPXmm-YOsOVcimGrzr9GwSmKeqGQBMTP0ZCpJ9NlFN-SR5HJ9xcH8Tc-dh201euilqPLzkfq2annbIS8V7gkS2ttnryjp0eTDIX3p4gKoLo1HfEARb4iB6r6ovDIzqytYMPacZj5t7uxBxSz2Aiu6qjkNOb5uY7Ss","token_type":"Bearer","expires_in":2056}
76.777209 AccessTokenResponse: {
  "access_token": "399d4582-967f-3083-831e-f5c4a6665e4a",
  "expires_in": 2056,
  "id_token": {
"claims": {
  "at_hash": "CWRMcEJCCQDVyKF1YCZIfg",
  "aud": [
"4rYClwGnY4CE_XXAkMCoWuI4mnIa"
  ],
  "auth_time": 1468835100,
  "azp": "4rYClwGnY4CE_XXAkMCoWuI4mnIa",
  "exp": 1468839944,
  "iat": 1468836344,
  "iss": "https://210.90.95.XXX:9443/";,
  "sub": "admin"
},
"jws header parameters": {
  "alg": "RS256",
  "kid": "1508327f853de893eeaa86c201526895d1e95143",
  "x5t": "NmJmOGUxMzZlYjM2ZDRhNTZlYTA1YzdhZTRiOWE0NWI2M2JmOTc1ZA"
}
  },
  "refresh_token": "e9f533c3-a867-3758-8edc-2c10b2be0cd3",
  "scope": "openid",
  "token_type": "Bearer"
}
76.788640  AuthorizationRequest 
76.789114 --> URL:
https://210.90.95.XXX:9443/oauth2/authorize?prompt=none&state=AstNRnS88v73aAjI&redirect_uri=https%3A%2F%2Fop.certification.openid.net%3A60746%2Fauthz_cb&response_type=code&client_id=4rYClwGnY4CE_XXAkMCoWuI4mnIa&scope=openid
76.789121 --> BODY: None
108.266371 <-- 
code=684a2084-b823-35fc-baed-d73fdb6a9694&state=AstNRnS88v73aAjI&session_state=62a0bd33903999d7245654681f715e9700377e6b5ccaaf84ecb98b40311d8214.9iW0pFCokaZQXs4mZAp1jg
108.266883 AuthorizationResponse: {
  "code": "684a2084-b823-35fc-baed-d73fdb6a9694",
  "session_state":
"62a0bd33903999d7245654681f715e9700377e6b5ccaaf84ecb98b40311d8214.9iW0pFCokaZQXs4mZAp1jg",
  "state": "AstNRnS88v73aAjI"
}
108.268413  AccessTokenRequest 
108.268842 --> URL: https://210.90.95.XXX:9443/oauth2/token
108.26884

Re: [Dev] [DAS] Setting akka Configuration Properties

[Isuru Haththotuwa]

Many thanks Niranda. But seems this is available from akka 2.4.x [1], while
DAS is using org.spark.project.akka*2.3.4.

[1].
http://doc.akka.io/docs/akka/2.4-M2/general/remoting.html#Peer-to-Peer_vs__Client-Server

On Mon, Jul 18, 2016 at 1:21 PM, Niranda Perera  wrote:

> Hi Isuru,
>
> I checked the Spark docs but it is not publicly documented, but if you
> check here [1], akka settings can be set in the spark conf. So, you should
> be able to set those configs in the spark-defaults.conf file in
> repository/conf/analytics/spark dir.
>
> Best
>
> [1]
> https://github.com/apache/spark/blob/branch-1.4/core/src/main/scala/org/apache/spark/SparkConf.scala#L320
>
> On Mon, Jul 18, 2016 at 12:48 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi all,
>>
>> When deploying DAS 3.0.1 min HA setup in a containerized environment, its
>> required for the akka local actor to bind to an IP from one network
>> interface and advertise another. This is possible via the configurations
>> [1]. I noted that we do not have a config file for akka RPC system in DAS.
>> Is it possible to set these properties in DAS?
>>
>> [1]. http://doc.akka.io/docs/akka/snapshot/additional/faq.html
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>



-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC1

[Amila De Silva]

Hi Malith,

For 1.10.0 the reported results have been obtained on an older setup. Will
obtain those on the new setup and report the values.

On Mon, Jul 18, 2016 at 2:44 PM, Malith Jayasinghe  wrote:

> Hi Abimaran,
>
> I am looking at the performance report of RC1 pack that you have attached.
>
> I notice that for scenario 3 there is a degradation performance (TPS and
> latency) in 2.0.0 RC1 compared to 1.10.0?
> Do we know why this is happening?
>
> Also did we notice this behaviour in 2.0.0 beta 2 pack?.
>
> I  notice that you have done detailed analysis of the performance (i.e.
> latency percentiles etc) for scenario 1 and scenario 2 but no such analysis
> for scenario 3?
>
> Thanks
>
> Malith
>
> On Mon, Jul 18, 2016 at 12:06 PM, Nuwan Dias  wrote:
>
>> We have encountered two issues [1] and [2] which need to be fixed. We
>> will cancel this vote and call for a RC2.
>>
>> [1] - https://wso2.org/jira/browse/APIMANAGER-5271
>> [2] - https://wso2.org/jira/browse/APIMANAGER-5270
>>
>> Thanks,
>> NuwanD.
>>
>> On Sat, Jul 16, 2016 at 11:24 PM, Tharindu Dharmarathna <
>> tharin...@wso2.com> wrote:
>>
>>> *Tested Scenarios*
>>>
>>> Throttling - 4 levels in tenant and super tenant.
>>>
>>> Black listing
>>>
>>> +1
>>>
>>> Go ahead and release.
>>>
>>> Thanks
>>>
>>> On Sat, Jul 16, 2016 at 11:11 AM, Abimaran Kugathasan >> > wrote:
>>>
 Hi All,

 Please find the Reformance Report for above RC pack.

 On Sat, Jul 16, 2016 at 5:25 AM, Abimaran Kugathasan >>> > wrote:

> Hi Devs,
>
> *WSO2 API Manager 2.0.0-RC1 Released*
>
> This is the 1st Release Candidate of the WSO2 API Manager 2.0.0
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> The distribution is available to download at [1]
>
> [1] : https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc1
>
> *WSO2 **API Manager Analytics 2.0.0 RC1** Released*
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> The distribution is available to download  [2]
>
> Fixed Issue in [3], known issues [4]
>
> [2] :
> https://github.com/wso2/analytics-apim/releases/download/v2.0.0-rc1/wso2am-analytics-2.0.0.zip
> [3] : https://wso2.org/jira/issues/?filter=13138
> [4] : https://wso2.org/jira/issues/?filter=13139
> 
>
>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>


 --
 Thanks
 Abimaran Kugathasan
 Senior Software Engineer

 Email : abima...@wso2.com
 Mobile : +94 773922820

 
 
   
 


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>
>>> *Tharindu Dharmarathna*Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <%2B94779109091>*
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Malith Jayasinghe
>
>
> WSO2, Inc. (http://wso2.com)
> Email   : mali...@wso2.com
> Mobile : 0770704040
> Lean . Enterprise . Middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update - Provide runtime environment for jaggery apps in AS6

[Nisala Nanayakkara]

Hi KasunG,

Yes.This is the branch. Currently we are maintaining two branches as this
tomcat version(tomcat 8) will not work with carbon 4.4.x products due to
the tomcat API changes. So we have to maintain two branches now. But we
will move the current master to branch 0.12.x branch and merger
tomcat-8.0.x-jaggery to master. Then its a two different versions, not a
feature branch.

Thanks,
Nisala

On Mon, Jul 18, 2016 at 2:05 PM, KasunG Gajasinghe  wrote:

> Hi Nisala,
>
> On Thu, Jun 30, 2016 at 7:17 AM, Nisala Nanayakkara 
> wrote:
>
>> Hi all,
>>
>> Please find the branch here.
>>
>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>
>
>
> From what I understood, this is a feature branch, is it not? Then, this
> does not really need a separate jenkins job since you will merge this into
> master soon. Please note that, you shouldn't have two diverged features in
> branches of the same repo.
>
> Thanks,
> KasunG
>
>
>>
>> Thanks,
>> Nisala
>>
>> On Thu, Jun 30, 2016 at 7:12 AM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi all,
>>>
>>> We have created a seperate branch[1] with the changes required for
>>> providing runtime environment for jaggery apps in AS6. Currently there is
>>> no jenkins builder setup for this, Please get the 1.0.0-SNAPSHOT version by
>>> building the branch in local repo. Please inform me if there are any issues.
>>>
>>> Thanks,
>>> Nisala
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile:(+94)717600022
>> WSO2 Inc., http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
>
>
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC1

[Malith Jayasinghe]

Hi Abimaran,

I am looking at the performance report of RC1 pack that you have attached.

I notice that for scenario 3 there is a degradation performance (TPS and
latency) in 2.0.0 RC1 compared to 1.10.0?
Do we know why this is happening?

Also did we notice this behaviour in 2.0.0 beta 2 pack?.

I  notice that you have done detailed analysis of the performance (i.e.
latency percentiles etc) for scenario 1 and scenario 2 but no such analysis
for scenario 3?

Thanks

Malith

On Mon, Jul 18, 2016 at 12:06 PM, Nuwan Dias  wrote:

> We have encountered two issues [1] and [2] which need to be fixed. We will
> cancel this vote and call for a RC2.
>
> [1] - https://wso2.org/jira/browse/APIMANAGER-5271
> [2] - https://wso2.org/jira/browse/APIMANAGER-5270
>
> Thanks,
> NuwanD.
>
> On Sat, Jul 16, 2016 at 11:24 PM, Tharindu Dharmarathna <
> tharin...@wso2.com> wrote:
>
>> *Tested Scenarios*
>>
>> Throttling - 4 levels in tenant and super tenant.
>>
>> Black listing
>>
>> +1
>>
>> Go ahead and release.
>>
>> Thanks
>>
>> On Sat, Jul 16, 2016 at 11:11 AM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi All,
>>>
>>> Please find the Reformance Report for above RC pack.
>>>
>>> On Sat, Jul 16, 2016 at 5:25 AM, Abimaran Kugathasan 
>>> wrote:
>>>
 Hi Devs,

 *WSO2 API Manager 2.0.0-RC1 Released*

 This is the 1st Release Candidate of the WSO2 API Manager 2.0.0

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.
 Refer to github readme for guides.

 The distribution is available to download at [1]

 [1] : https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc1

 *WSO2 **API Manager Analytics 2.0.0 RC1** Released*

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.
 Refer to github readme for guides.

 The distribution is available to download  [2]

 Fixed Issue in [3], known issues [4]

 [2] :
 https://github.com/wso2/analytics-apim/releases/download/v2.0.0-rc1/wso2am-analytics-2.0.0.zip
 [3] : https://wso2.org/jira/issues/?filter=13138
 [4] : https://wso2.org/jira/issues/?filter=13139
 




 --
 Thanks
 Abimaran Kugathasan
 Senior Software Engineer

 Email : abima...@wso2.com
 Mobile : +94 773922820

 
 
   
 


>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <%2B94779109091>*
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Malith Jayasinghe


WSO2, Inc. (http://wso2.com)
Email   : mali...@wso2.com
Mobile : 0770704040
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Imesh Gunaratne]

I just added AWS membership scheme template and a sample configuration to
BPS 3.5.1 [1].
@Rasanjaya: Would you mind trying this out?

[1]
https://github.com/wso2/puppet-modules/commit/af14b15d2361f311f6de328141c3ad2cb57428d9

Thanks

On Mon, Jul 18, 2016 at 2:23 PM, Imesh Gunaratne  wrote:

> Hi Devs,
>
> It looks like we have missed $subject:
>
> https://github.com/wso2/puppet-modules/tree/master/modules/wso2base/templates/clustering
> https://docs.wso2.com/display/CLUSTER44x/Setting+up+a+Cluster+in+AWS+Mode
>
> Thanks
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Puppet Modules] AWS Membership Scheme Configuration Support

[Imesh Gunaratne]

Hi Devs,

It looks like we have missed $subject:
https://github.com/wso2/puppet-modules/tree/master/modules/wso2base/templates/clustering
https://docs.wso2.com/display/CLUSTER44x/Setting+up+a+Cluster+in+AWS+Mode

Thanks

-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is it best practice to return null or an empty object from a method in DAO layer?

[Nuwan Pallewela]

Hi All,

I also think that using exception for flow control is an anti pattern.
Following [1] describes the best practices in handling exceptions.
And using null references is also not good practice. There is a design
pattern called Null Object Pattern[2] [3] to address this issue. So I think
combining these two we could decide how to approach for certain situation.

[1] http://www.onjava.com/pub/a/onjava/2003/11/19/exceptions.html?page=1
[2] https://sourcemaking.com/design_patterns/null_object
[3] https://en.wikipedia.org/wiki/Null_Object_pattern

Thanks,
Nuwan


On Mon, Jul 18, 2016 at 1:41 PM, Udara Liyanage  wrote:

> Hi,
>
> It is not performance that matters, using exceptions for flow control is
> an anti pattern [1] [2].
>
> [1] http://c2.com/cgi/wiki?DontUseExceptionsForFlowControl
> [2]
> http://programmers.stackexchange.com/questions/189222/are-exceptions-as-control-flow-considered-a-serious-antipattern-if-so-why
>
>
> On Sun, Jul 17, 2016 at 10:46 PM, Rasika Perera  wrote:
>
>> Hi All,
>>
>>
>>> Considering a method returning a user object the client code should not
>>> be able to proceed further if there is no user.
>>
>>  This is the use case we need to achieve. How do we enforce clients to
>> *not* to proceed if the user is not found? I really do promote Design by
>> Contract . NULL will
>> give over-flexibility here and it is not what we asked for either.
>> Further, it might caused redundant NULL checks and NPEs for FREE.
>>
>> Exceptions are meant to be used for exceptional cases, using them for
>>> flow control is a bad practice. So I don't think it is a good practice to
>>> throw Exceptions instead of returning null. In addition using exceptions is
>>> costly for performance.
>>
>> Yes, Exceptions might be costly if you used it in bad way. Why not for flow
>> control? If your code running happy path most of the times, returning
>> exception on a trap would not be that harmfull. Exceptions are much
>> similar to other objects except the native call fillInStackTrace
>> .
>>  Even
>> Throwable has a constructor without a stacktrace, if you worried on
>> performance. My rule of thumb is; If performance matters so much, you
>> may need to re-consider writing your application in Java instead try C or
>> C++. Java meant to be high-level and code should be self explanatory and
>> maintainable[1]. Please refer "Null References: The Billion Dollar
>> Mistake" by T. Hoare[2].
>>
>> This is my two cents for NULLs ;)
>>
>> Choosing return NULL over Exceptions is a choice of writing *unreliable*
>> applications over bad-performance.
>>
>> Thanks,
>> Rasika
>>
>> [1] http://wolfie.github.io/2010/03/14/exceptional-heresy.html
>> [2]
>> https://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare
>>
>> On Sun, Jul 17, 2016 at 5:58 PM, Udara Liyanage  wrote:
>>
>>>
>>>
>>> On Sun, Jul 17, 2016 at 2:53 PM, Nuwan Pallewela 
>>> wrote:
>>>
 Hi,

 On Wed, Jul 13, 2016 at 10:15 AM, Sabra Ossen  wrote:

> Hi,
>
> Thank you all for your prompt responses :)
>
> So if it's an ArrayList/Map it's better to return an empty object
> rather than null. Got it.
>
> Regarding a POJO object IMO the usage of null, empty object or
> exception depends on the scenario being considered.
>
> Based on Rasikas' reply since the jaggery level code is using the DAO
> method (via manager interface) basically if no user is found then the
> exception thrown should be propagated and in the UI an appropriate message
> is rendered. Also since anyone else could be using the back end, when an
> exception is thrown they would not have to be aware of the internal
> implementation (if null or an empty object is returned, specifically he
> should be aware if an empty object is returned so that he should write his
> front end code accordingly).
>
> IMO returning an exception is clearer in terms of code but I guess the
> discussion could continue further until a guideline is specified.
>
 +1 for throwing an exception in general. If we return a null or empty
 object if data is unavailable, we may have to do a null check or empty
 object check when trying to process it most probably. And that check may
 tend to hide the original problem of unavailability of data and hard to
 debug if we face an error in a different place because of that.IMO throwing
 a custom exception which we could handle and log later or give an error
 message  to user will be more suitable.
 What to use with ArrayList and Maps is also depends on how we are going
 to manipulate the returned value. If we are going to access data in a
 ArrayList by index calling index values individually, it is better to use
 exception otherwise we may need to have a null check before that. 

Re: [Dev] Update - Provide runtime environment for jaggery apps in AS6

[KasunG Gajasinghe]

Hi Nisala,

On Thu, Jun 30, 2016 at 7:17 AM, Nisala Nanayakkara  wrote:

> Hi all,
>
> Please find the branch here.
>
> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>


>From what I understood, this is a feature branch, is it not? Then, this
does not really need a separate jenkins job since you will merge this into
master soon. Please note that, you shouldn't have two diverged features in
branches of the same repo.

Thanks,
KasunG


>
> Thanks,
> Nisala
>
> On Thu, Jun 30, 2016 at 7:12 AM, Nisala Nanayakkara 
> wrote:
>
>> Hi all,
>>
>> We have created a seperate branch[1] with the changes required for
>> providing runtime environment for jaggery apps in AS6. Currently there is
>> no jenkins builder setup for this, Please get the 1.0.0-SNAPSHOT version by
>> building the branch in local repo. Please inform me if there are any issues.
>>
>> Thanks,
>> Nisala
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile:(+94)717600022
>> WSO2 Inc., http://wso2.com/
>>
>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is it best practice to return null or an empty object from a method in DAO layer?

[Udara Liyanage]

Hi,

It is not performance that matters, using exceptions for flow control is an
anti pattern [1] [2].

[1] http://c2.com/cgi/wiki?DontUseExceptionsForFlowControl
[2]
http://programmers.stackexchange.com/questions/189222/are-exceptions-as-control-flow-considered-a-serious-antipattern-if-so-why

On Sun, Jul 17, 2016 at 10:46 PM, Rasika Perera  wrote:

> Hi All,
>
>
>> Considering a method returning a user object the client code should not
>> be able to proceed further if there is no user.
>
>  This is the use case we need to achieve. How do we enforce clients to
> *not* to proceed if the user is not found? I really do promote Design by
> Contract . NULL will
> give over-flexibility here and it is not what we asked for either.
> Further, it might caused redundant NULL checks and NPEs for FREE.
>
> Exceptions are meant to be used for exceptional cases, using them for flow
>> control is a bad practice. So I don't think it is a good practice to throw
>> Exceptions instead of returning null. In addition using exceptions is
>> costly for performance.
>
> Yes, Exceptions might be costly if you used it in bad way. Why not for flow
> control? If your code running happy path most of the times, returning
> exception on a trap would not be that harmfull. Exceptions are much
> similar to other objects except the native call fillInStackTrace
> .
>  Even
> Throwable has a constructor without a stacktrace, if you worried on
> performance. My rule of thumb is; If performance matters so much, you may
> need to re-consider writing your application in Java instead try C or C++.
> Java meant to be high-level and code should be self explanatory and
> maintainable[1]. Please refer "Null References: The Billion Dollar
> Mistake" by T. Hoare[2].
>
> This is my two cents for NULLs ;)
>
> Choosing return NULL over Exceptions is a choice of writing *unreliable*
> applications over bad-performance.
>
> Thanks,
> Rasika
>
> [1] http://wolfie.github.io/2010/03/14/exceptional-heresy.html
> [2]
> https://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare
>
> On Sun, Jul 17, 2016 at 5:58 PM, Udara Liyanage  wrote:
>
>>
>>
>> On Sun, Jul 17, 2016 at 2:53 PM, Nuwan Pallewela  wrote:
>>
>>> Hi,
>>>
>>> On Wed, Jul 13, 2016 at 10:15 AM, Sabra Ossen  wrote:
>>>
 Hi,

 Thank you all for your prompt responses :)

 So if it's an ArrayList/Map it's better to return an empty object
 rather than null. Got it.

 Regarding a POJO object IMO the usage of null, empty object or
 exception depends on the scenario being considered.

 Based on Rasikas' reply since the jaggery level code is using the DAO
 method (via manager interface) basically if no user is found then the
 exception thrown should be propagated and in the UI an appropriate message
 is rendered. Also since anyone else could be using the back end, when an
 exception is thrown they would not have to be aware of the internal
 implementation (if null or an empty object is returned, specifically he
 should be aware if an empty object is returned so that he should write his
 front end code accordingly).

 IMO returning an exception is clearer in terms of code but I guess the
 discussion could continue further until a guideline is specified.

>>> +1 for throwing an exception in general. If we return a null or empty
>>> object if data is unavailable, we may have to do a null check or empty
>>> object check when trying to process it most probably. And that check may
>>> tend to hide the original problem of unavailability of data and hard to
>>> debug if we face an error in a different place because of that.IMO throwing
>>> a custom exception which we could handle and log later or give an error
>>> message  to user will be more suitable.
>>> What to use with ArrayList and Maps is also depends on how we are going
>>> to manipulate the returned value. If we are going to access data in a
>>> ArrayList by index calling index values individually, it is better to use
>>> exception otherwise we may need to have a null check before that. Same
>>> applies to Maps. If we are going to process each element in a ArrayList we
>>> could use Iterator and process. In that case empty ArrayList would do the
>>> job. So there is not going to be a one for all cases solution in this
>>> argument. It will depend on how we are going to process that returned value
>>> and the nature of the application.
>>>
>> Exceptions are meant to be used for exceptional cases, using them for
>> flow control is a bad practice. So I don't think it is a good practice to
>> throw Exceptions instead of returning null. In addition using exceptions is
>> costly for perfomance.
>>
>> If you return a  empty object the calling function will invoke functions
>> of the object which will result in undesi

Re: [Dev] [Mesos-Marathon] Issues in Creating Point to Point TCP Connections in Mesos-Marathon based Deployments

[Niranda Perera]

Hi Isuru,

Sorry for replying late, but I have replied to the previous mail you have
sent regarding akka configurations in Spark [1]

Best

[1] [DAS] Setting akka Configuration Properties

On Mon, Jul 18, 2016 at 1:03 PM, Isuru Haththotuwa  wrote:

> Hi all,
>
> For the DAS min HA usecase, there is an additional TCP point to point
> connection for spark masters. In the master branch of
> org.wso2.carbon.analytics.spark.core, we can use SPARK_LOCAL_IP property to
> set a different IP address for this [1]. But, in the  version 1.0.5 which
> was released with DAS 3.0.1 does not have this fix. I backported the fix
> and tested, it works.
>
> However, only setting this property to the host name does not solve this
> issue since akka system tries to bind to the same host IP, which is not
> visible to the internal network, resulting in error [2].
>
> The solution would be to define two IP addresses for akka system; one to
> bind (private Ip), another to advertise (routable IP) as explained in akka
> docs [3]. Can we do this from DAS side? Please share your input as this is
> a blocking issue for deploying DAS in mesos.
>
> [1].
> https://github.com/wso2/carbon-analytics/blob/master/components/analytics-processors/org.wso2.carbon.analytics.spark.core/src/main/java/org/wso2/carbon/analytics/spark/core/internal/AnalyticsComponent.java#L246
>
> [2]. ERROR {akka.remote.transport.netty.NettyTransport} -  failed to bind
> to /x.x.x.x:22093, shutting down Netty transport
>
> [3].
> http://doc.akka.io/docs/akka/snapshot/additional/faq.html#Why_are_replies_not_received_from_a_remote_actor_
>
>
> On Thu, Jul 14, 2016 at 10:04 PM, Isuru Haththotuwa 
> wrote:
>
>> Update:
>> DAS, CEP and MB are the three products that currently we have identified,
>> which need point to point TCP connections for HA deployment.
>>
>> *DAS and CEP:*
>>
>> This is required for event synchronization [1,2] using thrift transport.
>> Had a offline chat with Sinthuja on this. As per the ThriftDataReceiver
>> code [3], the thrift event receiver actually picks up the bind hostname
>> from repository/conf/data-bridge/data-bridge-config.xml file. In that case,
>> we can simply use the local IP for Thrift event receiver, and use the
>> mapped host ip and port for the event synchronization configuration.
>>
>>
>>
>> *MB:*
>> Required for slot co-ordination [4]. As the solution, we would need to
>> define a bind ip + port and a separate public ip + port to advertise. Had a
>> discussion regarding this with Ramith. If MB is using the same thrift data
>> receiver [5], we might be able to use data-bridge-config.xml to define a
>> bind ip. @Ramith: Can you please clarify this?
>>
>> [1].
>> https://docs.wso2.com/display/CLUSTER44x/Minimum+High+Availability+Deployment+-+DAS+3.0.1
>>
>> [2].
>> https://docs.wso2.com/display/CLUSTER44x/Clustering+CEP+4.0.0#ClusteringCEP4.0.0-Highavailabilitydeployment
>>
>> [3].
>> https://github.com/wso2/carbon-analytics-common/blob/master/components/data-bridge/org.wso2.carbon.databridge.receiver.thrift/src/main/java/org/wso2/carbon/databridge/receiver/thrift/conf/ThriftDataReceiverConfiguration.java
>>
>> [4].
>> https://docs.wso2.com/display/CLUSTER44x/Configuring+the+Broker+Nodes
>>
>> [5].
>> https://github.com/wso2/carbon-analytics-common/blob/f3ff09d9655bf599d45436f0630b6413fc3d1b60/components/data-bridge/org.wso2.carbon.databridge.receiver.thrift/src/main/java/org/wso2/carbon/databridge/receiver/thrift/ThriftDataReceiver.java
>>
>>
>> On Tue, Jul 12, 2016 at 1:52 PM, Udara Liyanage  wrote:
>>
>>>
>>>
>>> On Tue, Jul 12, 2016 at 12:56 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi all,

 This is to discuss about $subject.

 By default Mesos-Marathon [1] does not have an overlay network.
 Therefore when deploying wso2 products in distributed/HA manner in mesos,
 the products are unable to create point to point TCP connections directly
 from container to container.

 In Carbon products, p2p connections are created by Hazelcast, within
 cluster members. Since this is just for communication purposes, its
 possible to do a workaround by querying the API for the IPs of the host
 machine. This is done in the Mesos membership scheme [2].

 There are few places where we need to create TCP Listeners, for an
 example in CEP HA/Distributed setup [3]. For this, we can't just bind to
 the host node IP since the public IP is not visible to the container; and
 can't use the local container IP since container to container communication
 is not possible (due to the lack of an overlay network).

 One possible option is such scenarios is to use the HOST networking
 mode of Docker [4]. Then the container will be using the host IP and ports
 directly. One issue with this approach is since we are mapping container
 ports to host ports directly without assigning random ports from the host
 side, only one container can run in one host node. But, in a wa

Re: [Dev] [DAS] Setting akka Configuration Properties

[Niranda Perera]

Hi Isuru,

I checked the Spark docs but it is not publicly documented, but if you
check here [1], akka settings can be set in the spark conf. So, you should
be able to set those configs in the spark-defaults.conf file in
repository/conf/analytics/spark dir.

Best

[1]
https://github.com/apache/spark/blob/branch-1.4/core/src/main/scala/org/apache/spark/SparkConf.scala#L320

On Mon, Jul 18, 2016 at 12:48 AM, Isuru Haththotuwa  wrote:

> Hi all,
>
> When deploying DAS 3.0.1 min HA setup in a containerized environment, its
> required for the akka local actor to bind to an IP from one network
> interface and advertise another. This is possible via the configurations
> [1]. I noted that we do not have a config file for akka RPC system in DAS.
> Is it possible to set these properties in DAS?
>
> [1]. http://doc.akka.io/docs/akka/snapshot/additional/faq.html
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos-Marathon] Issues in Creating Point to Point TCP Connections in Mesos-Marathon based Deployments

[Isuru Haththotuwa]

Hi all,

For the DAS min HA usecase, there is an additional TCP point to point
connection for spark masters. In the master branch of
org.wso2.carbon.analytics.spark.core, we can use SPARK_LOCAL_IP property to
set a different IP address for this [1]. But, in the  version 1.0.5 which
was released with DAS 3.0.1 does not have this fix. I backported the fix
and tested, it works.

However, only setting this property to the host name does not solve this
issue since akka system tries to bind to the same host IP, which is not
visible to the internal network, resulting in error [2].

The solution would be to define two IP addresses for akka system; one to
bind (private Ip), another to advertise (routable IP) as explained in akka
docs [3]. Can we do this from DAS side? Please share your input as this is
a blocking issue for deploying DAS in mesos.

[1].
https://github.com/wso2/carbon-analytics/blob/master/components/analytics-processors/org.wso2.carbon.analytics.spark.core/src/main/java/org/wso2/carbon/analytics/spark/core/internal/AnalyticsComponent.java#L246

[2]. ERROR {akka.remote.transport.netty.NettyTransport} -  failed to bind
to /x.x.x.x:22093, shutting down Netty transport

[3].
http://doc.akka.io/docs/akka/snapshot/additional/faq.html#Why_are_replies_not_received_from_a_remote_actor_

On Thu, Jul 14, 2016 at 10:04 PM, Isuru Haththotuwa  wrote:

> Update:
> DAS, CEP and MB are the three products that currently we have identified,
> which need point to point TCP connections for HA deployment.
>
> *DAS and CEP:*
>
> This is required for event synchronization [1,2] using thrift transport.
> Had a offline chat with Sinthuja on this. As per the ThriftDataReceiver
> code [3], the thrift event receiver actually picks up the bind hostname
> from repository/conf/data-bridge/data-bridge-config.xml file. In that case,
> we can simply use the local IP for Thrift event receiver, and use the
> mapped host ip and port for the event synchronization configuration.
>
>
>
> *MB:*
> Required for slot co-ordination [4]. As the solution, we would need to
> define a bind ip + port and a separate public ip + port to advertise. Had a
> discussion regarding this with Ramith. If MB is using the same thrift data
> receiver [5], we might be able to use data-bridge-config.xml to define a
> bind ip. @Ramith: Can you please clarify this?
>
> [1].
> https://docs.wso2.com/display/CLUSTER44x/Minimum+High+Availability+Deployment+-+DAS+3.0.1
>
> [2].
> https://docs.wso2.com/display/CLUSTER44x/Clustering+CEP+4.0.0#ClusteringCEP4.0.0-Highavailabilitydeployment
>
> [3].
> https://github.com/wso2/carbon-analytics-common/blob/master/components/data-bridge/org.wso2.carbon.databridge.receiver.thrift/src/main/java/org/wso2/carbon/databridge/receiver/thrift/conf/ThriftDataReceiverConfiguration.java
>
> [4]. https://docs.wso2.com/display/CLUSTER44x/Configuring+the+Broker+Nodes
>
> [5].
> https://github.com/wso2/carbon-analytics-common/blob/f3ff09d9655bf599d45436f0630b6413fc3d1b60/components/data-bridge/org.wso2.carbon.databridge.receiver.thrift/src/main/java/org/wso2/carbon/databridge/receiver/thrift/ThriftDataReceiver.java
>
>
> On Tue, Jul 12, 2016 at 1:52 PM, Udara Liyanage  wrote:
>
>>
>>
>> On Tue, Jul 12, 2016 at 12:56 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is to discuss about $subject.
>>>
>>> By default Mesos-Marathon [1] does not have an overlay network.
>>> Therefore when deploying wso2 products in distributed/HA manner in mesos,
>>> the products are unable to create point to point TCP connections directly
>>> from container to container.
>>>
>>> In Carbon products, p2p connections are created by Hazelcast, within
>>> cluster members. Since this is just for communication purposes, its
>>> possible to do a workaround by querying the API for the IPs of the host
>>> machine. This is done in the Mesos membership scheme [2].
>>>
>>> There are few places where we need to create TCP Listeners, for an
>>> example in CEP HA/Distributed setup [3]. For this, we can't just bind to
>>> the host node IP since the public IP is not visible to the container; and
>>> can't use the local container IP since container to container communication
>>> is not possible (due to the lack of an overlay network).
>>>
>>> One possible option is such scenarios is to use the HOST networking mode
>>> of Docker [4]. Then the container will be using the host IP and ports
>>> directly. One issue with this approach is since we are mapping container
>>> ports to host ports directly without assigning random ports from the host
>>> side, only one container can run in one host node. But, in a way this
>>> defeats the purpose of containerization.
>>>
>> Using host mode would be a good alternative. I don't think limiting one
>> container per Mesos node (Mesos HOST=UNIQUE constrain) in this scenario
>>  since a HA Mesos deployment will have multiple Mesos nodes.
>> Another advantage of running in host mode is performance efficiency
>> rather than bridge mode. Networ

[Dev] [ESB] Unable to start ESB 5.0.0 Beta2 on top of IBM JDK

[Pubudu Priyashan]

Hi Senduran,

We are currently facing the issue logged at [1] when starting the ESB pack
with IBM JDK. Can we please take a look and get this fixed with the next
release? This blocks us from testing the release on IBM JDK. Do let me know
if you require any further information. Thanks!

[1] https://wso2.org/jira/browse/ESBJAVA-4772


Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547

Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Adding SVN dockerfiles to wso2/dockerfiles

[Pubudu Gunatilaka]

Hi,

At the moment there is no any official docker image for SVN[1]. I have
created the dockerfile and other relevant artifacts for SVN [2]. This is to
maintain a separate a docker image for SVN for deployment synchronization.
For dep sync in container deployments, there is a mail thread with subject
in [3].

Basically rsync is an option for dep sync. But when it compares to SVN,
the following are the main advantages.

- Can handle several manager nodes
- SVN Container can accommodate multiple products
- We can mount a single volume for SVN server only

Please share your thoughts.

[1] - https://hub.docker.com/
[2] - https://github.com/wso2/dockerfiles/pull/57
[3] - [Architecture] Dep sync strategies for Carbon 4 products in Kubernetes

Thank you!
-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev