Re: [Architecture] How to forcefully remove an entry from app factory registry path cache?
Hi, Given that we know the registry path of the resource of which cache to be deleted and have an instance of the registry we can manually delete the cache with a method like removeCache in the below file. However, it's not a clean or correct way of manipulating the registry cache. https://github.com/wso2-dev/carbon-governance/blob/master/components/governance/org.wso2.carbon.governance.custom.lifecycles.checklist/src/main/java/org/wso2/carbon/governance/custom/lifecycles/checklist/util/LifecycleBeanPopulator.java Shazni Nazeer Senior Software Engineer Mob : +94 37331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Wed, Nov 12, 2014 at 1:48 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Pulasthi, So when we are doing global invalidation, what is the method we are going to use to invalidate the cache within the JVM? :) Or are you going to do it by magic? thanks, dimuthu On Wed, Nov 12, 2014 at 1:36 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi Dimuthu, On Tue, Nov 11, 2014 at 4:17 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi, On Tue, Nov 11, 2014 at 3:43 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi Dimuthu, On Tue, Nov 11, 2014 at 2:05 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Pulasthi, Yes. We do not need global invalidation (although it would solve the problem), but the request is to sink AF Registry cache with the DB. We are in the same JVM, and we need a method/way to tell registry remove this particular path from Registry path cache. Such a method would need to be accessed through something like the remote registry right?. The Registry api does not provide such a method to remove entries from the Registry cache. It should not be remote. An OSGi level method would be fine. Is there a way to patch the registry that we use? I talked with Azeez regarding this. He also agrees that providing such a method to manipulate the cache is wrong. We need to think of some other solution for this. I am not sure if the global cache invalidation has completed or can be backported into 4.2.0. @Amal is the work on that complete ? Regards, Pulasthi thanks, dimuthu Regards, Pulasthi thanks, dimuthu On Tue, Nov 11, 2014 at 12:16 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi All, From what i understand the AF and SM are in different domains that is why distributed caching will not be able to handle this scenario right?. global cluster cache invalidation has been done with the use of a pub sub mechanism ( discussed in archi under Global cluster cache invalidation code review Notes ) but this will only be available in the next release AFAIK. Regards, Pulasthi On Tue, Nov 11, 2014 at 10:00 AM, Amalka Subasinghe ama...@wso2.com wrote: Hi, The scenario is, we have mounted SM's registry to the App Factory registry to remove the remote call for read the resources. but still the write calls happens via SM. see the image below. The problem is, once we do a write call to the SM's registry, App Factory registry cache won't get updated, so old information will be shown in App Factory pages. Is there a way to remove an entry from the App Factory registry cache when we do a write call to the SM's registry? then when we do a read call, it will load the cache again and show the updated information. Thanks Amalka ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] How to forcefully remove an entry from app factory registry path cache?
Hi, The global cache invalidation implementation is complete long time ago and the documentation can be found at [1]. This has been tested in registry and it's working well. However this is implemented to support from carbon 4.3.0 onwards. [1] https://docs.google.com/a/wso2.com/document/d/1yWE-3FfWaM2hKS6kqtb8uDR8o9szBH9qQjkPZqWJmPc Thank you, Amal. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Wed, Nov 12, 2014 at 2:23 PM, Shazni Nazeer sha...@wso2.com wrote: Hi, Given that we know the registry path of the resource of which cache to be deleted and have an instance of the registry we can manually delete the cache with a method like removeCache in the below file. However, it's not a clean or correct way of manipulating the registry cache. https://github.com/wso2-dev/carbon-governance/blob/master/components/governance/org.wso2.carbon.governance.custom.lifecycles.checklist/src/main/java/org/wso2/carbon/governance/custom/lifecycles/checklist/util/LifecycleBeanPopulator.java Shazni Nazeer Senior Software Engineer Mob : +94 37331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Wed, Nov 12, 2014 at 1:48 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Pulasthi, So when we are doing global invalidation, what is the method we are going to use to invalidate the cache within the JVM? :) Or are you going to do it by magic? thanks, dimuthu On Wed, Nov 12, 2014 at 1:36 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi Dimuthu, On Tue, Nov 11, 2014 at 4:17 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi, On Tue, Nov 11, 2014 at 3:43 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi Dimuthu, On Tue, Nov 11, 2014 at 2:05 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi Pulasthi, Yes. We do not need global invalidation (although it would solve the problem), but the request is to sink AF Registry cache with the DB. We are in the same JVM, and we need a method/way to tell registry remove this particular path from Registry path cache. Such a method would need to be accessed through something like the remote registry right?. The Registry api does not provide such a method to remove entries from the Registry cache. It should not be remote. An OSGi level method would be fine. Is there a way to patch the registry that we use? I talked with Azeez regarding this. He also agrees that providing such a method to manipulate the cache is wrong. We need to think of some other solution for this. I am not sure if the global cache invalidation has completed or can be backported into 4.2.0. @Amal is the work on that complete ? Regards, Pulasthi thanks, dimuthu Regards, Pulasthi thanks, dimuthu On Tue, Nov 11, 2014 at 12:16 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi All, From what i understand the AF and SM are in different domains that is why distributed caching will not be able to handle this scenario right?. global cluster cache invalidation has been done with the use of a pub sub mechanism ( discussed in archi under Global cluster cache invalidation code review Notes ) but this will only be available in the next release AFAIK. Regards, Pulasthi On Tue, Nov 11, 2014 at 10:00 AM, Amalka Subasinghe ama...@wso2.com wrote: Hi, The scenario is, we have mounted SM's registry to the App Factory registry to remove the remote call for read the resources. but still the write calls happens via SM. see the image below. The problem is, once we do a write call to the SM's registry, App Factory registry cache won't get updated, so old information will be shown in App Factory pages. Is there a way to remove an entry from the App Factory registry cache when we do a write call to the SM's registry? then when we do a read call, it will load the cache again and show the updated information. Thanks Amalka ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware -- -- Pulasthi Supun Software
Re: [Architecture] Proposal for Carbon Offsets
Ack? Paul On 10 October 2014 09:27, Paul Fremantle p...@wso2.com wrote: I have a simple proposal, which is that we predefine a standard offset for each product. e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... These would be baked into the distros. This would make life a lot easier for customers doing more than one product. Also for say BAM integration, life would be much better. Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposal for Carbon Offsets
Hi, I'm -0 on this proposal. If we have different offsets for different products, we will have to maintain a document to show the offsets we have given for each product. When doing product integrations, setting offset is not the only configuration step. It is a simple operation and I think it's better to let the user to do that along with other configurations. Then the user will know what really happens with ports and how to configure URLs. In most of the production deployments, the WSO2 instances will be in separate servers/VMs and we rarely modify the offset. Most of the time, we define common security groups to open ports. So, if we don't change offsets by default, we will be having common ports for each server. So, I think it's better to have no offsets by default in WSO2 products. Thanks! Best Regards, On Wed, Nov 12, 2014 at 5:42 PM, Paul Fremantle p...@wso2.com wrote: Ack? Paul On 10 October 2014 09:27, Paul Fremantle p...@wso2.com wrote: I have a simple proposal, which is that we predefine a standard offset for each product. e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... These would be baked into the distros. This would make life a lot easier for customers doing more than one product. Also for say BAM integration, life would be much better. Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposal for Carbon Offsets
Hi Johan, FYI. We have documented the ports used by WSO2 products [1]. Thanks! Best Regards, [1] https://docs.wso2.com/display/Carbon420/Default+Ports+of+WSO2+Products On Wed, Nov 12, 2014 at 6:27 PM, Johan Kumps johan.ku...@realdolmen.com wrote: Hi, I’ve been involved in the clustered installation of several WSO2 products for one of our customers lately. Indeed the fact to have to change the port offset is not a big deal. What we would like more is a documentation page stating all ports that have to be open in the firewall in order for the cluster to work properly. Kind regards, Johan, *From:* Architecture [mailto:architecture-boun...@wso2.org] *On Behalf Of *Isuru Perera *Sent:* woensdag 12 november 2014 13:43 *To:* WSO2 Architecture *Subject:* Re: [Architecture] Proposal for Carbon Offsets Hi, I'm -0 on this proposal. If we have different offsets for different products, we will have to maintain a document to show the offsets we have given for each product. When doing product integrations, setting offset is not the only configuration step. It is a simple operation and I think it's better to let the user to do that along with other configurations. Then the user will know what really happens with ports and how to configure URLs. In most of the production deployments, the WSO2 instances will be in separate servers/VMs and we rarely modify the offset. Most of the time, we define common security groups to open ports. So, if we don't change offsets by default, we will be having common ports for each server. So, I think it's better to have no offsets by default in WSO2 products. Thanks! Best Regards, On Wed, Nov 12, 2014 at 5:42 PM, Paul Fremantle p...@wso2.com wrote: Ack? Paul On 10 October 2014 09:27, Paul Fremantle p...@wso2.com wrote: I have a simple proposal, which is that we predefine a standard offset for each product. e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... These would be baked into the distros. This would make life a lot easier for customers doing more than one product. Also for say BAM integration, life would be much better. Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposal for Carbon Offsets
Hi, If we come up with this standard port offset for each product , AFAIU we are only thinking on scope within WSO2 products. Generally In most of the cases , there is a standard default port for most of the products which is related with their functionality. As an example most of the message brokers use port 5672 for their communication and if we are going to change it by default then new users will get confused. So, rather than coming with standard offset for each product by default, can we come in to a conclusion like , in any deployment we need to deploy each product with given offset value as paul suggested. WDYT ? Thanks Shammi On Fri, Oct 10, 2014 at 4:27 AM, Paul Fremantle p...@wso2.com wrote: I have a simple proposal, which is that we predefine a standard offset for each product. e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... These would be baked into the distros. This would make life a lot easier for customers doing more than one product. Also for say BAM integration, life would be much better. Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Best Regards, * Shammi Jayasinghe* Associate Tech Lead WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Process store: chevron diagram editor design review
Hi , A small addition to the above: - A Chevron Workflow could have one or more layouts - The layout details need not be stored with the Workflow instance Thank You, Sameera On Wed, Nov 12, 2014 at 5:20 PM, Himasha Guruge himas...@wso2.com wrote: Hi Chathura, After the meeting with Sameera, he suggested the following design model. Since every sub chevron element itself also represents a process,suggestion was to create two asset types named chevron and chevron workflow. 1.chevron.rxt : Includes all metadata fields.(Name,Version,Provider,Predecessor,Successor,Process model) 2. chevron workflow.rxt: Includes following two fields. 2.1 *sequence*: This will hold all chevron ids that we draw on the canvas. 2.2* layout:* This will hold the formatting data of chevron element drawn on the canvas. Such as chevron id, positionX,positionY. Views for these 2 asset types will be as follows. Please refer [1]. 3.Create page for chevron asset type : User can enter metadata fields listed, and on click of create button those values will be added to chevron.rxt. 4. Create page for chevron workflow asset type: User can drag and drop chevron icon can create their diagram. On click of create button, ids of the chevron icons will be saved under sequence field, layout details in layout field. An association will be made between the relevant chevron asset and chevron asset workflow. 5. Chevron view page : Chevron related data (name, version etc) will be loaded in a table while the associated diagram will be loaded in a canvas. The only catch is that all diagram related data ( layout and sequence) will be saved in JSON format. Therefore no xml will be included. Are there any restrictions such as the diagram should be maintained in xml format? Please provide your feedback on this design suggestion. Please refer [1] for further reference. I will continue working on the previous design model(with one asset type) until a decision is made. [1].chevron diagram editor design suggestion https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/view?usp=sharing Chevron diagram editor design suggestion.jpg https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/edit?usp=drive_web Thanks Regards, Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 himas...@wso2.com -- Sameera Medagammaddegedara Software Engineer Contact: Email: samee...@wso2.com Mobile: + 94 077 255 3005 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Process store: chevron diagram editor design review
Hi Himasha, A chevron in a chevron diagram may refer to another chevron diagram or to a process model. Therefore, we can't create an asset for a chevron until the user has specified its type. I think we should not prompt user to enter details like type of each chevron when modeling an abstract entity like chevron diagram. Other issue is that user should be able to add chevrons to a diagram, and some/all of those chevrons may not be modeled as a separate process/chevron with next level of detail. Therefore, IMO creating an asset for each chevron element in a diagram is not necessary. At this stage, let's avoid associating any details with individual chevrons except the name and optional associated asset (i.e. process model or chevron diagram). Later, we can improve this to load and display all properties of associated asset when a chevron is selected. I think we can use the below xml format which is similar to the one we discussed in the last meeting: chevronDiagram chevron id=c1 nameFeasibility assessment/name associatedAssetprocessId/associatedAsset chevron chevron id=c2 nameRecruitment/name chevron chevron id=c1 nameEquipment procurement/name associatedAssetprocessId/associatedAsset chevron flow source=c1 target=c2/ flow source=c1 target=c3/ layout position chevronId=c1 x120/x y200/y /position position chevronId=c2 x250/x y120/y /position position chevronId=c3 x250/x y280/y /position /layout chevronDiagram Note that the associatedAsset element is optional (chevron c2 doesn't have an associated asset). As Sameera mentioned, we can support multiple layouts for a chevron (by adding multiple layout elements in the xml). But let's start with a single layout for now. Regards, Chathura On Wed, Nov 12, 2014 at 10:19 PM, Sameera Medagammaddegedara samee...@wso2.com wrote: Hi , A small addition to the above: - A Chevron Workflow could have one or more layouts - The layout details need not be stored with the Workflow instance Thank You, Sameera On Wed, Nov 12, 2014 at 5:20 PM, Himasha Guruge himas...@wso2.com wrote: Hi Chathura, After the meeting with Sameera, he suggested the following design model. Since every sub chevron element itself also represents a process,suggestion was to create two asset types named chevron and chevron workflow. 1.chevron.rxt : Includes all metadata fields.(Name,Version,Provider,Predecessor,Successor,Process model) 2. chevron workflow.rxt: Includes following two fields. 2.1 *sequence*: This will hold all chevron ids that we draw on the canvas. 2.2* layout:* This will hold the formatting data of chevron element drawn on the canvas. Such as chevron id, positionX,positionY. Views for these 2 asset types will be as follows. Please refer [1]. 3.Create page for chevron asset type : User can enter metadata fields listed, and on click of create button those values will be added to chevron.rxt. 4. Create page for chevron workflow asset type: User can drag and drop chevron icon can create their diagram. On click of create button, ids of the chevron icons will be saved under sequence field, layout details in layout field. An association will be made between the relevant chevron asset and chevron asset workflow. 5. Chevron view page : Chevron related data (name, version etc) will be loaded in a table while the associated diagram will be loaded in a canvas. The only catch is that all diagram related data ( layout and sequence) will be saved in JSON format. Therefore no xml will be included. Are there any restrictions such as the diagram should be maintained in xml format? Please provide your feedback on this design suggestion. Please refer [1] for further reference. I will continue working on the previous design model(with one asset type) until a decision is made. [1].chevron diagram editor design suggestion https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/view?usp=sharing Chevron diagram editor design suggestion.jpg https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/edit?usp=drive_web Thanks Regards, Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 himas...@wso2.com -- Sameera Medagammaddegedara Software Engineer Contact: Email: samee...@wso2.com Mobile: + 94 077 255 3005 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposal for Carbon Offsets
On Wed, Nov 12, 2014 at 6:27 PM, Johan Kumps johan.ku...@realdolmen.com wrote: Hi, I’ve been involved in the clustered installation of several WSO2 products for one of our customers lately. Indeed the fact to have to change the port offset is not a big deal. What we would like more is a documentation page stating all ports that have to be open in the firewall in order for the cluster to work properly. +1 for documenting all default ports that need to be opened on a product by product basis. If a user adds an offset, it is just a matter of offsetting all those ports by the relevant number. Kind regards, Johan, *From:* Architecture [mailto:architecture-boun...@wso2.org] *On Behalf Of *Isuru Perera *Sent:* woensdag 12 november 2014 13:43 *To:* WSO2 Architecture *Subject:* Re: [Architecture] Proposal for Carbon Offsets Hi, I'm -0 on this proposal. If we have different offsets for different products, we will have to maintain a document to show the offsets we have given for each product. When doing product integrations, setting offset is not the only configuration step. It is a simple operation and I think it's better to let the user to do that along with other configurations. Then the user will know what really happens with ports and how to configure URLs. In most of the production deployments, the WSO2 instances will be in separate servers/VMs and we rarely modify the offset. Most of the time, we define common security groups to open ports. So, if we don't change offsets by default, we will be having common ports for each server. So, I think it's better to have no offsets by default in WSO2 products. Thanks! Best Regards, On Wed, Nov 12, 2014 at 5:42 PM, Paul Fremantle p...@wso2.com wrote: Ack? Paul On 10 October 2014 09:27, Paul Fremantle p...@wso2.com wrote: I have a simple proposal, which is that we predefine a standard offset for each product. e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... These would be baked into the distros. This would make life a lot easier for customers doing more than one product. Also for say BAM integration, life would be much better. Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919blog: **http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez *linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] WSO2 Products Tenant Creation Process calls the Reset Password
Came upon this thread when trying to find a solution for this exact issue we are facing right now. LDAPs cannot have password history policies because of this. It seems rather than using a dummy password first time, it uses the same password. We'll have to explore why it's done this way. On Tue, Mar 11, 2014 at 1:28 AM, Amila Maha Arachchi ami...@wso2.com wrote: What are the issues of having this? On Thu, Mar 6, 2014 at 9:08 AM, Danushka Fernando danush...@wso2.com wrote: Hi all I found that our tenant creation process is calling reset password call inside tenant creation process. When we call tenant creation it goes through *persistTenant* call in *TenantPersistor* class. And it calls *persistTenantInUserStore*. In the end of this call it calls for *updateTenantAdminPassword*. By the time Tenant Manager is created the tenant admin and have added the password to the LDAP. So is there a particular reason that we should do this? I cant see any reason that we call the update/reset password at this moment. So IMO we should remove this if no such reason. WDYT? Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list d...@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APPFAC] - Issue in deploying php applications in M6 release
Hi Roshan, I like to suggest the word none instead of empty Touched, not typed. Erroneous words are a feature, not a typo. On Nov 12, 2014 9:35 AM, Roshan Deniyage rosh...@wso2.com wrote: Its breaking not because of * but, code changes in M6 release. I'm going to change the * sign because of its misleading users. Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage On Tue, Nov 11, 2014 at 11:43 PM, Danushka Fernando danush...@wso2.com wrote: Can you list down the places this is used and where its breaking because its *. And with this are you going with any code changes? Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Tue, Nov 11, 2014 at 10:59 PM, Roshan Deniyage rosh...@wso2.com wrote: Hi, With the M6 release of the appfactory, it has introduced a new bug for PHP application type. Due to this, php application are not deployed after build. In apptype.xml files there is a tag called Extension and it is to specify the artifact extensions. I'm fixing this issue and for current release uses the string value * as the value in Extension tag for application types which doesn't have an extension like PHP. I'm changing the that value from * to (empty) for application types which doesn't have any extension. Since, * value may mislead the users. * may be interpreted as all extension rather than no extension. Any concern on this decision? Thanks, Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage ___ 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 ___ 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
Re: [Architecture] [APPFAC] - Issue in deploying php applications in M6 release
+1 for using none instead of empty On Thu, Nov 13, 2014 at 12:12 AM, Udara Liyanage ud...@wso2.com wrote: Hi Roshan, I like to suggest the word none instead of empty Touched, not typed. Erroneous words are a feature, not a typo. On Nov 12, 2014 9:35 AM, Roshan Deniyage rosh...@wso2.com wrote: Its breaking not because of * but, code changes in M6 release. I'm going to change the * sign because of its misleading users. Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage On Tue, Nov 11, 2014 at 11:43 PM, Danushka Fernando danush...@wso2.com wrote: Can you list down the places this is used and where its breaking because its *. And with this are you going with any code changes? Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Tue, Nov 11, 2014 at 10:59 PM, Roshan Deniyage rosh...@wso2.com wrote: Hi, With the M6 release of the appfactory, it has introduced a new bug for PHP application type. Due to this, php application are not deployed after build. In apptype.xml files there is a tag called Extension and it is to specify the artifact extensions. I'm fixing this issue and for current release uses the string value * as the value in Extension tag for application types which doesn't have an extension like PHP. I'm changing the that value from * to (empty) for application types which doesn't have any extension. Since, * value may mislead the users. * may be interpreted as all extension rather than no extension. Any concern on this decision? Thanks, Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage ___ 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 ___ 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 -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Making appfactory installation in a single node using ppuppet
Hi Anuruddha, On Tue, Nov 11, 2014 at 8:12 PM, Anuruddha Premalal anurud...@wso2.com wrote: Hi, Now in appfactory developer setup, we are using three single JVM private-paases which have separate activemqs running on the same node with port offsets. Appfactory use stratos messaging component to listen to topology, this component gets the topic url from a jndi property file. This cause an issue where we cannot listen to topology events from three different private-paas (dev, test, prod). This is a limitation we currently have in messaging component (in PPaaS 4.0.0). It can only read message broker IP and port from the jndi.properties file. Please feel free to provide a pull request or we can fix this in 4.1.0 release. Thanks ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Making appfactory installation in a single node using ppuppet
Hi Harsha, On Wed, Nov 12, 2014 at 8:38 AM, Harsha Thirimanna hars...@wso2.com wrote: As we discussed with Imesh, we have to set this jndi property to system variable for each enviorenment before start listener to that environment. There is hard coded of this jndi property file in topology listener. So if there is way to pass configs to initialize the connection when we start listner , it will be easy to do this. @Imesh, WDYT ? Yes as we discussed offline, as a workaround it is possible to create separate jndi.properties files for each message broker and place them in separate folders. Then the following system property could be set whenever a connection is made to the message broker: jndi.properties.dir https://github.com/wso2/private-paas/blob/master/source/components/org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/broker/connect/TopicConnector.java ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposal for Carbon Offsets
On Wed, Nov 12, 2014 at 8:33 PM, Afkham Azeez az...@wso2.com wrote: On Wed, Nov 12, 2014 at 6:12 PM, Isuru Perera isu...@wso2.com wrote: Hi, I'm -0 on this proposal. If we have different offsets for different products, we will have to maintain a document to show the offsets we have given for each product. Due to the same reason, I too think having multiple port offsets will be confusing since most users have got used to the standard ports, and are quite comfortable with setting different port offsets. IMO its better if we can have a general practice on this (without changing in product level). This will be only useful for demos/QSPs/POCs. So when we write docs on product integrations we can use this practice. As I know APIM + BAM usually BAM use 1 as the offset. When doing product integrations, setting offset is not the only configuration step. It is a simple operation and I think it's better to let the user to do that along with other configurations. Then the user will know what really happens with ports and how to configure URLs. In most of the production deployments, the WSO2 instances will be in separate servers/VMs and we rarely modify the offset. Most of the time, we define common security groups to open ports. So, if we don't change offsets by default, we will be having common ports for each server. So, I think it's better to have no offsets by default in WSO2 products. Thanks! Best Regards, On Wed, Nov 12, 2014 at 5:42 PM, Paul Fremantle p...@wso2.com wrote: Ack? Paul On 10 October 2014 09:27, Paul Fremantle p...@wso2.com wrote: I have a simple proposal, which is that we predefine a standard offset for each product. e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... These would be baked into the distros. This would make life a lot easier for customers doing more than one product. Also for say BAM integration, life would be much better. Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez *linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *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
Re: [Architecture] Process store: chevron diagram editor design review
Hi Chathura, Noted, will continue as we planned. Thanks Regards, Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 himas...@wso2.com On Wed, Nov 12, 2014 at 8:24 PM, Chathura Ekanayake chath...@wso2.com wrote: Hi Himasha, A chevron in a chevron diagram may refer to another chevron diagram or to a process model. Therefore, we can't create an asset for a chevron until the user has specified its type. I think we should not prompt user to enter details like type of each chevron when modeling an abstract entity like chevron diagram. Other issue is that user should be able to add chevrons to a diagram, and some/all of those chevrons may not be modeled as a separate process/chevron with next level of detail. Therefore, IMO creating an asset for each chevron element in a diagram is not necessary. At this stage, let's avoid associating any details with individual chevrons except the name and optional associated asset (i.e. process model or chevron diagram). Later, we can improve this to load and display all properties of associated asset when a chevron is selected. I think we can use the below xml format which is similar to the one we discussed in the last meeting: chevronDiagram chevron id=c1 nameFeasibility assessment/name associatedAssetprocessId/associatedAsset chevron chevron id=c2 nameRecruitment/name chevron chevron id=c1 nameEquipment procurement/name associatedAssetprocessId/associatedAsset chevron flow source=c1 target=c2/ flow source=c1 target=c3/ layout position chevronId=c1 x120/x y200/y /position position chevronId=c2 x250/x y120/y /position position chevronId=c3 x250/x y280/y /position /layout chevronDiagram Note that the associatedAsset element is optional (chevron c2 doesn't have an associated asset). As Sameera mentioned, we can support multiple layouts for a chevron (by adding multiple layout elements in the xml). But let's start with a single layout for now. Regards, Chathura On Wed, Nov 12, 2014 at 10:19 PM, Sameera Medagammaddegedara samee...@wso2.com wrote: Hi , A small addition to the above: - A Chevron Workflow could have one or more layouts - The layout details need not be stored with the Workflow instance Thank You, Sameera On Wed, Nov 12, 2014 at 5:20 PM, Himasha Guruge himas...@wso2.com wrote: Hi Chathura, After the meeting with Sameera, he suggested the following design model. Since every sub chevron element itself also represents a process,suggestion was to create two asset types named chevron and chevron workflow. 1.chevron.rxt : Includes all metadata fields.(Name,Version,Provider,Predecessor,Successor,Process model) 2. chevron workflow.rxt: Includes following two fields. 2.1 *sequence*: This will hold all chevron ids that we draw on the canvas. 2.2* layout:* This will hold the formatting data of chevron element drawn on the canvas. Such as chevron id, positionX,positionY. Views for these 2 asset types will be as follows. Please refer [1]. 3.Create page for chevron asset type : User can enter metadata fields listed, and on click of create button those values will be added to chevron.rxt. 4. Create page for chevron workflow asset type: User can drag and drop chevron icon can create their diagram. On click of create button, ids of the chevron icons will be saved under sequence field, layout details in layout field. An association will be made between the relevant chevron asset and chevron asset workflow. 5. Chevron view page : Chevron related data (name, version etc) will be loaded in a table while the associated diagram will be loaded in a canvas. The only catch is that all diagram related data ( layout and sequence) will be saved in JSON format. Therefore no xml will be included. Are there any restrictions such as the diagram should be maintained in xml format? Please provide your feedback on this design suggestion. Please refer [1] for further reference. I will continue working on the previous design model(with one asset type) until a decision is made. [1].chevron diagram editor design suggestion https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/view?usp=sharing Chevron diagram editor design suggestion.jpg https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/edit?usp=drive_web Thanks Regards, Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 himas...@wso2.com -- Sameera Medagammaddegedara Software Engineer Contact:
[Architecture] AM : API everywhere for DSS
Hi All, Myself with Tharindu(tharin...@wso2.com) is going to develop $subject as described below. Work flow - Step 01 : User creates the .dbs file with the use of DSS - Step 02 : There will be an additional option to expose/publish the API for the services exposed by the DSS UI Design Changes - Tier Availability - check options - Tenant Availability - check options Thank you, -- *Madusanka Premaratne* | Associate Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 835 70 73| Work: +94 112 145 345 Email: madusan...@wso2.com | Web: www.wso2.com [image: Facebook] http://www.facebook.com/maduzanka [image: Twitter] https://twitter.com/rmmpremaratne [image: Google Plus] https://plus.google.com/u/0/+MadusankaPremaratnemaduz/about/p/pub [image: Linkedin] http://lk.linkedin.com/in/madusanka/ [image: Instagram] http://instagram.com/madusankapremaratne [image: Skype] http://@rmmpremaratne ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] AM : API everywhere for DSS
Adding Tharindu On Thu, Nov 13, 2014 at 9:20 AM, Madusanka Premaratne madusan...@wso2.com wrote: Hi All, Myself with Tharindu(tharin...@wso2.com) is going to develop $subject as described below. Work flow - Step 01 : User creates the .dbs file with the use of DSS - Step 02 : There will be an additional option to expose/publish the API for the services exposed by the DSS UI Design Changes - Tier Availability - check options - Tenant Availability - check options Thank you, -- *Madusanka Premaratne* | Associate Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 835 70 73| Work: +94 112 145 345 Email: madusan...@wso2.com | Web: www.wso2.com [image: Facebook] http://www.facebook.com/maduzanka [image: Twitter] https://twitter.com/rmmpremaratne [image: Google Plus] https://plus.google.com/u/0/+MadusankaPremaratnemaduz/about/p/pub [image: Linkedin] http://lk.linkedin.com/in/madusanka/ [image: Instagram] http://instagram.com/madusankapremaratne [image: Skype] http://@rmmpremaratne -- *Madusanka Premaratne* | Associate Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 835 70 73| Work: +94 112 145 345 Email: madusan...@wso2.com | Web: www.wso2.com [image: Facebook] https://www.facebook.com/rmmpremaratne [image: Twitter] https://twitter.com/rmmpremaratne [image: Google Plus] https://plus.google.com/u/0/+MadusankaPremaratnemaduz/about/p/pub [image: Linkedin] http://lk.linkedin.com/in/madusanka/ [image: Instagram] http://instagram.com/madusankapremaratne [image: Skype] http://@rmmpremaratne ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APPFAC] - Issue in deploying php applications in M6 release
any reason for suggestions? Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage On Thu, Nov 13, 2014 at 12:36 AM, Mahesh Chinthaka mahe...@wso2.com wrote: +1 for using none instead of empty On Thu, Nov 13, 2014 at 12:12 AM, Udara Liyanage ud...@wso2.com wrote: Hi Roshan, I like to suggest the word none instead of empty Touched, not typed. Erroneous words are a feature, not a typo. On Nov 12, 2014 9:35 AM, Roshan Deniyage rosh...@wso2.com wrote: Its breaking not because of * but, code changes in M6 release. I'm going to change the * sign because of its misleading users. Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage On Tue, Nov 11, 2014 at 11:43 PM, Danushka Fernando danush...@wso2.com wrote: Can you list down the places this is used and where its breaking because its *. And with this are you going with any code changes? Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Tue, Nov 11, 2014 at 10:59 PM, Roshan Deniyage rosh...@wso2.com wrote: Hi, With the M6 release of the appfactory, it has introduced a new bug for PHP application type. Due to this, php application are not deployed after build. In apptype.xml files there is a tag called Extension and it is to specify the artifact extensions. I'm fixing this issue and for current release uses the string value * as the value in Extension tag for application types which doesn't have an extension like PHP. I'm changing the that value from * to (empty) for application types which doesn't have any extension. Since, * value may mislead the users. * may be interpreted as all extension rather than no extension. Any concern on this decision? Thanks, Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage ___ 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 ___ 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 -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ 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
Re: [Architecture] [APPFAC] - Issue in deploying php applications in M6 release
Hi, Technically there is no difference. However having empty in a configuration files does not look nice to me :-) . On Thu, Nov 13, 2014 at 9:49 AM, Roshan Deniyage rosh...@wso2.com wrote: any reason for suggestions? Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage On Thu, Nov 13, 2014 at 12:36 AM, Mahesh Chinthaka mahe...@wso2.com wrote: +1 for using none instead of empty On Thu, Nov 13, 2014 at 12:12 AM, Udara Liyanage ud...@wso2.com wrote: Hi Roshan, I like to suggest the word none instead of empty Touched, not typed. Erroneous words are a feature, not a typo. On Nov 12, 2014 9:35 AM, Roshan Deniyage rosh...@wso2.com wrote: Its breaking not because of * but, code changes in M6 release. I'm going to change the * sign because of its misleading users. Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage On Tue, Nov 11, 2014 at 11:43 PM, Danushka Fernando danush...@wso2.com wrote: Can you list down the places this is used and where its breaking because its *. And with this are you going with any code changes? Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Tue, Nov 11, 2014 at 10:59 PM, Roshan Deniyage rosh...@wso2.com wrote: Hi, With the M6 release of the appfactory, it has introduced a new bug for PHP application type. Due to this, php application are not deployed after build. In apptype.xml files there is a tag called Extension and it is to specify the artifact extensions. I'm fixing this issue and for current release uses the string value * as the value in Extension tag for application types which doesn't have an extension like PHP. I'm changing the that value from * to (empty) for application types which doesn't have any extension. Since, * value may mislead the users. * may be interpreted as all extension rather than no extension. Any concern on this decision? Thanks, Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile: +94 777636406 Twitter: *https://twitter.com/roshku https://twitter.com/roshku* LinkedIn : https://www.linkedin.com/in/roshandeniyage ___ 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 ___ 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 -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ 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 -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Proposal for Carbon Offsets
We need to pick offset values wisely which requires less number of changes (in configurations) for example: if we change Port Offset of APIM we require changes in 3 files (carbon.xml, synapse token api etc). On Thu, Nov 13, 2014 at 5:10 AM, Thilina Piyasundara thili...@wso2.com wrote: On Wed, Nov 12, 2014 at 8:33 PM, Afkham Azeez az...@wso2.com wrote: On Wed, Nov 12, 2014 at 6:12 PM, Isuru Perera isu...@wso2.com wrote: Hi, I'm -0 on this proposal. If we have different offsets for different products, we will have to maintain a document to show the offsets we have given for each product. Due to the same reason, I too think having multiple port offsets will be confusing since most users have got used to the standard ports, and are quite comfortable with setting different port offsets. IMO its better if we can have a general practice on this (without changing in product level). This will be only useful for demos/QSPs/POCs. So when we write docs on product integrations we can use this practice. As I know APIM + BAM usually BAM use 1 as the offset. When doing product integrations, setting offset is not the only configuration step. It is a simple operation and I think it's better to let the user to do that along with other configurations. Then the user will know what really happens with ports and how to configure URLs. In most of the production deployments, the WSO2 instances will be in separate servers/VMs and we rarely modify the offset. Most of the time, we define common security groups to open ports. So, if we don't change offsets by default, we will be having common ports for each server. So, I think it's better to have no offsets by default in WSO2 products. Thanks! Best Regards, On Wed, Nov 12, 2014 at 5:42 PM, Paul Fremantle p...@wso2.com wrote: Ack? Paul On 10 October 2014 09:27, Paul Fremantle p...@wso2.com wrote: I have a simple proposal, which is that we predefine a standard offset for each product. e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... These would be baked into the distros. This would make life a lot easier for customers doing more than one product. Also for say BAM integration, life would be much better. Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez *linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list
