Re: [Dev] Folder Structure for C5 based MB

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [Dev] Folder Structure for C5 based MB

Hasitha Amal De Silva
Hi Kishanthan, 

Agreed. As per Nandika, the product folder here is invalid since MB will only result in a set of components + features to be used by other carbon products. 

Based on that standing, we will not need to do product releases but do only component+feature releases. 

Thanks


On Thu, Apr 27, 2017 at 1:46 PM, Madhawa Gunasekara <[hidden email]> wrote:
Hi Eranda,

+1 to make it into one repo. AFAIU We don't need to have product folder here, Since We don't create a p2 profile in this repo. We should include only components and features in this repo.

Thanks,
Madhawa

On Thu, Apr 27, 2017 at 11:32 AM, Eranda Rajapakshe <[hidden email]> wrote:

Hi, HasithaD and I are working on bootstrapping the C5 based Message Broker product.


In the current version of WSO2 Message broker (3.x) we have following 3 repos.


  1. Andes - contains the messaging core, apache qpid fork and JMX monitoring objects.

  2. Carbon-business-messaging - contains admin services, wraps andes as a osgi service, and the UI impl.

  3. Product-mb - contains test cases, and distribution configurations.


For MB 4x, we have come up with a more unified structure based on a single repo (refer [2] as an example). The intention here is to reduce build and maintenance complexity. However, if there is a need to use separate components/features within MB into other products, we need to go for separate repos as and when required.


We will be working on product-mb/4.x.x branch [1]. Please let us know any suggestion and comments on this.


[1]. https://github.com/wso2/product-mb/tree/4.x.x


[2].

product-mb

├── components

│     ├── org.wso2.carbon.andes

│     ├── org.wso2.carbon.mb.services

│     ├── org.wso2.carbon.mb.ui

│     └── …..

├── features

│     ├── org.wso2.carbon.andes.feature

│     ├── org.wso2.carbon.mb.services.feature

│     ├── org.wso2.carbon.mb.ui.feature

│     └── …...

├── pom.xml

├── LICENSE.txt

├── README.md

└── product

      ├── carbon-home

      │       └── README.md

      ├── carbon.product

      ├── pom.xml

      └── src

              └── assembly

                     ├── bin.xml

                      └── filter.properties


Thanks,
--
Eranda Rajapakshe
Software Engineer
WSO2 Inc.
Mobile : <a href="tel:%2B94784822608" value="+94784822608" target="_blank">+94784822608

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




--
Madhawa Gunasekara
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile:
<a href="tel:+94+719411002" target="_blank">+94 719411002



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : +94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )


_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: [Dev] Folder Structure for C5 based MB

Pamod Sylvester
(+) NuwanD

+1, also APIM would embed the broker with all the features included ? (same as it's being used in EI) correct me if i am wrong ?  

Thanks,
Pamod

On Thu, Apr 27, 2017 at 1:49 PM, Hasitha Amal De Silva <[hidden email]> wrote:
Hi Kishanthan, 

Agreed. As per Nandika, the product folder here is invalid since MB will only result in a set of components + features to be used by other carbon products. 

Based on that standing, we will not need to do product releases but do only component+feature releases. 

Thanks


On Thu, Apr 27, 2017 at 1:46 PM, Madhawa Gunasekara <[hidden email]> wrote:
Hi Eranda,

+1 to make it into one repo. AFAIU We don't need to have product folder here, Since We don't create a p2 profile in this repo. We should include only components and features in this repo.

Thanks,
Madhawa

On Thu, Apr 27, 2017 at 11:32 AM, Eranda Rajapakshe <[hidden email]> wrote:

Hi, HasithaD and I are working on bootstrapping the C5 based Message Broker product.


In the current version of WSO2 Message broker (3.x) we have following 3 repos.


  1. Andes - contains the messaging core, apache qpid fork and JMX monitoring objects.

  2. Carbon-business-messaging - contains admin services, wraps andes as a osgi service, and the UI impl.

  3. Product-mb - contains test cases, and distribution configurations.


For MB 4x, we have come up with a more unified structure based on a single repo (refer [2] as an example). The intention here is to reduce build and maintenance complexity. However, if there is a need to use separate components/features within MB into other products, we need to go for separate repos as and when required.


We will be working on product-mb/4.x.x branch [1]. Please let us know any suggestion and comments on this.


[1]. https://github.com/wso2/product-mb/tree/4.x.x


[2].

product-mb

├── components

│     ├── org.wso2.carbon.andes

│     ├── org.wso2.carbon.mb.services

│     ├── org.wso2.carbon.mb.ui

│     └── …..

├── features

│     ├── org.wso2.carbon.andes.feature

│     ├── org.wso2.carbon.mb.services.feature

│     ├── org.wso2.carbon.mb.ui.feature

│     └── …...

├── pom.xml

├── LICENSE.txt

├── README.md

└── product

      ├── carbon-home

      │       └── README.md

      ├── carbon.product

      ├── pom.xml

      └── src

              └── assembly

                     ├── bin.xml

                      └── filter.properties


Thanks,
--
Eranda Rajapakshe
Software Engineer
WSO2 Inc.
Mobile : <a href="tel:%2B94784822608" value="+94784822608" target="_blank">+94784822608

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




--
Madhawa Gunasekara
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile:
<a href="tel:+94+719411002" target="_blank">+94 719411002



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Pamod Sylvester 
WSO2 Inc.; http://wso2.com
cell: +94 77 7779495

_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: [Dev] Folder Structure for C5 based MB

Hasitha Amal De Silva
[+NuwanD]

On Thu, Apr 27, 2017 at 1:53 PM, Pamod Sylvester <[hidden email]> wrote:
(+) NuwanD

+1, also APIM would embed the broker with all the features included ? (same as it's being used in EI) correct me if i am wrong ?  

Thanks,
Pamod

On Thu, Apr 27, 2017 at 1:49 PM, Hasitha Amal De Silva <[hidden email]> wrote:
Hi Kishanthan, 

Agreed. As per Nandika, the product folder here is invalid since MB will only result in a set of components + features to be used by other carbon products. 

Based on that standing, we will not need to do product releases but do only component+feature releases. 

Thanks


On Thu, Apr 27, 2017 at 1:46 PM, Madhawa Gunasekara <[hidden email]> wrote:
Hi Eranda,

+1 to make it into one repo. AFAIU We don't need to have product folder here, Since We don't create a p2 profile in this repo. We should include only components and features in this repo.

Thanks,
Madhawa

On Thu, Apr 27, 2017 at 11:32 AM, Eranda Rajapakshe <[hidden email]> wrote:

Hi, HasithaD and I are working on bootstrapping the C5 based Message Broker product.


In the current version of WSO2 Message broker (3.x) we have following 3 repos.


  1. Andes - contains the messaging core, apache qpid fork and JMX monitoring objects.

  2. Carbon-business-messaging - contains admin services, wraps andes as a osgi service, and the UI impl.

  3. Product-mb - contains test cases, and distribution configurations.


For MB 4x, we have come up with a more unified structure based on a single repo (refer [2] as an example). The intention here is to reduce build and maintenance complexity. However, if there is a need to use separate components/features within MB into other products, we need to go for separate repos as and when required.


We will be working on product-mb/4.x.x branch [1]. Please let us know any suggestion and comments on this.


[1]. https://github.com/wso2/product-mb/tree/4.x.x


[2].

product-mb

├── components

│     ├── org.wso2.carbon.andes

│     ├── org.wso2.carbon.mb.services

│     ├── org.wso2.carbon.mb.ui

│     └── …..

├── features

│     ├── org.wso2.carbon.andes.feature

│     ├── org.wso2.carbon.mb.services.feature

│     ├── org.wso2.carbon.mb.ui.feature

│     └── …...

├── pom.xml

├── LICENSE.txt

├── README.md

└── product

      ├── carbon-home

      │       └── README.md

      ├── carbon.product

      ├── pom.xml

      └── src

              └── assembly

                     ├── bin.xml

                      └── filter.properties


Thanks,
--
Eranda Rajapakshe
Software Engineer
WSO2 Inc.
Mobile : <a href="tel:%2B94784822608" value="+94784822608" target="_blank">+94784822608

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




--
Madhawa Gunasekara
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile:
<a href="tel:+94+719411002" target="_blank">+94 719411002



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Pamod Sylvester 
WSO2 Inc.; http://wso2.com
cell: <a href="tel:+94%2077%20777%209495" value="+94777779495" target="_blank">+94 77 7779495



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : +94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )


_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: [Dev] Folder Structure for C5 based MB

Hasitha Amal De Silva


On Thu, Apr 27, 2017 at 1:55 PM, Hasitha Amal De Silva <[hidden email]> wrote:
[+NuwanD]

On Thu, Apr 27, 2017 at 1:53 PM, Pamod Sylvester <[hidden email]> wrote:
(+) NuwanD

+1, also APIM would embed the broker with all the features included ? (same as it's being used in EI) correct me if i am wrong ?  

Thanks,
Pamod

On Thu, Apr 27, 2017 at 1:49 PM, Hasitha Amal De Silva <[hidden email]> wrote:
Hi Kishanthan, 

Agreed. As per Nandika, the product folder here is invalid since MB will only result in a set of components + features to be used by other carbon products. 

Based on that standing, we will not need to do product releases but do only component+feature releases. 

Thanks


On Thu, Apr 27, 2017 at 1:46 PM, Madhawa Gunasekara <[hidden email]> wrote:
Hi Eranda,

+1 to make it into one repo. AFAIU We don't need to have product folder here, Since We don't create a p2 profile in this repo. We should include only components and features in this repo.

Thanks,
Madhawa

On Thu, Apr 27, 2017 at 11:32 AM, Eranda Rajapakshe <[hidden email]> wrote:

Hi, HasithaD and I are working on bootstrapping the C5 based Message Broker product.


In the current version of WSO2 Message broker (3.x) we have following 3 repos.


  1. Andes - contains the messaging core, apache qpid fork and JMX monitoring objects.

  2. Carbon-business-messaging - contains admin services, wraps andes as a osgi service, and the UI impl.

  3. Product-mb - contains test cases, and distribution configurations.


For MB 4x, we have come up with a more unified structure based on a single repo (refer [2] as an example). The intention here is to reduce build and maintenance complexity. However, if there is a need to use separate components/features within MB into other products, we need to go for separate repos as and when required.


We will be working on product-mb/4.x.x branch [1]. Please let us know any suggestion and comments on this.


[1]. https://github.com/wso2/product-mb/tree/4.x.x


[2].

product-mb

├── components

│     ├── org.wso2.carbon.andes

│     ├── org.wso2.carbon.mb.services

│     ├── org.wso2.carbon.mb.ui

│     └── …..

├── features

│     ├── org.wso2.carbon.andes.feature

│     ├── org.wso2.carbon.mb.services.feature

│     ├── org.wso2.carbon.mb.ui.feature

│     └── …...

├── pom.xml

├── LICENSE.txt

├── README.md

└── product

      ├── carbon-home

      │       └── README.md

      ├── carbon.product

      ├── pom.xml

      └── src

              └── assembly

                     ├── bin.xml

                      └── filter.properties


Thanks,
--
Eranda Rajapakshe
Software Engineer
WSO2 Inc.
Mobile : <a href="tel:%2B94784822608" value="+94784822608" target="_blank">+94784822608

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




--
Madhawa Gunasekara
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile:
<a href="tel:+94+719411002" target="_blank">+94 719411002



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Pamod Sylvester 
WSO2 Inc.; http://wso2.com
cell: <a href="tel:+94%2077%20777%209495" value="+94777779495" target="_blank">+94 77 7779495



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:+94%2077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : +94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )


_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: [Dev] Folder Structure for C5 based MB

Hasitha Hiranya
+1 for a single feature repo, with separated, individually unit testable modules. 


On Thu, Apr 27, 2017 at 2:08 PM, Nuwan Dias <[hidden email]> wrote:
Yes, embed in the sense we would package the jars so that we can run MB as a separate process/runtime.

On Thu, Apr 27, 2017 at 1:56 PM, Hasitha Amal De Silva <[hidden email]> wrote:


On Thu, Apr 27, 2017 at 1:55 PM, Hasitha Amal De Silva <[hidden email]> wrote:
[+NuwanD]

On Thu, Apr 27, 2017 at 1:53 PM, Pamod Sylvester <[hidden email]> wrote:
(+) NuwanD

+1, also APIM would embed the broker with all the features included ? (same as it's being used in EI) correct me if i am wrong ?  

Thanks,
Pamod

On Thu, Apr 27, 2017 at 1:49 PM, Hasitha Amal De Silva <[hidden email]> wrote:
Hi Kishanthan, 

Agreed. As per Nandika, the product folder here is invalid since MB will only result in a set of components + features to be used by other carbon products. 

Based on that standing, we will not need to do product releases but do only component+feature releases. 

Thanks


On Thu, Apr 27, 2017 at 1:46 PM, Madhawa Gunasekara <[hidden email]> wrote:
Hi Eranda,

+1 to make it into one repo. AFAIU We don't need to have product folder here, Since We don't create a p2 profile in this repo. We should include only components and features in this repo.

Thanks,
Madhawa

On Thu, Apr 27, 2017 at 11:32 AM, Eranda Rajapakshe <[hidden email]> wrote:

Hi, HasithaD and I are working on bootstrapping the C5 based Message Broker product.


In the current version of WSO2 Message broker (3.x) we have following 3 repos.


  1. Andes - contains the messaging core, apache qpid fork and JMX monitoring objects.

  2. Carbon-business-messaging - contains admin services, wraps andes as a osgi service, and the UI impl.

  3. Product-mb - contains test cases, and distribution configurations.


For MB 4x, we have come up with a more unified structure based on a single repo (refer [2] as an example). The intention here is to reduce build and maintenance complexity. However, if there is a need to use separate components/features within MB into other products, we need to go for separate repos as and when required.


We will be working on product-mb/4.x.x branch [1]. Please let us know any suggestion and comments on this.


[1]. https://github.com/wso2/product-mb/tree/4.x.x


[2].

product-mb

├── components

│     ├── org.wso2.carbon.andes

│     ├── org.wso2.carbon.mb.services

│     ├── org.wso2.carbon.mb.ui

│     └── …..

├── features

│     ├── org.wso2.carbon.andes.feature

│     ├── org.wso2.carbon.mb.services.feature

│     ├── org.wso2.carbon.mb.ui.feature

│     └── …...

├── pom.xml

├── LICENSE.txt

├── README.md

└── product

      ├── carbon-home

      │       └── README.md

      ├── carbon.product

      ├── pom.xml

      └── src

              └── assembly

                     ├── bin.xml

                      └── filter.properties


Thanks,
--
Eranda Rajapakshe
Software Engineer
WSO2 Inc.
Mobile : <a href="tel:%2B94784822608" value="+94784822608" target="_blank">+94784822608

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




--
Madhawa Gunasekara
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile:
<a href="tel:+94+719411002" target="_blank">+94 719411002



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Pamod Sylvester 
WSO2 Inc.; http://wso2.com
cell: <a href="tel:+94%2077%20777%209495" value="+94777779495" target="_blank">+94 77 7779495



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:+94%2077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:+94%2077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
Phone : +94 777 775 729



--
Hasitha Abeykoon
Senior Software EngineerWSO2, Inc.; http://wso2.com


_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Reply | Threaded
Open this post in threaded view
|

Re: [Dev] Folder Structure for C5 based MB

Hasitha Amal De Silva
Hi all, 

Based on above feedback, I have created the branch "4.x.x" for MB 4 development work excluding the product directory. 


Thanks

On Thu, Apr 27, 2017 at 5:50 PM, Hasitha Hiranya <[hidden email]> wrote:
+1 for a single feature repo, with separated, individually unit testable modules. 


On Thu, Apr 27, 2017 at 2:08 PM, Nuwan Dias <[hidden email]> wrote:
Yes, embed in the sense we would package the jars so that we can run MB as a separate process/runtime.

On Thu, Apr 27, 2017 at 1:56 PM, Hasitha Amal De Silva <[hidden email]> wrote:


On Thu, Apr 27, 2017 at 1:55 PM, Hasitha Amal De Silva <[hidden email]> wrote:
[+NuwanD]

On Thu, Apr 27, 2017 at 1:53 PM, Pamod Sylvester <[hidden email]> wrote:
(+) NuwanD

+1, also APIM would embed the broker with all the features included ? (same as it's being used in EI) correct me if i am wrong ?  

Thanks,
Pamod

On Thu, Apr 27, 2017 at 1:49 PM, Hasitha Amal De Silva <[hidden email]> wrote:
Hi Kishanthan, 

Agreed. As per Nandika, the product folder here is invalid since MB will only result in a set of components + features to be used by other carbon products. 

Based on that standing, we will not need to do product releases but do only component+feature releases. 

Thanks


On Thu, Apr 27, 2017 at 1:46 PM, Madhawa Gunasekara <[hidden email]> wrote:
Hi Eranda,

+1 to make it into one repo. AFAIU We don't need to have product folder here, Since We don't create a p2 profile in this repo. We should include only components and features in this repo.

Thanks,
Madhawa

On Thu, Apr 27, 2017 at 11:32 AM, Eranda Rajapakshe <[hidden email]> wrote:

Hi, HasithaD and I are working on bootstrapping the C5 based Message Broker product.


In the current version of WSO2 Message broker (3.x) we have following 3 repos.


  1. Andes - contains the messaging core, apache qpid fork and JMX monitoring objects.

  2. Carbon-business-messaging - contains admin services, wraps andes as a osgi service, and the UI impl.

  3. Product-mb - contains test cases, and distribution configurations.


For MB 4x, we have come up with a more unified structure based on a single repo (refer [2] as an example). The intention here is to reduce build and maintenance complexity. However, if there is a need to use separate components/features within MB into other products, we need to go for separate repos as and when required.


We will be working on product-mb/4.x.x branch [1]. Please let us know any suggestion and comments on this.


[1]. https://github.com/wso2/product-mb/tree/4.x.x


[2].

product-mb

├── components

│     ├── org.wso2.carbon.andes

│     ├── org.wso2.carbon.mb.services

│     ├── org.wso2.carbon.mb.ui

│     └── …..

├── features

│     ├── org.wso2.carbon.andes.feature

│     ├── org.wso2.carbon.mb.services.feature

│     ├── org.wso2.carbon.mb.ui.feature

│     └── …...

├── pom.xml

├── LICENSE.txt

├── README.md

└── product

      ├── carbon-home

      │       └── README.md

      ├── carbon.product

      ├── pom.xml

      └── src

              └── assembly

                     ├── bin.xml

                      └── filter.properties


Thanks,
--
Eranda Rajapakshe
Software Engineer
WSO2 Inc.
Mobile : <a href="tel:%2B94784822608" value="+94784822608" target="_blank">+94784822608

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




--
Madhawa Gunasekara
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile:
<a href="tel:+94+719411002" target="_blank">+94 719411002



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Pamod Sylvester 
WSO2 Inc.; http://wso2.com
cell: <a href="tel:+94%2077%20777%209495" value="+94777779495" target="_blank">+94 77 7779495



--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:+94%2077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : <a href="tel:+94%2077%20203%207426" value="+94772037426" target="_blank">+94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )




--
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
Phone : <a href="tel:+94%2077%20777%205729" value="+94777775729" target="_blank">+94 777 775 729



--
Hasitha Abeykoon
Senior Software EngineerWSO2, Inc.; http://wso2.com




--
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : +94772037426
Blog    : http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )


_______________________________________________
Architecture mailing list
[hidden email]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture