Re: [Architecture] API Manager integration with Istio

[KasunG Gajasinghe]

Hi Sanjeewa,

Just for clarification, the purpose of the API Manager in here is to do QoS
like throttling, monetization, authorization?
Secondly, I'm not clear where would the APIM deployment lie. Does it live
on its own isolated namespace in K8S?

Thanks,
KasunG

On Tue, Jan 15, 2019 at 4:07 PM Sanjeewa Malalgoda 
wrote:

> Hi All,
> The intention of this mail is to discuss about API Manager istio
> integration and come to conclusion on design and architecture. With this
> particular feature our target group is users who already use API Management
> and have requirement to move towards service mesh architecture. We believe
> this will help us to prove our capability to integrate with service mesh
> architecture. This feature will allow users to expose their services
> deployed on service mesh as APIs and apply different QoS. Here is a brief
> overview on what we are planning to do.
>
>
> *Overview of the feature*
>
>- When users move towards microservice architecture from monolithic
>app architecture we will have thousands of microservices. When we break
>each monolith app to microservices it will create more services.
>- So managing all these microservices would be a challenge.
>- Istio helps to reduce the complexity of this type of deployments. It
>is a platform, including APIs that let it integrate into any logging
>platform, or telemetry or policy system.
>- Istio creates a “service mesh” that routes traffic between
>interrelated services in a secure and robust way so that the developers of
>each individual service can focus on what a service does rather than the
>details of how it communicates.
>- However when users need to expose these microservices services to
>outside in a secured controlled manner we need API Management.
>- Most of the time we need to create APIs(for microservices) and share
>them with other developers who might be part of your organization or who
>might be external.
>- So API Management within service mesh solution is required to
>operate successfully. With this capability, user can expose one or more
>services from an Istio mesh as APIs by adding API management capabilities.
>
>
> *Approach*When it comes to enabling API Management for service mesh there
> are multiple approaches we can follow. One way is use the mixer plugin
> model, which is a standard extension point available in Istio. We believe
> this is most suitable way of integrating API Management with istio.
>
> *Mixer* is a core Istio component which runs in the control plane of the
> service mesh. Mixer's plugin model enables new rules and policies to be
> added to groups of services in the mesh without modifying the individual
> services or the nodes where they run. API management policies
> authentication (by API key validation), throttling, etc can be deployed and
> managed at API Manager side without doing any changes to the actual
> microservice or sidecar proxy each time deployment happens. Following
> diagrams will explain how the mixer plugin captures telemetry and performs
> the policy check.
>
> Whenever user deploys a service, Istio injects a sidecar to the particular
> service as a proxy. For each request sent to the service, the sidecar proxy
> will capture a set of data and publish it to the Mixer. If the user needs
> to expose this service to outside in a managed way, an API should be
> created in API Manager. This can be done via different methods:
>
>- Automated process - When a user deploys a service which is required
>to be exposed, an API will be created in API Manager automatically.
>- Manual process - Once a service is deployed, the user can go to the
>API Manager developer portal and create API by giving service data and
>swagger file.
>
> *Route of a Successful Request*
>
>
>1. The client sends the request to the service (Istio capture the
>request and redirect to the istio-proxy). This enters the Kubernetes
>cluster via an ingress point.
>2. Proxy captures attributes and sends to the Mixer as attributes.
>3. Mixer adapter does the throttling, authentication parts and calls
>for the API Manager Deployment.
>4. API Manager Deployment captures the request and sends the relevant
>response to the mixer.
>5. Mixer makes the policy decisions and sends back to the istio-proxy.
>6. The proxy delivers the request to the microservice.
>7. Microservice executes the service logic and sends the response
>8. The response is sent out to the client
>
> API Manager team started initial work on this project and we will work on
> features in phased approach. First we will do introspection call which
> validates access token. Then we can think of throttling, usage data
> monitoring etc. We will create repo named
> istio-apim and start our work there. If you have any suggestions to above
> proposal please let us know.
>
> Thanks,
> sanjeewa.
> --
> *Sanjeewa Malalgoda*
> 

Re: [Architecture] [Dev] [VOTE] Release WSO2 Identity Server 5.7.0 RC3

[KasunG Gajasinghe]

Hi Pasindu, Sentha,

On Fri, Sep 14, 2018 at 11:10 AM Pasindu Jayaweera 
wrote:

> Hi all,
> TestGrid team has executed integration-tests with the RC and please find
> the effort in [1].
> We have observed bunch of test cases failing in our automated runs.
> However when re-executing the failed ones and also doing the manual
> testing, we observed the amount of failing test cases were reduced further.
> Given that the team has tested the same set of test cases in same hardware
> combinations and since they are passing, it could be an environment related
> issue, which might need more time to investigate.
>

Yes, sure. If there are any minor test-level failures, we can skip them for
this vote. I think IS folks can analyze and investigate this report better
by themselves as well. :)


We are doing more investigation to make sure that the intermittent issues
> we see are product-level issues, or intg-test case level issues.
> So, please allow some time for Testgrid to cast the vote.
>
> Thanks.
> Regards,
>
> [1] - Testgrid effort on testing IS 5.7.0 RCs
>
> Thanks.
> Regards,
> On Fri, Sep 14, 2018 at 10:08 AM Thumilan Mikunthan 
> wrote:
>
>> Hi all,
>> I have test the following scenarios on IS 5.7.0 RC3 pack and did not
>> encounter any issues.
>>   UMA 2.0 Flow
>>
>>- Obtain access token using password grant.
>>- Entitlement policy creation using write policy in xml and
>>publishing.
>>- Create,delete update nad view  resources and read description of
>>resource by invoking UMA registration endpoint.
>>
>> [+] Stable - Go ahead and release
>>
>> Best Regards,
>> M.Thumilan
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> *Pasindu Jayaweera*
> Software Engineer | WSO2 Inc
> Mobile: +94 718187375
> Blog: blog.pasindujayaweera.com
> 
>
> --

*Kasun Gajasinghe*Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] question to updates strategy

[KasunG Gajasinghe]

file does not really have an affect at runtime. What is actually important
is the Import-Package version ranges. This is specified in the maven
pom.xml under the maven-bundle-plugin section at build-time.


> Does it mean that it uses the latest version despite of specific version
> in its DEPENDENCIES file?
>
The same for /opt/wso/repository/components/dropins/org.wso2.
> carbon.identity.application.authenticator.samlsso-5.1.5.jar which depends
> on 
> "org.wso2.carbon.identity.application.authentication.framework:bundle:5.5.0",
> but there is no 5.5.0 jar for "application.authentication.framework",
> only version 5.7.5 (org.wso2.carbon.identity.application.authentication.
> framework_5.7.5.jar).
>
>
>
> Best regards,
>
> Roman
>
>
>
>
>
>
>
> *From:* Architecture [mailto:architecture-boun...@wso2.org] *On Behalf Of
> *KasunG Gajasinghe
> *Sent:* Tuesday, January 2, 2018 2:10 AM
> *To:* architecture@wso2.org
> *Subject:* Re: [Architecture] question to updates strategy
>
>
>
> Hi Roman,
>
>
>
> 5.1.5 and 5.1.7 are two patch releases of 5.1.x minor version. That means
> there shouldn't be any API changes nor incompatibility between the two.
> Hence, you can replace the said dropons jar with the newer version.
>
> OSGi accepts version ranges. Usually, it is set to one minor version to
> the next immediate one. For ex. [5.1.0, 5.2.0) - square bracket means
> inclusive [ - bracket means exclusive.
>
>
>
> There's no flag in WUM to do what you suggested. Have to check why the
> dropins jars are not in WUM.
>
>
>
> On Tue, Jan 2, 2018 at 2:21 AM Roman CHRENKO <roman_chre...@tempest.sk>
> wrote:
>
> Hi.
>
> I have some questions to updates strategy for WSO2 IS. (I know that WSO2
> IS 5.4.0 is released now, but I can better explain my question on version
> 5.3.0.)
>
> There was in basic installation package for WSO2 IS 5.3.0
> (wso2is-5.3.0.zip), in folder "repository/components/dropins" SAML
> Federation plugin (
> *org.wso2.carbon.identity.application.authenticator.samlsso*) version
> 5.1.5. There was a bug in the class DefaultSAML2SSOManager. Method
> buildLogoutRequest() incorrectly set (always!) 
> nameId.setFormat(NameIDType.UNSPECIFIED),
> which was interpreted by som trusted IDPs as wrong LogoutRequest. This bug
> was fixed in version 5.1.6: if some conditions are met, it sets:
> nameId.setFormat(NameIDType.ENTITY);
>
> In the time when version 5.1.7 was available in GIT, I tried to download
> updates for WSO2 IS by WUM. But updated zip-package contained only
> unpatched version 5.1.5. Command "wum list" shows basic and "updated"
> versions of WSO2 IS:
>
> c:\Program Files\WUM\bin>wum list
>
> Product Updated Filename
>
> wso2is-5.3.016 Oct 17 13:36 CEST
> wso2is-5.3.0.1497977325530.zip
>
> wso2is-5.3.0-   wso2is-5.3.0.zip
>
> Version 5.1.7 was released on Jun 27, 2017 (by https://github.com/wso2-
> extensions/identity-outbound-auth-samlsso/releases).
>
> -  How to instruct WUM to include also latest patches for
> specific component (for example SAML Federation plugin :
> org.wso2.carbon.identity.application.authenticator.samlsso)? Or is it a
> bug in WUM that it doesn't download latest patches for dropins?
>
> -  I know that I can download the source code of 5.1.6+ from GIT
> and build the plugin ("OSGI bundle") by Maven. But can I copy newly created
> JAR file into the dropins folder? Don't expect other OSGI components
> specific version 5.1.5? I am afraid that it can lead to inconsistent state
> of WSO2 IS. How to get to consistent state with version 5.1.6+?
>
>
>
> Best regards,
>
> Roman Chrenko
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
> --
>
>
> *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
> phone: +1 650-745-4499 <+1%20650-745-4499>, 77 678 0813
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] question to updates strategy

[KasunG Gajasinghe]

Hi Roman,

5.1.5 and 5.1.7 are two patch releases of 5.1.x minor version. That means
there shouldn't be any API changes nor incompatibility between the two.
Hence, you can replace the said dropons jar with the newer version.
OSGi accepts version ranges. Usually, it is set to one minor version to the
next immediate one. For ex. [5.1.0, 5.2.0) - square bracket means inclusive
[ - bracket means exclusive.

There's no flag in WUM to do what you suggested. Have to check why the
dropins jars are not in WUM.

On Tue, Jan 2, 2018 at 2:21 AM Roman CHRENKO 
wrote:

> Hi.
>
> I have some questions to updates strategy for WSO2 IS. (I know that WSO2
> IS 5.4.0 is released now, but I can better explain my question on version
> 5.3.0.)
>
> There was in basic installation package for WSO2 IS 5.3.0
> (wso2is-5.3.0.zip), in folder "repository/components/dropins" SAML
> Federation plugin (
> *org.wso2.carbon.identity.application.authenticator.samlsso*) version
> 5.1.5. There was a bug in the class DefaultSAML2SSOManager. Method
> buildLogoutRequest() incorrectly set (always!)
> nameId.setFormat(NameIDType.UNSPECIFIED), which was interpreted by som
> trusted IDPs as wrong LogoutRequest. This bug was fixed in version 5.1.6:
> if some conditions are met, it sets: nameId.setFormat(NameIDType.ENTITY);
>
> In the time when version 5.1.7 was available in GIT, I tried to download
> updates for WSO2 IS by WUM. But updated zip-package contained only
> unpatched version 5.1.5. Command "wum list" shows basic and "updated"
> versions of WSO2 IS:
>
> c:\Program Files\WUM\bin>wum list
>
> Product Updated Filename
>
> wso2is-5.3.016 Oct 17 13:36 CEST
> wso2is-5.3.0.1497977325530.zip
>
> wso2is-5.3.0-   wso2is-5.3.0.zip
>
> Version 5.1.7 was released on Jun 27, 2017 (by
> https://github.com/wso2-extensions/identity-outbound-auth-samlsso/releases
> ).
>
> -  How to instruct WUM to include also latest patches for
> specific component (for example SAML Federation plugin :
> org.wso2.carbon.identity.application.authenticator.samlsso)? Or is it a bug
> in WUM that it doesn't download latest patches for dropins?
>
> -  I know that I can download the source code of 5.1.6+ from GIT
> and build the plugin ("OSGI bundle") by Maven. But can I copy newly created
> JAR file into the dropins folder? Don't expect other OSGI components
> specific version 5.1.5? I am afraid that it can lead to inconsistent state
> of WSO2 IS. How to get to consistent state with version 5.1.6+?
>
>
>
> Best regards,
>
> Roman Chrenko
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Extending BCJSSE for Token binding

[KasunG Gajasinghe]

On Mon, Nov 13, 2017 at 1:03 PM, Inthirakumaaran Tharmakulasingham <
inthirakumaa...@wso2.com> wrote:

> I think there is a signature verification problem when using bouncy castle
> provider.You can find the details of the past problem in the link[1].(got
> this problem 3 years ago)
>
>
Alright, and there is a fix as well. So, this is not really an issue. :-)


> I started the conversation with BC developers and they're not going to
> implement token binding extension by them self in near future.The new
> extension, they added on user request was a small one and they already
> had implemented it but commented out for some reason.Details about that
> extension are in this link[2].But they are okay with sending PR for token
> binding implementation.If it is merged then we can reach java community
> easily.More details about the conversation can be found at this link[3].
>

Yes. Do keep them engaged, and send an early draft PR to BC community for
reviewing. This is going good. :)

Thanks,
KasunG


>
> When I talked to BC providers they mentioned about an extension API which
> can be used to add a new extension in the handshake.I did some digging into
> that and it seems is possible to create a token binding extension and have
> to put that into that API.Rest of the negotiations will be done by that
> API.So currently I am in the process of developing an extension that could
> fit into that API.
>
> Reference:
>   [1]Bouncy castle issue mail thread
> <http://wso2-oxygen-tank.10903.n7.nabble.com/Error-bcprov-jdk15on-1-49-0-wso2v1-jar-has-unsigned-entries-org-bouncycastle-LICENSE-class-td103606.html>
>   [2]https://github.com/bcgit/bc-java/issues/234
>   [3]https://github.com/bcgit/bc-java/issues/250
>
>
>
> On Fri, Nov 10, 2017 at 8:34 AM, KasunG Gajasinghe <kas...@wso2.com>
> wrote:
>
>> Hi Indra,
>>
>> Can you find out exactly what issues we faced before? I'm assuming it has
>> something to do with jar signing.
>>
>> The work we are doing is not specific to wso2 but applies to entire Java
>> community and bouncycastle users. So, our end goal should be get this
>> merged into bouncycastle project.
>>
>> Please start a dialogue with BC developers asap. They are on GitHub now I
>> suppose.
>>
>> Bouncycastle just added a new tls extension last month, and the community
>> quite active.
>>
>> @Prabath, please share your thoughts.
>>
>> Thanks,
>> KasunG
>>
>> On Thu, Nov 9, 2017 at 2:10 PM Inthirakumaaran Tharmakulasingham <
>> inthirakumaa...@wso2.com> wrote:
>>
>>> Hi,
>>> I am trying to create a Token binding library for TLS layer.One option
>>> for this to extend BCJSSE and write the implementations on top of it.But in
>>> the past, there have been some issues in making changes in Bouncy
>>> Castle.How can I proceed with this?OR any better way to write the library?
>>>
>>> Basically, our intention is to make a token binding library so that
>>> anyone can create HTTP client which can support token binding.Thus we hope
>>> to send a PR to BC after completing the implementation.
>>>
>>>
>>> --
>>> Inthirakumaaran
>>> Software Engineering - Intern | WSO2
>>>
>>> Email: inthirakumaa...@wso2.com
>>> Mobile:0766598050 <076%20659%208050>
>>>
>>> --
>>
>> *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
>> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>>
>>
>
>
>
> --
> Inthirakumaaran
> Software Engineering - Intern | WSO2
>
> Email: inthirakumaa...@wso2.com
> Mobile:0766598050 <076%20659%208050>
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Milestone Plan for Redis Connector

[KasunG Gajasinghe]

Have we written this connector? I can't seem to find it in the Store [1].

[1]
https://store.wso2.com/store/pages/top-assets?q=%22_default%22%3A%22redis%22

Thanks.

On Wed, Apr 15, 2015 at 4:00 PM, Vanjikumaran Sivajothy 
wrote:

> You have to forward this apim-> Esb
>
>
> On Wednesday, April 15, 2015, ly h  wrote:
>
>> Can we use it as axis transport in apim, or we must forward data from
>> apim to esb.
>>
>> 2015-04-15 10:39 GMT+08:00 Vanjikumaran Sivajothy :
>>
>>> Hi liuhf,
>>> Yes it is possible, you have to make sure that you have utilized this
>>> connector in proxy web services of Wso2 ESB and expose that via api manager
>>> as you want
>>>
>>>
>>> On Monday, April 13, 2015, ly h  wrote:
>>>
 If this finished, can we use it in APIManager? We want http<->redis.

 Best regards!

 liuhf

 2015-04-10 18:18 GMT+08:00 Naasheer Ali :

> Hi All,
> I'm gonna implement the Redis connector for WSO2 ESB.
> 1. Overview
>
>- Redis is an open source, BSD licensed, avanced* key-value cache *
>and* store. *It is often referred to as a* data structure server *since
>keys can contain *Strings, hashes, lists, sets, sorted sets
>bitmaps* and *hyperloglogs.*
>
> 2. Advantages of Redis
>
>- Redis can contain more complex data types, with atomic operation
>defined on those data types.
>- Redis data types are closely related to fundamental data
>structure and are exposed to the programmer as such, without additional
>abstraction layers.
>- Redis is an in-memory but persistent on disk database, so it
>represents a different trade off where very high write and read speed 
> is
>achieved with the limitation of data sets that can't be lager than 
> memory.
>- The memory representation of complex data structures is much
>simpler to manipulate compared to the same data structure on disk, so 
> Redis
>can do a lot, with little internal complexity.
>
> 3. Use Cases :
>
>- Queuing slow operations
>- cross-language develoment,
>- atomic counters and generating sequences
>- dealing with temporary data in your application
>- Redis as a cache
>
>
> Please find my milestone plan.
>
> Regards,
> --
>
> *Naasheer Ali* | Associate Software Engineer
>
> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka
>
> Email: naashe...@wso2.comr
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>

>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>
> --
> Sent from Gmail Mobile
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Cross Protocol Single Logout

[KasunG Gajasinghe]

Can you list possible customer usecases on why they want to use this?

On Thu, Aug 10, 2017 at 11:47 AM, Sugirjan Ragunaathan 
wrote:

> Hi,
>
> Currently I’m working on a project 'Cross protocol single logout'. WSO2
> Identity Server provides Single LogOut over applications, participating on
> the same session over the same authentication protocol and Single SignOn
> over the different protocols.
>
> [image: 1.png]
>
> Objective:
>
> Design and provide a solution to support cross protocol SLO
>
> Problem :
>
> WSO2 Identity Server supports multiple applications which are using
> different authentication protocols. It does not provide cross protocol
> Single Logout. For example, Assume that  you are using SAML based
> application and OIDC based application is same browser session. when you
> logout from a SAML based application it will only log you out from other
> SAML applications not from OIDC based application with the same session.
>
> Solution:
>
> The proposed solution for this problem is implementing a common event
> handler over different protocols. When a session is terminated because of
> user logout, an event should be published to invoke the ‘SLO  Event
> Handler’.So 'SLO Event Handler' notifies all the inbound authenticators and
> the authenticators handle respective logout actions. In order to listen
> the logout event, all the respective authenticators have to be subscribed
> in the ‘SLO event handler’ and have own separate event handlers to trigger
> the logout for their registered applications.
>
> [image: SolutionArchi.png]
>
>
> We would like to have your feedback and suggestions in this regard.
>
> Thanks.
>
> Regards,
> *R. Sugirjan*
> Software Engineering - Intern | WSO2
>
> Email:  sugir...@wso2.com
> Mobile: +94768489892 <076%20848%209892>
> 
>



-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] LDAP protocol inbound support for identity server

[KasunG Gajasinghe]

Proposal is good. I believe you are trying to use ApacheDS' ldap protocol
implementation? We only need to direct the LDAP request to the back-end
user store JDBC/LDAP as appropriate. If it is a LDAP user store, then we
are simply doing request pass-thru. But, ApacheDS has its own directory
storage. We do not need that. We only need the protocol support it has.

What is your plan to achieve this?

Thanks,
KasunG


On Wed, Aug 2, 2017 at 9:39 AM, Dineth Chalitha  wrote:

> Hi All,
>
>
> LDAP is a core protocol that is used to store user, role, and group
> information.Identity server already supports connecting to LDAP supported
> authz systems for authentication and authorization. The idea of this
> project is to make IS itself act as a LDAP protocol provider.
>
>
> *Problem Definition*
>
> Current Identity server can communicate with LDAP as a client. It means
> Identity server can use an  LDAP server as a user store. But Identity
> server does not expose a LDAP protocol endpoint by itself such that
> external clients can connect with IS directly . Also identity server work
> with different type of databases. The client’s LDAP request not supported
> to  communicate with those different type of databases.
>
> *Proposed solution*
>
> The architecture is designed to  convert that LDAPmessage to common medium
>  and then IS can use that data to communicate with any type of database.
>
> The general model adopted by this protocol is one of clients performing
> protocol operations against servers.  In this model, a client send a
> protocol request describing the operation to be performed to a server.  The
> server is then responsible for performing the necessary operation(s) in the
> Directory.Protocol operation are exchanged at the LDAP message layer.For
> the purposes of protocol exchanges, all protocol operations are
> encapsulated in a common envelope, the LDAPMessage.
>
> We suppose to do is capture the LDAPmessage  at LDAP endpoint and Identify
> the message element and map it into java objects. IS  can use these objects
> to do operation  with JDBC, MySQL,  LDAP or any other type of database.
>
>
>
>
>
>
>
>
> Steps.
>
>
>-
>
>Client invoke the LDAP operation or process from Identity server.
>-
>
>Identity server provide LDAP endpoint and It’s expose to client.
>-
>
>Client request the operation or process  as LDAPmessage to LDAP
>endpoint.
>-
>
>LDAP endpoint capture the message.
>-
>
>Extract the message type and elements of captured message.
>-
>
>Then message element map into java objects and pass to IS user store
>manager.
>-
>
>User store manager use those java objects to do the  operation with
>data sources.
>
>
>
>
>
> Feedback on the improvement for the design is much appreciated.
>
> Thank you,
> Best Regards.
>
> --
>
> *Dineth Chalitha*
>
> *Software engineer intern *
> *WSO2, Inc.:http://wso2.com *
>
> *lean.enterprise.middleware*
>
> *Mobile  :- +94 71 7463047 <071%20746%203047>*
>
>- *Linkedin* *:-
>https://www.linkedin.com/in/dineth-chalitha-basnayake-a79032ba/
>*
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [CARBON] C4 Migration from Log4J 1.x to Log4J 2.x

[KasunG Gajasinghe]

On Mon, Jul 31, 2017 at 3:50 PM, KasunG Gajasinghe <kas...@wso2.com> wrote:

> Hi Asma,
>
> Can you explain why we need to do this from a user perspective?  What are
> the advantages/disavantages?
>
> Log4j does not support the Log4j properties file format. So, this change
> is not backward-compatible.
>
> On Mon, Jul 31, 2017 at 2:53 PM, Asma Jabir <as...@wso2.com> wrote:
>
>> The logging framework for C4 will be implemented using pax-logging as
>> illustrated in the simple diagram below.
>>
>> [image: Inline image 3]
>>
>> As shown above:
>>
>>- org.wso2.carbon.logging will act as the Logging API
>>- *org.ops4j.pax.logging.pax-logging-log4j2.jar* will bridge the logs
>>to log4J2
>>- The custom appenders will be residing in a fragment of
>>*org.ops4j.pax.logging.pax-logging-log4j2*
>>
>> Also,
>>
>>- pax-logging.properties file will be added which points to the
>>log4j2.properties file for configurations
>>- org.wso2.carbon.logging.propfile_1.0.0.jar will be removed as it is
>>no longer necessary to provide the configuration in the classpath of the
>>org.wso2.carbon.logging
>>
>> Moreover, there is a log4j.properties file in org.wso2.carbon.server
>> which is used for writing the logs before OSGi is started. Also there is
>> logging-bridge.properties file which is the configuration file used for JUL
>> (java-util-logging). Therefore, similar to C5, the following changes will
>> be done in this module to reduce configuration files.
>>
>>- Currently org.wso2.carbon.server uses JCL (commons-logging) and
>>this will be changed to JUL
>>- *This eliminates the need for a separate log4j configuration file
>>for org.wso2.carbon.server.* Thus log4j.properties residing
>>inside org.wso2.carbon.server will be removed
>>- This resolves [1]
>>- All the configurations related to org.wso2.carbon.server will be
>>written in
>>* $CARBON_HOME/repository/conf/etc/logging-bridge.properties*
>>
>>
>> We are looking forward to move forward with this method and appreciate
>> your comments/suggestions on this.
>>
>>
>>
>> Regards,
>> Asma
>>
>> On Mon, Jul 17, 2017 at 11:38 AM, Asma Jabir <as...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> We already have a central logging module in the kernel which is
>>> org.wso2.carbon.logging [1] and that acts similar to the a Logging API. So
>>> we can can continue to use it and all the logging specific dependencies and
>>> imports will be residing here. But the custom appenders are located in
>>> org.wso2.carbon.utils [2] since it is the first to get resolved and
>>> therefore, this would have changes when re-writing the appenders. Overall,
>>> the changes will be only inside the kernel and application will not need
>>> any changes.
>>>
>>> Moreover, after further experimenting for approach 1 and 2 which were
>>> implementable, the following were understood.
>>>
>>>- When using plain log4j 2, it cannot be used with with the default
>>>functionality
>>>   - The bridge from jcl-log4j is implemented using a ServiceLoader
>>>   which needs special handling in OSGi environment [3].
>>>   - Also this needs additional OSGi fragments as stated in point 2
>>>   in the first mail
>>>   - The configuration file(log4j.properties) is currently packed to
>>>   carbon logging using a fragmented bundle (
>>>   org.wso2.carbon.logging.propfile_1.0.0.jar) - same method can be
>>>   follwed for log4j2 or the file can be given through a system property 
>>> which
>>>   makes org.wso2.carbon.logging.propfile_1.0.0.jar unnecessary
>>>
>>>
>>>- Also, external .jar files are not able to find the logging
>>>implementation which we are still investigating as to why this happens
>>>
>>> The above had been happening since the log4j2 implementation was not
>>> found in OSGi environment and it was not related to external jars.
>>> Therefore, by providing the configuration files *log4j-provider.properties
>>> *and *log4j2.properties,* in carbon-logging the issue was fixed.
>>>
>>>
>>>- Pax-logging overcomes the above issues and therefore, the default
>>>pax-logging api can be used
>>>   - This provides log4j2 bridge internally which will map any type
>>>   of logging to log4j2
>>> 

Re: [Architecture] License header in confi files

[KasunG Gajasinghe]

+1 Azeez. And, we should not blindly add them either. In the latest
carbon-commons version, the INFO message box displays the license text. [1]
:(

[1] https://github.com/wso2/carbon-commons/issues/273

On Wed, Jun 28, 2017 at 11:55 AM, Afkham Azeez  wrote:

> I was wondering whether we really need the license header in config files.
> These are files that will be edited by the users, and it really doesn't
> make much sense to have the license there, and also it makes the files
> unnecessarily long.
>
> How about removing the license headers from config files, going forward?
>
> --
> *Afkham Azeez*
> Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <077%20332%200919>blog: **http://blog.afkham.org*
> 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] WSO2 Enterprise Integrator 6.1.0 Released

[KasunG Gajasinghe]

+announce

On Tue, Apr 18, 2017 at 10:49 AM, Eranda Rajapakshe 
wrote:

> *WSO2 Enterprise Integrator 6.1.0 Released*
>
> WSO2 Enterprise Integrator team is pleased to announce the release of WSO2
> Enterprise Integrator 6.1.0.
>
> *Release Note*
>
> April 2017
>
> WSO2 EI is a unified distribution of WSO2 Enterprise Service Bus and Data
> Services Server, which works as a single runtime (Integrator) along with
> optional runtimes for WSO2 Analytics, Business Processor, Message Broker
> and MSF4J. This product distribution includes a shared component directory,
> with profile-based management capabilities for each runtime.
>
> WSO2 EI simplifies integration by allowing users to easily configure
> message routing, inter-mediation, transformation, logging, task scheduling,
> load balancing, failover routing, event brokering etc. Data services and
> various applications can also be hosted and exposed using WSO2 EI. These
> integration capabilities are further powered by the capabilities of the
> WSO2 Analytics, Business Processor and Message Broker runtimes.
>
>
> For more information on WSO2 Enterprise Integrator 6.1.0 and to download
> the product and tooling please visit http://wso2.com/integration/
>
>
> For WSO2 EI 6.1.0 Documentation, please visit
> https://docs.wso2.com/display/EI610/About+WSO2+Enterprise+Integrator
>
> Source can be found in
>
> EI Runtime 
>
> EI Tooling
> 
>
> Issues Fixed for this release
>
> https://github.com/wso2/product-ei/issues?q=is%3Aissue+is%3A
> closed+milestone%3A6.1.0
>
> *Known Issues*
>
> For a complete list of features to be implemented please refer the list of
> known issues :
>
> https://github.com/wso2/product-ei/issues
> Contact us
>
> WSO2 developers can be contacted via the mailing list: d...@wso2.org
>
> For details on subscriptions see http://wso2.org/mail
> Support
>
> We are committed to ensuring that your enterprise middleware deployment is
> completely supported from evaluation to production. Our unique approach
> ensures that all support leverages our open development methodology and is
> provided by the very same engineers who build the technology.
>
> For more details and to take advantage of this unique opportunity please
> visit http://wso2.com/support/
>
> Thank you for your interest in WSO2 Enterprise Integrator 6.1.0.
>
>
> - The WSO2 EI Team -
>
> --
> *Eranda Rajapakshe*
> Software Engineer
> WSO2 Inc.
> Mobile : +94784822608
>
> ___
> Dev mailing list
> d...@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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5][IS 6.0.0] Add and Update Group UI for IS 6.0.0

[KasunG Gajasinghe]

On Thu, Mar 16, 2017 at 8:50 AM, Pushpalanka Jayawardhana 
wrote:

>
>
> On Thu, Mar 16, 2017 at 8:46 AM, Pushpalanka Jayawardhana 
> wrote:
>
>> Hi All,
>>
>> I am working on implementing 'add group' and 'update group' UIs for IS
>> 6.0.0 as per the wire-frames [1] and [2].
>>
>> In group addition, user experience will be as, in the 'General' tab user
>> provides name and description of the role.
>> User can either conclude the group addition flow here or go to 'Users'
>> tab to select users who will be in this group.
>> User can either conclude the flow here or go to 'Roles' tab to select the
>> roles to be assigned to all the users in the newly added group.
>>
>
What this means is this the 'General', 'Users', 'Roles' tabs are part of a
wizard. Further, users don't need to complete all the pages in wizard; they
can finish at any step.

I think the current UI fails to capture that each of them are part of a
wizard. It looks quite ambiguous to me. @Dakshika, Minoli, can you guys
review this again to see what we can do? It may be as simple as adding a
'Next' button, or a complete overhaul.

Thanks,
KasunG



> At initial phase, only general and user tabs will be there as role
> management features are still to be reviewed.
>
>>
>> Same goes with the update flow.
>>
>> Claims will be defined for the group, to keep track of the attributes of
>> the group, such as group description.
>> Any thoughts are welcome to improve the flow or design.
>>
>> [1] - https://github.com/wso2-dev-ux/product-is/blob/master/Wire
>> frames/admin-portal/v3/4.2%20Add%20group%20-%20general%20info.png
>> [2] - https://github.com/wso2-dev-ux/product-is/blob/master/Wire
>> frames/admin-portal/v3/4.8%20Edit%20group%20-%20general%20info.png
>>
>> Thanks,
>> --
>> Pushpalanka.
>> --
>> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
>> Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
>> Mobile: +94779716248
>> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: lk.linkedin.com/in/p
>> ushpalanka/ | Twitter: @pushpalanka
>>
>>
>
>
> --
> Pushpalanka.
> --
> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
> Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
> Mobile: +94779716248
> Blog: pushpalankajaya.blogspot.com/ | LinkedIn: lk.linkedin.com/in/
> pushpalanka/ | Twitter: @pushpalanka
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [IAM] [IS 6.0.0] Moving to global configuration model

[KasunG Gajasinghe]

On Tue, Mar 14, 2017 at 5:59 PM, Danesh Kuruppu  wrote:

>
> We have to understand the pattern to follow when modifying/removing/adding
>> an item in a *list* with deployment.yaml. Copying the entire list to
>> deployment.yaml and modify accordingly is the straight-forward approach.
>>
>> But that does not scale well if the number of items is quite big like in
>> this config file [1]. May be we are overseeing something? Kernel folks,
>> please clarify.
>>
>> [1] https://github.com/wso2/carbon-identity-mgt/blob/master/
>> features/org.wso2.carbon.identity.claim.feature/resourc
>> es/conf/profile-mapping.yaml
>>
>>
>
> Currently we have to copy the entire list to deployment.yaml to
> add/modify/remove an item in a list, if you are getting the configuration
> object from config provider. We cannot edit bean variable value partially
> from the deployment.yaml.
> In this case, rather getting configuration bean object from the config
> provider, we can get only the configurations defined in the deployment.yaml
> from the method[1] and do the add/modify/delete logic at the component
> level.
>

Danesh, we can handle adding an item to a list with this method. But I
don't think we can do modifications or deletions since there is no way to
identify the existing item to modify. I don't see an immediate way to fix
this via deployment.yaml either!! One alternative is to identify this type
of configuration files, and keep them as it is.

Thanks.


> You need to pass the namespace value defined in bean class. So service
> will provide the configurations defined in the deployment.yaml as a Map. If
> configurations are not defined, it will return null.
>
> 1. https://github.com/wso2/carbon-kernel/blob/master/
> core/src/main/java/org/wso2/carbon/kernel/configprovider/
> ConfigProvider.java#L45
>
> Thanks
> --
>
> *Danesh Kuruppu*
> Senior Software Engineer | WSO2
> Curren
> Email: dan...@wso2.com
> Mobile: +94 (77) 1690552 <077%20169%200552>
> Web: WSO2 Inc 
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [IAM] [IS 6.0.0] Moving to global configuration model

[KasunG Gajasinghe]

On Thu, Mar 9, 2017 at 12:17 PM, Ashen Weerathunga  wrote:

>
>
> On Thu, Mar 9, 2017 at 11:06 AM, Harsha Thirimanna 
> wrote:
>
>>
>> On Thu, Mar 9, 2017 at 10:49 AM, Ashen Weerathunga 
>> wrote:
>>
>>> Hi all,
>>>
>>> We are in the process of moving carbon identity mgt [1] to the global
>>> configuration model [2]. In this model, we need to maintain all the server
>>> configurations in one configuration file (deployment.yaml). Currently, we
>>> have a number of config files in the carbon identity mgt as below (please
>>> add if I have missed any).
>>>
>>>- claim-mapping
>>>
>>> 
>>>- profile-mapping
>>>
>>> 
>>>- domain-config
>>>
>>> 
>>>- store-config
>>>
>>> 
>>>- challenge-questions
>>>
>>> 
>>>- identity-management
>>>
>>> 
>>>
>>> But as for the new model what are the configs that we need to move to
>>> deployment.yaml?
>>>
>>
>> ​What you mean by, "what are the configs" ?
>> Because anyway we have to move all into an one file, right ? That is not
>> possible to keep multiple files as in new model. Please make me correct if
>> I didn't get what meant.​
>>
>
> Yes. But shouldn't we need to distinguish between data and server configs?
>
> Basically as for the new model we need to defined default config values in
> the bean classes. If we need to override the default values, we need to
> copy the configuration segment to the deployment.yaml file and change the
> value. The server will pick the new configs from the deployment.yaml
>
> As an example we have large list in challenge questions
> 
> file. If we are moving this to deployement.yaml we need to add all this
> data to a bean class as default values. So AFAIU even if we need to add one
> more question we will have to add all these questions with the new question
> to the deployment.yaml. So is this the correct approach?
>
>

We have to understand the pattern to follow when modifying/removing/adding
an item in a *list* with deployment.yaml. Copying the entire list to
deployment.yaml and modify accordingly is the straight-forward approach.

But that does not scale well if the number of items is quite big like in
this config file [1]. May be we are overseeing something? Kernel folks,
please clarify.

[1]
https://github.com/wso2/carbon-identity-mgt/blob/master/features/org.wso2.carbon.identity.claim.feature/resources/conf/profile-mapping.yaml

Thanks,
KasunG


>>> [1] https://github.com/wso2/carbon-identity-mgt
>>> [2] https://github.com/wso2/carbon-kernel/blob/master/docs/D
>>> eveloperTools/UpdatingConfigurations.md
>>>
>>> Thanks,
>>> Ashen
>>> --
>>> *Ashen Weerathunga*
>>> Software Engineer
>>> WSO2 Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Email: as...@wso2.com
>>> Mobile: +94716042995 <94716042995>
>>> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
>>> *
>>> 
>>>
>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94716042995 <94716042995>
> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
> *
> 
>



-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Multiple runtime support for C5 based products

[KasunG Gajasinghe]

Hi Danesh,

Please find some comments in-line.

On Wed, Mar 8, 2017 at 8:16 PM, Danesh Kuruppu  wrote:

> Hi all,
>
> In C5 based products, we can have multiple runtimes in the product
> package. For each runtime, there will be configuration(deployment.yaml),
> securevault, execution scripts(carbon.sh etc), logs, deployment specific
> only for that runtime. resources(wso2carbon.jks) and lib directory will be
> common to every runtime and those are placed at top level.
> So the directory structure of the basic distribution will be something
> like,
>
>

What's the difference between top-level conf/ folder and the conf/ folders
under runtimes?

And, how will this new directory structure affect the p2.inf instructions?
In the p2.inf, we define from/where to the config files.



> wso2-carbon
>> |-- bin
>> |-- resources
>> |-- lib
>> |-- conf
>> |-- wso2
>> |-- 
>> |-- bin
>> |-- logs
>> |-- conf
>> |-- deployment.yaml
>> |-- log4j2.xml
>> |-- security
>> |-- secure-vault.yaml
>> |-- secrets.properties
>> |-- deployment
>> |-- 
>> 
>> |-- 
>> |-- lib
>> |-- features
>> |-- p2
>> |-- plugins
>>
>
>
>
> Each runtime will be started as different processes/JVM and for the
> distributed setup, we are going to provide a tool to run each runtime in
> different nodes/containers.
>

Does this mean we can run multiple runtimes at the same time from a given
product instance?

Thanks,
KasunG


> We are currently working on this. Please share your thoughts / suggestions.
>
> Thanks
> --
>
> *Danesh Kuruppu*
> Senior Software Engineer | WSO2
>
> Email: dan...@wso2.com
> Mobile: +94 (77) 1690552 <077%20169%200552>
> Web: WSO2 Inc 
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5] [Carbon-Feature-Plugin] Dynamic Creation of carbon.product via a Template

[KasunG Gajasinghe]

eve this is only needed at product build time, so we do not need
>>>>> to keep a file in the repo but only create the file during build time and
>>>>> then delete it (or may be use the target directory so that it will be
>>>>> anyway removed).
>>>>>
>>>> +1 to create the file at target directory during build time, I just
>>>> tested the implementation and it works fine. So, in going forward, we can
>>>> deprecate the static carbon.product file that exists in distribution folder
>>>> of the repo.
>>>>
>>>>>
>>>>> since both underlying, but external tycho and equinox launcher
>>>>>> plug-ins used by our carbon-feature-plugin require this file as an input.
>>>>>>
>>>>>> So IMO, the only improvement that we can introduce here is supporting
>>>>>> templated-dynamic-creation of the file at carbon-feature-plugin level
>>>>>> using the standard carbon kernel version values available in the
>>>>>> distribution pom.
>>>>>>
>>>>>> Thanks,
>>>>>> Dilan.
>>>>>>
>>>>>> *Dilan U. Ariyaratne*
>>>>>> Senior Software Engineer
>>>>>> WSO2 Inc. <http://wso2.com/>
>>>>>> Mobile: +94766405580 <%2B94766405580>
>>>>>> lean . enterprise . middleware
>>>>>>
>>>>>>
>>>>>> On Mon, Jan 23, 2017 at 7:33 AM, Kishanthan Thangarajah <
>>>>>> kishant...@wso2.com> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Jan 20, 2017 at 5:57 PM, Afkham Azeez <az...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I would suggest totally getting rid of it.
>>>>>>>>
>>>>>>>
>>>>>>> To maintain backward compatibility of the plugin, we need to have
>>>>>>> the file based supported. But from next major release of the plugin, we 
>>>>>>> can
>>>>>>> remove the usage of this file and use the pom based approach only.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Jan 20, 2017 at 5:24 PM, KasunG Gajasinghe <kas...@wso2.com
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> +1. carbon.product file hasn't really been used by the products.
>>>>>>>>> So, +1 to make it optional.
>>>>>>>>>
>>>>>>>>> On Fri, Jan 20, 2017 at 3:06 PM, Dilan Udara Ariyaratne <
>>>>>>>>> dil...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Folks,
>>>>>>>>>>
>>>>>>>>>> In the process of building C5, we currently require
>>>>>>>>>> carbon.product for the following goals.
>>>>>>>>>> [1] publish-product
>>>>>>>>>> [2] generate-runtime
>>>>>>>>>>
>>>>>>>>>> This file maintains current version of the carbon kernel to be
>>>>>>>>>> utilized by "carbon-feature-plugin" in the build process.
>>>>>>>>>> Keeping this value in carbon.product prevents the kernel from
>>>>>>>>>> been auto-released as it requires manual intervention to bump
>>>>>>>>>> version values as necessary during the release process.
>>>>>>>>>>
>>>>>>>>>> In order to solve this issue, we are currently in the process of
>>>>>>>>>> improving Carbon-Feature-Plugin to dynamically create this file 
>>>>>>>>>> during
>>>>>>>>>> build time using
>>>>>>>>>> a template where the necessary version value information is read
>>>>>>>>>> from corresponding distribution pom file.
>>>>>>>>>>
>>>>>>>>>> In order to support backward compatibility, we will still
>>>>>>>>>> maintain the original approach of keeping a carbon.product file 
>>>>>&g

Re: [Architecture] [Dev] WSO2 Enterprise Integrator 6.0.0 Milestone 2 Released !

[KasunG Gajasinghe]

Ok, thanks.

On Wed, Feb 1, 2017 at 4:50 PM, Nilmini Perera <nilm...@wso2.com> wrote:

> Hi all,
>
> A small change regarding the availability of documentation.
>
> We will make the documentation for EI public by mid next week.
> Since EI is merging multiple products, the current state of the
> documentation does not give the clearest picture about EI as a single
> product. We will do some more improvements to it before making it public.
>
> So, please note that we will not make the docs public EOD.
>
> Thanks.
>
> On Wed, Feb 1, 2017 at 11:36 AM, Malith Munasinghe <mali...@wso2.com>
> wrote:
>
>> Hi Kasun,
>>
>> On Wed, Feb 1, 2017 at 1:39 AM, KasunG Gajasinghe <kas...@wso2.com>
>> wrote:
>>
>>> Hi Malith,
>>>
>>> Have we prepared the vision docs for EI? Since this is a new product
>>> created by merging multiple products together, I'd like to know how we are
>>> positioning this.
>>>
>>
>>>
>>> Also, please provide the link to the documentation.
>>>
>>
>> The documentation for the product EI will be available EOD today.
>>
>>
>>>
>>> Thanks,
>>> KasunG
>>>
>>>
>>> On Tue, Jan 31, 2017 at 10:34 PM, Malith Munasinghe <mali...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> The WSO2 Integration team is pleased to announce the 2nd Milestone
>>>> release of WSO2 Enterprise Integrator (EI)  6.0.0.
>>>>
>>>> Source & binary distribution files of WSO2 Enterprise Integrator 6.0.0
>>>>
>>>> Distribution :  https://github.com/wso2/produ
>>>> ct-ei/releases/tag/v6.0.0-m2
>>>> Known Issues : https://github.com/wso2/product-ei/issues
>>>>
>>>> Thanks
>>>> ~Integration Team~
>>>> --
>>>> Malith Munasinghe | Software Engineer
>>>> M: +94 (71) 9401122 <+94%2071%20940%201122>
>>>> E: mali...@wso2.com
>>>> W: http://wso2.com
>>>> <http://wso2.com/signature>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> d...@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
>>> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>>>
>>>
>>
>>
>>
>> --
>> Malith Munasinghe | Software Engineer
>> M: +94 (71) 9401122 <+94%2071%20940%201122>
>> E: mali...@wso2.com
>> W: http://wso2.com
>> <http://wso2.com/signature>
>>
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nilmini Perera
>
> Associate Lead Technical Writer
> WSO2 Inc.
>
> Mobile: 0094776722152 <077%20672%202152>
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Fwd: Why re-write User class? Why re-wrap RealmService?

[KasunG Gajasinghe]

Hi Shariq,

On Wed, Feb 1, 2017 at 4:45 PM, Muhammed Shariq <sha...@wso2.com> wrote:

>
> On Wed, Feb 1, 2017 at 1:10 AM, KasunG Gajasinghe <kas...@wso2.com> wrote:
>
>> Hi Manu,
>>
>> #1. Because UUF's #createSession function expects an instance
>> of org.wso2.carbon.uuf.spi.auth.User not org.wso2.carbon.identity.mgt.
>> User.
>>
>> But, this is actually an improvement that we need to do. UUF should
>> either use org.wso2.carbon.identity.mgt.User or an extended class. We
>> should not have two User objects. *@UUF team*, what are you thoughts on
>> this?
>>
>
> If we do this, UUF will have a dependency to identity related components,
> that's not a good design IMO.
>


Carbon-identity-mgt is for Managing user identities. The User object in
there represents an identity. So, why do we have to maintain a separate
User hierarchy?

Thanks,
KasunG


>
>>
>> #2. The reason is to have a balance between Nashorn js code and Java
>> code. If we eliminate this client service class, then we have to move the
>> code to Nashorn js. So, this does not result in less code. Having a client
>> class is preferable since Java execution is faster and developers are more
>> familiar with that.
>>
>> On Tue, Jan 31, 2017 at 8:31 PM, Danushka Fernando <danush...@wso2.com>
>> wrote:
>>
>>> I guess the idea was to write an api layer for web app which will call
>>> backend services and get all the data and do all the processing and return
>>> data sets that can directly be used in the frond end / UUF application. If
>>> there are no security reasons, +1 to remove the Middle man.
>>>
>>> [1] https://sourcemaking.com/refactoring/smells/middle-man
>>>
>>> Thanks & Regards
>>> Danushka Fernando
>>> Senior Software Engineer
>>> WSO2 inc. http://wso2.com/
>>> Mobile : +94716332729 <071%20633%202729>
>>>
>>> On Tue, Jan 31, 2017 at 8:14 PM, Manuranga Perera <m...@wso2.com> wrote:
>>>
>>>>
>>>> -- Forwarded message --
>>>> From: Manuranga Perera <m...@wso2.com>
>>>> Date: Tue, Jan 31, 2017 at 2:44 PM
>>>> Subject: Why re-write User class? Why re-wrap RealmService?
>>>> To: Kasun Gajasinghe <kas...@wso2.com>, Indunil Upeksha Rathnayake <
>>>> indu...@wso2.com>, Danushka Fernando <danush...@wso2.com>, Ayesha
>>>> Dissanayaka <aye...@wso2.com>
>>>> Cc: Kishanthan Thangarajah <kishant...@wso2.com>, Rasika Perera <
>>>> rasi...@wso2.com>, Shariq Muhammed <sha...@wso2.com>, Shan Mahanama <
>>>> sh...@wso2.com>, Sajith Ariyarathna <sajit...@wso2.com>
>>>>
>>>>
>>>> 1) Why have we written org.wso2.is.portal.user.client.api.bean.UUFUser
>>>> instead of just reusing org.wso2.carbon.identity.mgt.User ?
>>>>
>>>>
>>>> 2) Even better, is there anything stopping us from directly calling
>>>> RealmService OSGi service from the UUF js (eg: for list users) instead
>>>> going through IdentityStoreClientServiceImpl wrapper.
>>>>
>>>> Less code the better.
>>>>
>>>> --
>>>> With regards,
>>>> *Manu*ranga Perera.
>>>>
>>>> phone : 071 7 70 20 50
>>>> mail : m...@wso2.com
>>>>
>>>>
>>>>
>>>> --
>>>> With regards,
>>>> *Manu*ranga Perera.
>>>>
>>>> phone : 071 7 70 20 50
>>>> mail : m...@wso2.com
>>>>
>>>> ___
>>>> Dev mailing list
>>>> d...@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>> ___
>>> Dev mailing list
>>> d...@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
>> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813
>>
>>
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks,
> Shariq
> Associate Technical Lead
>



-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] WSO2 Enterprise Integrator 6.0.0 Milestone 2 Released !

[KasunG Gajasinghe]

Hi Malith,

Have we prepared the vision docs for EI? Since this is a new product
created by merging multiple products together, I'd like to know how we are
positioning this.

Also, please provide the link to the documentation.

Thanks,
KasunG


On Tue, Jan 31, 2017 at 10:34 PM, Malith Munasinghe 
wrote:

> Hi All,
>
> The WSO2 Integration team is pleased to announce the 2nd Milestone release
> of WSO2 Enterprise Integrator (EI)  6.0.0.
>
> Source & binary distribution files of WSO2 Enterprise Integrator 6.0.0
>
> Distribution :  https://github.com/wso2/product-ei/releases/tag/v6.0.
> 0-m2
> Known Issues : https://github.com/wso2/product-ei/issues
>
> Thanks
> ~Integration Team~
> --
> Malith Munasinghe | Software Engineer
> M: +94 (71) 9401122 <+94%2071%20940%201122>
> E: mali...@wso2.com
> W: http://wso2.com
> 
>
> ___
> Dev mailing list
> d...@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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5] [Carbon-Feature-Plugin] Dynamic Creation of carbon.product via a Template

[KasunG Gajasinghe]

+1. carbon.product file hasn't really been used by the products. So, +1 to
make it optional.

On Fri, Jan 20, 2017 at 3:06 PM, Dilan Udara Ariyaratne 
wrote:

> Hi Folks,
>
> In the process of building C5, we currently require carbon.product for the
> following goals.
> [1] publish-product
> [2] generate-runtime
>
> This file maintains current version of the carbon kernel to be utilized by
> "carbon-feature-plugin" in the build process.
> Keeping this value in carbon.product prevents the kernel from been
> auto-released as it requires manual intervention to bump
> version values as necessary during the release process.
>
> In order to solve this issue, we are currently in the process of improving
> Carbon-Feature-Plugin to dynamically create this file during build time
> using
> a template where the necessary version value information is read from
> corresponding distribution pom file.
>
> In order to support backward compatibility, we will still maintain the
> original approach of keeping a carbon.product file somewhere appropriate
> in the distribution folder and read it accordingly when
>  tag is present in the pom file.
>
> In the meantime, as the way to go forward, we will introduce the following.
>
> Carbon-Feature-Plugin will be updated to read version and other optional
> values that were originally persisted in the file, from the pom itself.
> After reading these values, plugin will dynamically create the
> carbon.product which will then be taken into reference by underlying
> eclipse.tycho plugin as in the usual way of execution.
>
> WDYT ?
>
> Thank You.
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [IS 6.0.0] [User Portal] Challenge Questions in Self sign-up page of user portal

[KasunG Gajasinghe]

Security questions are a thing of the past. Google, Facebook they all have
removed the security questions based password recovery mechanisms. [1] [2]
 So, +1 to drop this support in IS 6.

[1]
http://googlesystem.blogspot.com/2014/12/google-drops-support-for-security.html
[2] https://www.facebook.com/help/community/question/?id=815382261879187

On Wed, Jan 18, 2017 at 5:37 PM, Nuwan Dias  wrote:

>
>
> On Wed, Jan 18, 2017 at 5:10 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> Currently we are working on implementing C5 user portal in IS. Appreciate
>> your suggestions/ideas for the following concerns regarding challenge
>> questions.
>>
>> *1)  Is it necessary to include challenge questions in IS 6.0.0 as a
>> recovery option?*
>> Seems like secret questions are neither secure nor reliable enough to be
>> used as a account recovery mechanism. And also most of the vendors has
>> completely removed support for security questions including google. In C5,
>> security question sets will be some what strengthen the recovery and makes
>> it hard to guess the questions. But seems like need to consider whether it
>> need to be implemented or not.
>>
>
> I personally have never used a security question to recover any of the
> accounts of which I forgot passwords. Its always a recovery through email
> or mobile. Therefore I don't see this as a valuable feature.
>
>>
>> *2)  Is it necessary to include security questions in user self sign-up
>> page? If needed, following way is appropriate?*
>> As we have planned, in C5, admin can create several security question
>> sets and can configure the minimum number of questions that need to be
>> answered by a user. So that in self sign up UI when populating security
>> questions to a user,
>>
>>- security questions need to be categorized according to the security
>>question sets
>>- all the sets need to be populated for the user
>>- user can select any number of security questions from different
>>sets not from a same set
>>- need to validate whether the user has answered for the minimum
>>number of questions
>>
>> When an answer to a question is personal, the question itself is probably
> personal too. Therefore I don't think an admin can decide on what questions
> to be asked from you. Its unlikely you'll remember an answer to a question
> which is not very relevant to you. If we're doing this (I'm negative on
> implementing the feature itself too :)), I think we should let the user
> decide his own questions and answers.
>
>
>> Appreciate your ideas on this.
>>
>> Thanks and Regards
>> --
>> Indunil Upeksha Rathnayake
>> Software Engineer | WSO2 Inc
>> Emailindu...@wso2.com
>> Mobile   0772182255 <077%20218%202255>
>>
>> ___
>> Dev mailing list
>> d...@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <077%20777%205729>
>



-- 

*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
phone: +1 650-745-4499, 77 678 0813
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] SSO Quick Start Guide for AS6

[KasunG Gajasinghe]

Hi Chanaka,

Where can I find the guide to run the quickstart?

Thanks.

On Tue, Sep 6, 2016 at 11:35 AM, Chanaka Cooray  wrote:

> Hi,
>
> From WSO2 Application Server(AS) 6.0.0-m3 onwards, it
> supports Single-Sign-On (SSO) for web applications with WSO2 Identity
> Server(IS). In addition to that, we are in the process of implementing
> $subject to demonstrate SSO functionality in AS 6.0.0 to the user with
> minimum configuration.
>
> The user would be able to run the sample by just running the script
> instead of going through the whole SSO documentation[1] to configure the
> SSO feature. The script is supposed to do the following things in order to
> configure the sample.
>
>- Configurations in both AS and IS
>   - configure wso2as-web.xml and server.xml files in AS
>   - configure service providers in IS
>- Deploy the SSO samples in AS
>   - deploy two sample web apps in the web apps directory
>- Start the two servers (AS and IS)
>- Create a new user in IS to log into the web apps
>   - using real world username and password will be more effective for
>   a sample than the default admin user.
>
> Addition to this script, we provide another script to clean the
> configuration changes made in the main script. By running the clean script,
> the user would be able to bring the default configurations in the AS.
>
> [1] https://docs.wso2.com/display/AS600/Accessing+
> Applications+using+Single+Sign-On
>
> Thanks,
> Chanaka.
> --
> Chanaka Cooray
> Software Engineer, WSO2 Inc. http://wso2.com
> Email: chana...@wso2.com
> Mobile: +94713149860
> 
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [C5] Upgrading Kernel Equinox version to Neon Releases

[KasunG Gajasinghe]

+1. It's good that we identified the issues that has previously prevented
us updating to latest Equinox version.

Thanks,
KasunG

On Tue, Jul 5, 2016 at 7:57 PM, Niranjan Karunanandham 
wrote:

> +1 to upgrade the tycho plugin. Currently we are using 0.13.0 and AFAIR
> the latest one is 0.25.0.
>
> Regards,
> Nira
>
> On Tue, Jul 5, 2016 at 3:11 PM, Sameera Jayasoma  wrote:
>
>> +1 for this.
>>
>> On Tue, Jul 5, 2016 at 2:48 PM, Chanaka Cooray  wrote:
>>
>>> [+architecture]
>>>
>>> On Tue, Jul 5, 2016 at 1:53 PM, Chanaka Cooray 
>>> wrote:
>>>
 Hi all,

 We have decided to upgrade the equinox version in kernel to Neon
 release which is the latest release of the equinox[1]. This has to be done
 due to several issues in kernel including [2] with the current equinox
 version.
 Addition to that, it is also required to upgrade tycho versions in
 carbon-maven-plugins [3] because of a jarsigner issue with the JDK 7, 8.

 [1] http://download.eclipse.org/equinox/
 [2] https://wso2.org/jira/browse/CARBON-15976
 [3] https://github.com/wso2/carbon-maven-plugins

 Thanks,
 Chanaka.
 --
 Chanaka Cooray
 Software Engineer, WSO2 Inc. http://wso2.com
 Email: chana...@wso2.com
 Mobile: +94713149860


>>>
>>>
>>> --
>>> Chanaka Cooray
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> Email: chana...@wso2.com
>>> Mobile: +94713149860
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Software Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://blog.sameera.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>> Lean . Enterprise . Middleware
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
>
> *Niranjan Karunanandham*
> Associate Technical Lead - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
> ___
> Dev mailing list
> d...@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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] [C5] Upgrading Kernel Equinox version to Neon Releases

[KasunG Gajasinghe]

Chanaka, let's test the fix for carbon-feature-plugin, and go for an
immediate release. Kernel version upgrade can be followed after that.

On Wed, Jul 6, 2016 at 11:39 AM, KasunG Gajasinghe <kas...@wso2.com> wrote:

>
> +1. It's good that we identified the issues that has previously prevented
> us updating to latest Equinox version.
>
> Thanks,
> KasunG
>
> On Tue, Jul 5, 2016 at 7:57 PM, Niranjan Karunanandham <niran...@wso2.com>
> wrote:
>
>> +1 to upgrade the tycho plugin. Currently we are using 0.13.0 and AFAIR
>> the latest one is 0.25.0.
>>
>> Regards,
>> Nira
>>
>> On Tue, Jul 5, 2016 at 3:11 PM, Sameera Jayasoma <same...@wso2.com>
>> wrote:
>>
>>> +1 for this.
>>>
>>> On Tue, Jul 5, 2016 at 2:48 PM, Chanaka Cooray <chana...@wso2.com>
>>> wrote:
>>>
>>>> [+architecture]
>>>>
>>>> On Tue, Jul 5, 2016 at 1:53 PM, Chanaka Cooray <chana...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> We have decided to upgrade the equinox version in kernel to Neon
>>>>> release which is the latest release of the equinox[1]. This has to be done
>>>>> due to several issues in kernel including [2] with the current equinox
>>>>> version.
>>>>> Addition to that, it is also required to upgrade tycho versions in
>>>>> carbon-maven-plugins [3] because of a jarsigner issue with the JDK 7, 8.
>>>>>
>>>>> [1] http://download.eclipse.org/equinox/
>>>>> [2] https://wso2.org/jira/browse/CARBON-15976
>>>>> [3] https://github.com/wso2/carbon-maven-plugins
>>>>>
>>>>> Thanks,
>>>>> Chanaka.
>>>>> --
>>>>> Chanaka Cooray
>>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>>> Email: chana...@wso2.com
>>>>> Mobile: +94713149860
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Chanaka Cooray
>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>> Email: chana...@wso2.com
>>>> Mobile: +94713149860
>>>>
>>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Software Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://blog.sameera.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>>
>> *Niranjan Karunanandham*
>> Associate Technical Lead - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>> ___
>> Dev mailing list
>> d...@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
>
>
>



-- 

*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

[KasunG Gajasinghe]

On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran <sinth...@wso2.com>
wrote:

> Hi,
>
> Anyhow ultimately when all the carbon products move to AS 6.0 based
> platform, we can merge all those into one.
>

Since, Carbon products will still be OSGi based using the embedded Tomcat,
Jaggery needs to support that as well.

As I understood, the deployment part differs mainly. ie. for AS6, you are
using a LifecycleListener; for Carbon, you have the JaggeryDeployer. The
rest can stay the same to a great extent. So, it's better if these two can
be merged into a single branch.

Thanks,
KasunG


> Thanks,
> Sinthuja.
>
> On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi Kasun,
>>
>> Yes.We can do a performance round. Currently we manage the Tomcat
>> Jaggery/ AS6 support code base under a new branch [1] in our jaggery
>> repository. Current jaggery is based on tomcat version 7 and Tomcat Jaggery
>> implementation is based on tomcat version 8. So there are some api changes
>> in the jaggery level. So it is difficult to manage these codebases in same
>> place.
>>
>> Thanks,
>> Nisala
>>
>> On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe <kas...@wso2.com>
>> wrote:
>>
>>>
>>> Good work Nisala.
>>>
>>> Can we also do a performance round to see whether there are any perf
>>> gains when running Jaggery apps in vanilla Tomcat/AS6?
>>>
>>> How are you going to manage the codebase for Carbon vs Tomcat Jaggery
>>> support? Better if we can maintain it in the same place.
>>>
>>> On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara <nis...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> This is an update regarding the feature 'Provide Support to run Jaggery
>>>> apps in Tomcat Server'.
>>>>
>>>> At present Jaggery scripts can only be executed in a jaggery server.
>>>> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is the
>>>> Runtime Environment that hosts Jaggery applications. The goal of this
>>>> feature is to provide support to run jaggery apps in a pure tomcat server
>>>> without any modifications to the jaggery apps.This will enable developers
>>>> to write Jaggery scripts and directly deploy them in apache tomcat server.
>>>> So this will improve the flexibility of the jaggery apps.
>>>>
>>>> This is an extension for the Apache tomcat 8 to run the jaggery app
>>>> without modifying it. Although this is implemented as a requirement of WSO2
>>>> Application Server 6, Users who want to run jaggery apps without jaggery
>>>> server, can use this feature to run their jaggery apps in Apache tomcat
>>>> server.
>>>>
>>>> I have attached the documentation and sample jaggery with this email.
>>>> Please find these attachments and relevant jaggery branch here[1]. Please
>>>> feel free to ask any questions.
>>>>
>>>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>>>
>>>> Thanks,
>>>> Nisala
>>>>
>>>> --
>>>> *Nisala Niroshana Nanayakkara,*
>>>> Software Engineer
>>>> Mobile:(+94)717600022
>>>> WSO2 Inc., http://wso2.com/
>>>>
>>>> ___
>>>> Dev mailing list
>>>> d...@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
>> d...@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
>
>
>


-- 

*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

[KasunG Gajasinghe]

On Mon, Jul 4, 2016 at 1:48 PM, Nisala Nanayakkara <nis...@wso2.com> wrote:

> Hi Manjula,
>
> Yes.Jaggery support will be inbuilt into the server with the release of
> AS-6.0.0 next milestone. This email and documentation is provided to inform
> the procedure of running jaggery apps in a pure tomcat server, not in the
> AS-6.0.0. I will update the finalized documentation and configuration
> details for AS-6.0.0 in a separate mail thread, once we finished the
> fine-tuning process.
>
> Thanks,
> Nisala
>
> On Mon, Jul 4, 2016 at 1:39 PM, Manjula Rathnayake <manju...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> IIUC, when we release the next AS-6.0.0 milestone, jaggery support is
>> inbuilt into the server. And users do not need to follow above instructions
>> to copy jars etc. Please correct If it is not.
>>
>
Yes, that's the case. So, we need separate documentation on how to deploy
Jaggery apps in AS6 as well.


>
>> thank you.
>>
>> On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran <sinth...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Anyhow ultimately when all the carbon products move to AS 6.0 based
>>> platform, we can merge all those into one.
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara <nis...@wso2.com>
>>> wrote:
>>>
>>>> Hi Kasun,
>>>>
>>>> Yes.We can do a performance round. Currently we manage the Tomcat
>>>> Jaggery/ AS6 support code base under a new branch [1] in our jaggery
>>>> repository. Current jaggery is based on tomcat version 7 and Tomcat Jaggery
>>>> implementation is based on tomcat version 8. So there are some api changes
>>>> in the jaggery level. So it is difficult to manage these codebases in same
>>>> place.
>>>>
>>>> Thanks,
>>>> Nisala
>>>>
>>>> On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe <kas...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Good work Nisala.
>>>>>
>>>>> Can we also do a performance round to see whether there are any perf
>>>>> gains when running Jaggery apps in vanilla Tomcat/AS6?
>>>>>
>>>>> How are you going to manage the codebase for Carbon vs Tomcat Jaggery
>>>>> support? Better if we can maintain it in the same place.
>>>>>
>>>>> On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara <nis...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> This is an update regarding the feature 'Provide Support to run
>>>>>> Jaggery apps in Tomcat Server'.
>>>>>>
>>>>>> At present Jaggery scripts can only be executed in a jaggery server.
>>>>>> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is 
>>>>>> the
>>>>>> Runtime Environment that hosts Jaggery applications. The goal of this
>>>>>> feature is to provide support to run jaggery apps in a pure tomcat server
>>>>>> without any modifications to the jaggery apps.This will enable developers
>>>>>> to write Jaggery scripts and directly deploy them in apache tomcat 
>>>>>> server.
>>>>>> So this will improve the flexibility of the jaggery apps.
>>>>>>
>>>>>> This is an extension for the Apache tomcat 8 to run the jaggery app
>>>>>> without modifying it. Although this is implemented as a requirement of 
>>>>>> WSO2
>>>>>> Application Server 6, Users who want to run jaggery apps without jaggery
>>>>>> server, can use this feature to run their jaggery apps in Apache tomcat
>>>>>> server.
>>>>>>
>>>>>> I have attached the documentation and sample jaggery with this email.
>>>>>> Please find these attachments and relevant jaggery branch here[1]. Please
>>>>>> feel free to ask any questions.
>>>>>>
>>>>>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>>>>>
>>>>>> Thanks,
>>>>>> Nisala
>>>>>>
>>>>>> --
>>>>>> *Nisala Niroshana Nanayakkara,*
>>>>>> Software Engineer
>>>>>> Mobile:(+94)717600022
>>>>>> WSO2 Inc., h

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

[KasunG Gajasinghe]

Good work Nisala.

Can we also do a performance round to see whether there are any perf gains
when running Jaggery apps in vanilla Tomcat/AS6?

How are you going to manage the codebase for Carbon vs Tomcat Jaggery
support? Better if we can maintain it in the same place.

On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara  wrote:

> Hi all,
>
> This is an update regarding the feature 'Provide Support to run Jaggery
> apps in Tomcat Server'.
>
> At present Jaggery scripts can only be executed in a jaggery server.
> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is the
> Runtime Environment that hosts Jaggery applications. The goal of this
> feature is to provide support to run jaggery apps in a pure tomcat server
> without any modifications to the jaggery apps.This will enable developers
> to write Jaggery scripts and directly deploy them in apache tomcat server.
> So this will improve the flexibility of the jaggery apps.
>
> This is an extension for the Apache tomcat 8 to run the jaggery app
> without modifying it. Although this is implemented as a requirement of WSO2
> Application Server 6, Users who want to run jaggery apps without jaggery
> server, can use this feature to run their jaggery apps in Apache tomcat
> server.
>
> I have attached the documentation and sample jaggery with this email.
> Please find these attachments and relevant jaggery branch here[1]. Please
> feel free to ask any questions.
>
> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>
> Thanks,
> Nisala
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> d...@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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Dep sync strategies for Carbon 4 products in Kubernetes

[KasunG Gajasinghe]

On Wed, Jun 8, 2016 at 5:42 PM, Akila Ravihansa Perera <raviha...@wso2.com>
wrote:

> Hi KasunG,
>
> How do you handle multiple manager scenario (for HA deployment) with the
> implementation that you have done? And what do you mean by standalone
> cluster mode?
>
>
What I meant was that this is for clustered deployments that are not
deployed on containers. A typical standard cluster.


> If we run this cron job on multiple managers then it can cause overwrites
> unless there is some kind of cluster coordination right?
>

Active-active multiple managers are not easy handle with rsync as I see
since you can't sync the folders in a bi-directional manner. In cases like
that, some kind of version control system is needed. This is where the SVN
based depsync comes in.


>
> Thanks.
>
>
> On Wednesday, 8 June 2016, KasunG Gajasinghe <kas...@wso2.com> wrote:
>
>>
>> We've also written rsync based artifact synchronization for the
>> stand-alone cluster mode. [1] This pushes the artifacts to workers
>> periodically via a cron job. A shared public key is used for
>> authentication.
>>
>> [1] https://gist.github.com/kasunbg/444df28a2e51a16bbd74
>>
>> On Wed, Jun 8, 2016 at 5:05 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Manoj,
>>>
>>> How are those multiple managers going to sync artifacts between each
>>> other using rsync? LB will route traffic only to 1st manager node and the
>>> 2nd manager node as the fail-over, right? If all the managers try to push
>>> artifacts to workers then there will be conflicts/overwrites.
>>>
>>>
>>> I think the whole artifacts deployment/sync strategy is going to be
>>> changed from C5 on-wards. AFAIU, we will not be publishing artifacts to
>>> gateway nodes directly in C5. Rather those artifacts will be injected at
>>> the Docker image build process. So why don't we stick with SVN based
>>> DepSync for now (C4 products)? What is the problem that we are trying to
>>> solve by moving to rsync that we couldn't/cannot fix in SVN based model?
>>>
>>> Thanks.
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *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
>>
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Dep sync strategies for Carbon 4 products in Kubernetes

[KasunG Gajasinghe]

We've also written rsync based artifact synchronization for the stand-alone
cluster mode. [1] This pushes the artifacts to workers periodically via a
cron job. A shared public key is used for authentication.

[1] https://gist.github.com/kasunbg/444df28a2e51a16bbd74

On Wed, Jun 8, 2016 at 5:05 PM, Akila Ravihansa Perera 
wrote:

> Hi Manoj,
>
> How are those multiple managers going to sync artifacts between each other
> using rsync? LB will route traffic only to 1st manager node and the 2nd
> manager node as the fail-over, right? If all the managers try to push
> artifacts to workers then there will be conflicts/overwrites.
>
>
> I think the whole artifacts deployment/sync strategy is going to be
> changed from C5 on-wards. AFAIU, we will not be publishing artifacts to
> gateway nodes directly in C5. Rather those artifacts will be injected at
> the Docker image build process. So why don't we stick with SVN based
> DepSync for now (C4 products)? What is the problem that we are trying to
> solve by moving to rsync that we couldn't/cannot fix in SVN based model?
>
> Thanks.
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] WSO2 Carbon Datasources 1.0.0 Released

[KasunG Gajasinghe]

WSO2 Carbon Datasources 1.0.0 Release

The Carbon team is pleased to announce the release of Carbon Datasources 1.0
.0. Listed below are the features introduced with this release.


Features

   - Create javax.sql.Datasource objects, and optionally bind it via JNDi
   - Exposing OSGi Services to fetch and manage data source objects.
   - Support for HikariCP jdbc connection pool implementation


Installing as a Carbon Feature

You may install carbon-datasource feature to your product with:


  org.wso2.carbon.datasources
  org.wso2.carbon.datasource.core.feature
  1.0.0
  zip


How to Contribute

   - WSO2 Carbon Datasources code is hosted in github.
   - The Git repository is https://github.com/wso2/carbon-datasources
   - Carbon Datasources 1.0.0 release tag is
   https://github.com/wso2/carbon-datasources/tree/v1.0.0


Contact Us

​WSO2 Carbon developers​ can be contacted via following mailing lists:

   -

   WSO2 Developers List: d...@wso2.org
   -

   WSO2 Architecture List: architecture@wso2.org


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] WSO2 Carbon Deployment 5.0.0 Released

[KasunG Gajasinghe]

WSO2 Carbon Deployment 5.0.0 Release

The Carbon team is pleased to announce the release of Carbon Deployment
5.0.0. Listed below are the features introduced with this release. The
Carbon deployment framework that was previously part of carbon-kernel is
now maintained separately with this release.

New Features

   - Carbon Deployment Framework to deploy artifacts
   - SDK to write artifact deployers and deployment lifecycle listeners
   - Artifact deployment notifier via JMS


Installing as a Carbon Feature

You may install carbon-deployment feature to your product by using the
following two dependencies. First one provides the core deployment framework,
while the second one provides the deployment notifier.


  org.wso2.carbon.deployment
  org.wso2.carbon.deployment.engine.feature
  5.0.0
  zip



  org.wso2.carbon.deployment
  org.wso2.carbon.deployment.notifier.feature
  5.0.0
  zip


How to Contribute

   - WSO2 Carbon Deployment code is hosted in github.
   - The Git repository is https://github.com/wso2/carbon-deployment
   - Carbon Deployment 5.0.0 release tag is
   https://github.com/wso2/carbon-deployment/tree/v5.0.0
   - Please report issues at Carbon Deployment Jira,
   https://wso2.org/jira/browse/CDEPLOY


Contact Us

​WSO2 Carbon developers​ can be contacted via following mailing lists:

   -

   WSO2 Developers List: d...@wso2.org
   -

   WSO2 Architecture List: architecture@wso2.org


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [C5] Java Util Logging vs Pax Logging for C5

[KasunG Gajasinghe]

Hi,

We have done an initial POC on the affect of logging framework for the C5
server startup between SLF4J (via pax logging) and JUL. Below are the
initial findings.

*TL;DR* The c5 kernel starts in *0.7 seconds* with JUL, a 350ms decrease
compared to pax-logging. But the time taken to log under a load test is
quiet high for JUL.

Product tested - wso2carbon-kernel-5.1.0-SNAPSHOT
JDK - 1.8.0_60
OS  - OS X El Capitan

Pax-Logging (SLF4J) Java Util Logging
startup 1.059s 0.705s
100k logs 4.5s 7.9s
1m logs 23.482s 57.723s


Current C5 kernel uses SLF4J API provided Pax-Logging. Pax-Logging uses
Log4J 2 as the back-end. With that, the server startup is around 1.059s.
The server startup decreased by around 350 ms after removing pax-logging
and replacing the slf4j logs with java util logging.

It seems that log4j2 loads ~750 classes to find classes with @Plugin
annotation which causes this delay in the startup. This seems to be
essential for its function.

[image: Inline image 2]

As the number of logs increases, the time taken to log all the log entries
increased considerably with java util logging.

[image: Inline image 3]

With these numbers, not sure whether we want to go with JUL.



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5] [Hamming] Audit logs in C5.

[KasunG Gajasinghe]

We had an offline discussion on what needs to logged for auditing purposes
in C5 kernel. It seems the only thing that needs to be logged in the user
name of the Principal when it gets set to the PrivilegedCarbonContext.
Therefore, we have added that into the MDC.

To Audit, the devs may use the org.wso2.carbon.kernel.Constants.AUDIT instance
which is a special logger with name "AUDIT_LOG".  The test cases show how
it's been used. Right now, this goes into a log file named audit.log. The
commits of the PR is at [1].

Next, we need to write a log4j appender for XDAS to publish the audit logs
to the distributed audit service. For that, we need to discuss the the best
place to maintain it, and whether it needs to come from Kernel.

[1]
https://github.com/wso2/carbon-kernel/commit/e77f7f972c90e378ad00f44ce9228fea98e2ca2b


On Tue, May 3, 2016 at 5:48 PM, KasunG Gajasinghe <kas...@wso2.com> wrote:

>
> MDC helps with capturing the information at relevant places such as at
> log-in time, and use that information later on when an auditable action is
> done.
>
> Then, we can capture this information using a logging appender and send it
> to an audit log file. We can also write a custom logging appender to
> communicate with a XDAS implementation. With a logging appender, we can
> decouple the dependency on XDAS implementation.
>
> I checked XDAS implementations, and found OpenXDAS [1]. Not sure how
> active the community is though. The last release seems to be on 2009.
>
> [1] https://sourceforge.net/projects/openxdas/
>
> On Tue, May 3, 2016 at 10:41 AM, Srinath Perera <srin...@wso2.com> wrote:
>
>> +1 for doing this and using XDAS and then adding analytics based on this
>> to security analytics
>>
>> Correlation like Prabath mentioned, we can do at DAS
>>
>> --Srinath
>>
>> On Tue, May 3, 2016 at 3:22 AM, Prabath Siriwardana <prab...@wso2.com>
>> wrote:
>>
>>> I guess one more thing we miss in C4 logs is - how to correlate all the
>>> logs related to a given message enters into the server..
>>>
>>> Thanks & regards,
>>> -Prabath
>>>
>>> On Thu, Apr 28, 2016 at 1:39 AM, Sameera Jayasoma <same...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Audit logs or Audit trails contain set of log entries which describe a
>>>> sequence of actions which have occurred over a time period. From audit
>>>> logs, it is possible to trace all the actions of a single user or all the
>>>> actions or changes introduced to a certain module in the system etc.  E.g.
>>>> It captures all the actions of a single user from the point he logs in to
>>>> the application.
>>>>
>>>> In previous versions of the Carbon platform, we only had a logger
>>>> called AUDIT and a separate appender which appends audit logs to separate
>>>> log file.
>>>>
>>>> The only drawback of this approach is that we don't have a proper way
>>>> to capture contextual information. In each and every audit log, we need to
>>>> capture logged in user details, IP address of client etc. In the previous
>>>> approach developers have to log this information with each and every audit
>>>> log attempt. This is suboptimal IMO, we need to implement a mechanism where
>>>> developers gives only the log message and system should append all the
>>>> other information to the log. I see few ways to implement this.
>>>>
>>>> 1) Write a custom appender which write audit logs to the file with
>>>> contextual information.
>>>> 2) Provide API to log audit logs. We can extract contextual information
>>>> from the CarbonContext in both of these methods.
>>>>
>>>> Any thoughts.
>>>>
>>>> Thanks,
>>>> Sameera.
>>>>
>>>> --
>>>> Sameera Jayasoma,
>>>> Software Architect,
>>>>
>>>> WSO2, Inc. (http://wso2.com)
>>>> email: same...@wso2.com
>>>> blog: http://blog.sameera.org
>>>> twitter: https://twitter.com/sameerajayasoma
>>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>>> Mobile: 0094776364456
>>>>
>>>> Lean . Enterprise . Middleware
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Prabath
>>>
>>> Twitter : @prabath
>>> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena
>>>
>>

Re: [Architecture] [C5] [Hamming] Audit logs in C5.

[KasunG Gajasinghe]

MDC helps with capturing the information at relevant places such as at
log-in time, and use that information later on when an auditable action is
done.

Then, we can capture this information using a logging appender and send it
to an audit log file. We can also write a custom logging appender to
communicate with a XDAS implementation. With a logging appender, we can
decouple the dependency on XDAS implementation.

I checked XDAS implementations, and found OpenXDAS [1]. Not sure how active
the community is though. The last release seems to be on 2009.

[1] https://sourceforge.net/projects/openxdas/

On Tue, May 3, 2016 at 10:41 AM, Srinath Perera  wrote:

> +1 for doing this and using XDAS and then adding analytics based on this
> to security analytics
>
> Correlation like Prabath mentioned, we can do at DAS
>
> --Srinath
>
> On Tue, May 3, 2016 at 3:22 AM, Prabath Siriwardana 
> wrote:
>
>> I guess one more thing we miss in C4 logs is - how to correlate all the
>> logs related to a given message enters into the server..
>>
>> Thanks & regards,
>> -Prabath
>>
>> On Thu, Apr 28, 2016 at 1:39 AM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi All,
>>>
>>> Audit logs or Audit trails contain set of log entries which describe a
>>> sequence of actions which have occurred over a time period. From audit
>>> logs, it is possible to trace all the actions of a single user or all the
>>> actions or changes introduced to a certain module in the system etc.  E.g.
>>> It captures all the actions of a single user from the point he logs in to
>>> the application.
>>>
>>> In previous versions of the Carbon platform, we only had a logger called
>>> AUDIT and a separate appender which appends audit logs to separate log
>>> file.
>>>
>>> The only drawback of this approach is that we don't have a proper way to
>>> capture contextual information. In each and every audit log, we need to
>>> capture logged in user details, IP address of client etc. In the previous
>>> approach developers have to log this information with each and every audit
>>> log attempt. This is suboptimal IMO, we need to implement a mechanism where
>>> developers gives only the log message and system should append all the
>>> other information to the log. I see few ways to implement this.
>>>
>>> 1) Write a custom appender which write audit logs to the file with
>>> contextual information.
>>> 2) Provide API to log audit logs. We can extract contextual information
>>> from the CarbonContext in both of these methods.
>>>
>>> Any thoughts.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> --
>>> Sameera Jayasoma,
>>> Software Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://blog.sameera.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Twitter : @prabath
>> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena
>>
>> Mobile : +1 650 625 7950
>>
>> http://blog.facilelogin.com
>> http://blog.api-security.org
>>
>
>
>
> --
> 
> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
> Site: http://home.apache.org/~hemapani/
> Photos: http://www.flickr.com/photos/hemapani/
> Phone: 0772360902
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] WSO2 Carbon Deployment 5.0.0-alpha Released

[KasunG Gajasinghe]

WSO2 Carbon Deployment 5.0.0-alpha Release

The Carbon team is pleased to announce the release of Carbon Deployment
5.0.0-alpha. Listed below are the features introduced with this release.
The Carbon deployment framework that was previously part of carbon-kernel
is now maintained separately with this release.

New Features

   - Carbon Deployment Framework to deploy artifacts
   - SDK to write artifact deployers and deployment lifecycle listeners
   - Artifact deployment notifier via JMS


Installing as a Carbon Feature

You may install carbon-deployment feature to your product by using the
following two dependencies. First one provides the core deployment
framework, while the second one provides the deployment notifier.


  org.wso2.carbon.deployment
  org.wso2.carbon.deployment.engine.feature
  5.0.0-alpha
  zip



  org.wso2.carbon.deployment
  org.wso2.carbon.deployment.notifier.feature
  5.0.0-alpha
  zip


How to Contribute

   - WSO2 Carbon Deployment code is hosted in github.
   - The Git repository is https://github.com/wso2/carbon-deployment
   - Carbon Deployment 5.0.0-alpha release tag is
   https://github.com/wso2/carbon-deployment/tree/v5.0.0-alpha
   - Please report issues at Carbon Deployment Jira,
   https://wso2.org/jira/browse/CDEPLOY


Contact Us

​WSO2 Carbon developers​ can be contacted via following mailing lists:

   -

   WSO2 Developers List: d...@wso2.org
   -

   WSO2 Architecture List: architecture@wso2.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] WSO2 Carbon Datasources 1.0.0-alpha Released

[KasunG Gajasinghe]

WSO2 Carbon Datasources 1.0.0-alpha Release

The Carbon team is pleased to announce the release of Carbon Datasources
1.0.0-alpha. Listed below are the features introduced with this release.


Features

   - Create javax.sql.Datasource objects, and optionally bind it via JNDi
   - Exposing OSGi Services to fetch and manage data source objects.
   - Support for HikariCP jdbc connection pool implementation


Installing as a Carbon Feature

You may install carbon-datasourc feature to your product with:


  org.wso2.carbon.datasources
  org.wso2.carbon.datasource.core.feature
  1.0.0-alpha
  zip


How to Contribute

   - WSO2 Carbon Datasources code is hosted in github.
   - The Git repository is https://github.com/wso2/carbon-datasources
   - Carbon Datasources 1.0.0-alpha release tag is
   https://github.com/wso2/carbon-datasources/tree/v1.0.0-alpha


Contact Us

​WSO2 Carbon developers​ can be contacted via following mailing lists:

   -

   WSO2 Developers List: d...@wso2.org
   -

   WSO2 Architecture List: architecture@wso2.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5] Artifact deployment coordination support for C5

[KasunG Gajasinghe]

On Mon, Mar 28, 2016 at 10:32 AM, Malaka Silva <mal...@wso2.com> wrote:

> Hi All,
>
> I think we have to think a way to manage the deployments in a round robin
> passion.
> So that we can make sure only single worker unavailable at a given time
> rather than the whole cluster.
>

With the new Lifecycle listener support, we can achieve this functionality
if needed. In there, you can write a lifecycle listener to remove itself
from a loadbalancer before doing the artifact deployment/undeployment.
After the deployment/undeployment is completed, it can join back again.
Then, there won't be any downtime since other nodes in the cluster will
continue to serve requests.
But, users need to do the artifact distribution themselves in a strategy
such as round-robin as they see fit since the artifact synchronization
across a cluster is not handled at Carbon level,.

With docker based architecture, doing a new deployment means you just
create a new docker image and spin it up, and then shutdown the older
instance.


> Are we planning to do this in C5?
>
> On Fri, Mar 25, 2016 at 1:42 PM, KasunG Gajasinghe <kas...@wso2.com>
> wrote:
>
>>
>>
>> On Fri, Mar 25, 2016 at 12:30 PM, Nandika Jayawardana <nand...@wso2.com>
>> wrote:
>>
>>> Hi Kasun,
>>>
>>> Since the end goal of making this information available at a central
>>> location is to be able to monitor the deployment for consistency and
>>> correctness, So we should look at from the tooling perspective. Any plans
>>> for providing a JMS based cluster monitoring tool ?.
>>>
>>
>> The monitoring aspect need to be think-through further. Sameera's
>> suggestion of an alerting system based on real-time analytics with CEP is
>> an option that we can provide by default. We could also provide a simple
>> dashboard to view the deployment status.
>>
>>
>>>
>>> Also, since we are asking users to do the synchronization , there would
>>> be other scenarios in addition to failed deployments such an not
>>> synchronizing with a particular node.
>>>
>>>
>> Yes, we will take this into account. The number of nodes should be
>> pre-defined before hand in the consumer side. Or, may be we can send a
>> server startup/shutdown message mentioning a new node has joined/left the
>> cluster.
>>
>> Thanks,
>> KasunG
>>
>>
>>> Regards
>>> Nandika
>>>
>>>
>>>
>>> On Fri, Mar 25, 2016 at 10:58 AM, KasunG Gajasinghe <kas...@wso2.com>
>>> wrote:
>>>
>>>> Hi Nandika,
>>>>
>>>> On Thu, Mar 24, 2016 at 7:43 PM, Nandika Jayawardana <nand...@wso2.com>
>>>> wrote:
>>>>
>>>>> What about providing a REST API from each node of the cluster which
>>>>> can be used to query deployed artifact information in addition to JMS
>>>>>  publishing.
>>>>>
>>>>
>>>> There will be admin services later on that will provide artifact
>>>> information, but we need to see how usable that is to understand failed
>>>> artifact deployments. Because users will need to poll and pull data from
>>>> each node periodically to find out whether the artifact deployment is
>>>> successful at that moment.
>>>>
>>>> Here, what we are proposing is a push model where all the nodes will
>>>> push its whenever an artifact is deployed. An interested consumer can
>>>> listen for these events and take actions as required.
>>>>
>>>> Thanks,
>>>> KasunG
>>>>
>>>>
>>>>> Regards
>>>>> Nandika
>>>>>
>>>>> On Thu, Mar 24, 2016 at 3:45 PM, KasunG Gajasinghe <kas...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 24, 2016 at 3:23 PM, Sameera Jayasoma <same...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Btw, who are the consumers of these messages? User can develop their
>>>>>>> own tools to monitor artifact deployment.
>>>>>>>
>>>>>>> We also can come with CEP query to analyze whether the artifact
>>>>>>> deployment happened successfully in a cluster and display this 
>>>>>>> information
>>>>>>> in a dashboard. We can come up with a DAS C-App.
>>>>>>>
>>>>>>
>>>>>> +1 for the idea.
>

Re: [Architecture] [C5] Artifact deployment coordination support for C5

[KasunG Gajasinghe]

On Fri, Mar 25, 2016 at 12:30 PM, Nandika Jayawardana <nand...@wso2.com>
wrote:

> Hi Kasun,
>
> Since the end goal of making this information available at a central
> location is to be able to monitor the deployment for consistency and
> correctness, So we should look at from the tooling perspective. Any plans
> for providing a JMS based cluster monitoring tool ?.
>

The monitoring aspect need to be think-through further. Sameera's
suggestion of an alerting system based on real-time analytics with CEP is
an option that we can provide by default. We could also provide a simple
dashboard to view the deployment status.


>
> Also, since we are asking users to do the synchronization , there would be
> other scenarios in addition to failed deployments such an not synchronizing
> with a particular node.
>
>
Yes, we will take this into account. The number of nodes should be
pre-defined before hand in the consumer side. Or, may be we can send a
server startup/shutdown message mentioning a new node has joined/left the
cluster.

Thanks,
KasunG


> Regards
> Nandika
>
>
>
> On Fri, Mar 25, 2016 at 10:58 AM, KasunG Gajasinghe <kas...@wso2.com>
> wrote:
>
>> Hi Nandika,
>>
>> On Thu, Mar 24, 2016 at 7:43 PM, Nandika Jayawardana <nand...@wso2.com>
>> wrote:
>>
>>> What about providing a REST API from each node of the cluster which can
>>> be used to query deployed artifact information in addition to JMS
>>>  publishing.
>>>
>>
>> There will be admin services later on that will provide artifact
>> information, but we need to see how usable that is to understand failed
>> artifact deployments. Because users will need to poll and pull data from
>> each node periodically to find out whether the artifact deployment is
>> successful at that moment.
>>
>> Here, what we are proposing is a push model where all the nodes will push
>> its whenever an artifact is deployed. An interested consumer can listen for
>> these events and take actions as required.
>>
>> Thanks,
>> KasunG
>>
>>
>>> Regards
>>> Nandika
>>>
>>> On Thu, Mar 24, 2016 at 3:45 PM, KasunG Gajasinghe <kas...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Thu, Mar 24, 2016 at 3:23 PM, Sameera Jayasoma <same...@wso2.com>
>>>> wrote:
>>>>
>>>>> Btw, who are the consumers of these messages? User can develop their
>>>>> own tools to monitor artifact deployment.
>>>>>
>>>>> We also can come with CEP query to analyze whether the artifact
>>>>> deployment happened successfully in a cluster and display this information
>>>>> in a dashboard. We can come up with a DAS C-App.
>>>>>
>>>>
>>>> +1 for the idea.
>>>>
>>>> The initial phase that is described in this thread is to provide the
>>>> deployment status notifications. Coordination will be the next step on top
>>>> of this.
>>>>
>>>>
>>>>
>>>>>
>>>>> Thanks,
>>>>> Sameera.
>>>>>
>>>>> On Wed, Mar 23, 2016 at 2:24 PM, Sameera Jayasoma <same...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> I believe we need both here.
>>>>>>
>>>>>> In JMS case, we need to publish events to a topic rather than a queue.
>>>>>>
>>>>>> Thanks,
>>>>>> Sameera.
>>>>>>
>>>>>> On Wed, Mar 23, 2016 at 2:02 PM, Srinath Perera <srin...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Kasun, I would go with JMS as it gives event persistence and you
>>>>>>> will not loose the events even if listener is restarted.
>>>>>>>
>>>>>>> --Srinath.
>>>>>>>
>>>>>>> On Wed, Mar 23, 2016 at 10:45 AM, KasunG Gajasinghe <kas...@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Given several issues we discovered with automatic artifact
>>>>>>>> synchronization with DepSync in C4, we have discussed how to approach 
>>>>>>>> this
>>>>>>>> problem in C5.
>>>>>>>>
>>>>>>>> We are thinking of not doing the automated artifact synchronization
>>>>

Re: [Architecture] [C5] Artifact deployment coordination support for C5

[KasunG Gajasinghe]

On Fri, Mar 25, 2016 at 10:20 AM, Aruna Karunarathna <ar...@wso2.com> wrote:

>
>
> On Wed, Mar 23, 2016 at 10:45 AM, KasunG Gajasinghe <kas...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Given several issues we discovered with automatic artifact
>> synchronization with DepSync in C4, we have discussed how to approach this
>> problem in C5.
>>
>> We are thinking of not doing the automated artifact synchronization in
>> C5. Rather, users should use their own mechanism to synchronize the
>> artifacts across a cluster. Common approaches are RSync as a cron job and
>> shell scripts.
>
>
> Which indicates that we only provide status notification mechanism, and
> it's users responsibility to deal with failed deployment artifacts?
>

Yes, that's what the initial implementation brings.


>
>> But, it is vital to know the artifact deployment status of the nodes in
>> the entire cluster from a central place. For that, we are providing this
>> deployment coordination feature. There will be two ways to use this.
>>
>> 1. JMS based publishing - the deployment status will be published by each
>> node to a jms topic/queue
>>
>> 2. Log based publishing - publish the logs by using a syslog appender [1]
>> or our own custom appender to a central location.
>>
>> The log publishing may not be limited to just the deployment
>> coordination. In a containerized deployment, the carbon products will run
>> in disposable containers. But sometimes, the logs need to be backed up for
>> later reference. This will help with that.
>>
>> Any thoughts on this matter?
>>
>> [1]
>> https://logging.apache.org/log4j/2.x/manual/appenders.html#SyslogAppender
>>
>> Thanks,
>> KasunG
>>
>>
>>
>> --
>> ~~--~~
>> Sending this mail via my phone. Do excuse any typo or short replies
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5] Artifact deployment coordination support for C5

[KasunG Gajasinghe]

Hi Nandika,

On Thu, Mar 24, 2016 at 7:43 PM, Nandika Jayawardana <nand...@wso2.com>
wrote:

> What about providing a REST API from each node of the cluster which can be
> used to query deployed artifact information in addition to JMS  publishing.
>

There will be admin services later on that will provide artifact
information, but we need to see how usable that is to understand failed
artifact deployments. Because users will need to poll and pull data from
each node periodically to find out whether the artifact deployment is
successful at that moment.

Here, what we are proposing is a push model where all the nodes will push
its whenever an artifact is deployed. An interested consumer can listen for
these events and take actions as required.

Thanks,
KasunG


> Regards
> Nandika
>
> On Thu, Mar 24, 2016 at 3:45 PM, KasunG Gajasinghe <kas...@wso2.com>
> wrote:
>
>>
>>
>> On Thu, Mar 24, 2016 at 3:23 PM, Sameera Jayasoma <same...@wso2.com>
>> wrote:
>>
>>> Btw, who are the consumers of these messages? User can develop their own
>>> tools to monitor artifact deployment.
>>>
>>> We also can come with CEP query to analyze whether the artifact
>>> deployment happened successfully in a cluster and display this information
>>> in a dashboard. We can come up with a DAS C-App.
>>>
>>
>> +1 for the idea.
>>
>> The initial phase that is described in this thread is to provide the
>> deployment status notifications. Coordination will be the next step on top
>> of this.
>>
>>
>>
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Wed, Mar 23, 2016 at 2:24 PM, Sameera Jayasoma <same...@wso2.com>
>>> wrote:
>>>
>>>> I believe we need both here.
>>>>
>>>> In JMS case, we need to publish events to a topic rather than a queue.
>>>>
>>>> Thanks,
>>>> Sameera.
>>>>
>>>> On Wed, Mar 23, 2016 at 2:02 PM, Srinath Perera <srin...@wso2.com>
>>>> wrote:
>>>>
>>>>> Kasun, I would go with JMS as it gives event persistence and you will
>>>>> not loose the events even if listener is restarted.
>>>>>
>>>>> --Srinath.
>>>>>
>>>>> On Wed, Mar 23, 2016 at 10:45 AM, KasunG Gajasinghe <kas...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Given several issues we discovered with automatic artifact
>>>>>> synchronization with DepSync in C4, we have discussed how to approach 
>>>>>> this
>>>>>> problem in C5.
>>>>>>
>>>>>> We are thinking of not doing the automated artifact synchronization
>>>>>> in C5. Rather, users should use their own mechanism to synchronize the
>>>>>> artifacts across a cluster. Common approaches are RSync as a cron job and
>>>>>> shell scripts.
>>>>>>
>>>>>> But, it is vital to know the artifact deployment status of the nodes
>>>>>> in the entire cluster from a central place. For that, we are providing 
>>>>>> this
>>>>>> deployment coordination feature. There will be two ways to use this.
>>>>>>
>>>>>> 1. JMS based publishing - the deployment status will be published by
>>>>>> each node to a jms topic/queue
>>>>>>
>>>>>> 2. Log based publishing - publish the logs by using a syslog appender
>>>>>> [1] or our own custom appender to a central location.
>>>>>>
>>>>>> The log publishing may not be limited to just the deployment
>>>>>> coordination. In a containerized deployment, the carbon products will run
>>>>>> in disposable containers. But sometimes, the logs need to be backed up 
>>>>>> for
>>>>>> later reference. This will help with that.
>>>>>>
>>>>>> Any thoughts on this matter?
>>>>>>
>>>>>> [1]
>>>>>> https://logging.apache.org/log4j/2.x/manual/appenders.html#SyslogAppender
>>>>>>
>>>>>> Thanks,
>>>>>> KasunG
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> ~~--~~
>>>>>> Sending this mail via my phone. Do excuse any typo or short replies
>>>>>>
>>>>&g

Re: [Architecture] [C5] Artifact deployment coordination support for C5

[KasunG Gajasinghe]

On Thu, Mar 24, 2016 at 3:23 PM, Sameera Jayasoma <same...@wso2.com> wrote:

> Btw, who are the consumers of these messages? User can develop their own
> tools to monitor artifact deployment.
>
> We also can come with CEP query to analyze whether the artifact deployment
> happened successfully in a cluster and display this information in a
> dashboard. We can come up with a DAS C-App.
>

+1 for the idea.

The initial phase that is described in this thread is to provide the
deployment status notifications. Coordination will be the next step on top
of this.



>
> Thanks,
> Sameera.
>
> On Wed, Mar 23, 2016 at 2:24 PM, Sameera Jayasoma <same...@wso2.com>
> wrote:
>
>> I believe we need both here.
>>
>> In JMS case, we need to publish events to a topic rather than a queue.
>>
>> Thanks,
>> Sameera.
>>
>> On Wed, Mar 23, 2016 at 2:02 PM, Srinath Perera <srin...@wso2.com> wrote:
>>
>>> Kasun, I would go with JMS as it gives event persistence and you will
>>> not loose the events even if listener is restarted.
>>>
>>> --Srinath.
>>>
>>> On Wed, Mar 23, 2016 at 10:45 AM, KasunG Gajasinghe <kas...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Given several issues we discovered with automatic artifact
>>>> synchronization with DepSync in C4, we have discussed how to approach this
>>>> problem in C5.
>>>>
>>>> We are thinking of not doing the automated artifact synchronization in
>>>> C5. Rather, users should use their own mechanism to synchronize the
>>>> artifacts across a cluster. Common approaches are RSync as a cron job and
>>>> shell scripts.
>>>>
>>>> But, it is vital to know the artifact deployment status of the nodes in
>>>> the entire cluster from a central place. For that, we are providing this
>>>> deployment coordination feature. There will be two ways to use this.
>>>>
>>>> 1. JMS based publishing - the deployment status will be published by
>>>> each node to a jms topic/queue
>>>>
>>>> 2. Log based publishing - publish the logs by using a syslog appender
>>>> [1] or our own custom appender to a central location.
>>>>
>>>> The log publishing may not be limited to just the deployment
>>>> coordination. In a containerized deployment, the carbon products will run
>>>> in disposable containers. But sometimes, the logs need to be backed up for
>>>> later reference. This will help with that.
>>>>
>>>> Any thoughts on this matter?
>>>>
>>>> [1]
>>>> https://logging.apache.org/log4j/2.x/manual/appenders.html#SyslogAppender
>>>>
>>>> Thanks,
>>>> KasunG
>>>>
>>>>
>>>>
>>>> --
>>>> ~~--~~
>>>> Sending this mail via my phone. Do excuse any typo or short replies
>>>>
>>>> ___
>>>> Architecture mailing list
>>>> Architecture@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> 
>>> Srinath Perera, Ph.D.
>>>http://people.apache.org/~hemapani/
>>>http://srinathsview.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Software Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://blog.sameera.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5] Lifecycle listeners to listen on Artifact deployment events

[KasunG Gajasinghe]

On Wed, Mar 23, 2016 at 10:12 AM, KasunG Gajasinghe <kas...@wso2.com> wrote:

>
>
> On Wednesday, March 23, 2016, Aruna Karunarathna <ar...@wso2.com> wrote:
>
>>
>>
>> On Tue, Mar 22, 2016 at 9:44 PM, KasunG Gajasinghe <kas...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> To provide extensibility to the C5 deployment engine, we need to add the
>>> lifecycle listener support to it. The immediate need is to provide the
>>> deployment coordination feature.
>>>
>>> Hi Kasun,
>>
>> Better if you can share the deployment coordiation plan for C5 as well.
>>
>
>
> Yes, that'll be a separate discussion! :-)
>

See [1].

[1] [C5] Artifact deployment coordination support for C5


>
>
>>
>> Regards,
>> Aruna
>>
>>> Initially, may be we can support following four lifecycle events. The
>>> first two will be triggered before and after artifact deployment, while the
>>> latter two will be triggered before and after artifact undeployment.
>>>
>>> BEFORE_START_EVENT
>>> AFTER_START_EVENT
>>> BEFORE_STOP_EVENT
>>> AFTER_STOP_EVENT
>>>
>>> The lifecycle listener registration can be done via OSGi services that
>>> implements org.wso2.carbon.kernel.deployment.LifecycleListener. This
>>> interface has one method -
>>>
>>> public interface LifecycleListener {
>>> void lifecycleEvent(LifecycleEvent event);
>>> }
>>>
>>> Any suggestions?
>>>
>>> Thanks,
>>> KasunG
>>>
>>> --
>>>
>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
>>> email: kasung AT spamfree wso2.com
>>> linked-in: http://lk.linkedin.com/in/gajasinghe
>>> blog: http://kasunbg.org
>>>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>
>
> --
> ~~--~~
> Sending this mail via my phone. Do excuse any typo or short replies
>



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [C5] Artifact deployment coordination support for C5

[KasunG Gajasinghe]

Hi,

Given several issues we discovered with automatic artifact synchronization
with DepSync in C4, we have discussed how to approach this problem in C5.

We are thinking of not doing the automated artifact synchronization in C5.
Rather, users should use their own mechanism to synchronize the artifacts
across a cluster. Common approaches are RSync as a cron job and shell
scripts.

But, it is vital to know the artifact deployment status of the nodes in
the entire cluster from a central place. For that, we are providing this
deployment coordination feature. There will be two ways to use this.

1. JMS based publishing - the deployment status will be published by each
node to a jms topic/queue

2. Log based publishing - publish the logs by using a syslog appender [1]
or our own custom appender to a central location.

The log publishing may not be limited to just the deployment coordination.
In a containerized deployment, the carbon products will run in disposable
containers. But sometimes, the logs need to be backed up for later
reference. This will help with that.

Any thoughts on this matter?

[1]
https://logging.apache.org/log4j/2.x/manual/appenders.html#SyslogAppender

Thanks,
KasunG



-- 
~~--~~
Sending this mail via my phone. Do excuse any typo or short replies
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [C5] Lifecycle listeners to listen on Artifact deployment events

[KasunG Gajasinghe]

On Wednesday, March 23, 2016, Aruna Karunarathna <ar...@wso2.com> wrote:

>
>
> On Tue, Mar 22, 2016 at 9:44 PM, KasunG Gajasinghe <kas...@wso2.com
> <javascript:_e(%7B%7D,'cvml','kas...@wso2.com');>> wrote:
>
>> Hi,
>>
>> To provide extensibility to the C5 deployment engine, we need to add the
>> lifecycle listener support to it. The immediate need is to provide the
>> deployment coordination feature.
>>
>> Hi Kasun,
>
> Better if you can share the deployment coordiation plan for C5 as well.
>


Yes, that'll be a separate discussion! :-)


>
> Regards,
> Aruna
>
>> Initially, may be we can support following four lifecycle events. The
>> first two will be triggered before and after artifact deployment, while the
>> latter two will be triggered before and after artifact undeployment.
>>
>> BEFORE_START_EVENT
>> AFTER_START_EVENT
>> BEFORE_STOP_EVENT
>> AFTER_STOP_EVENT
>>
>> The lifecycle listener registration can be done via OSGi services that
>> implements org.wso2.carbon.kernel.deployment.LifecycleListener. This
>> interface has one method -
>>
>> public interface LifecycleListener {
>> void lifecycleEvent(LifecycleEvent event);
>> }
>>
>> Any suggestions?
>>
>> Thanks,
>> KasunG
>>
>> --
>>
>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>>
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> <javascript:_e(%7B%7D,'cvml','Architecture@wso2.org');>
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com <javascript:_e(%7B%7D,'cvml','ar...@wso2.com');> |
> Web: www.wso2.com
>
>


-- 
~~--~~
Sending this mail via my phone. Do excuse any typo or short replies
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] WSO2 Carbon Datasources - 1.0.0-M1 Released

[KasunG Gajasinghe]

Hi,

Please note $subject.

The carbon-datasources feature can be installed with the following
dependency -


  org.wso2.carbon.datasources
  org.wso2.carbon.datasource.core.feature
  1.0.0-m1
  zip


Thanks,
KasunG

-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] C5 - Enabling SOAP support for BPEL with Apache CXF integration

[KasunG Gajasinghe]

Hi Amal,

Can you show the extension points we use inside the Apache CXF (Bus) box?

In addition to the invocation flow, can you also show how you handle the
service deployment?

Thanks,
KasunG

On Tue, Mar 15, 2016 at 11:03 AM, Amal Gunatilake  wrote:

> Hi All,
>
> Following is the initial architecture we came up with in-order to enable
> SOAP support in C5 for BPEL using Apache CXF integration.
>
> ​
>
> Any feedback is highly appreciated.
>
> [1]
> https://drive.google.com/a/wso2.com/file/d/0B7E7tgre4G1RanRObkRqSElkX2M/view?usp=sharing
>
> Best regards,
> Amal.
>
> --
> *Amal Gunatilake*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [MSF4J][Improvement] Intercceptors as an annotation

[KasunG Gajasinghe]

+1 to provide a way to register interceptor via a class-level annotation.
Is there really a need to register interceptor in a finer-level for service
methods?

I think that we need think about a better name for the annotation rather
than @Interceptor. This gives the impression that the given class itself is
a interceptor!

For ex. Jax-WS registers its service class with @WebService annotation. So,
users know that the given class denotes a web service. Further, it
registers the handler chain with annotation with @HandlerChain. [1]

[1]
http://tomee.apache.org/examples-trunk/webservice-handlerchain/README.html

Thanks,
KasunG

On Fri, Mar 11, 2016 at 2:29 PM, Afkham Azeez  wrote:

> It would be elegant to specify the interceptors as annotations rather than
> programatically adding them.
>
> e.g. 1
> Apply interceptors globally to all operations in a service
>
> @Path("/foo")
> @Interceptor(classes = {"org.wso2.msf4j.OAuthInterceptor",
> "org.wso2.msf4j.LogInterceptor"})
> public class FooService {
>
> }
>
> e.g.2
> Apply interceptors selectively to operations
>
> @Path("/foo")
> @Interceptor(classes = {"org.wso2.msf4j.LogInterceptor"})
> public class FooService {
>
>@Path("secure")
>@Interceptor(classes={"org.wso2.msf4j.OAuthInterceptor"})
>public void secureOp(){}
>
>@Path("unsecure")
>public void unsecureOp{}
> }
>
> Thoughts welcome. This would simplify the programming model for users of
> MSF4J.
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

[KasunG Gajasinghe]

It seems these gadgets should directly call the DAS analytics API to get
the summarized info.

For the folder structure, may be we can create a top-level module called
webapp-analytics and create the CApp there. If there are other artifacts
other than the CApp, then we'll have to add the capp as a sub-module.

On Fri, Feb 26, 2016 at 4:45 PM, Tharik Kanaka <tha...@wso2.com> wrote:

> Hi Lochana,
>
> Are you going to use existing analytics API used in DAS? Apart from that
> what are the javascript chart libraries are you going to use for these
> gadgets?
>
> Regards,
>
> On Fri, Feb 26, 2016 at 3:46 PM, Lochana Ranaweera <locha...@wso2.com>
> wrote:
>
>>
>> Hi KasunG,
>>
>> The final deliverable of the dashboard will be a set of gadgets that can
>> be deployed in the DS separately. It was suggested that ideally with the AS
>> build the gadgets could be packed as a car file.
>>
>> As of now, the gadgets are working along with an API that provides the
>> gadgets with properly structured data obtained out of a mysql database. The
>> table structure for the tables in the mysql database is to be provided
>> using a spark script.
>>
>> The following will have to be done by a user in order view web
>> application statistics by means of a dashboard created using these gadgets
>>
>> - Publish webapp statistics to the DAS using publisher valve at AS
>> - Execute the given Spark script to summarize the event data in to a
>> database
>> - Configure the datasource definition in Dashboard Server to retrieve
>> data from the database
>> - Create and publish a dashboard using preferred HTTP monitoring gadgets
>> through dashboard server portal
>>
>> Thanks.
>>
>> On Fri, Feb 26, 2016 at 2:08 PM, KasunG Gajasinghe <kas...@wso2.com>
>> wrote:
>>
>>> +architecture
>>>
>>> Hi Lochana,
>>>
>>> Can you describe what is the final deliverable of the dashboard? Also,
>>> please explain briefly how the users are going to use these gadgets as well
>>> as all other dependencies these need. Based on that, we can figure out how
>>> the folder structure should be.
>>>
>>> Btw, can you explain the overall effort required to port these gadgets?
>>> What needs to be done?
>>>
>>> Thanks.
>>>
>>> On Fri, Feb 26, 2016 at 12:42 PM, Lochana Ranaweera <locha...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> This is regarding the HTTP Monitoring Dashboard for AS 6.0.0. It is to
>>>> be deployed as a collection of user preferred set of gadgets in the
>>>> Dashboard Server.
>>>> As of now, I have ported the* basic* HTTP monitoring functionality as
>>>> separate gadgets for DS.
>>>>
>>>> A typical HTTP monitoring gadget has the following structure:
>>>>
>>>> gadget-name
>>>>├── css
>>>>├── js
>>>>├── fonts
>>>>├── images
>>>>├── index.xml
>>>>└── gadget.json
>>>>
>>>> What will be the best structure to version control thus created gadgets
>>>> in the given branch
>>>> <https://github.com/wso2/product-as/tree/wso2as-6.0.0> of AS 6.0.0?
>>>> Should it be in modules or should it be inside contents directory in
>>>> the distribution module?
>>>> The directory structure of the build for new AS 6.0.0 is given below:
>>>>
>>>>
>>>> ​
>>>> Appreciate your suggestions on this matter.
>>>>
>>>> Thanks and Regards,
>>>> --
>>>> Lochana Ranaweera
>>>> Intern Software Engineer
>>>> WSO2 Inc: http://wso2.com
>>>> Blog: https://lochanaranaweera.wordpress.com/
>>>> Mobile: +94716487055 <http://tel%2B716487055>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
>>> email: kasung AT spamfree wso2.com
>>> linked-in: http://lk.linkedin.com/in/gajasinghe
>>> blog: http://kasunbg.org
>>>
>>>
>>>
>>
>>
>>
>> --
>> Lochana Ranaweera
>> Intern Software Engineer
>> WSO2 Inc: http://wso2.com
>> Blog: https://lochanaranaweera.wordpress.com/
>> Mobile: +94716487055 <http://tel%2B716487055>
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Tharik Kanaka*
>
> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka
>
> Email: tha...@wso2.com | Web: www.wso2.com
>



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

[KasunG Gajasinghe]

+architecture

Hi Lochana,

Can you describe what is the final deliverable of the dashboard? Also,
please explain briefly how the users are going to use these gadgets as well
as all other dependencies these need. Based on that, we can figure out how
the folder structure should be.

Btw, can you explain the overall effort required to port these gadgets?
What needs to be done?

Thanks.

On Fri, Feb 26, 2016 at 12:42 PM, Lochana Ranaweera 
wrote:

> Hi all,
>
> This is regarding the HTTP Monitoring Dashboard for AS 6.0.0. It is to be
> deployed as a collection of user preferred set of gadgets in the Dashboard
> Server.
> As of now, I have ported the* basic* HTTP monitoring functionality as
> separate gadgets for DS.
>
> A typical HTTP monitoring gadget has the following structure:
>
> gadget-name
>├── css
>├── js
>├── fonts
>├── images
>├── index.xml
>└── gadget.json
>
> What will be the best structure to version control thus created gadgets in
> the given branch 
> of AS 6.0.0?
> Should it be in modules or should it be inside contents directory in the
> distribution module?
> The directory structure of the build for new AS 6.0.0 is given below:
>
>
> ​
> Appreciate your suggestions on this matter.
>
> Thanks and Regards,
> --
> Lochana Ranaweera
> Intern Software Engineer
> WSO2 Inc: http://wso2.com
> Blog: https://lochanaranaweera.wordpress.com/
> Mobile: +94716487055 
>
>


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [BPMN]Skipping the instance creation with same state

[KasunG Gajasinghe]

Hi Firzhan,

Are you providing a Java API as well in addition to the REST API? The
reason is that underlying BPMN engine provides both REST and a rich Java
API since it is an embedable engine.

Thanks.

On Fri, Dec 11, 2015 at 12:37 PM, Firzhan Naqash  wrote:

> Hi Philippe,
>
> Thanks for your suggestions. We are primarily trying to address the
> process instance creation based only on the variable state of the instances.
>
> Although the *businessKey* attribute could be used for this purpose, we
> had to address the following concerns.
>
>   -  There might be use cases where business key can't be determined
> before the process start.
>
>   -  In some occasions, after the process startup values of the
> correlation variable can be updated.
>
>
> On the above mentioned scenarios, since activiti is not providing any
> direct APIs to update the business key, process instance based correlation
> is the only possible alternative[1].
>
>
> [1]
> https://forums.activiti.org/content/changing-business-key-after-process-start
>
>
> Regards,
> Firzhan
>
>
> --
> *Firzhan Naqash*
> Senior Software Engineer - Integration Platform Team
> WSO2 Inc. http://wso2.com
>
> email: firz...@wso2.com
> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
> blog: http://firzhanblogger.blogspot.com/
>   *
> *twitter: https://twitter.com/firzhan007
>  | linked-in: 
> **https://www.linkedin.com/in/firzhan
> *
>
> On Fri, Dec 11, 2015 at 4:08 PM, Philippe Sevestre 
> wrote:
>
>> -1 for that.
>>
>> Why don´t you use the businessKey attribute for this requirement ?
>> Activiti does not allow one to start two instances of a given process
>> with the same value for that property, so it can be used in scenarios like
>> you described.
>>
>> OTOH, if the decision on whether to allow or not the creation depends on
>> the _*dynamic_* state of an existing instance, which in the general case
>> is the set that contains its variables AND the current step of each
>> execution, then simply checking for variables might not be enough to
>> address all cases.
>>
>> So, IMO, this kind of logic really belongs to the process itself and can
>> be implemented in an initial synchronous system task activity where the
>> check can be made arbitrarily complex.
>>
>>
>>
>> Em 11/12/2015 07:45, "Nandika Jayawardana"  escreveu:
>>
>>> We need this functionality in order to simplify the client side
>>> implementation. Otherwise, the client has to do multiple calls in order to
>>> implement this scenario.
>>>
>>> Nandika
>>>
>>> On Thu, Dec 10, 2015 at 11:41 PM, Firzhan Naqash 
>>> wrote:
>>>

 Hi,

 Currently in the BPMN Rest API, process instance start operations are
 not conditional. But there are occasions, process instances  should not be
 initialized when ever there is a already created instance with same state (
 Same variable values).

 Therefore, in order to perform checked instance creation, we can add
 new json property "*skipinstanceCreationIfExist*". By default this
 property is false and if the request set it to true, this will search for
 instance variables mentioned in the query.

  If instance is found it will be returned back to the user or else new
 instance will be created.

 {
"message":"star

"variables": [
   {
 "name":"productID",
 "value":"pid123456"
   },

   skipInstanceCreationIfExist:true
]
 }

 Any thoughts/suggestions are welcome,



 Regards,
 Firzhan



>>>
>>>
>>> --
>>> Nandika Jayawardana
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] carbon-feature-plugin 2.0.0 Milestone 1 Released

[KasunG Gajasinghe]

Hi Dinusha,

Looks good. Could you please share the documentation that is accessible
without a Google login? May be we can add this to wso2 carbon documentation?

Thanks.

On Mon, Oct 19, 2015 at 2:43 PM, Dinusha Boteju  wrote:

> WSO2 Carbon Feature plugin 2.0.0 - Milestone 01 Released!
>
> We are pleased to inform you the 1st milestone release of carbon feature
> plugin 2.0.0 is now available to use. Source for this release is available
> here .
>
>
> carbon-feature-plugin (formerly known as carbon-p2-plugin) is a maven
> plugin developed within the WSO2. With the new 2.0.0 - M1 release we have
> changed the architecture of the tool, changed few maven goals existed in
> previous versions, introduced new features and made the configuration of
> the plugin consistent than before.
>
>
> *Features*
>
>
>- Generate Carbon features
>- Generate p2 repositories
>- Publish a product into p2 repository
>- Generate product Profiles
>- Install carbon features into a product profile
>- Uninstall carbon features from a product
>
>
> These goals are achieved through 6 maven goals defined in the plugin;
>
>- maven goal for generate carbon features  : generate (formerly known
>as p2-feature-gen)
>- maven goal for generate repositories: generate-repo
>(formerly known as p2-repo-gen)
>- maven goal for publishing a product  : publish-product
>- maven goal for generate profiles   : generate-profile
>(formerly known as materialize-product)
>- maven goal for install features into a product : install (formerly
>known as p2-profile-gen)
>- maven goal for uninstalling features  : uninstall
>
> In the new version, the plugin configuration is different from that of the
> previous versions. Thus please refer the documentation when you use the new
> carbon feature plugin.
>
> Documentation for WSO2 carbon feature plugin 2.0.0 - M1 can be found from
> here
> .
>  We
> are in the process of converting this documentation into a document in WSO2
> wiki.
>
> *Reporting Issues*
>
> Since carbon-feature-plugin 2.0.0 - M1 is at it's early stage, please
> report bugs you come across, documentation faults and feature requests
> through the public issue tracking system
> .
> ​
>  Carbon-Feature-Plugin documentation
> 
> ​
>
> Thanks,
> WSO2 Carbon Team
>
> --
> *Dinusha Boteju*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: dinus...@wso2.com 
> phone:(+94) 776640275 <%28%2B94%29%2039736>
>



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [MSS] [Carbon 5] [netty-http] JAX-RS Engine implementation

[KasunG Gajasinghe]

Hi Samiyuru,

Can you check with Netty-http developers as to why they had made these
constraints? They must had a good reason to introduce a parent class etc.
We should find what it is to fix it on our end.

On Wed, Sep 23, 2015 at 11:21 AM, Afkham Azeez  wrote:

> I have forked the code at https://github.com/wso2/product-mss/. Let's
> optimize it for our use cases not worrying too much about doing
> non-backward compatible changes.
>
> Azeez
>
> On Mon, Sep 21, 2015 at 5:01 PM, Samiyuru Senarathne 
> wrote:
>
>> Hi,
>>
>> In MSS based on Carbon 5, netty-http is used on top of netty for the
>> JAX-RS engine. Here, netty-http provides JAX-RS annotation processing
>> functionality using reflection. But the way that netty-http supports JX-RS
>> resource classes is bit too much coupled with netty-http implementation.
>>
>> IE in netty-http:
>>
>>1.
>>
>>All resource classes should implement co.cask.http.HttpHandler
>>interface.
>>2.
>>
>>First two parameters of all resource methods must be
>>io.netty.handler.codec.http.HttpRequest and co.cask.http.HttpResponder
>>3.
>>
>>No support for javax.ws.rs.core.Context
>>
>> In addition to that, there are few missing features in netty-http that we
>> need in MSS that should be implemented in netty-http side.
>>
>> Therefore, in order to use netty-http in MSS, multiple changes have to be
>> done to the netty-http library. In this case,
>>
>>1.
>>
>>We can do the changes and send pull request.
>>2.
>>
>>Or we can maintain our own code base.
>>
>>
>> What do you think about these concerns?
>>
>> Thank you.
>> --
>> Samiyuru Senarathne
>> *Software Engineer*
>> Mobile : +94 (0) 71 134 6087
>> samiy...@wso2.com
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Custom AS specific WebApp configuration file for web applications

[KasunG Gajasinghe]

Yes, Amila. The configuration file webapp-classloading.xml will still be
supported but deprecated. i

On Tue, Jul 14, 2015 at 10:36 AM, Amila Maha Arachchi ami...@wso2.com
wrote:

 +1 for the idea.

 Can we (or, are we going to) support the existing config files for one
 more release after 6.0. i.e. Code should look for this new file, if it is
 not there, it should work using the old config files. This way, existing
 apps will function smoothly in an AS 6.0 upgrade. I think I saw Kasun has
 said that old files are going to be deprecated which means my above
 assumption is right?

 On Mon, Jul 13, 2015 at 12:05 PM, KasunG Gajasinghe kas...@wso2.com
 wrote:


 Our next release is AS 5.3.0. AS 6.0 is planned for Q4 this year. So, we
 do not need this for DevS 3.8.

 Thanks.

 On Mon, Jul 13, 2015 at 9:49 AM, Jasintha Dasanayake jasin...@wso2.com
 wrote:

 I am also +1 for having a dedicated config file for AS webApp , BTW may
 I know what is time frame for this (AS 6.0.0) , Do we need to add this
 support for upcoming DevS 3.8.0 ?

 Thanks and Regards
 /Jasintha

 On Fri, Jul 10, 2015 at 7:07 PM, Manuri Perera manu...@wso2.com wrote:

 Hi,

 I have attached the current draft of the schema and a sample XML file
 herewith.
 The file name is yet to be decided.

 Thank you.​​
 ​​​
  wso2-web-1.0.xsd
 https://drive.google.com/a/wso2.com/file/d/0B4nvDnaOipEvdjRBbjZRU2hoYTA/view?usp=drive_web
 ​​
  wso2-web-sample.xml
 https://drive.google.com/a/wso2.com/file/d/0B4nvDnaOipEvSE1LY1VnTmdJMEE/view?usp=drive_web
 ​

 On Fri, Jul 10, 2015 at 10:45 AM, Kasun Gajasinghe kas...@wso2.com
 wrote:

 Hi Susinda,

 We are deprecating the webapp-classloading.xml in favor of this
 config. There are some new configurations as well that needs to be
 supported in devS side.

 The schema is not finalized yet. Manuri will share the current draft,
 and status. Note that this is targeted for AS 6.0.

 Thanks,
 KasunG

 On Jul 10, 2015, at 9:57 AM, Susinda Perera susi...@wso2.com wrote:



 On Thu, Jul 9, 2015 at 12:12 PM, KasunG Gajasinghe kas...@wso2.com
 wrote:


 Adding DevStudio folks so that they can track this change.

 From DevStudio side what we have to give is the wso2as-web.xml file?
 Are we giving a empty xml file or do we decided any template?


 On Mon, Jul 6, 2015 at 2:20 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Sameera,

 We need to show that this file is specific to web-applications
 deployed on AS and/or any other servers with webapp-mgt + CRE features
 right?

 So can we name it as wso2-web.xml ? This way it is generic across
 the platform.

 I agree with RuwanA on the fact that wso2as.xml will be a config
 file for the AS and will not give a sense that it is only used for
 web-applications.

 Examples
 http://geronimo.apache.org/GMOxDOC30/geronimo-webxml.html

 http://docs.oracle.com/cd/E26576_01/doc.312/e24929/dd-files.htm#GSDPG00078
 https://docs.jboss.org/jbossweb/7.0.x/appdev/jbossweb.html

 Thanks,

 On Fri, Jul 3, 2015 at 3:36 PM, Sameera Jayasoma same...@wso2.com
 wrote:

 +1 for this.

 How about wso2as.xml?

 Thanks,
 Sameera.

 On Thu, Jul 2, 2015 at 7:14 PM, KasunG Gajasinghe kas...@wso2.com
 wrote:

 *Overview*

 Currently, there are several AS specific configuration options
 that are available for webapp developers when deploying webapps in 
 AS. A
 set of identified configurations we have are as follows.

 1. Configure the ClassLoader Runtime Environment and Classloading
 for web apps (such as Carbon/CXF/Tomcat/...)
 2. Mark a JAX-RS webapp to be published as a Managed API for
 API-Everywhere story.
 3. Enable Single Sign On support for webapps
 4. Webapp SaaS configurations.
 5. Enable WebApp Statistics publishing to DAS/BAM

 *Why?*

 Right now, we are using different mechanisms to configure these.
 Mostly, we ask webapp developers to put the configuration options as a
 context-param in the web.xml. We also have a custom AS specific
 configuration file called webapp-classloaading.xml to configure
 classloading runtimes.

 Using web.xml for this purpose is not a clean approach since
 web.xml it should only contain configurations that are portable across
 different application servers. For this purpose, Tomcat uses a custom
 context.xml to put Tomcat specific configurations. JBoss has 
 jboss-web.xml.
 WebLogic has weblogic.xml, and so on..

 *How?*

 The idea here is to generalize the current webapp-classloading.xml
 we already have into a configuration file where all the webapp 
 related WSO2
 AS configurations can be put. We could name this file as 
 wso2as-web.xml or
 wso2as-application.xml.

 This is targeted for AS6 for immediate use with API-Everywhere
 feature. The implementation is fairly simple, and may be carried out 
 as a
 fast-track training project.

 WDYT?

 Thanks,
 KasunG

 --

 *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
 email: kasung AT spamfree wso2.com
 linked-in: http://lk.linkedin.com/in/gajasinghe
 blog: http://kasunbg.org






 --
 Sameera

Re: [Architecture] Custom AS specific WebApp configuration file for web applications

[KasunG Gajasinghe]

Our next release is AS 5.3.0. AS 6.0 is planned for Q4 this year. So, we do
not need this for DevS 3.8.

Thanks.

On Mon, Jul 13, 2015 at 9:49 AM, Jasintha Dasanayake jasin...@wso2.com
wrote:

 I am also +1 for having a dedicated config file for AS webApp , BTW may I
 know what is time frame for this (AS 6.0.0) , Do we need to add this
 support for upcoming DevS 3.8.0 ?

 Thanks and Regards
 /Jasintha

 On Fri, Jul 10, 2015 at 7:07 PM, Manuri Perera manu...@wso2.com wrote:

 Hi,

 I have attached the current draft of the schema and a sample XML file
 herewith.
 The file name is yet to be decided.

 Thank you.​​
 ​​​
  wso2-web-1.0.xsd
 https://drive.google.com/a/wso2.com/file/d/0B4nvDnaOipEvdjRBbjZRU2hoYTA/view?usp=drive_web
 ​​
  wso2-web-sample.xml
 https://drive.google.com/a/wso2.com/file/d/0B4nvDnaOipEvSE1LY1VnTmdJMEE/view?usp=drive_web
 ​

 On Fri, Jul 10, 2015 at 10:45 AM, Kasun Gajasinghe kas...@wso2.com
 wrote:

 Hi Susinda,

 We are deprecating the webapp-classloading.xml in favor of this config.
 There are some new configurations as well that needs to be supported in
 devS side.

 The schema is not finalized yet. Manuri will share the current draft,
 and status. Note that this is targeted for AS 6.0.

 Thanks,
 KasunG

 On Jul 10, 2015, at 9:57 AM, Susinda Perera susi...@wso2.com wrote:



 On Thu, Jul 9, 2015 at 12:12 PM, KasunG Gajasinghe kas...@wso2.com
 wrote:


 Adding DevStudio folks so that they can track this change.

 From DevStudio side what we have to give is the wso2as-web.xml file?
 Are we giving a empty xml file or do we decided any template?


 On Mon, Jul 6, 2015 at 2:20 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi Sameera,

 We need to show that this file is specific to web-applications
 deployed on AS and/or any other servers with webapp-mgt + CRE features
 right?

 So can we name it as wso2-web.xml ? This way it is generic across
 the platform.

 I agree with RuwanA on the fact that wso2as.xml will be a config file
 for the AS and will not give a sense that it is only used for
 web-applications.

 Examples
 http://geronimo.apache.org/GMOxDOC30/geronimo-webxml.html

 http://docs.oracle.com/cd/E26576_01/doc.312/e24929/dd-files.htm#GSDPG00078
 https://docs.jboss.org/jbossweb/7.0.x/appdev/jbossweb.html

 Thanks,

 On Fri, Jul 3, 2015 at 3:36 PM, Sameera Jayasoma same...@wso2.com
 wrote:

 +1 for this.

 How about wso2as.xml?

 Thanks,
 Sameera.

 On Thu, Jul 2, 2015 at 7:14 PM, KasunG Gajasinghe kas...@wso2.com
 wrote:

 *Overview*

 Currently, there are several AS specific configuration options that
 are available for webapp developers when deploying webapps in AS. A set 
 of
 identified configurations we have are as follows.

 1. Configure the ClassLoader Runtime Environment and Classloading
 for web apps (such as Carbon/CXF/Tomcat/...)
 2. Mark a JAX-RS webapp to be published as a Managed API for
 API-Everywhere story.
 3. Enable Single Sign On support for webapps
 4. Webapp SaaS configurations.
 5. Enable WebApp Statistics publishing to DAS/BAM

 *Why?*

 Right now, we are using different mechanisms to configure these.
 Mostly, we ask webapp developers to put the configuration options as a
 context-param in the web.xml. We also have a custom AS specific
 configuration file called webapp-classloaading.xml to configure
 classloading runtimes.

 Using web.xml for this purpose is not a clean approach since web.xml
 it should only contain configurations that are portable across different
 application servers. For this purpose, Tomcat uses a custom context.xml 
 to
 put Tomcat specific configurations. JBoss has jboss-web.xml. WebLogic 
 has
 weblogic.xml, and so on..

 *How?*

 The idea here is to generalize the current webapp-classloading.xml
 we already have into a configuration file where all the webapp related 
 WSO2
 AS configurations can be put. We could name this file as wso2as-web.xml 
 or
 wso2as-application.xml.

 This is targeted for AS6 for immediate use with API-Everywhere
 feature. The implementation is fairly simple, and may be carried out as 
 a
 fast-track training project.

 WDYT?

 Thanks,
 KasunG

 --

 *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
 email: kasung AT spamfree wso2.com
 linked-in: http://lk.linkedin.com/in/gajasinghe
 blog: http://kasunbg.org






 --
 Sameera Jayasoma,
 Software Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://blog.sameera.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 0094776364456

 Lean . Enterprise . Middleware


 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




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

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com
 http://kishanthan.wordpress.com

Re: [Architecture] Custom AS specific WebApp configuration file for web applications

[KasunG Gajasinghe]

Adding DevStudio folks so that they can track this change.

On Mon, Jul 6, 2015 at 2:20 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:

 Hi Sameera,

 We need to show that this file is specific to web-applications deployed on
 AS and/or any other servers with webapp-mgt + CRE features right?

 So can we name it as wso2-web.xml ? This way it is generic across the
 platform.

 I agree with RuwanA on the fact that wso2as.xml will be a config file for
 the AS and will not give a sense that it is only used for web-applications.

 Examples
 http://geronimo.apache.org/GMOxDOC30/geronimo-webxml.html
 http://docs.oracle.com/cd/E26576_01/doc.312/e24929/dd-files.htm#GSDPG00078
 https://docs.jboss.org/jbossweb/7.0.x/appdev/jbossweb.html

 Thanks,

 On Fri, Jul 3, 2015 at 3:36 PM, Sameera Jayasoma same...@wso2.com wrote:

 +1 for this.

 How about wso2as.xml?

 Thanks,
 Sameera.

 On Thu, Jul 2, 2015 at 7:14 PM, KasunG Gajasinghe kas...@wso2.com
 wrote:

 *Overview*

 Currently, there are several AS specific configuration options that are
 available for webapp developers when deploying webapps in AS. A set of
 identified configurations we have are as follows.

 1. Configure the ClassLoader Runtime Environment and Classloading for
 web apps (such as Carbon/CXF/Tomcat/...)
 2. Mark a JAX-RS webapp to be published as a Managed API for
 API-Everywhere story.
 3. Enable Single Sign On support for webapps
 4. Webapp SaaS configurations.
 5. Enable WebApp Statistics publishing to DAS/BAM

 *Why?*

 Right now, we are using different mechanisms to configure these. Mostly,
 we ask webapp developers to put the configuration options as a
 context-param in the web.xml. We also have a custom AS specific
 configuration file called webapp-classloaading.xml to configure
 classloading runtimes.

 Using web.xml for this purpose is not a clean approach since web.xml it
 should only contain configurations that are portable across different
 application servers. For this purpose, Tomcat uses a custom context.xml to
 put Tomcat specific configurations. JBoss has jboss-web.xml. WebLogic has
 weblogic.xml, and so on..

 *How?*

 The idea here is to generalize the current webapp-classloading.xml we
 already have into a configuration file where all the webapp related WSO2 AS
 configurations can be put. We could name this file as wso2as-web.xml or
 wso2as-application.xml.

 This is targeted for AS6 for immediate use with API-Everywhere feature.
 The implementation is fairly simple, and may be carried out as a fast-track
 training project.

 WDYT?

 Thanks,
 KasunG

 --

 *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
 email: kasung AT spamfree wso2.com
 linked-in: http://lk.linkedin.com/in/gajasinghe
 blog: http://kasunbg.org






 --
 Sameera Jayasoma,
 Software Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://blog.sameera.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 0094776364456

 Lean . Enterprise . Middleware


 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




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

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com*
 Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan*




-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] Custom AS specific WebApp configuration file for web applications

[KasunG Gajasinghe]

*Overview*

Currently, there are several AS specific configuration options that are
available for webapp developers when deploying webapps in AS. A set of
identified configurations we have are as follows.

1. Configure the ClassLoader Runtime Environment and Classloading for web
apps (such as Carbon/CXF/Tomcat/...)
2. Mark a JAX-RS webapp to be published as a Managed API for API-Everywhere
story.
3. Enable Single Sign On support for webapps
4. Webapp SaaS configurations.
5. Enable WebApp Statistics publishing to DAS/BAM

*Why?*

Right now, we are using different mechanisms to configure these. Mostly, we
ask webapp developers to put the configuration options as a context-param
in the web.xml. We also have a custom AS specific configuration file called
webapp-classloaading.xml to configure classloading runtimes.

Using web.xml for this purpose is not a clean approach since web.xml it
should only contain configurations that are portable across different
application servers. For this purpose, Tomcat uses a custom context.xml to
put Tomcat specific configurations. JBoss has jboss-web.xml. WebLogic has
weblogic.xml, and so on..

*How?*

The idea here is to generalize the current webapp-classloading.xml we
already have into a configuration file where all the webapp related WSO2 AS
configurations can be put. We could name this file as wso2as-web.xml or
wso2as-application.xml.

This is targeted for AS6 for immediate use with API-Everywhere feature. The
implementation is fairly simple, and may be carried out as a fast-track
training project.

WDYT?

Thanks,
KasunG

-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] WSO2 AS 5.3.0 Alpha Released !!

[KasunG Gajasinghe]

Hi folks,

WSO2 Application Server team is pleased to announce the first alpha release
of WSO2 AS 5.3.0. The AS 5.3.0 Alpha distribution is available at [1]. This
release introduces several major features and improvements.

*New Features*
-

* JavaEE 6 Web Profile support via TomEE 1.7.2 integration
* Websocket 1.1 API Support as defined by the JSR-356 specification
* SAML2 Single-Sign-On support for web applications
* Tomcat Virtual Hosts support
* HTTP Session Persistence support
* WS-Discovery support for CXF JAX-WS and JAX-RS services
* OSGi ServiceLoader Mediator specification support via SPI-Fly

* Removed the first class support provided for deploying Axis2 AAR Services
* Removed the data services hosting support from AS. Users can use the WSO2
Data Services Server product to deploy data services.


*Existing **Key Features*
---

* Support for Servlet 3, JSP 2.2, EL 2.2, JSTL 1.2 specifications.
* Full JAX-WS 2.2 and JAX-RS 2.0 Specification support
* Integration of Jaggery - server side scripting framework
* Unified Application listing and management UI for WebApps, JAX-WS/RS,
Jaggery
* Multi Tenant support for standalone deployment
* 100% Apache Tomcat compliance runtime
* Lazy loading for web applications and services
* Tooling - Application Server related artifacts can be easily generated
using WSO2 Developer Studio
* Clustering support for High Availability and High Scalability
* Full support for WS-Security, WS-Trust, WS-Policy and WS-Secure
Conversation
* JMX and Web interface based monitoring and management
* WS-* and REST support
* GUI, command line, and IDE based tools for Web service development
* Equinox P2 based provisioning support
* WSDL2Java/Java2WSDL/WSDL 1.1, and UI-based try it (invoke any remote Web
service)

*Issues Fixed in This Release*

  https://wso2.org/jira/issues/?filter=12252

*Known Issues*

  https://wso2.org/jira/issues/?filter=12253


*How You Can Contribute*


   - Source Code Repository
  - https://github.com/wso2/


   - Mailing Lists

Join our mailing list and correspond with the developers directly.


   - Developer List : d...@wso2.org | Subscribe
  dev-requ...@wso2.org?subject=subscribe
  - User List : StackOverflow.com
  http://stackoverflow.com/questions/tagged/wso2


   - *Reporting Issues*

WSO2 encourages you to report issues and your enhancement requests for
the WSO2 AS using the AS Public JIRA https://wso2.org/jira/browse/WSAS.


[1] http://svn.wso2.org/repos/wso2/people/kasung/as5.3.0-alpha/


*~ WSO2 Application Server Team~*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] WebSocket Implementations which are based on Tomcat 7.x needs to change according to JSR-356 websocket spec to support in Tomcat 8.x

[KasunG Gajasinghe]

Hi,

The current plan is to upgrade the Tomcat version to 8.x in Carbon 4.5.0.
So, to move to Carbon 4.5.0 (when it's released) you will need to move the
tomcat proprietary websocket implementation to JSR356.

On Thu, May 7, 2015 at 5:29 PM, Thusitha Thilina Dayaratne 
thusit...@wso2.com wrote:

 Hi All,

 I'm working on introducing Tomcat 8.x support to the Carbon kernel and the
 WSO2-AS.
 With the Tomcat 8.x, it no longer supports the tomcat specific WebSocket
 implementation which was there in Tomcat 7.x. Tomcat 8.x implements Java
 WebSocket 1.1 API defined by JSR-356 [1,2].
 Therefore all the previous WebSocket implementations used in WSO2
 products, which are based on Tomcat 7.x need to be changed in order to
 support with the Tomcat 8.x.

 e,g. AFAIK jaggery uses the tomcat 7.x based WebSocket implementation.
 This will not supports with the Tomcat 8.x.

 [1] - https://tomcat.apache.org/tomcat-8.0-doc/web-socket-howto.html
 [2] - http://www.oracle.com/technetwork/articles/java/jsr356-1937161.html

 Thanks
 Best Regards
 --
 Thusitha Dayaratne
 Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 Mobile  +94712756809
 Blog  alokayasoya.blogspot.com
 Abouthttp://about.me/thusithathilina


 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Data Services services.xml support is removed? svn commit r206697 - in carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4: . src/main/j

[KasunG Gajasinghe]

Thanks for clarifications. This change will affect the users who use the
services.xml with DSS though. We should have deprecated the support for
services.xml first.

On Thu, Apr 23, 2015 at 1:41 PM, Chanika Geeganage chan...@wso2.com wrote:

 Yes, the car file that includes the dataservice config is deployed through
 the default deployer and it expects only a single file. Therefore, we
 couldn't include the service.xml file into the car file. So we remove this
 method and introduced some parameters (transports and security policy) into
 the dataservice config.

 Thanks


 On Thu, Apr 23, 2015 at 10:34 AM, Anjana Fernando anj...@wso2.com wrote:

 Hi Kasun,

 Yeah, I guess we've removed this functionality, since we were replacing
 that functionality with additional properties we've introduced, for giving
 security policies and mentioning transports. @Chanika, I guess that's the
 case? .. and I guess, the reason for doing this is because of some tooling
 complications we had with services.xml? ..

 Cheers,
 Anjana.

 On Wed, Apr 22, 2015 at 6:27 PM, KasunG Gajasinghe kas...@wso2.com
 wrote:

 Hi Anjana/Chanika,

 Did we decide to remove the services.xml support for the data services?
 I noticed the below commit which made its way into DSS 3.2.1.

 Thanks.

 -- Forwarded message --
 From: chan...@wso2.com
 Date: Thu, Aug 28, 2014 at 9:54 AM
 Subject: [Commits] [Carbon-platform] svn commit r206697 - in
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4:
 . src/main/java/org/wso2/carbon/dataservices/core
 To: comm...@wso2.org


 Author: chan...@wso2.com
 Date: Thu Aug 28 09:54:36 2014
 New Revision: 206697
 URL: http://wso2.org/svn/browse/wso2?view=revrevision=206697

 Log:
 Fixing DS-953

 Modified:

  
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/pom.xml

  
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/src/main/java/org/wso2/carbon/dataservices/core/DBDeployer.java

 Modified:
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/pom.xml
 URL:
 http://wso2.org/svn/browse/wso2/carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/pom.xml?rev=206697r1=206696r2=206697view=diff

 ==
 ---
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/pom.xml
   (original)
 +++
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/pom.xml
   Thu Aug 28 09:54:36 2014
 @@ -127,7 +127,7 @@
  dependency
  groupIdorg.wso2.carbon/groupId
  artifactIdorg.wso2.carbon.dataservices.common/artifactId
 -version4.2.3/version
 +version4.2.4/version
  /dependency
  dependency
  groupIdorg.wso2.carbon/groupId

 Modified:
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/src/main/java/org/wso2/carbon/dataservices/core/DBDeployer.java
 URL:
 http://wso2.org/svn/browse/wso2/carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/src/main/java/org/wso2/carbon/dataservices/core/DBDeployer.java?rev=206697r1=206696r2=206697view=diff

 ==
 ---
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/src/main/java/org/wso2/carbon/dataservices/core/DBDeployer.java
   (original)
 +++
 carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.4/src/main/java/org/wso2/carbon/dataservices/core/DBDeployer.java
   Thu Aug 28 09:54:36 2014
 @@ -18,6 +18,7 @@
   */
  package org.wso2.carbon.dataservices.core;

 +import org.apache.axiom.om.OMAttribute;
  import org.apache.axiom.om.OMElement;
  import org.apache.axiom.om.impl.builder.StAXOMBuilder;
  import org.apache.axiom.soap.SOAP11Constants;
 @@ -35,8 +36,10 @@
  import org.apache.axis2.transport.http.HTTPConstants;
  import org.apache.axis2.wsdl.WSDLConstants;
  import org.apache.axis2.wsdl.WSDLUtil;
 +import org.apache.neethi.Policy;
  import org.apache.commons.logging.Log;
  import org.apache.commons.logging.LogFactory;
 +import org.apache.neethi.PolicyEngine;
  import org.apache.ws.commons.schema.utils.NamespaceMap;
  import org.wso2.carbon.CarbonConstants;
  import org.wso2.carbon.base.MultitenantConstants;
 @@ -56,6 +59,7 @@
  import org.wso2.carbon.ndatasource.common.DataSourceConstants;
  import org.wso2.carbon.ndatasource.common.DataSourceException;
  import org.wso2.carbon.ndatasource.core.DataSourceManager;
 +import org.wso2.carbon.registry.core.Registry;
  import org.wso2.carbon.user.core.UserStoreException;
  import org.wso2

Re: [Architecture] How to release a milestone product pack ?

[KasunG Gajasinghe]

Hi Sagara,

You can use the following system property to ignore snapshot validation
check during release:prepare. So, for milestones, we can simply use this
one.

* -DignoreSnapshots=true*

The maven doc reference can be found in [1] under
*allowTimestampedSnapshots.*

So, shall we use this intead?

[1]
http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html

Thanks.


On Tue, Mar 10, 2015 at 5:36 PM, Selvaratnam Uthaiyashankar 
shan...@wso2.com wrote:

 Sameera/Kishanthan/KasunG/Srinath,

 Can you guys comment on this please?

 On Tue, Mar 10, 2015 at 5:33 PM, Sagara Gunathunga sag...@wso2.com
 wrote:



 On Tue, Mar 10, 2015 at 5:12 PM, Selvaratnam Uthaiyashankar 
 shan...@wso2.com wrote:

 Why do we have to use the release plugin for the milestone releases? I
 don't think it is correct to use the release plugin for milestone release.


 Maven release plugin was already used by some other teams during
 milestone releases and I also under impression that we should use release
 plugin for all releases.   If we are not suppose to use release plugin,
 shall we agree on following procedure.

  1.  Create a tag in product repo.
  2.  Create tags in SNAPSHOT dependency repos.
  3.  RM locally build the pack, test and release.


  Thanks !



 We chat yesterday, but I didn't realize we talked about Maven release
 plugin. It shouldn't be forked.

 @Kasun, it is similar to ESB depends on carbon-mediation. It is
 developed and maintained by same team. It is valid to depend on SNAPSHOT
 for a milestone release. However, you can't depend on SNAPSHOT components
 developed by some other team (again, there are exceptions, but team has to
 justify that). For example, ESB can't depend on corbon-governance SNAPSHOT.


 On Tue, Mar 10, 2015 at 8:10 AM, Sagara Gunathunga sag...@wso2.com
 wrote:




 On Tue, Mar 10, 2015 at 12:34 AM, Kasun Indrasiri ka...@wso2.com
 wrote:

 How about depending only on released components for a given product
 milestone? Because a given milestone is a stable pack that depends on the
 stables upstream components.


 If I reiterate the problem, ATM  carbon-governance/carbon-registry are
 stable in terms of set of completed features but not yet production ready
 as whole hence IMHO we should avoid proper release numbers (e.g  
 carbon-registry-4.3.2
 ) for something not yet production ready, we should use either post-fix
 like SNAPSHOT or M2, M3 etc.

 If we just use proper release numbers for milestone versions it will
 make disaster for end users (both internal and external) because they can't
 simply find which version is production ready and which one is not yet
 ready, usually users tend to use latest available version but with this
 approach there is a high chance that latest one is not production ready.
 BTW some of the popular project like Spring[1] use set of post-fix so that
 end users can easily distinguish GA, Alpha, Beta, M-X versions.

 [1] - http://repo1.maven.org/maven2/org/springframework/spring-core/

 Thanks !


 On Mon, Mar 9, 2015 at 2:06 PM, Sagara Gunathunga sag...@wso2.com
 wrote:


 We are about to release G-Reg 5.0.0 M3 pack but found an issue when
 releasing a milestone version.  Let me take G-Reg as an example, G-Reg
 5.0.0-M3 version is depends on carbon-governance SNAPSHOT version  and 
 that
 is a legitimate use as well ( As G-Reg 5.0.0-M3 version, we actually
 release some of the completed features of 
 carbon-governance/carbon-registry
 repos.)  but Maven release plug-in does not support to release any 
 project
 with SNAPSHOT dependencies [1] [4], so we have 2 options to solve this
 issue.



 *1. ) Modify Maven release plug-in to allow  SNAPSHOT dependencies.*

 Pros
 -
 - Fix is relatively straightforward, we just have to remove
 validation in code and allow  SNAPSHOT dependencies.

 - No change to release process.


 Cons
 -
 - We have to fork and maintain Maven release plug-in locally and will
 lose new changes from Apache.

 - If we consider G-Reg-5.0.0-M3 pack, technically it's a milestone
 version not a snapshot version so as a principle 'creation process of the
 pack' should be repeatable but if we allow SNAPSHOT dependencies inside
 product packs 'creation process of the pack' is not repeatable.  This is
 not something standard, if we decided to go with this approach at least 
 we
 should not call them as milestone packs instead SNAPSHOT packs (like
 nightly builds)  e.g -   G-Reg-5.0.0-SNAPSHOT-08-03-15 pack etc.






 *2.) Instead of SNAPSHOT dependencies, first release own dependencies
 with M-'X'   (e.g  - carbon-governance-4.4.0-M1 ) and then use these
 released versions within the milestone product pack. *

 Example - G-Reg 5.0.0-M3 pack can have carbon-governance-4.4.0-M2 and
 carbon-registry-4.3.2-M5  but NOT carbon-identity-4.3.1-M2

 Pros
 -
 - Again relatively straightforward, we don't need to fork and
 maintain Maven release plug-in.

 - AFAIK adding post-fix to distinguish Milestone, Alpha, Beta
 

Re: [Architecture] Exploded web app deployment for developer studio

[KasunG Gajasinghe]

Hi Awanthika,

It seems your mail body is empty. :-)

On Wed, Feb 25, 2015 at 6:16 PM, Awanthika Senarath awanth...@wso2.com
wrote:

 Adding Architecture group

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Dev] Fixing CApp story for Carbon 4.3.0

[KasunG Gajasinghe]

There's a parameter called allowRoles that can be used to enforce roles. It
could contain a comma separated roles list. But, I believe it would be much
cleaner if the roles can also be included in the RampartConfig of the
policy.

ESB can go ahead with this approach. Security wizard already resides in
carbon-identity component.

On Tue, Feb 17, 2015 at 10:42 AM, Kishanthan Thangarajah 
kishant...@wso2.com wrote:

 OK, lets go ahead with this. The initial plan is to write this for STS
 only so that IS can own this. But If ESB also need this, where are we going
 to maintain this?

 On Mon, Feb 16, 2015 at 11:53 AM, Johann Nallathamby joh...@wso2.com
 wrote:

 [Adding Godwin to the thread]

 IS team has already started working on this targeting the IS 5.1.0
 release on Git based on carbon-kernel 4.3.0.

 Following are items we will be doing.

 1. We will continue using the security wizard to apply STS policies and
 persist it to registry.

 2. Previously the security policies as well as metadata were persisted in
 filesystem for axis2 services. Now we will be persisting them both in
 registry.
 In  ESB the security policies only were stored in registry, so we will
 also try to reuse the same logic/location to store the security policies.

 3. Recently we found that ESB also has a problem after removing the
 security wizard. In this new approach although security policies are
 applied in dev studio and persisted in registry we haven't thought about
 the role based access control which you get when doing through the security
 wizard. This got stored in the metafile. I was under the impression that
 this was also decided to be removed with these new changes. But looks like
 they still need it. So once we do this change they also will be able to use
 it.

 If you have any concerns please raise them now.

 Thanks.

 On Mon, Jul 7, 2014 at 3:15 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:




 On Sun, Jul 6, 2014 at 3:12 PM, Johann Nallathamby joh...@wso2.com
 wrote:

 Hi Kishanthan,


 On Tue, Jul 1, 2014 at 8:03 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 Hi All,

 We recently had a meeting on $subject. Our current story for CApp
 (Carbon Application) development approach is broken when including
 application of QoS for services. This was mainly due to the issues we 
 faced
 with,

 - the file-based metadata persistence layer for services.
 - the possibility to change/apply QoS via mgt console.
 - clustering and deployment synchronization.

 To fix these, as the first step, we have removed the file based
 persistence layer from platform. This layer was mainly used to persist QoS
 related settings of the axis2services. This can be replaced by using
 services.xml file for each service.  All types of axis2services (other 
 than
 proxy-services) has support for services.xml currently. For proxy 
 services,
 the application of some QoS (Ex: security) can be defined inline by
 referring the relevant policies from registry.

 We need a meeting to discuss about the following next steps.
 - How this will affect ESB (proxy-services) and how to fix those.
 - Removing the current way of applying QoS via mgt console and
 providing a different approach, which will not be part of the CApp
 development process.


 This will have serious impact on STS functionality of IS. STS is a
 specialised axis2 service, deployed from an OSGi bundle and shared across
 all tenants. The security policy used to secure the STS is within the scope
 of a tenant and is deployed as a service metafile like any other service.
 STS  is unsecured by default. Tenant admins would secure the STS with
 preferred policy.

 Two reason why the above approach would not work for IS,

 1. Securing STS is a admin functionality in my opinion. It is not a
 development time aspect. This may be not the case for other services.

 2. Since STS is a shared service editing services.xml won't work.

 If we go with this new approach in platform, we need to do the
 following from IS side.

 1. We need to continue using the security wizard UI to apply policies
 and modify the backend service to persist policy in either registry or
 Identity DB.

 2. We need to modify the Security Deployment Interceptor which reads
 the security policy from filesystem, to read it from registry or database.


 Yes, this would be the option here. You can also use the same approach
 like how proxy services keep policy references for applied security
 scenarios with registry.



 @Sagara/KasunG
 How is AS team planning to handle this. Are you going to deprecate
 usage of security wizard UI and leave it to development time? Or are you
 having any other approach in mind?

 Thanks,
 Johann.


 Thanks,
 Kishanthan.

 --
 *Kishanthan Thangarajah*
 Senior Software Engineer,
 Platform Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com
 http://kishanthan.wordpress.com*
 Twitter - 

Re: [Architecture] Feature Level Automation Testing

[KasunG Gajasinghe]

Hi,

Will we be writing integration tests or unit tests with this approach? If
we are writing integration tests here, then we will have integration tests
in carbon component/feature repos in addition to what we already have in
product repos.

It's important to have automation tests at product level. So, when writing
a new integration test, how can we decide which repo it should go to? Will
we have to duplicate any test?



On Wed, Oct 29, 2014 at 6:51 PM, Irham Iqbal iq...@wso2.com wrote:

 Hi all,

 I am working on creating an environment to write test cases to test
 standalone features. With new GIT module components and features should be
 released prior to product releases, so all features must be thoroughly
 tested and should be production ready. Carbon runtime is needed to test the
 standalone features, so our plan is to start carbon-core by installing all
 features resided in a project repository.

 For creating test execution environment, all features will be installed on
 carbon-core using carbon-p2-plugin. Before installing we have to create
 p2-repo with relevant features in it. To do that, need to have pom with all
 feature dependencies required (including common dependencies) . P2-repo
 will be created by installing that pom with relevant features specified.
 When installing a feature you have to find out and install all the other
 features this feature is depending on.

 After creating carbon-core with all required features, test framework
 dependency will be used with new extension classes to facilitate sever
 management, code coverage generation and user/tenant creation.

 I've done a POC to verify feature installation on carbon-core in
 carbon-deployment project and everything seems to work fine. Just need
 clarify whether this is the correct approach for feature level testing and
 any suggestions for alternatives. Kindly expecting your ideas on this.

 Attached diagram depict proposed architecture.


 ​​
 ​Thanks,
 Iqbal

 --
 Irham Iqbal
 Software Engineer - Test Automation
  WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware
 phone: +94 777888452




-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] Functionality of CAppDeployer cleanup operation

[KasunG Gajasinghe]

Hi,

I've been testing the CAppDeployer functionality these days. One thing I
noticed was that the cleanup operation in CappAxis2Deployer is an empty
code block!

Usually, the cleanup operation of an axis2 deployer gets called during the
termination of ConfigurationContext. ie. during a tenant unload for
tenants, and during a server shutdown for super-tenant. Is there any
special reason we have not implemented this method?

I think we have to implement this method, and call the cleanup operation of
the deployers of artifacts packed inside the CApp. Further,
CappAxis2Deployer maintains a list of currently deployed CApps in the
tenant. We have to remove all these references too. Otherwise, this will
cause severe memory leaks, isn't it?

WDYT?

Thanks,
KasunG

-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Tomcat virtual host support for tenant users

[KasunG Gajasinghe]

Hi Nipuni,

What happens when a tenant uploads a webapp to a virtual host? Can the user
invoke it?



On Tue, Sep 23, 2014 at 2:39 PM, Nipuni Perera nip...@wso2.com wrote:

 Hi,

 I am working on an improvement for WSO2-AS to enable tomcat virtual host
 support [1].  With the current improvements we support the creation of
 additional virtual hosts as required by the users. A user need to modify
 catalina-server.xml (inside CARBON-HOME/repository/conf/tomcat/) to add
 an additional host to tomcat as below.

 Engine name=Catalina defaultHost=localhost
 ...
   Host name=localhost unpackWARs=true deployOnStartup=false
 autoDeploy=false
 appBase=${carbon.home}/repository/deployment/server/webapps/
   ...
   /Host
   Host name=www.vhost.com unpackWARs=true
 deployOnStartup=false autoDeploy=false
 appBase=${carbon.home}/repository/deployment/server/dir/
  ...
   /Host
 /Engine

 Therefore this feature (adding virtual hosts) is only available for the
 super tenant. Does a tenant should be able to add webapps to virtual
 hosts?. Image below (webapp-upload-page.png) shows the webapp upload page
 (for both tenants and super tenant) according to the current
 implementation. Users can select under which host name the uploaded webapp
 should deploy to. Does this option should visible for tenants as well?
 ​
  webapp-upload-page.png
 https://docs.google.com/a/wso2.com/file/d/0B3LbkLV5KkU_MFFpWlVUbHpPQmM/edit?usp=drive_web
 ​
 [1] https://wso2.org/jira/browse/WSAS-1727

 Thanks,
 Nipuni
 --
 Nipuni Perera
 Software Engineer; WSO2 Inc.; http://wso2.com
 Email: nip...@wso2.com
 Git hub profile: https://github.com/nipuni
 Mobile: +94 (71) 5626680
 http://wso2.com




-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture